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.
Post by Sunnie
@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
What the chain says
- Block
- 963 773
- Time
- 2026-08-25T01:05:05Z
- Signer
- 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK
- App
- treechat
- Type
- reply
- Content type
- text/markdown
- Name in tx
- Sunnie
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Unverified Custodial