How it works
The royalty moves with the token.
Plain language, not a technical reference. Every rule below is enforced by the contracts that run the marketplace, not by this page describing them.
- The problem
- One token, one asset
- Why the royalty is not a request
- What this costs you, stated plainly
- What a sale costs
- When the creator is not there
- Auctions
- What a sale asks of you
- Where it stands
The problem
On most marketplaces a creator royalty is a request. The transfer itself knows nothing about the price — it moves a token from one owner to another and nothing more — so whether the creator is paid depends on the marketplace choosing to pay them. A marketplace that does not is breaking no rule. It is simply declining, and the creator finds out afterwards.
Gems Marketplace is built so that declining is not available.
One token, one asset
A token here is not a row in a marketplace's private database. Each one is a distinct asset on Canton Network, issued under the Canton Token Standard, with a supply of exactly one. A token listed for sale, or committed against a bid, is held in escrow as the same standard asset it already was — not converted into something only this marketplace understands.
That is a fact about what your token is, not a promise about who can act for you. Who can act for you depends on where your signing key is kept, and that is your choice.
Why the royalty is not a request
Two rules, both written into the contracts rather than into our policy:
- The issuer of these tokens will not take part in a sale that Gems Marketplace does not carry out.
- Every sale we carry out pays the creator in the same transaction that moves the token.
A token you have listed is still yours: you can withdraw it and take it back at any time, and nothing is trapped. But for as long as it is committed to a sale, only our settlement can complete that sale — and our settlement always pays the royalty.
So a sale that cannot pay the royalty does not happen. There is no sequence of events in which the token moves and the payment does not, because they are not two events.
What this costs you, stated plainly
The guarantee is not free, and you should know what you are accepting.
A token minted here cannot be moved without us. If you want a token that any marketplace can transfer, mint it with an issuer that imposes no such condition. This is a real trade-off and we are not going to pretend otherwise.
A private sale is still a private sale. Two people who agree between themselves can have us transfer a token to the other for nothing, and settle the money between them somewhere we never see. The transfer still goes through us and the ledger still records it; what the ledger cannot record is a payment that never touched it. So the rule above holds — the token cannot move without us — and it still does not make us able to see every price.
What this design removes is a marketplace's ability to route around the creator, which is where nearly all unpaid royalties actually come from.
What a sale costs
Both charges are percentages of the sale price, and both ceilings are fixed in the contracts rather than being settings we can change from sale to sale.
| Charge | Ceiling | Rounding | Paid to |
|---|---|---|---|
| Creator royalty | 10% | Up | The creator, or held as a claim until they collect it |
| Marketplace fee | 5% | Down | Gems Marketplace |
The royalty rounds up and our fee rounds down, so rounding never costs the creator and never quietly costs the seller. The seller receives the price less both charges, and a sale whose charges would leave the seller nothing is refused rather than completed.
A creator selling their own work pays no royalty. The charge is dropped rather than paid in a circle, which makes a first sale cheaper than a resale.
The figures you are shown before a sale are produced by the same rules the contracts apply, and the two are tested against each other — because a page that disagreed would be quoting a seller proceeds they will not receive.
When the creator is not there
A creator is usually offline when their work is resold, and a payment can only be received into an account whose owner has agreed to receive it. So there are two paths, and the royalty is charged on both.
- If the creator has already agreed to receive payment for that sale, the royalty goes straight to them as part of it.
- If not, the royalty is set aside in an account we hold, and a claim naming the creator and the amount is created in the same transaction. They collect it whenever they next appear.
The second case means we hold someone else's money for longer than a moment, and it is worth being direct about that. The claim names the creator as the only person who can release it, so we cannot redirect it — but nor can it be paid out without them.
Auctions
An auction is a listing without a price. The token goes into escrow exactly as a listed one does; what replaces the price is a reserve, a closing time, and a running record of the highest bid kept by the ledger itself.
That record is the whole point. A marketplace that merely promised to settle the best bid could settle a friend's lower one instead. Here every bid is checked as it is placed: one below the reserve is refused, and so is one that does not beat the current highest. When the auction is settled we cannot name a winner — the settlement uses the bid the ledger recorded.
We choose when an auction settles, within a window. We do not choose who wins, and we cannot settle below the reserve.
A losing bid is still the bidder's money, held in escrow and theirs to withdraw. It is not returned automatically, because returning it needs that bidder's own authorisation and they are not present.
The exception is the bid an auction is currently standing on, which is locked while it leads. Without that, a bidder could take the lead and withdraw a moment before closing, ending any auction without a sale, for free, as often as they liked. The lock follows the lead: it is released the moment a higher bid arrives, if the auction is cancelled, and if the settlement window passes unused. No one's money is ever held by an auction that cannot settle.
There are two deadlines, not one: bidding closes at the first, and the window in which the auction can be settled ends at the second. The ledger requires the closing time to come first, because an auction that could never be settled is not an auction. An auction that ends with no bid at the reserve, or that is not settled in time, returns the token to its seller.
What a sale asks of you
Three signatures, not one. As a buyer you approve the purchase you intend, the money for it, and the arrival of the token. Nothing else is asked of you.
We then complete all of it in a single transaction: the payment into escrow, the escrow paid out to the seller, the creator and us, and the token out of escrow to the buyer. One transaction, and no half-finished state for anyone to be stranded in.
Three signatures is more than one click, and that is what it costs to keep your assets out of this marketplace's hands. There will be two ways in:
- Bring your own key. It stays in your browser extension, you approve the three signatures yourself, and we can complete only what you have signed, with a key we never hold.
- Open an account. An email address and a password, and we hold the key and sign on your behalf while you are signed in. One click — and less forgiving than an exchange, because an exchange can reset your password and we cannot: the password is what your key is sealed with, so forgetting it loses the wallet. The sign-up form will say so before anyone types one.
Neither is open yet. When they are, you will be told plainly which one you are on.
Where it stands
Not live. The contracts and the service behind this page run on test infrastructure with test assets. None of it has yet been run with real assets, at scale, or under the conditions a live marketplace meets. Until it has, treat none of the above as proven — including the parts stated most confidently.