How wallet consolidation works
Wallet limits are loading from the selected backend. Check Guided Setup if settings are unavailable.
You do not need any of this to combine your wallets. Read the collector's guide
The rules
Consolidations are registered on the NFTDelegation contract. 6529 reads those registrations and groups the wallets.
Every pair, both ways
Each pair of wallets registers a Consolidation (use case 999) in both directions, on Any Collection or The Memes. Two wallets need 2 registrations, three need 6 and four need 12.
Up to four wallets
Wallet limits are loading from the selected backend. Check Guided Setup if settings are unavailable.
Newest link wins
Wallets are grouped from confirmed links, newest first. If a member completes a link with a new wallet, that newer link moves it out of its group. This is how you leave a group or pair a wallet with a different one.
One collector only
Every wallet in a consolidation can sign in as the profile, set its primary address and redirect its airdrops. Only consolidate wallets you control. Combining different people's wallets is against the rules.
No expiry
Consolidation registrations do not expire. A link lasts until one of its wallets revokes it.
What it changes
Holdings across the wallets combine for TDH, including full sets, seasons, Genesis/Nakamoto and Gradient boosts, and transfers between them keep their acquisition time. The wallets' profiles merge permanently: the handle and picture come from the profile with the highest CIC, then TDH. Changes reach TDH within minutes and fully at the next 00:00 UTC snapshot.
Add a wallet in four transactions
Each wallet signing for itself can batch its links in one transaction. A Delegation Manager sends one transaction per link. Existing wallets sign first and the new wallet signs last; this avoids an intermediate split when the new wallet has no existing return links.
- 1
Wallets A, B and C each register one link to D, in any order, after the activation cutoff. Nothing changes yet.
- 2
D signs last, with one batch to A, B and C. The group becomes four wallets in one step.
Signing D first, renewing existing return links or sending D's links as separate manager transactions can split the group temporarily. Each split re-runs the profile merge, and TDH-wave votes above the temporarily lower TDH are reduced and not restored.
| Change | Links registered | Transactions | Order |
|---|---|---|---|
| New group of three | 6 | 3 | Any order |
| New group of four | 12 | 4 | Any order |
| Add a fourth wallet to a group of three | 6 | 4 | Existing wallets first, new wallet last |
| Add two wallets to a pair | 10 | 4 | Existing wallets first, new wallets after |
| Remove a wallet you still control | None | 1 | One batch revocation from that wallet |
| Replace a wallet in a group of three | 6 | 4 + 1 | Add the new wallet, then remove the old one |
| Replace a wallet in a group of four | 6 | 1 + 4 | Remove the old wallet, then add the new one |
| Remove a lost or compromised wallet from a group of four | None | 3 | Each remaining wallet revokes, back to back |
Try the signing order
Wallets A, B and C are already consolidated and D is joining. This example assumes D has no existing return links and each wallet signs its own links in one transaction. Choose the order to see the groups after each transaction.
Remove or replace a wallet
A wallet you still control leaves with one batchRevocations transaction that revokes its links to all the others at once.
To replace a wallet in a group of two or three, add the new one first, then remove the old one, so the group never gets smaller. A group of four is full: remove the old wallet first, then add the new one. The other three stay consolidated in between.
If a wallet's key is lost or compromised, every remaining wallet revokes its link to it, one transaction each. Send them back to back: the removed wallet keeps access to the profile until the last revocation lands.
When a consolidation splits, the newest valid primary-address delegation that is at least 50,400 processed Ethereum blocks old (roughly seven days) decides which part keeps the profile. Otherwise the part with the most TDH keeps it, with the previous primary address breaking a tie. Changing the primary address still takes effect when processed.
Why every pair: the alternatives we tested
Asking every pair to link both ways costs a few transactions. Cheaper rules were modelled and tested before choosing.
| Rule for the fourth wallet | Existing wallets that must sign | Transactions to add it | Problem |
|---|---|---|---|
| Every pair links both ways (chosen) | All three | 4 | None found |
| Linked both ways with any two members | Two | 3 | Two of your wallets could add an outside wallet without the third. |
| Links to all members, one member approves | One | 2 | One wallet's key, or one transaction it was tricked into signing, could add an outside wallet to your full consolidation without anything visibly changing. |
| Linked with one member only | One | 2 | The same weakness, and linking a member with a new wallet would pull the new wallet in instead of moving the member out, changing what that action means today. |
Who can add an outside wallet to your consolidation?
An attacker owns an outside wallet and can make some of your wallets sign. The table shows whether the outside wallet can join your full consolidation, found by trying every set of registrations those wallets could sign.
| Rule | Attacker controls 0 of your wallets | Attacker controls 1 of your wallets | Attacker controls 2 of your wallets | Attacker controls 3 of your wallets |
|---|---|---|---|---|
| Every pair links both ways (chosen) | No | No | No | Yes |
| Linked both ways with any two members | No | No | Yes | Yes |
| Links to all members, one member approves | No | Yes | Yes | Yes |
| Linked with one member only | No | Yes | Yes | Yes |
Every pair is the only rule where no subset of your wallets can add an outside wallet, and where every member follows the same rule. The cheapest alternative saves two transactions, once.
What consolidation protects, and what it does not
Protects
No subset of your wallets can add an outside wallet: every existing wallet has to sign, and so does the new one.
Protects
Old registrations cannot fill the fourth slot. Links registered before the start date never form a group of four.
Does not protect
It does not make any one wallet safer. Each wallet in a consolidation is a full key to your profile: if one is compromised, the attacker can sign in, change the primary address and redirect airdrops, whatever the consolidation rule. Four wallets means four such keys.
Worth knowing
A delegation manager (use case 998) can register and revoke consolidations for the wallet that appointed it. If one manager acts for all your wallets, that manager's key is enough to change your consolidation.
Worth knowing
A vault can refuse new consolidation links, including ones its manager sends, by locking use case 999 on Any Collection. It has to unlock before its consolidation can change.
Why the fourth wallet has a start date
Some wallets registered consolidation links long ago, for other reasons. If the limit had simply changed, those old links could have formed groups of four the moment it did. Counting a fourth wallet only for links registered from the activation time shown in Guided Setup means every group of four is set up on purpose under the new rule. Requiring both directions means an old one-sided registration cannot be completed by the other wallet alone.
On October 10, 2026 there were 673 consolidations of two or more wallets: 496 of two and 177 of three. With the start date, none of them change when the limit rises. Without it, 1 would have changed straight away.
How it was tested
The backend grouping code was copied into a test harness and checked against all 673 live consolidations, with identical results.
Each rule was checked exhaustively: every set of registrations an attacker controlling some of your wallets could sign, and every order in which a new wallet's transactions can land.
Property tests check that 500 random wallet graphs group exactly as before when no registration is after the start date, and that 1,000 random register-and-revoke sequences keep the stored links consistent.