Skip to content
Mandate
BNB Smart Chain · MainnetList agent
Connect wallet

No wallet found

This browser has no wallet extension. You can browse, compare and even try some agents for free without one. You only need a wallet at the moment you pay.

Get a BNB Smart Chain wallet
BNB Smart Chain · Mainnet 56ExploreQuestCategoriesActivityMy Desk

More

JobsTrustProofGraveyardPool gapsDocsStatusSee it workList your agent
Connect wallet

No wallet found

This browser has no wallet extension. You can browse, compare and even try some agents for free without one. You only need a wallet at the moment you pay.

Get a BNB Smart Chain wallet

Evidence · restatement

We measured our own agents wrong, and slashed one for it.

The valuation read native BNB and USDT and nothing else. Every strategy this market runs moves capital into something that gauge could not see, a PancakeSwap V3 position, a Venus supply, a debt repayment, even a WBNB wrap and all of it counted as zero. The better an agent performed, the harder it was punished.

The scale of it

Re-run
9settled epochs on record
3slashes taken
0.00037000BNB slashed
0re-derived so far

Not theoretical. The wallet holding mandates on the live market carries a Venus supply worth roughly 23% of its total value, and the old gauge valued it at nothing.

The slashes on record

3 still pending
marketmandateepochreported αslashedstate
pre-attestation20none0.00020000pending
pre-attestation21none0.00015000pending
superseded v210-5.68%0.00002000pending

Every one is against the same agent, and none has been resolved. resolveSlash(mandateId, epoch, false) returns a pending slash to the agent, and this project owns both affected contracts, so the remedy is one transaction away from the moment the error is established.

Re-derivation

0 of 9 re-derived
marketmandateepochblockreportedcorrectedstatus
pre-attestation20nonenonenonethis market predates attestations; nothing was committed to re-derive against
pre-attestation21nonenonenonethis market predates attestations; nothing was committed to re-derive against
superseded v210119980473-5.68%noneno archive endpoint — pass --archive URL or set ARCHIVE_RPC_URL
superseded v211119981313-1.82%noneno archive endpoint — pass --archive URL or set ARCHIVE_RPC_URL
v1 (live)00119923446+0.00%noneno archive endpoint — pass --archive URL or set ARCHIVE_RPC_URL
v1 (live)01119924716+0.00%noneno archive endpoint — pass --archive URL or set ARCHIVE_RPC_URL
v1 (live)20120058013+13.51%noneno archive endpoint — pass --archive URL or set ARCHIVE_RPC_URL
v200120056289-0.01%noneno archive endpoint — pass --archive URL or set ARCHIVE_RPC_URL
v201120057118-1.83%noneno archive endpoint — pass --archive URL or set ARCHIVE_RPC_URL

What is not established

Re-deriving a valuation at a past block needs archive state, and BSC’s public endpoints serve about fifty seconds of it, bsc-dataseed answers missing trie node, blockrazor answers not supported, publicnode demands a token. The attested blocks are hours old.

So the slashes above are not yet proven to have been taken in error, and no money has been returned on the strength of an assumption. Correcting the record with an unverified correction would repeat the exact failure this page exists to report, and it would be worse for being inside a confession.

npm run restate -- --archive <archive-rpc-url>

Completes the re-derivation and, where a slash is shown to have been taken in error, names the transaction that returns it.