
Loraclet
21 posts

Loraclet
@Loraclet
Uncovering the lore behind the signal



















PonsV2 is live on Robinhood Chain mainnet and the first token was deployed by the team itself. Here's the onchain proof. The docs still claim the launch factory isn't deployed. It is. I recovered the full v2 stack from verified bytecode and on-chain logs on RH Chain (4663). Factory verified as PonsV2LaunchFactory: 0x7E1EAbd52Ae29598e6483F72dCf1a70b14284dB8 robinhoodchain.blockscout.com/address/0x7E1E… Full stack, all verified and wired: Launch deployer 0xdD89f26beA3916233d002D1189F973B78D38aA70 robinhoodchain.blockscout.com/address/0xdD89… Meme hook (Uniswap v4) 0x8e99D2009D60A917e9B1c00C04C077b8c0c3a044 robinhoodchain.blockscout.com/address/0x8e99… Fee escrow 0xbc39B6502E1a6Ab36E4A5c5026A35F08342A0A9c robinhoodchain.blockscout.com/address/0xbc39… Buyback vault 0x2d6e3aA895EDa2603189c2A89679bD4279175FdB robinhoodchain.blockscout.com/address/0x2d6e… Locker 0x28b6F0116c7F234951cf0e67319ed53863Df2197 robinhoodchain.blockscout.com/address/0x28b6… Graduation executor 0xbccBb394E40d718710F4275C23f9F851B680565a robinhoodchain.blockscout.com/address/0xbccB… Graduation guard 0xFef36C2ca32D3eCD18C371021950d44033Bee531 robinhoodchain.blockscout.com/address/0xFef3… Launching is gated. launchEnabled = false. The only way to deploy right now is the launcher whitelist, and setWhitelistedLauncher is onlyOwner. Two addresses on the whitelist: Factory owner: 0x0815A4881f9c4073a70fdF00600EbA54c5a5baAa robinhoodchain.blockscout.com/address/0x0815… The launcher, added to the whitelist by the owner: 0xD48e5622A6f0d015388FBEd4272a336535927Fa4 robinhoodchain.blockscout.com/address/0xD48e… Both WhitelistedLauncherUpdated events were emitted by transactions sent from the owner 0x0815A488… the owner whitelisted itself, then whitelisted 0xD48e5622…. The single existing launch "INITIAL": 0x91c4b7a5c655c2fcd7bc173c1e8e2469352695c2 robinhoodchain.blockscout.com/token/0x91c4b7… Deployed by 0xD48e5622…, the exact address the owner personally whitelisted. Its creatorFeeRecipient is that same wallet. It launched against a custom pair (not ETH) and has already graduated into a Uniswap v4 pool (phase 2). Its curve: 0x5E40DD2c72b76B2E51dBb33B1526b3B2e99fF016. So the chain of custody is unambiguous: owner → whitelists a launcher → that launcher deploys the one and only v2 token → fees route back to it. No third party. INITIAL is the team's own end-to-end mainnet test of the launch → curve → graduation flow. Config 0: 1B supply, 1% curve fee, 0.0005 ETH launch fee, phantom reserve 1.68 / graduation threshold 4.2 → ~28.6% reserved for the pool, ~71.4% sold on the curve. 8 approved quote assets. Caveats, stated plainly: all three audits are still open treat v2 as unaudited. This is a whitelisted test phase, not a public launch. Verify every address yourself.



v2, this week let's win







0x91c4b7a5c655c2fcd7bc173c1e8e2469352695c2 I checked and PonsV2 is on mainnet and currently live. The factory address is 0x7E1EAbd52Ae29598e6483F72dCf1a70b14284dB8, and I found two dev addresses on the whitelist. One of them (0xD48e5622A6f0d015388FBEd4272a336535927Fa4) deployed INITIAL (0x91c4b7a5c655c2fcd7bc173c1e8e2469352695c2) this token is probably part of the project itself, which is why I'm going in.













