pull down to refresh

206 sats \ 1 reply \ @optimism 20h \ on: The BitVault B-SSL vault proposal doesn't make any sense bitcoin
CSV has a consensus limit of 388 days
minor note: or 65,535 blocks (which is targeted to be a bit more), see BIP-68
Bit (1 << 22) determines if the relative lock-time is time-based or block based: If the bit is set, the relative lock-time specifies a timespan in units of 512 seconds granularity. The timespan starts from the median-time-past of the output’s previous block, and ends at the MTP of the previous block. If the bit is not set, the relative lock-time specifies a number of blocks.
So you can relative-lock for 65535 / 6 (blocks per h) / 24 (h per day) = 455 "targeted days worth of blocks" (though that of course doesn't mean that it will actually take 455 days for that block height to be reached.)
write
preview
121 sats \ 0 replies \ @Scoresby OP 19h
Ah, yes! Thank you. I once found a really good explanation of the CSV 512 second granularity vs blocks but could not resurrect it while working on this post. (I seem to remember it from learnmeabitcoin, but couldn't find it there and had to settle for BitMex's explanation).
reply