reply on: Reflex - Payment Operations and Analytics Tools by Amboss \ stacker news ~bitcoin

pull down to refresh

0 sats \ 7 replies \ @joda 22 Feb \ on: Reflex - Payment Operations and Analytics Tools by Amboss bitcoin

Lol how many hops before it's "clean"?

Or is every node tainted and we go from blacklisting to whitelisting?

26 sats \ 6 replies \ @ambosstech 23 Feb

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.

0 sats \ 5 replies \ @nout 23 Feb

Please make it stupid and half broken, don't make it good.

0 sats \ 4 replies \ @ambosstech 23 Feb

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.

0 sats \ 3 replies \ @nout 23 Feb

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.

0 sats \ 2 replies \ @ambosstech 23 Feb

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.

0 sats \ 1 reply \ @fanis 23 Feb

"deterministic checks for channels’ source of funds" = channel bad if funds come directly from blacklisted address?

0 sats \ 0 replies \ @ambosstech 24 Feb

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.