deggen

2. Coinbase handling. I'm thinking on whether BEEF [BRC-62](https://brc.dev/62) handles these. Full tx plus a Merkle path, if index within block is 0 then ensure `current height - 100 >...

Thanks I really appreciate the thoughtful review. BUMP went through a good few versions before landing where it is. Your recommended change in summary is: - do more validation and...

The client txid flag is an idea from @tonesnotes - which he may be better placed to articulate and defend.

I don't think I'm concerned about phantom merkles -- my understanding is that the thing this would allow is for someone to fake the number of txids in a block....

The duplicate offsets and redundant inclusions also don't concern me that much. What's the incentive for someone to send more than necessary? Is this just to keep things orderly and...

> they match the combined hash of the two hashes in the level below This was a total oversight until now, I think it warrants inclusion in the spec because...

I agree with the principle of minimal data, everything extraneous should be removed if possible. That was the goal of the format. The txid flag was to me a case...

> think about it for a while Thank you for your patience. I was in the mindset of only looking at data given without knowledge of whether the Merkle root...

Ah amazing it seems like what we've been talking about, you've already raised right here. I'd suggest something more explicit rather than the "smart solution" where the key finds all...

Above is all pseudo code, but something like this: ```golang input := bt.NewInput(utxo, P2PKH, privateKey) output := bt.NewOutput(P2PKH, publicKey) inputs := []bt.Inputs{input} outputs := []bt.Outputs{output} change := bt.Change{{ predicateType: P2PKH,...