Robinhood Chain. EVM chain id 4663.

There is no column for safe.

A token diligence engine that already runs, publishing block-pinned readings of other tokens on this chain. Eleven surfaces listed separately, two of them assessed at the pinned block, never averaged and never collapsed into one number.

Read an entry What we have not checked

Pre-launch. No contract address exists yet. No holders, no volume, no market cap.

The roll at block 55,558,221. Two cut, nine uncut. Scroll the rule sideways to read all eleven.

The office

The Sheriff's job in the story is not to fight anyone. It is to arrive with a roll, count what is there, and write it down.

That is the job here.

$SHERIFF is backed by a working token diligence engine. The diligence read is deterministic: python3 and an RPC endpoint, no API keys, no third-party scanner and no oracle. It reads bytecode and contract state directly, at a block it names, and it prints what it found next to what it could not reach.

The market figures on this site are a different thing and are labelled as one. Price, volume and liquidity come from a third-party market API. We did not measure them and we do not stand behind them the way we stand behind a bytecode read.

The engine does not produce a score. It produces an entry.

An unrun check is not a pass.

What an entry looks like

Every entry on the roll has the same four parts, in the same order, whatever the answer is.

The answer: The question that was actually asked, answered conditionally, in the asker's terms. Not a summary of the work. Not a score.
Conditional on: The block, the chain, the assumptions, the exact contracts read.
Stale when: The specific change that would make this entry wrong.
Strongest contrary evidence: The best argument against our own answer, written by us.

Below that: eleven surfaces, listed one by one, each carrying its own rating or its own reason for having none. Below that: an evidence ledger, one row per material claim, each row carrying its block pin, its query, its evidence type and its coverage.

One clean surface never offsets a dirty one. Nothing is averaged.

Entry 001 · SLINK · Pin 55,558,221

THE ANSWER

No mint, pause, blacklist, upgrade or ownership selector was found in the deployed runtime, and no DELEGATECALL is present, at the pinned block. No match is not proof of absence: non-standard dispatchers and packed tables can hide functionality from a PUSH4 scan.

The paired asset USDG (0x5fc5360d0400a0fd4f2af552add042d716f1d168) and its implementation exposes: grantRole(bytes32,address), mint(address,uint256), revokeRole(bytes32,address), upgradeTo(address), upgradeToAndCall(address,bytes). For a regulated tokenized security this is expected and appropriate: the issuer must be able to mirror corporate actions, redemptions and legal orders. It is a dependency of this market, not a finding against it.

CONDITIONAL ON

Chain 4663 at block 55,558,221. The deployed runtime of 0xfa89ed9d12bf74add8253ddfaa426c4d8a0fa603, 3,248 bytes, read at that block. Deployed-runtime PUSH4 selector scan plus EIP-1967 proxy/beacon resolution, read directly from the chain RPC at the pinned block.

The market figures beside this entry are a third-party snapshot. They were not measured by us and they carry no pin.

Read the full entry

The coverage

Eleven surfaces. Two assessed.

A single number hides the one finding that matters, so these are never collapsed and never averaged. Below is the whole list, and beside each one is either what this engine found or the reason it has nothing to say.

Two of the eleven are assessed at the pinned block. Nine are not. That is written here, on our own page, at the same size as the findings.

Hover or focus a notch to light its row. Every row is reachable from the keyboard. Scroll the rule sideways to read all eleven.

01Token controlsNO PRIVILEGED SELECTOR FOUND40 of 40No mint, pause, blacklist, upgrade or ownership selector was found in the deployed runtime, and no DELEGATECALL is present, at the pinned block. No match is not proof of absence: non-standard dispatchers and packed tables can hide functionality from a PUSH4 scan.

02Canonical LP-principal custodyUnassessedLP position ownership, locker terms and side-pool removal paths were not read by this pass.

03Side-pool removal riskUnassessedNot attempted by this pass.

04Sellability and exit depthUnassessedNo pinned quotes at holder size were taken; executable exit depth is unmeasured.

05Current concentrationUnassessedHolder distribution requires transfer replay over the full history and was not performed.

06Historical launch integrityUnassessedNot attempted by this pass.

07Admin, treasury and reward custodyUnassessedNot attempted by this pass.

08Reward accounting and livenessUnassessedNot attempted by this pass.

09Utility and redemption rightsUnassessedNot attempted by this pass.

10External dependenciesISSUER-CONTROLLED DEPENDENCY22 of 40Of the forty tokens on the roll, twenty-two are paired against an asset whose resolved implementation exposes a privileged selector. Sixteen are paired against the chain's native asset, where no third-party token contract sits under the market. Two are paired against WETH, where no privileged selector was found on the resolved code, which is not proof of absence.

11Development and disclosureUnassessedNot attempted by this pass.

Coverage none admits exactly one rating: unknown. A check we could not run is not a check, and it is not a fail either.

How wide a notch is cut

24px a palm
16px a thumb
10px a little finger
5px a swelling of barleycorn
1.5px a single cut

Width records the size of what was entered, on the Exchequer scale. It is not a score, it is never added up, and an uncut notch has no width because nothing was entered.

Entry 001. What a pons token can do to you.

Chain 4663 · Pin 55,558,221 · Unfinalized head

The answer

No mint, pause, blacklist, upgrade or ownership selector was found in the deployed runtime, and no DELEGATECALL is present, in any of the forty tokens read at the pinned block. Thirty-eight of the forty carry a 3,248-byte runtime. The only calls that reduce supply are holder-initiated: burn and burnFrom.

Conditional on

Chain 4663 at block 55,558,221. Forty deployed tokens, selected as the forty highest 24-hour volume rows in a third-party market snapshot. That selection is not a sample of the chain and was not designed to be one.

Stale when

The pons factory deploys a different runtime. A token is launched from a version we did not read. Any state change after block 55,558,221 supersedes the pin.

Strongest contrary evidence

A PUSH4 selector scan shows that a four-byte sequence is present in a runtime. It does not show that a function is reachable, by whom, or in what state. No match is not absence: a non-standard dispatcher, a packed selector table or fallback-only routing hides functionality from this scan entirely. The pin was an unfinalized head, so this is provisional even for the forty we read.

The forty were taken as the highest 24-hour volume rows in a third-party market snapshot. A token being absent from the roll means nothing at all about it.

That is a good result, so we say so plainly. It is also the shape of the whole product: the good news carries the same four boundaries as the bad news, and it costs the same number of words.

Entry 002. The dependency nobody mentions.

Chain 4663 · Pin 55,530,245 · Unfinalized head

The answer

SGOV (0x92FD66527192E3e61d4DDd13322Aa222DE86F9B5), SPCX and SPY are 283-byte beacon proxies. All three point at one beacon, 0xe10b6f6b275de231345c20d14ab812db62151b00, whose implementation is 0xb35490d6f9163de4f80d88dc75c3516eb64c5ae2.

That implementation carries mint(address,uint256), burn(address,uint256), pause() and unpause(). The beacon itself carries upgradeTo(address), grantRole, revokeRole, pause() and unpause().

USDG does not share that beacon. Different issuer, different architecture. It is not therefore unprivileged: read separately at block 55,558,221, the USDG implementation exposes grantRole, mint, revokeRole, upgradeTo and upgradeToAndCall of its own.

Both halves of this are true

This is expected and it is correct. A regulated tokenized security has to be able to mint, burn and pause in order to mirror corporate actions, redemptions and legal orders. It is not a rug finding. It is not an accusation against the issuer or against Robinhood.

It is a dependency. If your position is denominated in one of these, you inherit it, and it was not written anywhere you were going to look.

How often it applies

Of the forty tokens on the roll, twenty-two are paired against an asset whose resolved implementation exposes a privileged selector. Sixteen are paired against the chain's native asset, where no third-party token contract sits under the market. Two are paired against WETH, where no privileged selector was found on the resolved code, which is not proof of absence.

Paired against an asset with a privileged selector on its resolved implementation22

Paired against the chain's native asset16

Paired against WETH, no privileged selector found on the resolved code2

Conditional on

Chain 4663. The beacon read at block 55,530,245: bytecode of the three proxies, the beacon and the implementation. The roll counts at block 55,558,221.

Stale when

upgradeTo is called on the beacon. Roles are granted or revoked. A new wrapper is deployed outside this beacon.

Not checked, and rated accordingly

We did not enumerate who holds the beacon's roles. The contract uses AccessControl rather than Ownable, so there is no single owner to name: owner() reverts. We did not walk the role members. Coverage: none. Rating: unknown.

This entry carries a different pin from entry 001 and the pin is printed on it. The beacon read was taken at block 55,530,245; the roll was taken at 55,558,221. Two reads, two blocks, two stamps. There is no page-global pin anywhere on this site and no entry inherits another entry's block.

The roll

Forty entries, read at block 55,558,221 on chain 4663. Each carries eleven surfaces, two of them assessed, and its own uncut notches.

How these forty were chosen. They are the forty highest 24-hour volume rows in a third-party market snapshot taken at the time of the read. They were not chosen by us for being interesting and they are not a sample of the chain. A token being absent from this roll means nothing at all about it.

001SLINK0xfa89…a603USDG6 of 11 shown. Open for all eleven2/1155,558,221

002PONS0x39db…4571WETH6 of 11 shown. Open for all eleven2/1155,558,221

003ZZZ0x7dbf…ee6aETH (native)6 of 11 shown. Open for all eleven2/1155,558,221

004SHROOM0xab09…5b29MU6 of 11 shown. Open for all eleven2/1155,558,221

005Ponsan0x9721…319fUSDG6 of 11 shown. Open for all eleven2/1155,558,221

006OZZY0xd85c…c7d9USDG6 of 11 shown. Open for all eleven2/1155,558,221

Open all 40 entries

The market case

Why this chain needs an officer

Every figure below is measured on pons. None of them are about $SHERIFF.

Tokens launched, all-time4,228,127

Graduated921

Share that graduated0.022%

Median graduated market cap$31,000

Graduates under $50,000, at every age bucketabout 65%

Both older than 72 hours and above $2M18

Traded in 24 hours across graduated tokens$434.7M

Graduations in the last 24 hours154

Graduation is a bar, not a result. Sixty-seven tokens cleared it in six hours. Many clear it on the creator's own first buy, at zero hours to graduate, which means the number tells you a wallet spent money and nothing else.

Two kinds of token are still alive after day seven, and only two.

Chain-native lore

212 tokens, $116.6M traded in 24 hours, 15 of them above $1M. Robin the Frog at $7.8M, claimed as the chain's mascot. Longbow. The Bull. ROBINCAT.

A real mechanism with a flow story

Delta at $12.8M. Touch Grass at $8.8M. Longbow at $8.2M, a credit layer. Pare at $6.9M, which splits a stock from its dividend stream. Orbio at $6.6M, which routes fees into AI credits.

The dead ground

50 cats launched and 2 are above $1M. 13 politics-and-celebrity tokens launched and none of them are.

Longbow is in both lists. That is not a filing error, and it is the target.

The roles in this story were claimed quickly and one was left. The Sheriff is the only character in it whose job description is financial: he inspects your books and he taxes you. $SHERIFF is deliberately both survivor types at once. The lore is the last unclaimed role in this chain's own story. The mechanism is the engine that publishes the roll.

The fee configuration, and the part of it we cannot yet stand behind

The trade fee on pons is 1.00%. A creator may take up to 10% of that fee. $SHERIFF will be configured to take the maximum.

10% of the 1.00% trade fee is 0.10% of traded volume.

That is the whole of it. Anyone writing "10% tax" without the second half of that sentence, including us, is printing a number ten times larger than the one that exists.

The intended configuration also switches on pons holder fee sharing, which routes creator fees pro-rata to holders who claim them from their pons profile.

Unverified

What we have not verified

We have not confirmed that holder fee sharing is holder-executable and non-discretionary. We have not read, onchain, whether a holder can claim without a creator or an admin choosing to permit it. Until that path is read and entered on the roll with a pin, it is an intended configuration and not a right you hold. A promise is not a right.

Read

What we do know

On pons v2, creator fees are swept rather than pulled. Claimable lags earned. Fees that have been earned may not yet be claimable, and that gap is a function of when the sweep runs.

Unverified

Why there is no percentage on this page

There is no yield figure here and there will not be one until there is an entry to point at. Any number would be a forecast, and a forecast in this position is exactly the thing this engine exists to catch.

The $SHERIFF market row

Pre-launch

$SHERIFF has not launched. There is no contract address, no pool and no price, so there is no holder count, no volume and no market cap to print. Nothing is estimated in their place.

Source: third-party market API. Not measured by us and not covered by any pin on this page.

The gaps

What this office has not checked

Every line below is a hole in our own work, written before anyone asked for it.

Nine of the eleven surfaces are unassessed.
Two assessed: token controls and external dependencies. Canonical LP-principal custody, side-pool removal risk, sellability and exit depth, current concentration, historical launch integrity, admin and treasury custody, reward accounting and liveness, utility and redemption rights, and development and disclosure are not assessed for any token on the roll. Coverage: none. Rating: unknown, on all nine, for all forty.
We did not enumerate who holds the beacon's roles.
The equity wrappers use AccessControl, not Ownable. There is no single owner to name: owner() reverts. We did not walk the role members, so we cannot tell you who can call upgradeTo, grantRole or pause on that beacon. Coverage: none. Rating: unknown.
A selector scan is not a reachability proof.
We scanned PUSH4 selectors in the deployed runtime. That shows a four-byte sequence is present in the bytecode. It does not show the function can be called, by which address, or in which state. And the reverse holds: no match is not absence. A function reachable through a dispatcher we did not model would not appear in our scan.
We read forty tokens, not the factory.
Forty deployed tokens, chosen as the forty highest 24-hour volume rows in a third-party market snapshot. We did not enumerate every version the pons factory has deployed. A different version could carry a different runtime and our conclusion would not cover it.
The pin was an unfinalized head.
Block 55,558,221 was the chain head at the time of reading, not a finalized block. Every current-state claim taken from that read is provisional. A reorganisation at that depth would invalidate the pin itself, not only the conclusion drawn from it.
Our own snapshot disagrees with the measured graduation count.
The market figures on this site record 921 graduated tokens. Our local snapshot holds 912 graduation records. We have not explained the nine-record gap and we have not resolved which is right. The figures we print come from the measured read; our snapshot is used only for per-token metadata and is not the authority on any count.
Market figures are third-party.
Price, market cap, volume and liquidity on this site come from a third-party market API. We did not measure them, we did not verify them against the chain, and they are not covered by any pin on this page.
We could not find a public pons API.
Two endpoints were probed and neither answered. That is a statement about two paths, not proof that no endpoint exists. Nothing on this site depends on one.
This engine reads one launchpad out of eight.
Robinhood Chain runs eight launchpad venues: pons-v2, pons-dot-family, bankr-robinhood, virtuals-robinhood, clanker-robinhood, hoodit, easya-kickstart-robinhood and mint-club-robinhood. The roll reads pons-launched tokens only. A token from any of the other seven is not covered here at all, and two tokens that look identical on a feed can differ on whether anyone retains authority over them for life.
The fee-sharing claim is unverified.
Repeated here so it cannot be missed by anyone who reads only this page.
Verdicts expire, and we do not hide it.
An entry is true of a block. State moves. Roles get granted, pools get created, implementations get swapped. An entry with a superseded pin is a historical document and it is labelled as one. We do not refresh a page quietly and let an old conclusion keep looking current.
We will be wrong, and the correction gets its own pin.
A correction is entered as a new entry with its own block, not as a silent edit. The wrong version stays readable next to the right one. A roll you can quietly rewrite is not a roll.
A clean entry is not a prediction.
A favourable entry says: within a stated search, at a stated block, no executable path was found. It says nothing about price, and it is not financial advice. Nothing here is.
$SHERIFF has no numbers of its own.
Pre-launch means no holders, no volume, no market cap, no chart and no history. Every figure on this site describes the chain or other people's contracts.

Open this on its own page

Launch terms

Launchpadpons, ponsfamily.com/launchpad

ChainRobinhood Chain, EVM chain id 4663, verified by eth_chainId

PairETH

Launch fee0.0005 ETH

Graduationwhen the bonding curve raises 4.2 ETH

Liquiditylocked by the launchpad at graduation. This is the pad's mechanism, not ours, and no lock of ours binds any wallet.

Trade fee1.00%, of which the creator may take up to 10%

Creator shareintended at the maximum: 10% of the 1.00% fee, which is 0.10% of traded volume

Holder fee sharingintended ON. Unverified as holder-executable. See the fee configuration.

Snipe protection99% tax in the launch second, decaying to zero over 3 seconds

Contract addressdoes not exist until launch

Pad mechanism

Snipe protection

If you buy in the first second, almost all of it goes to the tax. Wait three seconds. This is a launchpad setting, not a policy of ours, and it applies to everyone equally.

Pre-launch

Contract address

There is no $SHERIFF contract address until launch. Anything presenting one before it appears here is not $SHERIFF. When it exists, it will appear on this page with the block it was deployed at.

Published

Dev wallet

One address, published before the launch block. No second wallet and no bundling. Nothing bought inside the three-second snipe window. No lock binds this address. It is published so you can watch it. Its size and its share of supply will be printed here as a number at a pinned block.

Why the pair is ETH

On pons you choose the paired asset from about 55 tokenized assets, and the chart is denominated in whatever you choose. It is the most under-used lever on the launchpad. In the last 24 hours of graduated launches, 71 paired to native ETH, 30 to USDG, 6 to SPY, 2 to SPCX and effectively nothing to the other fifty.

We took ETH for one reason that follows directly from entry 002. SPY and SPCX sit behind a beacon whose role holders we have not enumerated. We are not going to denominate our own chart in a dependency we just told you we had not finished checking.

USDG is the second-deepest pair and it does not share that beacon. We read its implementation separately and it exposes privileged selectors of its own. Unread, therefore unused, was the position before that read; after it, the position is that we are not denominating in an issuer-controlled asset while publishing entries about issuer control.

Open the terms on their own page

Questions

Do you score tokens out of 100?: No. A score averages a critical finding against unrelated clean checks. One removable side pool is not cancelled out by ten passes. Eleven surfaces, rated separately, or nothing.
Will you ever call a token safe?: No. The most we will write is: no current executable removal path found at the pinned block, within the stated search. That is a true sentence. "It is safe" is not one.
Is a finding an accusation?: No. Most findings are dependencies, not crimes. The equity wrappers on this chain can mint, burn and pause, and that is correct behaviour for a regulated security. The problem was never that it is true. The problem is that nobody was telling you.
Can I pay for an entry?: No. Entries are not for sale and the roll is public. If that policy ever changes, the change is entered on the roll before it takes effect.
Will you review my token?: Requests go into the queue and the queue is public. We do not promise an entry, and we do not promise a favourable one.
What does holding $SHERIFF give me?: The token, the roll, and the fee configuration described in the fee section with its unverified parts labelled as unverified. It is not a claim on revenue, not a governance right, and not a promise of return.
How does the engine work?: Deterministically. python3 and an RPC endpoint. It reads bytecode and state at a block it names, and it publishes the query alongside the finding so you can run it yourself. Market figures come from a third-party API and are not part of that read.
Why the villain?: Because the villain is the only character in this story with a financial job, and because on a chain of 4,228,127 tokens the role nobody wanted turned out to be the useful one.

There is no column for safe.

The office

What an entry looks like

Eleven surfaces. Two assessed.

Entry 001. What a pons token can do to you.

Entry 002. The dependency nobody mentions.

The roll

Why this chain needs an officer

The fee configuration, and the part of it we cannot yet stand behind

What this office has not checked

Nine of the eleven surfaces are unassessed.

We did not enumerate who holds the beacon's roles.

A selector scan is not a reachability proof.

We read forty tokens, not the factory.

The pin was an unfinalized head.

Our own snapshot disagrees with the measured graduation count.

Market figures are third-party.

We could not find a public pons API.

This engine reads one launchpad out of eight.

The fee-sharing claim is unverified.

Verdicts expire, and we do not hide it.

We will be wrong, and the correction gets its own pin.

A clean entry is not a prediction.

$SHERIFF has no numbers of its own.

Launch terms

Why the pair is ETH

Questions