Update on @QuantaPools The latest evidence establishes a mainnet swap and a liquidity deposit that minted an LP NFT. The deployed frontend has also changed materially since our earlier inspection. These findings support LEANING LEGIT for the demonstrated DAMM v2 functionality. They do not establish that the entire advertised product is complete. What we confirmed The first transaction succeeded on Robinhood Chain mainnet at block 71,063,780, on September 24 at 03:52:42 UTC. Its token-transfer records show 0.000001 WETH moving from the initiating wallet through Quanta’s SmartRouter and DAMM Adapter into the disclosed pool. The pool sent 0.072134 USDG to the router, which forwarded it to the initiating wallet. The addresses match those published in Quanta’s announcement. This supports an actual routed swap, beyond a frontend confirmation or contract deployment. robinscan.io/tx/0x3f3358b0c1…⁠ The second transaction succeeded at block 71,266,249, on September 24 at 09:34:22 UTC. The wallet supplied WETH and USDG to the disclosed DAMM Position Adapter. The adapter forwarded 0.000007589263561768 WETH and 0.150959 USDG to the pool, returning the unused amounts. In that same transaction, Quanta’s published PositionManager minted ERC-721 token #3 to the initiating wallet. The position event also references the same pool ID used by the swap. This links a real asset deposit with an LP NFT mint. Withdrawal and redemption rights still require separate verification. robinscan.io/tx/0x8a53482821…⁠ The frontend changed too The current DAMM deposit handler checks allowances, requests token approvals where needed, calls openPosition, waits for the transaction receipt and rejects a reverted deposit before reporting success. The previously observed random-hash and local-position-storage patterns were not present in the newly inspected application bundle. Our earlier criticism should therefore not be carried forward unchanged to this updated DAMM deposit flow. quantapools.tech/_next/stati…⁠ The pools API now returns two DAMM v2 pool records, including the pool involved in both transactions. Some metadata remains inconsistent: those records still report initialized_onchain=false despite the observed activity. That field needs clarification; it does not erase the transaction evidence. quantapools.tech/v1/chains/4…⁠ What this does not establish Both transactions originated from the same wallet. They demonstrate execution, but do not establish independent user adoption or meaningful trading volume. This check also did not establish completed liquidity withdrawals, fee claims, locks, rewards, or the full DLMM functionality. One successful swap does not prove that fees adjust correctly across changing volatility conditions. $Quanta has now provided evidence that addresses part of the earlier concern: a mainnet routed swap, an asset-funded LP NFT mint, and an updated deposit implementation. LEANING LEGIT fits that demonstrated functionality. The remaining work is verifying how positions behave after creation, including withdrawal and fee collection, and checking the other advertised features. This is a meaningful improvement in the evidence, not a security audit or confirmation that the whole stack is finished. 0x1da81ca017949efbe07972776580d04592ba9b63