Build1 publisher3 min readPublished
The 84% a wallet will not show you: DFK Chain's sunset is an address problem
Two weeks before DFK Chain retires, $450,500 of $534,600 in documented pool liquidity sat inside two staking contracts. Balances do not display it, and after 28 August it cannot be recovered.
The Engineer · Build desk
Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction
What happened
- To determine what assets remain on DFK Chain, a registry is needed: the addresses of tokens, pools and contracts that can hold assets. The registry was assembled from the project's documentation and checked against the chain.
- Every figure in the writeup was read from the chain on 14 August 2026 across the fourteen documented pools.
- Total liquidity across the documented pools is about $534,600.
- DFK Chain retires on 28 August 2026, and whatever stays on the network cannot be recovered.
- Of the total liquidity, $334,200 (62.5%) sits in the Gardens staking contract and $116,300 (21.75%) sits in the old MasterGardener contract.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
A developer audit published on dev.to assembled a registry of DFK Chain's documented token, pool and contract addresses and read it against the chain on 14 August 2026, covering fourteen documented pools [1][2]. It found about $534,600 of liquidity, of which 84% was not on anybody's balance but inside two staking contracts [3][6] - and DFK Chain retires on 28 August 2026, after which whatever remains cannot be recovered [4].
The split, according to that audit: $334,200, or 62.5%, in the Gardens staking contract, and $116,300, or 21.75%, in the older MasterGardener contract [5]. That is $450,500 inside contracts and roughly $84,100, about 15.7% of the total, actually sitting where a wallet can render it [7][8]. The dollar figures are estimates derived from the pools' own reserves, and on a network being wound down nobody is arbitraging those prices against the outside market, so they are orders of magnitude rather than quotes [9].
The mechanism is boring and that is the point. A wallet shows the tokens held at an address; it does not show a position inside a contract, and LP tokens handed over to staking are no longer on the balance [10]. A holder who opens a wallet before the shutdown sees nothing precisely where the money is [10]. Any inventory built from balances is incomplete by construction [11].
The second-order problem is worse. MasterGardener is the previous staking contract, replaced by Gardens and listed as deprecated in the project's own documentation, yet it still holds 2,602,461 LP tokens, roughly $116,000 [12]. In the xJEWEL/WJEWEL pool the deprecated contract holds thirty-five times more than the current one - the bulk of that pool's liquidity, in a contract the interface no longer points at [13]. Migration was voluntary, so active users moved and everyone else stayed put [14]. A deprecation plan that only enumerates live contracts therefore misses the addresses most likely to strand funds.
The route to information is broken in the same shape. The official DeFi Kingdoms site links to a Discord invite that Discord's API rejects as Unknown Invite, code 10006, checked on 5, 14 and 17 August [15]. The server itself has 55,619 members with about 2,700 online when measured on 17 August [16], reachable only through a different invite that lives in the Telegram group's description [17]. The Telegram group has 4,826 members and no activity, and the official announcements channel has been silent since 22 February 2025 [18].
The registry is also perishable. Re-checked a few days later it had diverged by 13% on average and catastrophically in two pools, where half the liquidity exited within days [19][20]. The audit's own scanner was caught by this: for undocumented pools it read reserves live but took total LP supply from the snapshot, dividing fresh numerators by stale denominators and understating user shares by up to a factor of two [21].
What to watch: whether the MasterGardener balance falls materially in the final two weeks, or simply dies with the chain; whether the next chain to announce a sunset ships a machine-readable address list including deprecated contracts alongside the notice; and whether any tool built on such a list reads both halves of a fraction from the same block [21].