pull down to refresh

514 sats \ 1 reply \ @OT 22 Feb
OFAC compliance
This is going to be a thing now isn't it?
reply
alwayshasbeen.webm
reply
11 sats \ 0 replies \ @clr 23 Feb
Amboss has always looked spooky. Now it appears to be confirmed.
reply
Lol how many hops before it's "clean"?
Or is every node tainted and we go from blacklisting to whitelisting?
reply
We're checking single hops from the OFAC list. This is a deterministic check as adding additional hops introduces uncertainty.
Reflex is not an enforcement tool; it is a tool for lightning businesses to get bank accounts or navigate regulation.
reply
Please make it stupid and half broken, don't make it good.
reply
It's fully configurable for your business based on your business policies. If your policies are stupid and half broken, you can apply them and make stupid decisions as well.
reply
What about the defaults: are you defaulting to exclude as many people as possible based on the list? It's good that businesses can customize, but 95% won't.
reply
Definitely not. Exclude what is deterministically from the OFAC list and Ransomware list (there are no OFAC funds in lightning).
You could request to customize this to be more restrictive using heuristics, but at some point your lightning operations will look like bubble boy.
reply
0 sats \ 1 reply \ @fanis 23 Feb
"deterministic checks for channels’ source of funds" = channel bad if funds come directly from blacklisted address?
reply
Essentially. If the business creates a policy for no OFAC funds, the channel (and consequently the node) would fail the OFAC check. Good/bad is a judgement but Reflex is designed to check information against a configurable policy.
This is will great when it advances enough to be available to the average end-user.
reply
stackers have outlawed this. turn on wild west mode in your /settings to see outlawed content.