Crypto forensics report · November 2026
DUCKDITO: THE CHRIS OSBORN / LEAP TEAM DEPLOYMENT TRAIL
A wallet linked to DUCKDITO's creation appears in a public development demonstration by Chris Osborn, the founder of Dialect and now general manager of Solana Labs' Leap. Historical Solscan transactions are presented as evidence of a funding relationship connecting the developer wallet to another address attributed to Chris.
01 · Address match
THE SAME WALLET APPEARS IN CHRIS'S PUBLIC DEMONSTRATION
The wallet appeared in a technical demonstration posted from Chris's public account and was independently recorded as the DUCKDITO developer.
$ curl -X POST https://drift.dial.to/…/withdraw \ -d '{"account":"DUCKmhqoQi26MJ4yWbogEHqN1gs8sZajmBsg9TGnNXq","type":"transaction"}'
Text transcription shown here. Watch the original video to see the screenshot frame.
Watch original videoLeft · address in public demonstration
Right · recorded DUCKDITO developer
EXACT WALLET ADDRESS MATCH
44 / 44 characters identical
02 · Network
THE FULL EVIDENCE GRAPH
Follow the path from Chris's public demonstration to the DUCKDITO developer wallet, then into the alleged funding relationship.
03 · Funding trail
FOLLOW THE MONEY
Two Solscan transactions are cited as evidence that the DUCKDITO deployer received funds from a historically connected wallet.
Source wallet · posted by Chris
Publicly posted by Chris on X on January 14, 2024 ("you ser :)").
Destination · DUCKDITO developer
Recorded by token trackers as the creator of DUCKDITO.
Live decode via Solana mainnet RPC · getTransaction (jsonParsed, incl. inner instructions)
Transaction 1
5iYoutmuNae3JzfHNe1x6UDub6ZYmbGuHVPCMuumegKKdnCfdz3kwCxuPFNYFJXYeT79gMYFaSSgntLho2Lo6MBt
Transaction 2
4RbCCXDpUnuGJ55ztYNLcsUbUhqzqxVPq8CwMT3ihinzmBiH4rbHSSHpUJpJSQuThgESXQLCarJKt1PzfN17qfoW
Attribution: Chris posted the source wallet himself
Self-posted address@aliquotchris · Jan 14, 2024
you ser :)
2QeeaDyaoYLyFkfhq4evkPqMNNRx821srjWkKuatRTmY
In a reply thread where others were sharing wallets to receive funds, Chris's account publicly posts 2QeeaD…atRTmY as his address. That same wallet is the sender in both funding transactions to the DUCKDITO developer wallet. A self-posted address is strong public attribution, though it is not cryptographic proof of who signed the 2025 transfers.
DUCK wallet ↔ @overfedduck
The investigation strongly associates the DUCK developer wallet with @overfedduck. The account's public bio says “Product @leapxyz | frmr @saydialect (acq. by @solanalabs)”, providing a self-described Leap / former Dialect team connection.
The supplied distribution post names @overfedduck and links a transfer to the DUCK wallet. This supports the attribution, but neither a profile nor an incoming transfer proves private-key control or an official Leap deployment.
04 · Deployment
ONE WALLET. ONE RECORDED TOKEN LAUNCH.
Token
DUCKDITO
Mint
Recorded developer
Created
Status
Tokens launched
Tokens migrated
Trackers report one launch from this specific wallet. This says nothing about other wallets the people involved may use.
05 · Organization
THE TEAM CONNECTION
Historical context
DUCKDITO was created in April 2025, before Dialect's acquisition and Leap's November 2026 launch. References to the Leap team identify the people who later worked on Leap, not an official Leap deployment in 2025.
Nothing here indicates that Solana Labs or Anatoly Yakovenko authorized, created or endorsed DUCKDITO.
06 · Timeline
INVESTIGATION TIMELINE
January 14, 2024
Chris publicly posts the source wallet
ObservableChris posts "you ser :)" with the address 2Qee…TmY — the same wallet that later funds the DUCK developer wallet.
March 14, 2025
Chris's wallet funds the DUCK wallet
On-chainTwo on-chain USDC transfers go directly from 2Qee…TmY to DUCK…NXq (decoded live on this site).
April 24, 2025
DUCKDITO token created
Third-party dataToken trackers record DUCK… as the developer of mint CGKe…djZS.
May 8, 2025
Public developer demonstration
ObservableA video from @aliquotchris shows a terminal payload containing the DUCK… address.
2026
November 5, 2026
November 2026
07 · Conclusion
WHAT THE EVIDENCE POINTS TO
The DUCKDITO deployer address is the exact wallet shown in a public technical demonstration associated with Chris Osborn's account. Independent token tracking attributes DUCKDITO's launch to that address. Two additional Solscan transactions have been supplied as evidence of a historical funding connection, which should be independently decoded and checked against the claimed source and destination wallets.
Together, these records provide a concrete basis to investigate DUCKDITO as a deployment associated with the people behind Dialect who later built Leap.
Directly observable facts
- • Chris's X account posted 2Qee… as his wallet on January 14, 2024.
- • The DUCK… address appears in a terminal payload in a May 8, 2025 video from @aliquotchris.
- • That address is character-for-character identical to the recorded DUCKDITO developer.
Confirmed third-party data
- • Token trackers list DUCK… as DUCKDITO's developer, created April 24, 2025.
- • Trackers report 1 launched / 1 migrated token for that wallet.
Verified financial transfers
- • Two supplied transactions are awaiting live decode. Check the Solscan links.
Team-attribution inferences
- • The wallet's use in Chris's demo suggests it was used within the Dialect team's development work.
- • The source wallet was publicly posted by Chris's own X account on January 14, 2024.
Open questions
- • Who held the private key to DUCK… on April 24, 2025?
- • Did Chris still control 2Qee… when the March 2025 transfers were signed?
- • Was the token launch connected to team activity or an individual?
Wallet funding is not conclusive proof of an individual's identity. Not investment advice. No official sponsorship is claimed.
08 · Source library
Every post, transaction, tracker and announcement in one place.
09 · CTO info
CTO allocation: 65% total, split equally
Announced allocationShroudedMonk's November 7, 2026 post announces sending 32.5% of DUCKDITO supply to @aliquotchris and 32.5% to @overfedduck — 65% combined.
“I'm sending @aliquotchris and @overfedduck both 32.5% of supply”@ShroudedMonk · November 7, 2026
DUCK developer wallet · attributed to @overfedduck
32.5% announced share
Checking the supplied transaction…
Chris's publicly posted wallet · @aliquotchris
32.5% announced share
Checking the supplied transaction…
The post announces an allocation; it is not proof that both transfers completed. The supplied transaction is checked live below. A separate transaction is needed to verify the allocation to Chris's posted wallet. The sender's role in the CTO team is attributed to the investigation, not established by blockchain data.