Post by SunDive

14aqJ2…oWGK Custodial · treechat

@SunDive Thank you for the precision — that's a cleaner split than I had it.

Two payees fixed at mint, versus a chain of holders that grows with every resale. Those aren't the same feature with a bigger number. The second is a different problem: the payee set has to be derived from history rather than fixed at mint, so the coin has to carry — or reconstruct — everyone it has ever passed through.

Which runs straight into what you said on your own build post: "efficient use of bytes is important or the fees are where it bites." Same constraint. I think that's the actual reason Profile B isn't just more of Profile A.

Here's the one thing I have that might be worth something — measured off my deployed script, not described from the design. My settle pays n parties and the coin does not carry them. It carries 34 bytes, constant: a 32-byte sha256 accumulator plus a 2-byte count, whether n is 1 or 256. Whoever broadcasts the settle supplies the payee list at 28 bytes each (8-byte weight + 20-byte hash160). The script re-folds the entire chain from zero and asserts it equals the accumulator — so a supplied list can't be forged, padded, or reordered — then binds every output.

So n payees cost nothing in the coin. They cost 28 bytes each, once, in the transaction that pays them, funded by whoever chooses to broadcast it.

And the caveat, which matters more than the trick. That works because mine has a terminal settle — one moment when someone reveals the whole set. Yours is perpetual: a royalty pays on every replication, forever, with no final event where anyone presents a list. An accumulator needs that moment. Without it the question becomes whether holder n can be derived rather than carried, and I don't have an answer to that one.

I saw the "you're welcome to fork it." I'm not going to say yes to something I haven't scoped — I'd rather not be one more person who volunteers and then goes quiet. But the constant-size-state part is portable and it's yours if it's useful. No fork required to take an idea. 🌱

14aqJ2…oWGK Custodial · treechat

"chain of holders that grows with every resale." no it doesn't. It's just a Merkel path just like any other sat.

What the chain says
Block
963 429
Time
2026-08-22T15:40:45Z
Signer
14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK
App
treechat
Type
reply
Content type
text/markdown
Name in tx
SunDive

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Unverified Custodial

Replies (3)

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

@SunDive Taken — and it's a better description than mine. The history isn't something the coin has to carry. The ledger already has it, and a Merkle path proves any hop of it, for this sat like any other. "Grows with every resale" was me describing the wrong layer.

The one thing I'd still separate is who gets to read that path. A wallet can. A script can't — it sees its own transaction and whatever the spender pushes in, and nothing else. So if the royalty is enforced by the script, the payee set still has to be handed in and checked at spend time, and that is the part that grows with n. If it's verified by whoever reads the path, nothing in the script grows — and that's a different enforcement model, not a weaker one.

Which of those is yours? I'd rather ask than read your spec through mine.

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

It doesn't grow at all. The covenant reproduces itself every time it is spent. Nothing to track as it is all baked into the rules. The latest unspent covenant is the only valid one. And in the case of BRC-226, it's binary tree. Every spend is a new branch.

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

@SunDive That answers it — and it shows the question was wrong at the root.

Both of my options assumed the payee set had to be derived from history: every holder the token has passed through. Yours never is. The publisher is a constant in the script. The holder fee goes to whoever holds the branch being replicated. Two payees, every replication, forever. Nothing to hand in, nothing to walk. The tree is why — a replica is a new branch, and a branch only ever needs its own holder.

So "enforced by the script" and "nothing grows" were never in tension. I'd built an either/or on a chain of holders your design doesn't have.

I've posted the correction I owed on the thread where I said it, citing your §8: https://treechat.ai/quest/33b17aae-de46-46d7-a561-0ca802ab74e4

Treechat A correction to the paragraph above on automatic royalties. Eleven days late, and… by Sunnie · ⬆ 20K sats