One product. One mission. FRENT POS — onchain payments built for real-world use, powered by Base and Polygon We’re here to build something useful, reliable and built to last Own your rails. Build onchain

FRENT POS: 0.5% per payment, capped at $10. Free for payments up to $1 Compare that with: Stripe: 1.5% BitPay: 2% + $0.25 NOWPayments: 1% Native USDC directly to your wallet on Base or Polygon. Network fees are separate 🔗 frent.tech/pos/compare

The aa33 thesis isn’t based on a logo or a few suspicious transfers. It’s based on a long onchain trail. Before launching $WALLET, aa33 already had established multichain history and connections to wallets associated with Robinhood Wallet engineering. It funded an address before that wallet began interacting with Robinhood Stock Token contracts and later participated in the OpenAI Stock Token demo referenced publicly by Vlad. aa33 also deployed a test Stock Token on Base for “Mercury ui_multiplier / ui_quantity integration testing.” Later, aa33 appeared extremely early on Robinhood Chain after being funded by F718. Another fresh wallet funded by the same F718 environment only six blocks earlier led into addresses that deployed and operated Robinhood’s Stock Token infrastructure, including testing the same multiplier mechanics aa33 had previously worked on. Two days before $WALLET launched, aa33 executed a swap containing the “robinhood-fees-enabled” integrator identifier and Robinhood Wallet’s same-chain fee structure. After $WALLET launched, another wallet funded alongside aa33 used the corresponding “rh-xchain-fees-enabled” cross-chain route to acquire $WALLET. Later, programmable Definitive vaults began handling $WALLET in size. One particularly interesting flow started with a major TIBBIR holder, moved through a Definitive vault, sold TIBBIR, transferred capital cross-chain, acquired $WALLET and returned almost all of that $WALLET to the original holder. None of this proves Robinhood created $WALLET, controlled aa33 or intends to give $WALLET official utility. The operator could still be a contractor, partner, tester or deeply connected ecosystem participant. But taken together, the evidence raises a much more interesting question than whether aa33 was simply a random memecoin deployer: why was the future $WALLET deployer repeatedly interacting with Robinhood-related Wallet, Stock Token, routing and early-chain infrastructure before $WALLET even existed? That’s what makes HOOD Summit interesting. Not because Robinhood necessarily announces $WALLET, but because we may learn more about the architecture these breadcrumbs appear to sit inside

You can polish one transaction forever while the queue keeps growing At some point, shipping is the optimization

Base is fast enough that waiting for the chain often isn’t the UX problem anymore. Waiting for your indexer, RPC or frontend to agree with it is