31C4 registers richiereitz.eth, sets the reverse record and later funds f1a.
The case moves through six dated stages.
Read the evidence in order. Each stage adds a fact that the next stage must explain.
f1a and aa33 exchange value 34 times across four chains.
F718 uses Robinhood’s canonical inbox, then funds aa33 at block 1,009.
aa33 tests ERC-8056, then its funding cluster reaches production Stock Token role wallets.
aa33 launches with no creator buy; Noxa later disables launches and sets its revenue shares to zero.
Named signer, official integration, deployed utility or a verified revenue route would move the thesis.
Two evidence trails converge on aa33.
Every node separates what is observed, what it supports and where the claim must stop.
Human-facing trail
Public profile→richiereitz.eth→f1a↔aa33
Protocol trail
F718 L1→Official Inbox→a75a alias→F718 L2→aa33
aa33 outputs and open questions
Demo addressProduction rolesERC-8056WALLETMandate + utility
Observed
aa33 is the convergence point
Open primary source ↗
The same address receives pre-public Robinhood Chain funding, exchanges value with f1a across four chains, funds the future demo address, tests ERC-8056 and later launches WALLET.
Arbitrum’s alias rule resolves a75a to F718.
Adding Arbitrum’s published offset to F718 returns a75a exactly.
Address aliasing explains the a75a match.
Community screenshots correctly captured a75a in early Robinhood Chain blocks. The original interpretation went too far by treating it as an independent validator or sequencer address.
ObservedF718 called Robinhood’s official Delayed Inbox on Ethereum. The corresponding L2 deposit messages appear from a75a.
ExplainedOffchain Labs’ code adds a fixed offset to an L1 sender. Applying it to F718 returns a75a exactly.
BoundaryThe RPC miner field does not identify a75a as a BoLD validator. Official docs name Offchain Labs and Alchemy as validators.
L1 sender
0xF718d37dBC25799f7cFf04B5AacdA94e87619649Add offset
0x1111000000000000000000000000000000001111Modulo
2^160Calculated L2 alias0x0829d37dbc25799f7cff04b5aacda94e8761a75a
Protocol significance: applying Arbitrum’s published offset to F718 returns a75a exactly, proving that F718 used the canonical L1-to-L2 path. The permissionless bridge does not identify the operator.
ENS transactions link richiereitz.eth to 31C4.
31C4 registers richiereitz.eth
The decoded ENS call sets 31C4 as owner and address. A second transaction sets the reverse name to richiereitz.eth.
registerWithConfig → owner 0x31C4…5091 → setName("richiereitz.eth")31C4 directly funds f1a
A normal Ethereum transfer sends 0.002733465268590297 ETH from the ENS-linked address to f1a. No router or bridge sits between them.
0xe67ade55f0460d28eb6216df1410647dfad382e56ff912ba17f4c60101ad598af1a begins a sustained relationship with aa33
The pair exchange ETH, USDC and USDG across Ethereum, Arbitrum, Base and Robinhood Chain. The activity spans eighteen months and runs in both directions.
34 indexed direct value-transfer events · 7 f1a→aa33 · 27 aa33→f1aaa33 deliberately targets f1a through smart-account execution
Four reverse-direction native sends decode as EntryPoint handleOps calls. Each user operation encodes f1a as the recipient and a specific value.
Ethereum × 2 · Arbitrum × 1 · Robinhood Chain × 1The audit found 34 direct value events between f1a and aa33.
The table counts direct native or token value movements between the two addresses. Contract interactions without transferred value are excluded.
| UTC | Chain | Direction | Amount | Route | Source |
|---|
Four smart-account calls encode f1a as the destination.
A refund interpretation fails when the user operation itself encodes f1a as destination and specifies the exact value. The call is deliberate at the execution layer.
Decoded across four transactions: EntryPoint.handleOps → sender aa33 → execute(destination f1a, native value, empty calldata)
This proves intentional value transfer between the accounts. It does not prove shared ownership or the identity of the signer.
F718 was using the canonical Robinhood bridge before the public opening.
Eight direct depositEth calls reached the exact Delayed Inbox listed in Robinhood’s official documentation. Every call predates public mainnet.
0x927fdea5…2fc3f0x5ddfeade…2ea7a0xc23193d3…0368b0x2ce659e9…1fd650xe004c423…395480xc4a64af2…b54320x41e69871…a07ae0xb4c0ff94…0b5e7block 1009 · 0.15 ETH · 0x16dfbec9…3c166Correct context: Robinhood’s terms say Offchain Labs operates the sequencer on Robinhood’s behalf, and the governance page names Offchain Labs and Alchemy as the two validators. Neither statement attributes F718 to those companies. The hard finding is narrower: F718 repeatedly used the canonical Robinhood Chain inbox before public mainnet, received the bridged funds on L2, and directly funded aa33.
aa33 shows five dated proximity signals before launching WALLET.
Five dated events form the sequence.
The record covers demo-wallet funding, ERC-8056 testing, pre-public chain funding, multichain transfers with f1a and the WALLET launch.
12 Jun
2025
2025
Future demo address funded
aa33 sends Arbitrum gas to the address later used in the OpenAI Stock Token demo, 18 days before Vlad Tenev’s public post.
09 Apr
2026
2026
ERC-8056 contract deployed
aa33 deploys verified TestERC8056Token on Base, mints, changes the multiplier and corrects it to 2e18.
15 May
2026
2026
Pre-public chain funding received
F718 sends aa33 0.15 ETH at Robinhood Chain block 1,009 after repeated canonical bridge deposits.
Jun 2026
f1a relationship continues
Round stablecoin probes and decoded smart-account sends run across multiple chains, including Robinhood Chain.
10 Jul
2026
2026
aa33 launches WALLET
The Noxa factory call records zero initial creator buy and no creator allocation. WALLET is the deployer’s only identified token launch in the reviewed history.
aa33 and F718 sit upstream of Robinhood’s production Stock Token operators.
The verified AccessControlsRegistry records one grantor assigning the observed production roles. F718 funded fb956, which later funded every role wallet and the grantor. aa33 opened 624c’s Robinhood Chain history; F718 later supplied 624c before it funded 12 of the 13 role wallets and the grantor.
Complete role-set provision
F718 funded fb956 with 0.1 ETH. fb956 funded the grantor, then sent 0.0025 ETH to all 13 role wallets and the grantor.
F71815 May · 0.1 ETH
→
fb956Provisioning wallet
→
0743 grantor19 May · 0.01 ETH
+
13 / 13 roles27 May funding burst
Bootstrap, top-up, activation
aa33 supplied 624c’s first two observed transactions. F718 later sent 4.0001 ETH; 22 minutes 55 seconds after the 3 ETH top-up, 624c began funding role wallets.
aa33 + F718Bootstrap + top-ups
→
624cOperational wallet
→
0743 grantor22 Jun · 0.05 ETH
+
12 / 13 roles22 to 24 Jun
Permission granted, then used
Select a rolePermissions became operations.
Counts are from the supplied 18 August raw snapshot. Sample calls and current address counters were checked independently.
26.33×Observed funding-pattern rate ratio
4 / 6Operational or privileged2 / 79Other F718-funded EOAs
Within F718’s complete 85-address EOA recipient cohort, a tiny transfer of 0.0001 ETH or less followed by larger funding within seven days appeared at 26.33 times the observed rate in the independently classified operational or privileged cohort. Fisher exact p = 0.000107.
Attribution boundary
This is a descriptive within-sender association, not a random control experiment. The six-address operational cohort is small, and the confidence interval is wide. The result strengthens the selective-provisioning evidence; it does not identify signers, establish common ownership or prove Robinhood authorized WALLET.
The launch and market structure support the thesis. They do not identify the actor.
These findings describe WALLET’s launch and liquidity structure. They do not identify aa33’s operator.
Clean launch
The decoded factory call records a fixed one-billion supply, initialBuyAmount = 0 and no creator allocation. This is structurally cleaner than a launch with a built-in deployer allotment.
Bullish structure · not identityBase LP custody
Uniswap V3 position #41841 remains owned by the verified LaunchLocker at the 19 August snapshot. The verified implementation exposes fee collection and contains no principal-withdrawal function. This report therefore describes the position as locked under that implementation.
Bullish protection · bounded wordingAutomated V3 operatorSophisticated market evidence · not Robinhood evidence
0xbB0033…37Fd added WETH through a progressive sequence from 0.002145 to 0.1373. The regularity is consistent with automated concentrated-liquidity management.
No current WALLET utility
Robinhood Chain uses ETH for gas. WALLET is a separate ERC-20 and is absent from the current official canonical token registry. Rewards, staking, fee incentives, governance, access or wallet functionality remain possible only as future scenarios.
Possible future utility; no implementation found0.80% fee mechanism
An analysed Robinhood wallet path collected exactly 0.80% in a transaction two days before WALLET launched. No distributor, staking contract, buyback route, treasury rule or official promise connects that revenue to WALLET today.
Real mechanism · no WALLET accrual proofEvidence
Interpretation
Does not prove
31C4 registers richiereitz.eth and funds f1a
A named Robinhood-Wallet-adjacent trail reaches aa33 through a sustained counterparty.
That the named individual controlled f1a, aa33 or WALLET.
34 direct f1a ↔ aa33 value events
The relationship is operational and persistent, not a one-off accidental touch.
Shared ownership, employment or a corporate instruction.
F718 makes 8 canonical deposits and funds aa33
aa33 sits one hop from a repeat pre-public Robinhood Chain operator.
That F718 is Robinhood, OCL, Alchemy or a validator.
F718 funds both provisioning branches; aa33 opens 624c’s history
The WALLET funding cluster reaches wallets that supplied the production Stock Token role set.
Shared signer control, employment or a Robinhood instruction to launch WALLET.
Tiny-test funding appears in 4/6 operational recipients versus 2/79 other F718-funded EOAs
The independently reproduced 26.33× rate ratio supports selective operational provisioning inside F718’s recipient cohort.
Causation, common ownership, signer identity or corporate authorization.
aa33 funds demo address and tests ERC-8056
The deployer shows product-specific stock-token proximity before WALLET.
Corporate authorization or planned WALLET utility.
Clean launch, locked base LP, automated liquidity
The market was formed without a creator allotment and has sophisticated support.
Robinhood identity, guaranteed liquidity or future price performance.
WALLET entered public trading without creator inventory. Noxa then wound down the launch system.
The sequence is consistent with a clean public hand-off: launch the asset, leave the base liquidity in the locker, close new launches and remove protocol revenue. The chain does not establish whether that outcome was planned for WALLET.
aa33 launches WALLET
The decoded factory call records a one-billion supply, zero initial creator buy and no creator allocation.
Noxa disables new launches
The public explanation cited bot spam and infrastructure pressure. The admin transaction stopped new factory launches.
Protocol revenue falls to zero
Noxa removed the token-treasury share, reduced the protocol share and then set the remaining protocol share to zero.
The base LP remains in LaunchLocker
Position #41841 remains held by the verified locker. The reviewed implementation contains no principal-withdrawal function.
Thesis impact: the sequence is bullish for market structure because it left no known creator inventory and no continuing Noxa protocol share. It is not evidence that Robinhood authorized WALLET or instructed Noxa to withdraw.
Random origin is the harder story.
No reviewed source authorizes WALLET as a Robinhood token. An outsider-origin explanation must still account for the ENS path, F718 funding, demo-wallet timing, ERC-8056 testing and the two provisioning routes into production Stock Token operators.
Signer unknownPrivate-key control remains unresolved. The chain proves actions, not the person at the keyboard.
Mandate unconfirmedNo public Robinhood acknowledgment, contract or statement authorizes WALLET.
Utility unannouncedETH is gas. No WALLET rewards, staking, governance or fee connection has been announced.
Current evidence: the bridge alias is resolved, f1a and aa33 exchanged value 34 times, and the ENS link is recorded onchain. Signer control and mandate remain unresolved.
Five public events would materially change the thesis.
Each catalyst has a verifiable trigger. Until one occurs, it remains outside the evidence set.
#
Catalyst
Evidence required
Current state
01
Official acknowledgment
A Robinhood-controlled channel names the token contract, signs from a known address or links WALLET to a product.
Not observed
02
Product integration
WALLET appears in an official interface, contract registry, rewards flow, access system or governance process.
Not observed
03
Onchain value accrual
A verified distributor, staking contract, buyback route or treasury rule sends measurable value to WALLET holders.
Mechanism absent
04
Signer or operator attribution
A signature, reproducible funding cluster or public disclosure links f1a, aa33 or F718 to a named operator.
Unresolved
05
Custody or liquidity change
Position #41841 changes owner, the locker implementation changes, or automated liquidity materially expands or contracts.
Monitor onchain
Research rule: screenshots of scripts, private claims and address lists mark leads for investigation. A catalyst enters this report only when the underlying transactions, signatures, contract code or first-party statement can be reproduced.
Primary-source ledger.
Community research supplied the leads. Contract calls, explorer records and official documentation carry the claims.
ENS and public identity context
Robinhood protocol path
F718 and aa33
Production Stock Token permission graph
Verified AccessControlsRegistry
Role grants + use
0743 grantor assigns the minter role21 May 2026
F718 funds fb9560.1 ETH
fb956 funds the 0743 grantor19 May 2026
aa33 opens 624c’s observed history20 May 2026
F718 sends 624c the 3 ETH operational top-up22 Jun 2026
624c begins the role-wallet funding sequence22m 55s later
Reproducible F718 funding fingerprint
Product proximity and WALLET
Market and utility boundaries
Launch and Noxa wind-down
Method: direct transfers were regenerated from Blockscout account histories for Ethereum, Arbitrum, Base and Robinhood Chain, then matched by exact sender and recipient. Native top-level transactions, internal calls with value and ERC-20 transfers are counted. Zero-value interactions are excluded. Production roles were parsed from decoded RoleGranted logs, and funding coverage was checked against the grantor plus the 13 role wallets. Sample role calls were verified against decoded transaction inputs. The four production-call counts are retained as 18 August dataset values and labelled accordingly. Account-abstraction claims were checked against decoded handleOps inputs. ENS claims were checked against decoded registration and reverse-record transactions. Bridge claims were matched to Robinhood’s published L1 contract address. The F718 funding fingerprint was rebuilt from the published 113-transfer ledger across all 85 EOA recipients; all source hashes matched live Blockscout history through the ledger cutoff. Data snapshot: 19 August 2026. Statistical reproduction: 20 August 2026.
Research leads credited to @whisper_alpha@CryptoLuche_@DanteLago07@Truthexpounder@genrih99999. Reconstruction, corrections and source audit prepared for the $WALLET Research Hub.