45 / 100
$GPAD
0xc3d0…834cad· Robinhood Chain
ngl, not gonna lie
The launchpad deploys tokens, but the claimed physical compute and rising floor show nothing real behind them.
The site's deploy flow works on Robinhood Chain: a createToken transaction was built and would go through. The headline pitch, that 25% of purchases fund biomedical GPU nodes and a researcher-funded floor, is not backed. The site itself shows 0 active nodes and $0.00 rent paid, and the contract is unverified. The dev looks clean, but the top 10 wallets hold 66% of the supply.
Checked 2 h ago
Red flags2
Physical compute claim is contradicted by the site
The site shows 0 active biomedical nodes (sim), $0.00 rent paid and 0 nodes funded. That contradicts the claim that real compute is live with paid leases.
tokenHolders are concentrated and liquidity is near zero
The top 10 wallets hold 66%, and one wallet holds 48%. Liquidity is about $0.23 with no buys in 24h, so exiting is hard.
48%3.4%2.9%2.7%
Watch out4
The 25% compute funding is unbacked
Nothing visible shows where the 25% of purchases goes. The site shows only a small compute reserve (about $12).
claim sourcetokenContract source is unverified
The contract can't be read, so the price floor that only rises and the receiveYield mechanism cannot be checked.
tokenclaim sourceAudit claim has no support
No auditor or report is shown for the 'final stretch' audit.
tokenSite and X are linked and new
The site lists the exact CA and links to the X account. The domain is 18 days old and the X account 15 days old with modest engagement.
registrationpagefirst screen@gridpadnet
Checks out2
Deploy flow builds a real transaction
After filling the form and connecting MetaMask, the site asked to sign a createToken call on chain 4663. ngl's simulation showed it would succeed.
wallet requestscreenshotDev looks clean
No other buyers in the launch block, the dev holds none of the supply, and 1.9% was burned. This is the dev's first coin.
launchdevtransferburn
Ask the agent
Anything about $GPAD. ngl answers from this check, or goes back to the site and tries what you ask.
Hands-on tests
WorksToken deployment flow (DEPLOY TOKEN to wallet signature)
Deploy reaches the wallet signature request
- What it did:
- On /deploy filled Name 'Test Coin', Ticker 'TEST', initial buy 0.01 ETH, uploaded the 512x512 test PNG as logo, connected MetaMask, pressed DEPLOY TOKEN.
- What the site showed:
- Site asked the wallet to sign a transaction to 0x68B25B61BBAb323F4C022DeaF9a481B19b9Bbf26, value 0.01, call 0x6fc80f0b on chain 4663 (Robinhood Chain). ngl's log: 'simulate eth_call createToken ok · token 0xCBADC7...98cE6e · mints 141,421 TEST', then 'confirm the transaction in MetaMask' and 'Request rejected in your wallet.' ngl refused the signature after simulating it without sending.

WorksAsset logo upload
Logo upload accepted by the form
- What it did:
- Clicked Upload image and attached the test PNG.
- What the site showed:
- Form showed the image as attached: '1,908 bytes WEBP · stored on-chain in the creation event' with a Remove button.

WorksInitial buy preset and quote
Initial buy quote updates for 0.01 ETH
- What it did:
- Set initial buy to 0.01 ETH via preset.
- What the site showed:
- Quote showed 'You receive (exact) 141,421 TEST', opening spot $0.0002590, opening floor $0.00004317, market cap $37.

WorksConnect wallet
MetaMask connects on deploy page
- What it did:
- Clicked Connect, chose MetaMask.
- What the site showed:
- Signer shown as MetaMask: 0xa95408…9bd14A; the deploy button became active.
