Verified transaction
The creator’s first position
was sold at +13 seconds.
Three purchases, one exit. The creator’s trade is separate from the wider wallet group.
E07Independent on-chain investigation
WADDLES.
Launch forensics.
The wallets, funding routes and first trades behind the Robinhood Chain launch. Every finding linked to its evidence.
Wallet relationshipsInteractive map ↗
Selected relationships · full context in the funding map
The creator’s first position
Inspect the evidence
57 entries, with direct source links and explicit evidence grades.
Open sources ↗Cross-chain recordsTrace the transfers
301 indexed bridge requests, searchable by wallet and transaction.
Open explorer ↗Networks in the bridge data
Ethereum · Solana · BNB Chain · Robinhood · Base · HyperEVM · Monad ·
Launch attribution
The most defensible attribution is to a pseudonymous operation centred on creator A and funding coordinator C, with B and D participating in its finances and trading. A recurring Solana wallet, FjD, supplied substantial upstream capital through Relay. No verified evidence connects the financing to Amazon or AWS.
Verified launch transaction sender · Wallet A
0x81D7a91860a70B312E68c075C896aA06281cCC63This is the externally owned address that initiated the launch. The factory and contract-creation helper are separate infrastructure. E01E02
Who orchestrated the deployment? A signed the launch transaction and is named as deployer in the factory event. A also bought WADDLES, sold its initial holding and changed the creator-fee recipient. Those actions establish the operator address, regardless of how an explorer labels the lower-level contract creator. E02E04E07E09
Who visibly financed the operation? B supplied A’s first observed Robinhood ETH. C seeded A, B and D equally on Ethereum, originated two BNB-to-Robinhood funding requests into A, and financed five more trading wallets just 25 seconds before launch. D also supplied A with 0.55 ETH. The flows establish multiple direct funders, with C occupying the clearest capital-allocation role. E03E12E16E18E19E21
Where did upstream capital come from? A verified Solana deposit by FjD is linked by Relay to C’s first Ethereum funding. Immediately before that deposit, FjD received SOL from six Pump AMM sales. Across the retrieved bridge dataset, FjD sends funds to all four core wallets and receives return flows from all four. E13E14E15E39E40E48
Answering “who” at the resolution the evidence permitsA is the verified deployment operator. C is the strongest visible funding coordinator. FjD is a recurring upstream capital counterparty. B and D are financially and operationally connected participants. The beneficial owners, any private agreement between them, and any outside sponsor remain unidentified.
Funding network
Select a view, then select any wallet to inspect its full address and role. Solid arrows mark recorded transfers or events; dashed arrows mark a cross-chain relationship supplied by a bridge index. The diagrams are selective explanatory maps, not exhaustive transaction graphs.
Evidence map / select a node
Recorded transfer / eventBridge correlation
A transaction path is not an ownership path.Relay solvers, public batch-transfer contracts, swap routers, AMM pools and exchange wallets serve many unrelated users. This report does not absorb those services or their customers into the WADDLES operator cluster. The July exchange trail is historical wallet ancestry; the August trading-proceeds trail is the more immediate source of the specific Ethereum seed.
Deployment and first trades
WADDLES launched on 29 August 2026 at 13:47:02 UTC, in Robinhood block 49,201,242. The initiating transaction is below. It carries 0.0005 ETH from A to the Pons V2 launch factory. The observed gas fee is separate: 0.0002736799058 ETH. E02
Launch transaction
0xf227bb992620e48ea737b79586efcd6b3e94c8e6ea7a708e694295eb87b17f91| Receipt element | What it establishes |
|---|---|
| Transaction sender | 0x81D7a91860a70B312E68c075C896aA06281cCC63The EOA initiating deployment; wallet A. |
| Pons V2 factory | 0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7ePublic launch infrastructure, not the human creator. |
| Creation helper | 0x3711ceA4feaDE896C913C68F01Eda97Cb06D1A42Low-level token-creation attribution. Following only this address would miss the initiating EOA. |
| Log 29 · mint | 1,000,000,000 WADDLES from the zero address to 0xeC4702Ef81Fe8d47708231B4E60E582372b21899. |
| Log 31 · exemption | SnipeTaxExempted(A). An explicit launch privilege; its quantitative effect requires the applicable curve logic. |
| Log 32 · fee receipt | SafeL2 0x263ed295dAFaE1d9AAdD6E56c4B6F9f38eE019Dd receives 0.0005 ETH from the factory. |
| Log 33 · TokenLaunched | Binds the exact token, curve, deployer A and AMZN pair token. Configuration ID 0. Graduation threshold 29.330291092142702509 AMZN.A configured threshold is not evidence that this amount was deposited at launch. |
The creator’s first thirteen seconds
A bought three times, held approximately 8.43823% of the minted supply, and sold that entire initial position 13 seconds after launch: seven seconds after its first buy. The three purchases and sale are distinct receipts. This statement concerns A’s address, not the whole connected group. E04E05E06E07
Launch replay · 29 Aug 2026 · UTC
+00s
13:47:02 · block 49,201,242
Launch+6s+8s+10s+13s+89s
Token deployed
One billion WADDLES minted to the curve. A pays the launch fee.
A’s WADDLES balance0
A’s trading ETH out0
| UTC / offset | Creator action | Amount / outcome | Receipt |
|---|---|---|---|
| 13:47:02 / +0s | Launch | 0.0005 ETH launch fee | E02 |
| 13:47:08 / +6s | First buy | 0.200583358784841679 ETH74,773,770.579440143274737964 WADDLES received | E04 |
| 13:47:10 / +8s | Second buy | 0.05 ETH8,775,687.942975294888235557 WADDLES received | E05 |
| 13:47:12 / +10s | Third buy | 0.005 ETH832,839.862981708812727857 WADDLES received | E06 |
| 13:47:15 / +13s | Approval + full initial-position sale | 84,382,298.385397146975701378 WADDLES0.415698539319334160 ETH returned to A internally by the router | E07E08 |
| 13:48:31 / +89s | Creator-fee recipient changed | A → rewards-distributor contract | E09 |
Creator-wallet cash result
Sale proceeds+0.415698539319334160
Three buy inputs−0.255583358784841679
Launch fee−0.000500000000000000
Six transaction gas fees−0.000413612897462000
Net ETH delta+0.159201567637030481
What that result excludes
The calculation uses integer wei values from the creator’s transactions and internal-call export. It includes launch, three buys, sale approval and sale. It excludes later administration, other wallets, subsequent fees, earlier capital acquisition and unrelated tokens. Failed transactions by B are not charged to A. It is not a consolidated operation P&L. E47
No additional WADDLES transfers involving A appear in its 530-row token export. That bounded observation does not establish that related wallets liquidated their positions, or that A could never reacquire tokens after the snapshot.
ETH funding and the AMZN swap route
There is no incoming AMZN transfer to A in the retrieved 530-row token history. The first WADDLES purchase acquires AMZN inside the router transaction and sends it directly into the curve.
The request to trace “the first AMZN funding into the creator” assumes that AMZN was first deposited in that wallet. The observed transaction does not follow that model. A supplies ETH; the router wraps and trades it through WETH and USDG into the AMZN quote asset. The AMZN transfer’s destination is the curve, while A receives WADDLES. A quote token’s name does not reveal who supplied the originating ETH. E04E47
ETHA supplies
0.200583358784841679→
0.200583358784841679→
WETHRouted amount
0.198577525196993263→
0.198577525196993263→
USDGIntermediate asset
483.536552→
483.536552→
AMZNSent to curve
1.801223537258714669→
1.801223537258714669→
WADDLESReceived by A
74,773,770.579440…
74,773,770.579440…
Amounts are sequential assets within one transaction. They must not be added as separate funding sources. The difference between transaction ETH input and routed WETH is not assumed to be gas; transaction gas is accounted for separately.
ROUTEInspect the contracts in the first purchaseExact receipt intermediaries
Router: 0x65050A9b7E5075A2bA5cED7b1b64EE66262c40Dc
Wrapped ETH: 0x0Bd7D308f8E1639FAb988df18A8011f41EAcAD73
USDG: 0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168
AMZN: 0x12f190a9F9d7D37a250758b26824B97CE941bF54
WETH/USDG pool: 0x52e65B17fB6E5BA00Ed806f37Afcd2DaA50271Ca
USDG/AMZN pool: 0x2F4579Ca81717d3D61BF8b6f06571877Bbe54A07
These pools describe the first creator purchase. Other launch transactions can use different pools; the report does not assume a universal route. E04
The five observed external ETH credits before launch
A’s earliest observed native funding on Robinhood is B’s payment of 0.598400569755541058 ETH on 27 August at 00:42:13 UTC. The complete non-capped external export contains five positive-value incoming transactions before the WADDLES launch. Together they total 2.390064808179368790 ETH. This is a credit total across several days, not A’s launch-time balance or a WADDLES-only budget. E03E47
| UTC | Visible sender → A | ETH credited | Upstream finding |
|---|---|---|---|
| 27 Aug 00:42:13 | B | 0.598400569755541058 | Direct transfer; first observed Robinhood ETH. E03 |
| 27 Aug 11:23:01 | Relay solver | 0.203428842574496990 | Relay attributes 0.7261 BNB source deposit to C. E19 |
| 28 Aug 18:52:36 | Relay solver | 0.323439262958475215 | Relay attributes 7.713 SOL to 9DpwVes72nJzYmLpC7CBYuiH7trYSHYmk41ATWZX5bVW. Ownership unresolved. E20 |
| 28 Aug 23:47:31 | D | 0.550000000000000000 | Direct transfer from a wallet sharing the earlier Ethereum funding batch. E18 |
| 29 Aug 13:37:34 | Relay solver | 0.714796132890855527 | C deposits 2.5489 BNB. Destination fill arrives 9 minutes 28 seconds before launch. E16E17 |
The two C-origin bridge fills into A sum to 0.918224975465352517 ETH. This cross-chain connection is materially more informative than treating the Relay solver’s hot wallet as the financier. The source request supplies C’s address, source-chain transaction, destination recipient, destination transaction and order identifier. The source BNB receipts were not all independently retrieved from BNB Chain RPC; those bridge edges retain their provider-correlation classification. E16E19E48
Following B’s first funding further back
B first receives 0.009215567466473319 ETH from 0x919968A4238A54B381f022a360260eF5D7E015aC at 17:05:43 UTC on 26 August. One second later, B’s PONCHO sale produces a router return of 0.097627627583075165 ETH. Its subsequent pre-A-funding history includes a larger Relay fill and further trading receipts. B’s payment to A therefore came from an active trading wallet, not an isolated fresh withdrawal address. E49E47
A larger 0.303599405752190025 ETH fill reaches B at 00:37:05 UTC on 27 August. Its exact source request remains unresolved. B and C then submit matching 0.166666666666666666 ETH router transactions in block 47,020,335 at 00:38:09. B’s token record identifies HUGGY. Multiple subsequent matching-time actions precede B’s payment to A. This is another coordination signal, but it does not establish that these wallets created HUGGY or PONCHO. E50E51E52
An unresolved edge stays unresolved.The high-volume 0x9199…15aC export is capped at 10,000 rows and covers 10–11 September, not B’s August funding. Unsupported Relay query parameters returned unfiltered data and were discarded. A newer specific-request endpoint required an API key. None of those gaps is filled with a guessed exchange or owner label.
Upstream capital reconstruction
The clearest upstream chain begins with trading proceeds, crosses Relay, and ends in an equal funding batch to A, B and D. The older exchange trail is a separate historical branch.
25 August, 17:20:47–17:21:24 · Six Solana sales
FjD signs six transactions with Pump AMM Sell instructions involving the same mint, DMUzXdincSucnKTMLtVFBCBcAwuNehoqyrmbYi5hpump. The combined net increase in its SOL balance is 39.672872389 SOL. Its preceding balance is 0.526959075 SOL; after these transactions it holds 40.199831464 SOL. These are net balance increases, not an assertion about cost basis or trading profit. E39
17:23:23 · 21 SOL sent elsewhere
FjD sends 21 SOL to B4cjS9Rh79aaqiSpcRkwWus9eDsHLVc4oWNbbQpmEnnt. After the transaction fee, 19.199751530 SOL remains. The recipient’s ownership was not established. This outgoing payment is included so the cash reconstruction does not silently ignore a large intervening flow. E40
17:23:52 · 19.191 SOL deposited into Relay
The next indexed account transaction deposits 19.191 SOL. The verified raw transaction shows FjD signing and its balance falling to 0.008746530 SOL after the 0.000005 SOL fee. This tightly connects the recent sale proceeds to the bridge deposit without assuming that a July withdrawal survived unchanged for seven weeks. E14
Ethereum destination · 0.755815846807527938 ETH to C
Relay request 0x478f3d342719e11065d2d14b68f8f41d97369438ee57a7d6c03d2741cd08b849 maps the Solana deposit to the Ethereum payment. The destination solver is 0x331D9a049D496385998067ABF6CBb6371C8D2466. Raw Solana data and the Ethereum receipt independently support the two transfer legs; Relay’s index supplies the cross-chain correlation. E13E15
17:25:35 · C seeds A, B and D equally
C’s nonce-0 Ethereum transaction sends 0.370251764935688688 ETH through a public BatchTransfer contract, paying 0.123417254978562896 ETH to each of A, B and D. Decoded input and transfers identify all three outputs. Equal precision, common source and one batch make this a strong direct operational link. It is not a direct Robinhood deposit: these three seed transfers occur on Ethereum. E12
The six Solana receipts
| 25 Aug UTC | Slot | Net SOL increase | Raw receipt / explorer |
|---|---|---|---|
| 17:20:47 | 441,678,305 | 4.700362931 | mKNLTK8Z7qaoe…sol-fjd-before-eth-tx-6.json |
| 17:20:48 | 441,678,307 | 4.116996241 | 3aszrqEQ4t8ov…sol-fjd-before-eth-tx-5.json |
| 17:20:49 | 441,678,309 | 3.681342343 | 2T7GyDLxqWcne…sol-fjd-before-eth-tx-4.json |
| 17:20:49 | 441,678,310 | 3.29162067 | 2YUidTJh1usHX…sol-fjd-before-eth-tx-3.json |
| 17:20:50 | 441,678,312 | 7.317205475 | 5BYPZdhf5RdFW…sol-fjd-before-eth-tx-2.json |
| 17:21:24 | 441,678,407 | 16.565344729 | eXs41EixAYn9k…sol-fjd-before-eth-tx-1.json |
Going further back: the exchange-labelled branch
FjD’s first indexed Solana funding is a 20.473453 SOL payment from DV on 3 July at 17:45:06 UTC. Eighty-six seconds earlier, a Solscan-labelled “Binance 2” wallet sent DV 106.3046625 SOL. Both transfers were checked using raw Solana RPC. E35E36E37
DV’s earliest indexed funding also comes from that labelled address: 0.799 SOL on 31 March, as one output of a larger payment batch. This supports an exchange-adjacent history for the intermediary. It does not identify the withdrawing customer, the account-holder’s jurisdiction or the WADDLES financier. E38
The commingling test matters
Before the July 106.3046625 SOL credit, DV already held 193.076121824 SOL. The incoming exchange payment increased the balance to 299.380784324 SOL. Therefore, the subsequent 20.473453 SOL sent to FjD cannot be uniquely assigned to that one withdrawal by amount and timing alone. E36
DV’s public profile showed extensive fan-out and repeated exchange interactions. Its service-like behaviour is a reason to stop ownership clustering at this boundary. It could be an intermediary handling many customers; the exact business and customer were not established.
What the Binance label does: and does not: meanThe chain verifies payments from a particular Solana public key. “Binance 2” is an explorer’s attribution of that key. Even if the label is correct, a customer withdrawal does not make the exchange the sponsor of everything a recipient later launches. Linking that withdrawal to an individual requires evidence that public chain records do not supply.
Connected wallets
The cluster hypothesis is supported by several different kinds of evidence across different dates. No single shared service, common token holding or similar trade amount is treated as sufficient to prove common control.
Common initial funding
C’s Ethereum batch seeds A, B and D with exactly the same amount in one transaction. A, B and D are recipients of coordinated capital allocation before WADDLES exists. E12
Funding five additional traders immediately before deployment
At 13:46:37 UTC on 29 August, C sends 0.625571459169428060 ETH through 0x3f43479c8536F7eE8180d0f67a050980dC5Bc8C8. Each of five recipients gets exactly 0.125114291833885612 ETH. The decoded batch call and five internal payments were inspected. All five addresses subsequently trade the exact WADDLES contract. E21E25E54E55E56E57
Matching launch execution
A and B submit the same unusually precise 0.200583358784841679 ETH amount in the same first-buy block, 49,201,303. B’s transaction reverts; A’s succeeds. Two seconds later, A, B, C and satellite S1 have independently checked 0.05 ETH purchases in block 49,201,323. A, B and C follow with matching 0.005 ETH attempts at +10 seconds in their exports. Exact timing for the other four satellites’ first receipts is not asserted here without the same individual receipt check. E04E05E22E23E24E25E47
Direct token sharing
D sends B 19,615,648.344521630523000680 WADDLES at 13:47:43 UTC, 41 seconds after launch. The earlier TONY launch includes a direct A-to-C allocation. The later INUNOMICS launch includes allocations to B, C and D. These are direct financial relationships beyond independently using the same trading software. E26E29E31
Later common recipients
On 1 September at 19:53:20 UTC, A, B and C send ETH to the same address, 0x9f46fF59DD7C885f30ab937456623e86323bb0f8, in block 51,983,664. Their amounts are 0.012011064204763738, 0.012031480605911526 and 0.012164743980906443 ETH. E32E33E34
Explorer histories also showed all five satellites sending ETH to D in block 49,503,891. That observation is retained as a UI-transcribed supporting lead: this package does not contain all five full sweep receipts. The independently identified funding batch and token-purchase receipts carry the stronger reproducible evidence.
Strong coordination inference; ownership remains a hypothesis.A shared launch-trading tool could explain similar timestamps and standard purchase sizes. It explains less of the full pattern: equal wallet seeding, direct funding, earlier token transfers, capital recycling and common recipients. The best-supported interpretation is coordinated operation; a single person, a team, or a shared managed trading service cannot be distinguished conclusively.
Wallet dossiers
Letters are analyst labels for readability, not public identities. Selecting a wallet reveals its full address. Services are listed to explain the route and are excluded from the inferred operator group.
ALLView all full wallet and contract addressesStatic reference · available without JavaScript
Previous launches and recurring flows
The Pons creator profile identifies four launches by A. MILO and TONY precede WADDLES and their factory deployment events were checked separately. INUNOMICS follows it. The named assets below are distinct contracts, not ticker-based guesses. E11E27E28E30
27 Aug · 12:23:57 UTC
MILO
A launches, buys at +7 seconds, then sells two halves at +15 and +30 seconds. Early creator trading predates WADDLES.
0x67A2213823F20bFd79a89Da00f3408A7873A8691E27E4728 Aug · 15:50:17 UTC
TONY
Name: “Official Mascot Google”. A buys at +10 seconds and sends 19.9038 million tokens to C at +23 seconds.
0x05f005b9b6793a80147D9c019d133Cde08d35fc8E28E2929 Aug · 13:47:02 UTC
WADDLES
AMZN pair. C funds five traders immediately beforehand. A buys three times and sells its initial position at +13 seconds.
0xbB6Ee7aa6D56266CCEf3B1c0706bCCCE2F9a0CdDE02E21E0729 Aug · 14:58:46 UTC
INUNOMICS
Later launch-and-buy uses 3.0005 ETH. A subsequently distributes tokens to B, C, D and another recipient.
The linked launch identifies the contract and allocations.
E30E31MILO’s creator buy uses 0.1 ETH and returns approximately 45.7487 million tokens. Its two creator sales produce 0.094813869207074016 and 0.085421545630329273 ETH. Those receipts show a prior rapid creator trading sequence. TONY provides the more discriminating cross-wallet link: A sends C 19,903,814.047022781957285795 tokens directly. E47E29
The TONY name shows that a major-company mascot narrative appeared in an earlier launch by the same creator. It is contextual evidence about repeated branding, not proof that Google or Amazon participated. PONCHO, HUGGY, Quantbruhs and Goobs occur in observed trading histories, but token interaction alone is insufficient to identify their creators. They are not added to A’s confirmed launch list.
INUNOMICS takes place 1 hour 11 minutes 44 seconds after WADDLES. Its funding and allocations are useful for clustering, but they must not be retroactively counted as WADDLES launch financing. Similarly, later shared-recipient sweeps establish continued relationships, not a launch-time budget. E30E31
The recurring Solana capital counterparty
Across 301 distinct Relay requests returned for A, B, C and D, FjD is sender on 44 requests into those wallets and recipient on 34 return requests. These 78 requests show repeated two-way capital movement. They span several destination chains and should not be mistaken for 78 WADDLES-specific payments. E48
FjD ↔ A5 / 4
Requests into A / returns to FjD
FjD ↔ B9 / 9
Requests into B / returns to FjD
FjD ↔ C19 / 13
Requests into C / returns to FjD
FjD ↔ D11 / 8
Requests into D / returns to FjD
Counts are deduplicated by request ID, across the provider-returned core-wallet histories from 25 August to 2 September. They do not describe FjD’s full lifetime history. A request returning funds is evidence of a relationship; it is not necessarily repayment, profit distribution or movement between keys owned by one person.
Most frequent bridge routes in the dataset
Request counts, not economic value. BNB, ETH and SOL are not summed as if they were one asset.
A later coordinated return
On 2 September, four HyperEVM-to-Robinhood requests within roughly 23 seconds send funds from A, B, C and D to 0x79fe9839c2ac634529da86369ec7d0d70062fe5d. A supplies 0.326 HYPE, B and D 0.3256 HYPE each, and C 0.114 HYPE. Destination ETH amounts differ with execution. E48
This is useful corroboration of continued shared routing. It does not establish the recipient’s beneficial owner. The bridge explorer below exposes the individual source and destination transactions rather than reducing the relationship to an unlabeled line.
Fees and rewards infrastructure
The launch uses Pons’s factory, a bonding curve, a swap router and an AMZN quote asset. A then changes the creator-fee recipient from its own address to 0xF574664C58F37033A6cfB6B092d7d8972FB9a2d2 at 13:48:31 UTC. The event identifies a contract destination, which Pons’s API describes as an active rewards distributor. E02E04E09E10
At capture, that API reported 444 epochs, 109.450357033126359769 AMZN distributed and 0.333504065855840716 AMZN unallocated. Those are protocol-index snapshot fields. They are not independently reconstructed totals from a complete transfer ledger. The supplied distributor exports have a 10,000-row cap and a gap between their coverage windows. E10E47
The technical presence of a rewards mechanism is consistent with token trading and fee distribution. It does not show Amazon paying dividends, AWS sponsoring the project, or an AMZN issuer owning the launch wallets. A corporate-looking quote asset can appear in an ordinary swap path without any corporate wallet funding the user’s trade.
The fee-recipient change occurs 89 seconds after launch. A later Dexscreener “community takeover” label dated 30 August is an off-chain listing claim. It cannot, by itself, establish who controlled keys before or after that date, whether any sale of the project occurred, or whether the fee-recipient transaction implemented such a takeover. E09E45
Contract analysis boundaryThe launch event, privileged exemption and fee-recipient transition were inspected. This work is not a full bytecode, proxy-admin, upgradeability or distributor-permission audit. Pons snapshot fields such as zero tax or disabled buyback settings must not be promoted into a blanket guarantee about all contract behaviour.
Amazon and AWS: testing the link
The mascot and public website can be real while the asserted relationship to this token remains unproven. Those are separate questions requiring separate evidence.
| Claim or signal | What was checked | Finding |
|---|---|---|
| AWS has a Waddles duck | AWS-community mascot article by Sean Boult. E41 | The article describes the ASCII duck’s origin and adoption. It does not identify the investigated token contract or launch wallets. |
| There is a substantial website / AWS infrastructure | The author’s website-building account and linked public source. E42E43 | The account describes a static React site, initial AWS hosting and a later move to Amplify. This is ordinary website infrastructure, with no verified contract integration in the inspected repository. |
| AMZN is the trading pair | Factory launch event and first swap transfers. E02E04 | Confirmed. The asset is acquired inside the swap route. Pair selection does not identify a corporate financier. |
| Tagged Amazon / AWS accounts imply a relationship | User-supplied promotional text and the named X account. E46 | A mention or tag is not acknowledgement, a signature or a funding transaction. Full X history could not be retrieved here. |
| A public repository hides token infrastructure | 37 source/config/text files at a pinned commit. E43 | No exact target contract, creator address or inspected web3 integration terms found. This is a bounded negative finding, not proof about private or future code. |
The repository inspection is reproducible at commit ad6228608caab99e54c2dd2effe972c06691d579 of sboult/waddles.website. Searches included the exact WADDLES contract, A’s address, AMZN, wallet, blockchain, ethers, viem, wagmi, x402 and Strands. Generic “token” occurrences concerned development text or a dependency; “pons” substring hits were unrelated. A file-hash and search-result manifest is retained in the evidence bundle; source files can be retrieved from the pinned public repository. E43
The website author is identified as an author of a public website and articles only. Nothing in the retrieved on-chain trail ties that person to A, C or FjD. Naming the author as the token deployer would exceed the evidence. Likewise, a hosting provider is not authenticated as the owner of a customer’s blockchain wallet by serving a website.
The user-provided social account was investigated as a lead, but direct X retrieval returned HTTP 403. No complete account-ownership history, deleted-post archive or authenticated corporate endorsement was obtained. The supplied promotional language therefore remains a hypothesis, rather than an independent attribution source. E46
Evidence that would materially change this conclusionAn authenticated statement naming this exact contract, a signed message linking a known corporate identity to a launch wallet, or a verified corporate treasury payment with demonstrable purpose would be relevant. The investigated material supplied none of those links. A future or private relationship cannot be excluded by this public snapshot.
Evidence classification
What the records show
- A initiates the exact WADDLES deployment and appears as deployer in the event. E02
- B sends A its first observed Robinhood ETH. C seeds A, B and D equally on Ethereum. E03E12
- C distributes equal ETH amounts to five additional wallets before launch. E21
- A’s first buy routes ETH into AMZN inside the router. Its initial position is sold at +13 seconds. E04E07
- Raw Solana transactions establish sales, the 19.191 SOL deposit and historical DV payments. E14E35E36E39
What best explains it
- A, B, C and D participate in a coordinated operating arrangement, supported by several independent relationships.
- C acts as a funding coordinator, including a separate launch-time batch for five traders.
- FjD is a recurring source and return destination for operating capital. Common beneficial ownership with EVM keys is not established.
- Automation or shared execution tooling is plausible from matching amounts and block timing. The software or operator was not identified.
- Relay’s explicit request records correlate source and destination transactions; they are not the same evidentiary layer as a raw receipt.
What cannot be claimed
- Amazon, AWS, a named employee or the mascot’s author commissioned the token.
- A Binance-labelled withdrawal identifies a particular Binance customer or makes Binance a sponsor.
- Every connected address belongs to one person.
- AMZN use demonstrates access to proprietary Amazon infrastructure or equity cash flows.
- All early buyers were insiders, all group positions were sold, or a complete operation profit has been measured.
Competing explanations assessed
| Explanation | Fit to evidence | Assessment |
|---|---|---|
| A coordinated pseudonymous trading / launch operation | Explains initial seeding, direct finance, synchronized trades, repeated launches and common recipients. | Best supportedAddress-level conclusion, with human ownership unresolved. |
| Several collaborators using shared trading tooling | Compatible with the same evidence; economic coordination does not require one beneficial owner. | Plausible variant |
| Independent buyers coincidentally using Pons and Relay | Explains shared services and some common trade sizes, but poorly explains direct equal funding, token sharing and later common transfers. | Weaker for core cluster |
| Amazon / AWS directly financed or orchestrated the launch | No authenticated wallet link, corporate funding transaction or exact-contract endorsement in retrieved evidence. | Unsupported |
Transaction explorer
Search the selected core transaction ledger by hash, address, title or evidence ID. Attached ETH value is not the same as net cash flow: a failed call returns its value, and sale proceeds may appear only in internal transfers. The receipt remains the authoritative reference for each event.
| UTC / evidence | Event / transaction | Sender → recipient | Attached ETH / status |
|---|
Cross-chain request explorer
The 301-row dataset contains the source chain and transaction, destination chain and transaction, request ID, order ID and the provider’s attributed sender and recipient. Search FJD to inspect the recurring capital relationship, C for the coordinator’s requests, or choose “Before WADDLES launch” to remove later activity. Chain labels are essential: the same EVM address can receive BNB on BNB Chain and ETH on Robinhood in different requests.
| UTC / request | Sender → recipient | Source | Destination |
|---|
Times in this explorer are Relay request creation times, not necessarily source or destination block timestamps. Amounts are provider-recorded. A source and destination pair is correlated through Relay; only selected legs were independently checked against public chain receipts.
Methodology and coverage
This is a public-source, point-in-time investigation, compiled on 11 September 2026. It begins with the exact contract and follows transaction senders, event parameters, token transfers, internal native-value calls, source-side bridge participants and recurring counterparties. It does not infer the person behind an address from a social-media name or an explorer’s nearest label.
Eleven existing local Blockscout CSV exports were preserved unchanged, contributing 25,369 raw rows. These are overlapping event and transaction datasets, not 25,369 unique transactions. A, B and C’s external histories contain 1,961 distinct transaction hashes after deduplication. Key receipts and launch events were inspected in the public explorer; the archived CSVs and analyst UI observations are labelled according to their actual provenance. E47
Relay queries for A, B, C and D were paginated to their returned end: 44, 57, 158 and 69 rows respectively, with 27 overlapping requests removed. The result is 301 distinct requests. This is completeness relative to the queried provider endpoint, not proof that the endpoint indexes every historical bridge transaction. Unsupported-filter responses were excluded from attribution. E48
On Solana, 34 retained raw transaction responses preserve key source transactions, balance arrays, instructions, timestamps and slots. Six pages of FjD signatures cover 6,000 returned entries; that listing is not 6,000 fully decoded transactions. Selected transactions around the Ethereum seed and July funding were decoded in detail. EVM access relied chiefly on explorer pages and exports where direct RPC/API retrieval was unavailable.
Export coverage, measured from the rows
The dates embedded in some original filenames are malformed. The table uses actual timestamps inside the records. The column named “UnixTimestamp” contains formatted UTC text. A non-capped file can still reflect indexer omissions; absence claims are restricted to the retrieved history.
| Wallet / dataset | Rows | First row UTC | Last row UTC | Limitation |
|---|---|---|---|---|
| A · Launch operatorInternal calls | 151 | 2026-08-27 01:03:54 | 2026-09-01 19:52:25 | No row cap reached |
| B · First ETH funderInternal calls | 137 | 2026-08-26 17:05:44 | 2026-09-01 19:52:25 | No row cap reached |
| A · Launch operatorToken transfers | 530 | 2026-08-25 16:16:12 | 2026-09-02 09:57:08 | No row cap reached |
| REWARDS · Rewards distributorToken transfers | 10,000 | 2026-08-29 20:03:21 | 2026-09-04 18:11:35 | 10,000-row cap |
| REWARDS · Rewards distributorToken transfers | 1,469 | 2026-09-05 11:24:06 | 2026-09-11 10:19:39 | No row cap reached |
| B · First ETH funderToken transfers | 468 | 2026-08-25 16:06:23 | 2026-09-02 10:41:08 | No row cap reached |
| C · Funding coordinatorExternal transactions | 844 | 2026-08-27 00:37:48 | 2026-09-01 19:53:20 | No row cap reached |
| A · Launch operatorExternal transactions | 616 | 2026-08-27 00:42:13 | 2026-09-01 19:53:20 | No row cap reached |
| 0x919968…E015aCExternal transactions | 10,000 | 2026-09-10 22:29:45 | 2026-09-11 10:22:00 | 10,000-row cap |
| REWARDS · Rewards distributorExternal transactions | 647 | 2026-08-29 20:03:21 | 2026-09-11 10:19:20 | No row cap reached |
| B · First ETH funderExternal transactions | 507 | 2026-08-26 17:05:43 | 2026-09-01 19:53:20 | No row cap reached |
Distribution coverage is materially incomplete.The older distributor token export ends at a 10,000-row cap. The next file starts on 5 September at 11:24:06, while the older file ends on 4 September at 18:11:35. Launch-to-first-export activity is also not established by those files. Summing them would understate full coverage and cannot independently reproduce the Pons cumulative distribution field.
Reproducibility and evidence preservation
- Start at the receipt. Confirm chain 4663, the exact contract, launch transaction, sender and
TokenLaunchedevent. Do not substitute a similarly named token. - Verify each funding edge. For native ETH, inspect external and internal value transfers. For tokens, compare exact contract addresses and base units. For reverted transactions, count gas rather than attached value.
- Separate bridge legs. Check the source deposit and destination fill independently where possible, then inspect the Relay request and order identifiers that correlate them. Distinguish an API attribution from raw chain data.
- Recompute amounts in base units. Creator cash accounting uses integer wei and decimal arithmetic. Token quantities use contract decimals. Display rounding never changes archived precision.
- Test competing cluster explanations. Direct funding and token sharing carry more weight than shared routers. Service and exchange boundaries remain outside the inferred common operation.
- Verify the archive. The evidence bundle includes original exports, selected RPC/API responses, a repository inspection manifest, retrieval records and a SHA-256 manifest. A checksum establishes file integrity from capture onward; it does not authenticate the provider’s interpretation.
What remains unresolved
| Open question | What is missing | Effect on the finding |
|---|---|---|
| Natural person or entity behind A, C and FjD | Authenticated key-to-identity evidence or lawful off-chain account records. | Prevents naming a real-world financier or operator. |
| B’s exact early bridge origin | Matched source request and independently checked source receipt for its 0.303599405752190025 ETH fill. | One funding branch remains open; other direct relationships still stand. |
| All five satellite sweep receipts | Complete receipt captures and exact base-unit amounts for the observed same-block returns to D. | Retained as a supporting explorer observation, not the principal evidence for clustering. |
| Full operation-wide profitability | Complete histories and inventories for D, all satellites, C’s internal/token activity and all relevant chains, plus fee and basis treatment. | Only A’s initial WADDLES trade cash result is quantified. |
| Distributor control and complete payments | Full code/admin review and uncapped, continuous transfer history. | No comprehensive safety or rewards-accounting conclusion. |
| Current social team / takeover ownership | Authenticated account history and evidence connecting it to keys or corporate identities. | Current branding cannot retrospectively identify the August launch operator. |
| Private corporate involvement | Affirmative authenticated documentation or verified treasury/key links. | Unsupported by this investigation; public negative findings do not prove universal absence. |
Evidence register
Every numbered citation opens an entry here. Each entry identifies its evidentiary layer and a direct source link. Public explorers can change or be unavailable; retained captures and original exports are in the evidence bundle. UI observations are analyst transcriptions, not raw RPC receipts.
57 evidence entries
E01Exact token and deployment recordOn-chain
Blockscout contract page. Low-level contract creator is a creation helper; transaction sender and TokenLaunched.deployer identify A.
https://robinhoodchain.blockscout.com/token/0xbB6Ee7aa6D56266CCEf3B1c0706bCCCE2F9a0CdDE02WADDLES launch receiptOn-chain
2026-08-29 13:47:02 UTC; block 49,201,242; creator A; PonsV2LaunchFactory; value 0.0005 ETH. Log 33 binds token, curve, deployer and AMZN. Log 29 mints one billion tokens; log 31 exempts A from snipe tax.
https://robinhoodchain.blockscout.com/tx/0xf227bb992620e48ea737b79586efcd6b3e94c8e6ea7a708e694295eb87b17f91E03Creator first ETH on RobinhoodOn-chain
B sends A 0.598400569755541058 ETH on 2026-08-27 at 00:42:13 UTC; block 47,022,732. Earliest native funding observed in retrieved creator history and checked live.
https://robinhoodchain.blockscout.com/tx/0x402bbf38e05161bb08ad52b82f009c1a2c3a1248d7f1a3755f2ee4987eb359fbE04First creator buy: ETH to AMZN to WADDLESOn-chain
At 13:47:08, A supplies 0.200583358784841679 ETH. The router acquires 1.801223537258714669 AMZN and sends it to the curve; A receives 74,773,770.579440143274737964 WADDLES.
https://robinhoodchain.blockscout.com/tx/0xf36a56ca474ea2cf55f420dc3d84a22c80a5a556d334cc760cc7e57d815fd88eE05Creator second buyOn-chain
At 13:47:10, 0.05 ETH buys 8,775,687.942975294888235557 WADDLES; block 49,201,323.
https://robinhoodchain.blockscout.com/tx/0x220cdd8a725dff2dbd63aa54b018376ce0e70a6de09f236cdd51d42b443b33beE06Creator third buyOn-chain
At 13:47:12, 0.005 ETH buys 832,839.862981708812727857 WADDLES; block 49,201,344.
https://robinhoodchain.blockscout.com/tx/0x9490152b92fda427b4adf981de0482f1084fc79142f07aee57a7ab350466ce5dE07Creator sells its initial positionOn-chain
At 13:47:15, A sells 84,382,298.385397146975701378 WADDLES. Internal transfer from router pays A 0.415698539319334160 ETH. This is the creator-wallet trade, not total group profit.
https://robinhoodchain.blockscout.com/tx/0x9ca41778afe95186b454a115f209748e3abedc5680bbf81f624887931f406863E08Approval for the creator saleOn-chain
Approval in the same block/time as the sale. Included in the six-transaction gas calculation, with the launch and three buys.
https://robinhoodchain.blockscout.com/tx/0xc1f75a6b2d670c08de9d851e5b6b821541c4a51ec44f0e678e9acd44e23e50c9E09Creator-fee recipient changedOn-chain
At 13:48:31, A calls transferCreatorFeeRecipient. Factory/curve logs change the recipient from A to 0xF574664C58F37033A6cfB6B092d7d8972FB9a2d2. This does not establish a human community takeover.
https://robinhoodchain.blockscout.com/tx/0x8077447636349a635d2645576d2c87de279dd7c34a68ed56b8df8e565b481e4fE10Pons rewards distributor snapshotProtocol index
Pons reports state active, 444 epochs, 109.450357033126359769 AMZN distributed and 0.333504065855840716 AMZN unallocated at capture. Provider snapshot, not an independently summed complete distribution ledger.
https://www.ponsfamily.com/api/pons-v2-market/0xbB6Ee7aa6D56266CCEf3B1c0706bCCCE2F9a0CdD/distributorRetained files: pons-distributor.json
E11Creator’s four Pons launchesProtocol index
Profile lists MILO, TONY, WADDLES and INUNOMICS with isDeployer true. Earlier MILO and TONY factory events were separately checked.
https://www.ponsfamily.com/api/pons-profile?address=0x81D7a91860a70B312E68c075C896aA06281cCC63Retained files: pons-profile.json
E12Equal Ethereum funding batchOn-chain
2026-08-25 17:25:35 UTC; block 25,833,689. C calls BatchTransfer with 0.370251764935688688 ETH: exactly 0.123417254978562896 ETH each to A, B and D. C transaction nonce 0. The batch contract is an intermediary.
https://etherscan.io/tx/0xf57a6fed8330566a8c553fde464a6116a1c63b01b59e0e49683523f7214a380eRetained files: eth-f133.txt
E13C first Ethereum fundingOn-chain
Relay solver 0x331D9a049D496385998067ABF6CBb6371C8D2466 pays C 0.755815846807527938 ETH. Relay request links the payment to FjD’s 19.191 SOL deposit.
https://etherscan.io/tx/0x56542f2991fa79474f3f020348e4d8021d0c9db8f294370927e5fd1a9f4035a4Retained files: eth-c-first-tx.txt
E14Verified Solana deposit behind C Ethereum fundingOn-chain
2026-08-25 17:23:52 UTC; FjD signs a 19.191 SOL deposit. Raw Solana RPC transaction confirms sender, instruction and balance change. FjD balance falls from 19.199751530 to 0.008746530 SOL.
https://solscan.io/tx/5RYCHsytTu8SU63pTyKcvKM4ksAZuXm3mNFXrQdoap2S6ZBfRH67AxDA4b8uVTaHW77SH9moEdyABJkZrjw1JSzxRetained files: sol-fjd-eth-bridge.json
E15Relay bridge correlation: FjD → C on EthereumBridge record
Request 0x478f3d342719e11065d2d14b68f8f41d97369438ee57a7d6c03d2741cd08b849 links source E14 to destination E13. Source and destination transactions are distinct on-chain facts; their cross-chain relationship uses Relay’s index.
https://api.relay.link/requests/v2?user=0x3C95d9e0F76e08cD9a6cb5c7dB508c4F4072B9F3&limit=50Retained files: relay-3c95-p4.txt
E16C funds A from BNB before launchBridge record
Relay request 0x1788010652bf76a17f44f5b8e89087b0b2e634c2fee3b93b1b6d72e75df1c89f: C deposits 2.5489 BNB; A receives 0.714796132890855527 ETH at 13:37:34, 568 seconds before launch. Source tx 0x6a270b6c8ab87c897d9322feb2b726ed1954b42209e511a9b78a4e2139a9722e.
https://api.relay.link/requests/v2?user=0x81D7a91860a70B312E68c075C896aA06281cCC63&limit=50Retained files: relay-requests.txt
E17Pre-launch ETH bridge fill into AOn-chain
0.714796132890855527 ETH from Relay solver into A at 2026-08-29 13:37:34 UTC. Destination transfer independently appears in the creator export.
https://robinhoodchain.blockscout.com/tx/0x41fc006a804892a416a29ce585d8fe31238726fcf730fb8893f8de38909e7550E18D supplies 0.55 ETH to creatorOn-chain
D → A, 0.55 ETH, 2026-08-28 23:47:31 UTC.
https://robinhoodchain.blockscout.com/tx/0x57e6b191ad9808416bdce12c03452fc8506ec6be4c785217b9f67ffb84795bb3E19Earlier C-origin bridge fill into AOn-chain
2026-08-27 11:23:01 UTC: A receives 0.203428842574496990 ETH. Relay request 0x2d0cea059325572cd15e8589780aa5c0fa02a165d8b135ecc51cfd04da426716 identifies C’s 0.7261 BNB deposit on BNB Chain.
https://robinhoodchain.blockscout.com/tx/0x38b8233767b622b7f15bb4c0b7e4e76329c558e1b051e69d81458af7085d80abE20Other pre-launch Solana-origin fillOn-chain
2026-08-28 18:52:36 UTC: A receives 0.323439262958475215 ETH. Relay attributes the source 7.713 SOL to 9DpwVes72nJzYmLpC7CBYuiH7trYSHYmk41ATWZX5bVW. No real-world identity attached.
https://robinhoodchain.blockscout.com/tx/0xd33229d546a0afe2f6841b1cfef121a42ae6826ebb22b4780af7de6cc4f1377bE21Five equal funding payments 25 seconds before launchOn-chain
2026-08-29 13:46:37 UTC; block 49,200,998. C sends 0.625571459169428060 ETH through BatchTransfer 0x3f43479c8536F7eE8180d0f67a050980dC5Bc8C8. Five recipients each receive exactly 0.125114291833885612 ETH; decoded input and internal calls checked live.
https://robinhoodchain.blockscout.com/tx/0xe7bea77b6cd763fc1615d66c43198886244a3f695d47dcb79b06056552269f26E22B matching first buy attempt revertsOn-chain
Same block as A’s first buy, same attached amount 0.200583358784841679 ETH. Status failed: do not count the attached value as a successful spend or acquired tokens. Only gas was spent.
https://robinhoodchain.blockscout.com/tx/0x08b5226074e23cf9186eae8abed4926634bc1ab399895296843d2050a5922bdaE23B buys alongside creatorOn-chain
Block 49,201,323 / 13:47:10: 0.05 ETH; B receives 9,825,618.666452793456997277 WADDLES.
https://robinhoodchain.blockscout.com/tx/0xe1bd7bef6ce5f5d61408b9c2922dd2d51f15fb614f9449be65e5d27934ef6423E24C buys in the same waveOn-chain
Block 49,201,323 / 13:47:10: 0.05 ETH; C receives 11,075,900.242998797817359790 WADDLES. Checked live.
https://robinhoodchain.blockscout.com/tx/0x4f8e1acf5cb870fe190d904dede8d9402473c511ed02f1a6b0dfdd0bc092d051E25Satellite 1 buys in the same waveOn-chain
Block 49,201,323 / 13:47:10: 0.05 ETH; 10,217,761.551806799934471857 WADDLES. Checked live.
https://robinhoodchain.blockscout.com/tx/0x4ee1d431a4c845ad2de1846b59ca03d029b6faa872f4eb4533718ba49de1cb94E26D transfers WADDLES to BOn-chain
2026-08-29 13:47:43 UTC: D sends B 19,615,648.344521630523000680 WADDLES. Cross-wallet token movement directly connects D to launch trading.
https://robinhoodchain.blockscout.com/tx/0x4b4c1e39e67308102e3f328ad4555a5cc0481326c12433fb09f4f714459f846fE27MILO launch by the same creatorOn-chain
2026-08-27 12:23:57 UTC. TokenLaunched event token 0x67A2213823F20bFd79a89Da00f3408A7873A8691, deployer A; one billion tokens minted. Pair token 0x4a0E65A3EcceC6dBe60AE065F2e7bb85Fae35eEa.
https://robinhoodchain.blockscout.com/tx/0x79a42f8a2560506baf72910b225ef8d4db9e6a97a001252c1c0d2c6a7d200714E28TONY launch by the same creatorOn-chain
2026-08-28 15:50:17 UTC. TokenLaunched event token 0x05f005b9b6793a80147D9c019d133Cde08d35fc8, deployer A. Token name is Official Mascot Google; that name is not Google endorsement.
https://robinhoodchain.blockscout.com/tx/0xc8b7069a8abd8864a4a4f725756c365493a9fc305d9d551a12c88772ecf12a4bE29Creator transfers TONY to COn-chain
2026-08-28 15:50:40 UTC: 19,903,814.047022781957285795 TONY from A to C. Direct token sharing links the financial coordinator to an earlier creator launch.
https://robinhoodchain.blockscout.com/tx/0x122184a464959a03a33c239b84676d225f72cae999e21327fc297bc53bd7178cE30Later INUNOMICS launchOn-chain
2026-08-29 14:58:46 UTC: launchAndBuy with 3.0005 ETH; A receives 629,139,072.847682119205298013 INUNOMICS. Creator profile corroborates ownership. This launch occurred after WADDLES.
https://robinhoodchain.blockscout.com/tx/0x2d89f5ee5e19907b6c03fbf6428db12d727bf3c95838f2a69228e148ad96f470E31INUNOMICS distributed to related walletsOn-chain
2026-08-29 14:59:37 UTC: A sends INUNOMICS to D, C, B and 0x454cca50cb699ae485f62a878ec13f5e56457a9e. Supports recurring multi-wallet activity; not proof of identical beneficial owners.
https://robinhoodchain.blockscout.com/tx/0x6b80d0a852f96ff883738c9638aab5d5ac7948ea31448e2b6c782d03cf64b812E32A September 1 common sweepOn-chain
A sends 0.012011064204763738 ETH to 0x9f46…b0f8 in block 51,983,664 at 19:53:20 UTC.
https://robinhoodchain.blockscout.com/tx/0x2886c058f6c6498ab601b0228f2c5bec97e2e6d98bb672127d8cc61dbd52ee37E33B September 1 common sweepOn-chain
B sends 0.012031480605911526 ETH to the same recipient in the same block.
https://robinhoodchain.blockscout.com/tx/0x28252e455401dd82181d30dad3c2be12033df7606e7d7f068fc3786f994ca53eE34C September 1 common sweepOn-chain
C sends 0.012164743980906443 ETH to the same recipient in the same block.
https://robinhoodchain.blockscout.com/tx/0x0eb7a406a6fbf2cf96f7bf847626d0c363598807cbe8beead6c4bd73d15a3bf4E35FjD first Solana fundingOn-chain
2026-07-03 17:45:06 UTC; slot 430,567,970: DV sends 20.473453 SOL to FjD. Verified in raw RPC and Solscan. Historical wallet ancestry, not proof these same funds survived to August.
https://solscan.io/tx/WMdyqziymMDe3cfu1Gqer2PJjcV2G4PyVoJG2FQoF5dqdU3MGXaWmFCaQ7xG1YXywtkVMgNbZ8bpy62oXYh5rzxRetained files: sol-fjd-first-tx.json
E36Binance-labelled wallet replenishes DVOn-chain
2026-07-03 17:43:40 UTC: 5tzF…uAi9 sends DV 106.3046625 SOL, 86 seconds before E35. DV already held 193.076121824 SOL, so exact coin provenance cannot be assigned to this deposit alone.
https://solscan.io/tx/Gez7VbfT3zJDGsG8yLKyRkY2nPkBWTZduqJCaxXS2DtdnSQmPxoGfot4BvrUyT7gJNyNZb3jQ9NsULR63jihUYcE37Binance 2 public labelExplorer label
Solscan labels 5tzF…uAi9 Binance 2. The label is third-party attribution; the transfers are verifiable independently. It does not identify any customer.
https://solscan.io/account/5tzFkiKscXHK5ZXCGbXZxdw7gTjjD1mBwuoFbhUvuAi9E38DV’s earliest indexed exchange paymentOn-chain
2026-03-31 15:51:23 UTC: Binance-labelled 5tzF…uAi9 sends 0.799 SOL to DV as one output of a larger payment batch. Verified by raw RPC.
https://solscan.io/tx/4EpTfpGNhj9FVbVB2DiFn67Vuhto5jjS2iXffALdQ3D5bd49xTfktDkwUWuFsK8kBEji3uLihpn8tVms51Xw5cFuRetained files: sol-dv-first-tx.json
E39Solana trading proceeds before bridgeOn-chain
Final of six verified Sell transactions in the Pump AMM program between 17:20:47 and 17:21:24 on August 25. All sell mint DMUzXdincSucnKTMLtVFBCBcAwuNehoqyrmbYi5hpump. Combined net SOL balance increase: 39.672872389. Each raw transaction is retained.
https://solscan.io/tx/eXs41EixAYn9k2ew9WXks1duoCe4J5EpZsyLXif55S5r4dHTzfBYWqRSmhdVMnaRTNCjjkqjUZVdgi82GpZx7EDRetained files: sol-fjd-before-eth-tx-1.json, sol-fjd-before-eth-tx-2.json, sol-fjd-before-eth-tx-3.json, sol-fjd-before-eth-tx-4.json, sol-fjd-before-eth-tx-5.json, sol-fjd-before-eth-tx-6.json
E40FjD sends 21 SOL before bridgeOn-chain
17:23:23 UTC: FjD sends 21 SOL to B4cjS9Rh79aaqiSpcRkwWus9eDsHLVc4oWNbbQpmEnnt. After the fee, 19.199751530 SOL remains; the next indexed account transaction deposits 19.191 SOL into Relay.
https://solscan.io/tx/3KdtgRyfgFVMDS4D4SEby2pDUQ8newvYtaNxWqR21WTAc8kevfaoPQWWYZ3ksACJWkpdFRRMktUzs1nZmNpGvN6VRetained files: sol-fjd-before-eth-tx-0.json
E41Mascot provenance articleOff-chain context
Sean Boult’s AWS-community article describes Waddles as an ASCII duck mascot and dates its first appearance to March 12. Mascot provenance is not token-contract endorsement.
https://dev.to/aws/aws-waddles-what-the-duck-23nnE42The actual website-building accountOff-chain context
August 4 article describes using Codex to build a static React site, initial AWS hosting and later Amplify migration. It describes a website-building workflow; it does not identify this token or its launch wallets.
https://dev.to/aws/i-vibe-coded-a-website-at-35000-feet-2nfmE43Pinned public mascot website sourceRepository inspection
37 text/source/config files retrieved from commit ad6228608caab99e54c2dd2effe972c06691d579. No exact target contract, creator address, AMZN, wallet, blockchain, ethers, viem, wagmi, x402 or Strands matches. Generic token and substring pons hits were checked and were unrelated. Negative finding is limited to this commit and repository.
https://github.com/sboult/waddles.website/tree/ad6228608caab99e54c2dd2effe972c06691d579Retained files: github-tree.txt
E44Robinhood network identityOfficial documentation
Mainnet chain ID 4663; gas asset ETH; Arbitrum Layer 2 on Ethereum. Mainnet and testnet are explicitly distinct.
https://docs.robinhood.com/chain/connecting/E45Community takeover labelOff-chain context
Dexscreener displays a community takeover claim dated August 30. A listing label does not authenticate changes in wallet ownership or establish current team identity.
https://dexscreener.com/robinhood/0xbB6Ee7aa6D56266CCEf3B1c0706bCCCE2F9a0CdDE46User-provided social accountUnverified claim
Direct X retrieval returned 403 in this research environment. The supplied promotional text is treated as a hypothesis, not authenticated contract attribution. A complete deleted-post or account-ownership history was not obtained.
https://x.com/WaddlesAMZNE47Raw creator and peer CSV exportsLocal export
Existing local Blockscout CSVs were copied without modification. A: 616 external transactions, 151 internal calls, 530 token transfers. B: 507, 137, 468. C: 844 external transactions. Important transactions were checked against live explorer pages. CSV timestamp fields contain formatted UTC timestamps despite their UnixTimestamp header.
evidence-bundle.zipE48Core-wallet Relay historyBridge record
301 distinct requests after deduplication across fully paginated wallet queries for A, B, C and D. These are the provider’s returned wallet matches, not all chain activity. Four source histories return 44, 57, 158 and 69 rows respectively; 27 duplicated requests overlap. Unfiltered results from unsupported query parameters were excluded.
https://api.relay.link/requests/v2?user=0x3C95d9e0F76e08cD9a6cb5c7dB508c4F4072B9F3&limit=50Retained files: relay-3c95.txt, relay-3c95-p2.txt, relay-3c95-p3.txt, relay-3c95-p4.txt
E49B first observed gas fundingOn-chain
2026-08-26 17:05:43: 0x919968A4238A54B381f022a360260eF5D7E015aC sends B 0.009215567466473319 ETH. High-volume counterparty; exact initiating bridge request was not recovered. Do not attribute its entire clientele to the launch group.
https://robinhoodchain.blockscout.com/tx/0x1e897fba93dbaf3a9643e98278f496d6893e36cfce81dce20e4da0153dc2f9f6E50B’s larger early bridge fill: unresolved sourceOn-chain
2026-08-27 00:37:05: Relay solver sends B 0.303599405752190025 ETH. No exact source-side match recovered in the paginated wallet results. V3 lookup required an API key. This edge remains unresolved.
https://robinhoodchain.blockscout.com/tx/0xfae3e3bfc99c0a20873ee927ebaf0ebc989231edddf098f59b958050ce3440c9E51Synchronized earlier HUGGY trading by BOn-chain
2026-08-27 00:38:09, block 47,020,335: B submits 0.166666666666666666 ETH to the router; C submits the identical amount in the same block. Token transfer records identify HUGGY for B. Shared trading does not establish who deployed HUGGY.
https://robinhoodchain.blockscout.com/tx/0x52f8443c50414701899303515b727c6a9129c4635967d4c544234127aa79d07fE52Synchronized earlier trading by COn-chain
Same block, amount and router as E51. Multiple subsequent matching-time actions reinforce an operational connection.
https://robinhoodchain.blockscout.com/tx/0xd8803be5f5005dbe45df3d04935a330fa4fed3409d39b58bc622dd6ff6ff5265E53Launch purchase blockOn-chain
Block 49,201,323 is 2026-08-29 13:47:10 UTC. Individually inspected receipts for A, B, C and S1 confirm matching 0.05 ETH purchases here. This is not an exhaustive analysis of every transaction in the block.
https://robinhoodchain.blockscout.com/block/49201323E54Satellite 2 WADDLES purchaseOn-chain
Earliest WADDLES transfer in the fully loaded satellite history. Exact token contract checked; transaction is linked for independent receipt verification.
https://robinhoodchain.blockscout.com/tx/0x514b7d010d9db24ea38c2efaa1267e9601633a5ca3457fb1689a423a914b1faaE55Satellite 3 WADDLES purchaseOn-chain
Earliest WADDLES transfer in the fully loaded satellite history. Exact token contract checked; transaction is linked for independent receipt verification.
https://robinhoodchain.blockscout.com/tx/0x8284826bfd59ec460d8f047883092b83d7f65843a9b5c51ca4460d61398de9fbE56Satellite 4 WADDLES purchaseOn-chain
Earliest WADDLES transfer in the fully loaded satellite history. Exact token contract checked; transaction is linked for independent receipt verification.
https://robinhoodchain.blockscout.com/tx/0x849879ddca2b82d1bf7d0a1479d8f6d7a5a22bdab87e3593693fd493e5155966E57Satellite 5 WADDLES purchaseOn-chain
Earliest WADDLES transfer in the fully loaded satellite history. Exact token contract checked; transaction is linked for independent receipt verification.
https://robinhoodchain.blockscout.com/tx/0x779e1c1767880534a911cc2f1918282dd9ea3e90497ecbb90da6c29c7b818e3dInspect the complete investigation
A deployed WADDLES. C organised visible funding. B and D participated in the financial network. FjD repeatedly supplied and received cross-chain capital. Those are the defensible findings; the real-world owners remain unknown.
This report is a static publication with same-origin structured data and client-side interaction code. The interface uses a local system sans-serif stack and remains fully readable offline. The report uses no analytics and requests no wallet connection. The downloadable publication package preserves the report records, structured evidence and source archive used for this investigation.
Research cut-off: 11 September 2026. Record dates and coverage vary by source. Static snapshot; not a live monitoring service. The archive README explains inclusions, exclusions and independent verification.