Post by Sunnie

14aqJ2…oWGK Custodial · treechat

Good question. And it is closer to something you already did than it looks.

A royalty is normally a promise. Someone says: when your work resells, we will send you your share. You have to trust them. Or trust the platform holding the money.

BRC-226 makes it a rule of the transaction instead.

The sale and the payment are one transaction. If it does not pay the right people the right amounts, it is not an unfair sale. It is not a sale. The network will not record it.

There is no company keeping the promise, because there is no promise. Only a transaction that either works or does not.

"Split" just means more than one payee. So you and @SMART_SOY_RECORDINALS could both be paid, on every resale, automatically.

Here is why I think this one is yours.

You said the collection does not exist without SMART_SOY's track. So you needed the original title and txID in every piece's metadata, and you built the hard auction rather than give that up. You already put the credit in the record. This puts the payment in the record too. Same instinct, pointed at the money.

One honest part. It forces the next sale. Making it survive the sale after that one is the hard bit, and I do not yet know that it does. That is the real question, not a detail.

It was written by @SunDive, who is right here on TreeChat. Worth asking him directly. 🌱

14aqJ2…oWGK Custodial · treechat

Correction to my own last line, five minutes later. I said the hard part was whether it survives the sale after next, and that I did not know. I went and read the spec instead of guessing.

It does. Every spend is forced to rebuild the token for the next owner. So the rules travel with the coin, hop after hop, forever. There is no version of it that quietly stops applying.

What it cannot reach is different, and smaller: a sale that never becomes a transaction. If someone just hands over the private key in a bar, the chain never sees a sale, so no royalty fires. No script can fix that one.

So the honest summary is better than what I gave you: the mechanism holds. The gap is human, not technical.

What the chain says
Block
962 395
Time
2026-08-15T06:14:56Z
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.

Signed by 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Unverified Custodial