On Thu, Aug 5, 2021 at 8:07 AM Sjors Provoost via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> One thing on my wish list - for this BIP, BIP 88 (Hierarchical
> Deterministic Path Templates) or yet another one - is to include a birth
> date (minimum block height). E.g. tr([m/86'/0'
Hi Billy,
> It sounds like you're proposing an opcode
No. I don’t have enough knowledge of Bitcoin to be able to tell how (and
if) rate-limiting can be implemented as I suggested. I am not able to
reason about opcodes, so I kept my description at a more functional level.
> I still don't understa
Thanks for writing this up!
I think your modular BIP approach makes sense. (the abstract should mention
this too)
Contents look good to me, modulo missing test vectors. I also suggest dropping
combo(), see below.
Regarding the use of h vs ', especially since they result in a different
checks
> A maximum amount is allowed to be spent within EVERY epoch.
It sounds like you're proposing an opcode that takes in epochStart and
epochEnd as parameters. I still don't understand why its useful to specify
those as absolute block heights. You mentioned that this enables more
straightforward va
Hi,
@IC
There were 325 words that were not uniquely identified by the first 4
chars. I've fixed that.
Also, simple words (* by simple I mean 4 char words *) now fill more space;
@S7R
You were right about __adesiv__ - fixed that; The other sugestions,
_topmodel_, _walkman_, _web_, _yachting
