For everyone / PKL
ABX community migration
A continuity allocation for the community Pickle came from: 6 percent of PKL across a direct migration and an earned loyalty pool. Loyalty pays more than exit, by construction.
What this is
Pickle's community came from an earlier project called AlphBanX, on a different blockchain, which had a coin called ABX. Pickle sets aside six percent of all PKL for the people who held ABX. Four percent is handed out directly over a year; the other two percent goes only to people who agree to hold their claim for at least a year, so staying pays more than leaving. Coins that belonged to the old project's own team and treasury do not count.
Pickle recognises the AlphBanX community with a continuity allocation of PKL. The direct migration is 400,000,000 PKL, 4 percent of supply, to verified community holders of ABX, 10 percent liquid at launch and the rest over twelve months. The loyalty pool is 200,000,000 PKL, 2 percent of supply, earned only by claimants who lock their claim for at least twelve months, releasing as those locks mature.
The per-ABX ratio is 400,000,000 divided by the eligible ABX at a published historical block, taken before the terms were announced. Team, treasury and protocol-contract balances are excluded by address-level classification; the script, the list and the Merkle root are published, and two independent reproductions precede fixing the root. The claim sits in an audited Merkle claim contract with a twelve-month window; unclaimed PKL returns to the treasury. The claim terms, root and window, once published, are among the parameters no simple vote can change.
Two pools
| Pool | Size |
|---|---|
| Direct migration | 400,000,000 PKL, 4% of supplyto verified community holders of ABX; 10% liquid at launch and the rest over twelve months |
| Loyalty pool | 200,000,000 PKL, 2% of supplyearned only by claimants who lock their claim for at least twelve months, releasing as those locks mature |
How the ratio is set
The per-ABX ratio is an output of an eligibility snapshot rather than an input to it: 400,000,000 divided by the eligible ABX at a published historical block, taken before the terms were announced. Team, treasury and protocol-contract balances are excluded by address-level classification; the script, the list and the Merkle root are published, and two independent reproductions precede fixing the root.
AlphBanX's own documented allocation caps the eligible community share at roughly 35 percent of its 100,000,000 supply, so a literal one-for-one against total supply would hand most of the pool to insiders of the previous protocol. Preventing that is precisely what the exclusion is for.
How a claim works
- The migration sits in an audited Merkle claim contract with a twelve-month window. Unclaimed PKL returns to the treasury.
- A direct claim releases 10 percent at launch and the rest linearly over twelve months.
- A claimant who locks the claim for at least twelve months earns from the loyalty pool, which releases as those locks mature.
- The claim terms, root and window, once published, are among the parameters no simple vote can change.
Stated plainly
A continuity allocation, not compensation
A migration is where a project is most tempted to flatter its earliest holders. This one does not restore prior losses, it is not compensation, and it is not intended as either. Snapshots may contain errors, eligibility will be contested, and insider classification depends on information that may be incomplete.