pull down to refresh

120 sats \ 4 replies \ @optimism 22 Sep \ on: Default threshold for re-org risk bitcoin
what is the minimum confirmations you would set before users can spend?

Ideally this be configurable for amount ranges, or I need to be able to set both a tx size and tx volume constraint for automated processing.

If I can only configure this, then it's going to be 3 or 4.
If I can set additional thresholds, something like max 1 tx per block, max 100k sats, I'd even be fine with 1 - I wouldn't wanna take custody of huge amounts of sats anyway.

write
compose
126 sats \ 3 replies \ @justin_shocknet OP 22 Sep

We already have 3 tiers, so would be exposing that to get away from hard coding

Settings table would be like this

eg

<1M sats = 1
1M-100M = 2 
>100M = 3
reply
18 sats \ 2 replies \ @optimism 22 Sep

the tier<n>LimitSats are cumulative? or per-tx?

(edit: also s/M/k/g)

reply
126 sats \ 1 reply \ @justin_shocknet OP 22 Sep

per tx

so you're saying if you got 10 100k transactions you'd prefer treat them all as tier 2 instead of tier 1?

reply
120 sats \ 0 replies \ @optimism 22 Sep

Yes. At least within the scope of the threshold. Active attackers will per their job description fuck you if you don't have cumulative controls.

For simplicity, pleb people amounts:

100k = 1
500k = 3
default = 6

So 100k = 1 means 100k cumulative in the current block can go through, everything after that goes into tier 2, until 500k, requiring 3 confirmations, and everything after 500k in last(3) blocks goes into 6 confirmations. Could probably live with just the first and default tier at 3 though

This means that at current orphan rates I'd risk 100k per ~month.

reply