Ownership Deals

A registration is soulbound — it cannot be sent from one wallet to another. Deals are how Chain Daddy moves one anyway: both sides agree, and the operator burns the seller's registration and mints a new one to the buyer.

Two of the four deal types work that way. The other two change no ownership at all: a consolidation announces that a ticker is winding down into another token, and a collab is an agreement to split the creator fees of a token that has not launched yet.

The registry has a deal path with a 7-day notice. Chain Daddy does not use it.

OpenCrownRegistry offers a second, permissionless route — initiateDeal then executeDeal — and that one really does enforce a 7-day announcement period (AnnouncementPeriodNotMet), a 30-day holding period before a deal may start, and a 30-day expiry. A Chain Daddy deal never goes through it: settlement here calls burnForDeal and mintFromDeal directly, which carry none of those gates. If you read elsewhere that deals have a notice period, that is the other path, and this page describes this one.

Settlement destroys the registration

A buyout or an acquisition is not a transfer. The seller's registration is burned and a new one is minted to the buyer, as two separate transactions. On EVM chains there is no undo if the second one never lands. See How settlement works.

Deal Types

Type	What it does	Where you start it	Chains
Collab	Agree now to launch a new token together and split its creator fees	Make Offer on someone's token page	EVM only
Buyout Offer	Take over the registration and offer current holders a conversion	Make Offer on someone's token page	EVM only
Project Acquisition	Acquire the whole project — the registration, the token owner() role, socials	Make Offer on someone's token page	EVM and Solana
Consolidation (API type merge)	Wind your own registration down into another token	the Consolidate action (the circular-arrows icon) on your own token row in My Tokens	EVM and Solana

The offer chooser hides a type it cannot serve on the registration you are looking at, and says why. On a Solana registration only Project Acquisition is offered: a collab pays out by naming both parties as fee recipients of an EVM launch, and a buyout requires the on-chain funds check, which has no Solana equivalent today.

Consolidation is deliberately absent from that chooser. It is the one deal a project makes with itself, so it is reached from your own token list, not from a stranger's offer form.

Collab

A collab is an agreement, made before the token exists, to split the creator fee stream of a token the two of you will launch together. Nothing about your existing registration changes, no money moves at proposal time, and nothing settles on chain.

You name three things:

• Ticker — the token you will launch together, 16 characters or fewer. It binds the agreement to one token: at launch the server compares the ticker being launched against the one you agreed, character for character, and refuses a mismatch. The cap is the launch form's own, so a longer ticker would be agreeable and then unlaunchable.
• Their share of the creator fees — above 0% and below 100%, in whole basis points. This divides the creator side of the fee stream, after the protocol cut and the mandatory airlock floor, so the number the two of you agreed stays the number you agreed even if those other rates change. A split at either end is a solo launch, and the launch itself rejects one.
• The liquidity you commit — whole US dollars, at least $1,000 by default.

A commitment, not an escrow

Nothing is taken and nothing is held. Chain Daddy has no escrow, and a launch has no deposit field to put one in. What is recorded is the figure you said you would provide, alongside a balance check proving you held it when you said so — by default 20% of the commitment, so a $1,000 commitment asks you to show $200. The same wallet could be empty a minute later.

The dollar figure is converted to the launch's numeraire at launch, not at proposal. A collab can sit unanswered for weeks, and a rate fixed today would be the wrong amount of ETH by then.

Either party can be the one who launches; the other is paid their agreed share of the fee stream either way. Once the collab is agreed, its deal page carries a Launch TICKER with this collab button that opens the launch form with the ticker and the deal already attached. The launch then names both wallets as fee recipients at the agreed split — a beneficiary set that is fixed at creation and cannot be corrected afterwards, which is why the server refuses a launch it cannot match to the agreement rather than quietly launching solo.

The deal closes when that launch is confirmed on chain. Until then it rests in announced indefinitely; nothing expires it.

The $1,000 floor is the default, and is configured per environment.

Buyout Offer

The buyer takes over the registration and publishes terms for existing holders to convert out of the token.

You set:

• Offer amount and currency — what you are paying the current holder.
• Redemption rate — how much of the redemption token a holder gets per token they hold.
• Redemption token — what holders receive.
• Redemption window — at least 30 days. This is a floor because the holders being given a deadline did not choose the party setting it.
• Redemption contract (optional) — see below.
• Assets included — Token Ownership (always), and any of: the token owner() role, Twitter/X, Discord, Telegram, website/domain, other. Nothing but the registration is pre-selected. The list is recorded with the offer and cannot be edited afterwards, so tick only what the two of you actually agreed.

The redemption contract field

Optional, and honest about what it is: an address you paste in, checked only for being a well-formed address. Chain Daddy does not deploy it, fund it, call it, or check that anything is behind it. There is no redemption pool on this platform and no on-chain escrow anywhere in the deal system.

The redemption terms are a promise the buyer publishes and the buyer keeps. Leave the field blank if you are handling redemptions by hand.

Assets included

The assets list is a record of what the two of you agreed changes hands beyond the registration itself: the token's owner() role, the Twitter/X account, the Discord server, the Telegram group, the website or domain, and a free "other".

Only Token Ownership is pre-selected, and nothing else is assumed. The list is written into the offer's terms and cannot be edited afterwards — the terms are recorded once, at creation. Chain Daddy does not transfer any of these for you and cannot verify that they were handed over; the list is the agreement, and the two of you carry it out.

Project Acquisition

The whole project changes hands: the registration, plus whatever else is on the assets list — commonly the token's owner() role, the social accounts and the domain.

Where the token has a readable market cap, the offer is expressed as a percentage of market cap; otherwise it is named in US dollars and converted to the currency you pick at that currency's current price. Offers above 100% of market cap are allowed and are normal — a buyer usually pays a premium to persuade an owner to sell.

An acquisition settles the same way a buyout does: the registration is burned and re-minted to the buyer. It is the only deal type available on a Solana registration.

Consolidation

Called "Migration" in earlier versions of this page, and the form is still titled "Migration Proposal".

A consolidation announces that one of your registrations is winding down into another token, and gives its holders a window to swap. It is owner-only: an offer to consolidate a registration you do not hold is refused with a 403, because a consolidation dissolves the thing it names.

You set:

• Swap ratio — 1:2, or a bare decimal like 1.5.
• Destination token — the contract address or mint holders are moving to. Checked for shape only. There is no destination chain in the terms, so Chain Daddy cannot and does not prove the token exists; the address you type is the address holders are shown.
• Swap window — 1 to 730 days. This is the deal's whole clock: the window opens the moment you create the consolidation, so there is no separate acceptance deadline.

What a consolidation does: it publishes a destination, a ratio and a deadline. What it does not do: move the registration, move any token, run the swap, or take a fee. Nothing settles on chain — the registration stays exactly where it is, with you, unless you separately retire it yourself. The two of you honour the swap off-platform.

Holders only see the consolidation notice on the token page once the deal has been agreed. A proposal nobody has accepted is shown to no one.

Only one live consolidation window is allowed per registration. Two open windows would mean whichever closed last silently became the token's public notice.

Consolidating across several chains

Announce your move creates one consolidation per chain as a conditional group: up to 32 members, one shared swap window for the whole set, so the consolidation closes at a single moment rather than as several drifting ones. Because you hold every registration in the set, it agrees them all in the same action.

A group is all or nothing

A grouped deal takes effect only once every member has been agreed. Until then, a member that shows accepted is not settled and holders are told nothing — the notice appears only when the set is complete, so one member that failed to go through holds the announcement back on every chain. And a member that is cancelled cannot be revived: cancelled is terminal, so one dead member means the whole set has to be created again from scratch.

Making an Offer

A buyer opens a deal from the token's page (Make Offer) and picks a type. For a buyout they set the amount and currency, prove they hold the funds, and set the holder redemption terms:

Once submitted, the offer is signed and sent to the current owner for review.

How long an offer stands depends on the type, and there is only ever one clock:

• A collab and an acquisition carry an offer window — 7, 14, 30, 60 or 90 days, chosen on the form, default 30. If the owner has not answered by then, the offer is withdrawn.
• A buyout and a consolidation name their own window instead — the redemption window and the swap window — and that window is the whole clock. They carry no separate acceptance deadline, which is why neither form asks for one. Sending an offer window on one of these is refused rather than quietly ignored.

Reviewing an Offer

When someone offers for your token, it appears in your deals and you are notified. Open it to see the full terms — amount, payment method, buyer, their message, and how much of the offer the buyer proved they held — then Accept or Reject:

Accepting is a signature, not a transaction. You pay no gas and need no balance to accept, and you receive the offer amount in full — nothing is deducted. Rejecting closes the offer with no on-chain action.

You can only have one live sale of a ticker at a time. Accepting a buyout or acquisition takes a double-sale lock on that ticker for your wallet across every chain: a second one is refused until the first is resolved or cancelled. Collabs and consolidations are outside the lock, because neither disposes of a registration.

Controlling what you are offered

Settings → Notifications carries Offers on your registrations, which applies to every registration you hold:

• Not accepting offers — refuses every type, including the ones that carry no price. A collab proposal is a contact too.
• Minimum offer — your own floor, on top of the protocol's $500 one. It applies to the types that name a price (a buyout or an acquisition); a collab names none, so the switch above is what covers those.

Both are enforced when the offer is made, not after. An offer below your floor is refused before a deal row exists, so it never reaches your inbox or your deal list — and the person making it is told the figure, because a floor nobody can see is a riddle rather than a rule.

Staying in the Loop

Deal activity — new offers, acceptances, and token alerts — surfaces in the notifications panel (the bell in the top bar):

How settlement works

Only a buyout and a project acquisition settle on chain. A consolidation and a collab never touch the registration.

Both chains end the same way — the registration is burned and a new one is minted to the buyer — but they get there differently, and the difference decides what happens when something goes wrong.

On an EVM chain

1. The buyer offers. Funds verified, terms signed.
2. The owner accepts. A signature, no gas. The deal moves to payment_pending.
3. The buyer pays the owner off-platform, in whatever way the two of you agreed. There is no payment leg on chain and Chain Daddy never holds the money.
4. The owner signs "payment received". A gasless signature. No burn is dispatched without it: it is the only thing standing between "the holder agreed to sell" and "the holder was paid", and there is deliberately no operator override.
5. The owner signs a burn consent. An EIP-712 message naming the buyer, valid for 24 hours. If it lapses, sign a fresh one — the old signature stops working the moment a new one is prepared.
6. The operator broadcasts the burn, then the mint. Two transactions. It pays the gas for both, and the registry's own claim fee for the new registration, out of its own balance — neither party pays gas to settle.

On Solana

1. The buyer offers, and the owner accepts — as above.
2. Both parties sign the settlement terms. Nothing below will build until both signatures are collected and verified; the burn commits a hash of exactly those terms, and the mint demands exactly those two signatures back.
3. The holder signs and submits the burn in their own wallet, on a transaction the operator has already co-signed.
4. The buyer signs and submits the settlement — one transaction carrying their USDC payment to the seller, both parties' signed agreement, and the mint. Solana reverts the whole transaction if any part of it fails, so there is no ordering in which the buyer has paid and the seller can still walk away.

The operator co-signs and pays the network fee on both Solana transactions, but only the party whose assets move can complete one — which is why the buyer, not the operator, submits the transaction that spends their USDC.

This is the irreversible part

The burn and the mint are two separate transactions. Between them the ticker belongs to nobody.

On EVM chains there is no restore. The registry burns the ERC-721 and keeps no way to give it back. If the mint never lands, the seller's registration is gone — and the product tells both parties exactly that. Sixty days after the burn, anyone may call the registry's cancelPendingDeal, which frees the symbol so it can be registered again from scratch, first-claim-wins, with no priority for the previous holder. Chain Daddy has no button for this today.

On Solana the registration can be reclaimed. The burn parks it in a pending-deal account with a settlement window — 7 days by default. If the buyer has not completed by then, its holder reclaims it from the deal page, and nothing has been paid to anyone.

Rules and limits

Rule	Value	Why
Minimum offer	$500, flat	A floor under lowball offers. An offer priced in a currency nothing can quote in dollars is refused rather than measured — otherwise 500 units of an unquoted token would clear a $500 floor
The holder's own floor	Whatever the registration's holder set, up to $100,000,000	Their answer to "who may make me an offer"
Offer window	7, 14, 30, 60 or 90 days — default 30, and only on a collab or an acquisition	Off-ladder values are refused, not rounded: a caller who asks for 45 and silently gets 30 finds out when their offer lapses two weeks early. A buyout or a consolidation is bounded by its own window instead, and sending one an offer window is refused too
An expired offer	Terminal	A lapsed offer is cancelled and cannot be revived. Make a new one
Fund verification	Required at offer creation for buyout, acquisition and collab on EVM chains	An unverified offer of those types is refused outright
How much you must hold	20% by default, up to 50% for a volatile currency — of the offer, or for a collab of the liquidity it commits	A risk-adjusted balance read, not an escrow
How long a verification lasts	1 hour	It is a balance at a block. An hour covers verifying, re-reading the terms and submitting; longer would turn the check into decoration. Re-verify and submit again
Buyout redemption window	At least 30 days	Someone else's holders are being given a deadline by a party they did not choose
Consolidation swap window	1 to 730 days	Your own holders, your own call — a real ticker retirement has run one day
Solana pricing	USDC only	Settlement pays in USDC, so an offer priced in anything else is agreed and then cannot be completed
Escrow	None, on either chain	There is no escrow provider and no contract that could hold a deposit. escrow as a payment method is refused at creation
Members in one conditional group	32	A consolidation spans the chains a ticker actually reached

The offer-window default and the collab liquidity floor are configured per environment; the values above are the defaults.

What a deal costs

Chain Daddy charges no facilitation fee for a deal, on either chain. Making an offer, accepting one, consolidating and agreeing a collab are all free, and on EVM the operator pays the gas and the registry claim fee for the settlement transactions.

What you pay is what the two of you agreed to pay each other. Payment on an EVM deal moves directly between the parties, off-platform; on Solana the buyer's USDC payment is part of the settlement transaction.

The published fee schedule has been removed

Earlier versions of this page published a sliding-scale facilitation fee (5%/3%/2%/1% brackets, a $20,000 cap, a 2% protocol contribution capped at $10,000, and a "first 10 deals" launch discount), with worked examples and a comparison against M&A advisers.

No code on either chain ever charged it. Solana settlement signs a payment amount with the operator fee explicitly set to zero, and the EVM settlement path has no money leg at all. The schedule, the examples and the comparison table have been deleted rather than restated, because a documented price nothing collects is worse than no price at all. If a fee is introduced, it will appear in the signed settlement terms first and on this page second.

Cancelling

Either party to a deal can cancel it, and a cancelled deal cannot be reopened.

• Before the burn lands, cancelling costs nothing and changes nothing on chain: an offer, an accepted deal awaiting payment, and a live consolidation window can all be cancelled.
• Once the burn is confirmed on chain, the deal is executing and can no longer be cancelled. It can only complete or fail — and on EVM, a failure at that point is the unrecoverable case above.

An offer nobody answers before its clock runs out — the offer window, or the deal's own window where it has one — is cancelled automatically.

The "release" step has been removed

Earlier versions of this page described a four-step lifecycle in which the seller released their registration and the buyer then filed a fresh one within 60 days. Neither party does either: settlement is two operator-broadcast transactions, and the 60 days is the registry's claim window before a burned symbol can be registered again by anyone. The sequence above is what runs.

Holder protections

Protection	What it actually is
Mutual consent	The buyer signs their offer and the owner signs the acceptance. On EVM the owner then signs both a "payment received" attestation and a burn consent; on Solana both parties sign the settlement terms before anything can be built. No single party can move a registration
The burn is bound to the buyer	The EVM consent commits to a deal id computed over the seller, the buyer, the token id, a deadline and a random salt, and the registry refuses to mint to anyone else. Solana enforces the same committed buyer on its pending-deal account
Payment before burn	On EVM, no burn is dispatched until the registration's holder has signed that they were paid — and there is no operator override. On Solana the payment is an instruction inside the settlement transaction, so it cannot be skipped at all
A consolidation window	Holders get the window the owner published — 1 to 730 days — and see it on the token page with the destination and the ratio
One live sale at a time	A holder cannot accept a second buyout or acquisition for the same ticker while one is in flight, on any chain
A public record	The burn and the mint are real transactions on the OpenCrown registry, visible to anyone. The deal itself lives in Chain Daddy's database, and both the record and the terms the parties agreed are readable through the public deal API — a collab's terms are the one exception, withheld from anyone who is not a party so an unlaunched ticker is not handed to whoever reads it first

Two protections that were listed here and are not real

"Every deal is visible on-chain for 30 days before execution" and "only one active deal per registration" were both published on this page. Neither was ever enforced.

There is no notice period before a registration moves: a deal can go from accepted to burned in a day. The clocks that exist are the offer window, the buyout redemption window, the consolidation swap window and the 24-hour burn consent — all listed above.

And several buyers can hold live offers on one registration at the same time; for an offer marketplace that is the right behaviour. What is enforced is at acceptance rather than at offer: the double-sale lock above.

What holders see

Holders are the other party to every deal, and there is a page written for them: Deal notices on a token page. It is worth reading before you announce anything, because it says exactly what your holders will and will not be shown.

Edge cases

An offer nobody answers. It is cancelled when its clock runs out. Terminal — make a new one.

The owner changes their mind before paying. Cancel. Nothing has happened on chain.

The buyer's wallet is compromised before settlement. Cancel, and take a new offer from a new address. The burn consent names the buyer, so a consent signed for the old address cannot be redirected — but it has to be cancelled before the burn is dispatched.

A settlement fails part-way on EVM. The registration is gone and cannot be restored. Both parties are told so. Sixty days after the burn the symbol can be registered again by anyone.

A settlement fails part-way on Solana. After the settlement window (7 days by default) the holder reclaims the registration from the deal page. Nothing was paid.

A collab that never launches. It rests in announced indefinitely. Nothing expires it and nothing is owed.