PACTAby Fractal Neurons
Request a dossier
Delta-Neutral Synthetic Dollar (staked strUSD) (Ethereum)

Tori Finance: control-plane safety record

1 indexed control-plane surface for Tori Finance, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0xd058…1697

What differs

Changed / discrepant

  • trUSD TIMELOCK_ADMIN_ROLE: a second ToriTimelock, not the documented timelock: Tori trUSD 0xd0580192E98eA6CEB9c7b6191Ed2E27560911697 (Ethereum, EIP-1967 proxy, implementation 0xb1d133fE29255EB4Ac9B05d647d49cd7F05ff631): hasRole … observed vs 'It holds the Timelock Admin role on the core contracts' (docs.tori.finance/security/roles.md) documented
    Show the full onchain evidence

    Tori trUSD 0xd0580192E98eA6CEB9c7b6191Ed2E27560911697 (Ethereum, EIP-1967 proxy, implementation 0xb1d133fE29255EB4Ac9B05d647d49cd7F05ff631): hasRole(TIMELOCK_ADMIN_ROLE 0x5f58e3…846ca5, 0xcd3c66e73abF927EAAF1238aEB5F251b4f2f667b) = true and hasRole(TIMELOCK_ADMIN_ROLE, 0xA952453E39F77108Ee37C1b92de593F1C59A6ef4) = false at this pin; the reverse at Pacta's published pin #26,448,221 (record tori-finance-control-plane). 0xA952453E39F77108Ee37C1b92de593F1C59A6ef4 is the timelock the roles page names; 0xcd3c66e73abF927EAAF1238aEB5F251b4f2f667b is a second ToriTimelock (verified source; renounceRole disabled). Both have getMinDelay() = 86,400 s and the 3-of-5 Safe 0x0C6Bbfd2d5666d44bf28580eDEec0263692C8316 holds PROPOSER_ROLE on both: the delay is unchanged, but trUSD upgrades are now queued on a timelock the documentation does not name.

Matched

  • Timelock delay: 1 d

Protocol maintainer and fixed this gap? Get it re-verified on mainnet in 24h

Control-plane scorecard

Upgradeability: Not determinedTimelock floor: ModerateSigner quorum: StrongEmergency / freeze scope: Not determinedDocs-vs-chain parity: Weak

Delta Docs and chain differ

Aligned means the docs are accurate, not that the protocol is low-risk. The rosette rates the controls themselves.
Upgradeability
Not determined · Upgrade path not in the published records
Timelock floor
Moderate · 1d minimum enforced delay across control surfacesEvidence: tori-trusd-timelock-admin-undocumented-timelock-s32: observed_delay_seconds = 86400
Signer quorum
Strong · Lowest controlling quorum: 3-of-5Evidence: tori-trusd-timelock-admin-undocumented-timelock-s32: … have getMinDelay() = 86,400 s and the 3-of-5 Safe 0x0C6Bbfd2d5666d44bf28580eDEec0263692C8316 …
Emergency / freeze scope
Not determined · No pause / freeze authority in the published records
Docs-vs-chain parity
Weak · Documentation differs from the chain (parameter delta)

Each slice is derived only from the pinned records on this page and their controller facts (/api/v1/scorecards.json). A hollow slice is not determined by the published evidence (never a guess); docs-vs-chain parity is uncompared for RPC-observed protocols. How to read it.

Check it live (free)

The pre-flight API re-reads the controller, proxy and capabilities of one contract at the latest block. No key, no wallet. The score rates that single contract, not the whole protocol.

cURL
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0xd0580192E98eA6CEB9c7b6191Ed2E27560911697"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "ethereum", "address": "0xd0580192E98eA6CEB9c7b6191Ed2E27560911697"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "ethereum", "address": "0xd0580192E98eA6CEB9c7b6191Ed2E27560911697"})

Provenance · research credit

Reported by @veriton-dev through the Pacta Wave 2 pool (PR #106, fixture bounties/wave-2/ethereum-tori-finance-timelock-admin-post-pin.json), merged under the Apache-2.0 commercial grant and paid $1.00 USDC (tx 0xe7e5…9d0c); credited on tori-trusd-timelock-admin-undocumented-timelock-s32. Pacta then re-read every value below on two independent RPCs at its own Sprint pin and compared it with the documentation; the classifications and the Base EAS attestation are Pacta's. See the leaderboard.

trUSD TIMELOCK_ADMIN_ROLE: a second ToriTimelock, not the documented timelock

Status
Delta
Target
Tori trUSD 0xd058…1697 · Etherscan
Pinned block
Ethereum #26,451,608 · Etherscan · sprint 32
Block hash
0x0266af5b…217a17
Attestation
Base EAS attestation 0x0968…bddc

Observed onchain. Tori trUSD 0xd0580192E98eA6CEB9c7b6191Ed2E27560911697 (Ethereum, EIP-1967 proxy, implementation 0xb1d133fE29255EB4Ac9B05d647d49cd7F05ff631): hasRole(TIMELOCK_ADMIN_ROLE 0x5f58e3…846ca5, 0xcd3c66e73abF927EAAF1238aEB5F251b4f2f667b) = true and hasRole(TIMELOCK_ADMIN_ROLE, 0xA952453E39F77108Ee37C1b92de593F1C59A6ef4) = false at this pin; the reverse at Pacta's published pin #26,448,221 (record tori-finance-control-plane). 0xA952453E39F77108Ee37C1b92de593F1C59A6ef4 is the timelock the roles page names; 0xcd3c66e73abF927EAAF1238aEB5F251b4f2f667b is a second ToriTimelock (verified source; renounceRole disabled). Both have getMinDelay() = 86,400 s and the 3-of-5 Safe 0x0C6Bbfd2d5666d44bf28580eDEec0263692C8316 holds PROPOSER_ROLE on both: the delay is unchanged, but trUSD upgrades are now queued on a timelock the documentation does not name.

Documented. 'It holds the Timelock Admin role on the core contracts' (docs.tori.finance/security/roles.md)

Reproduce on any archive node
cast call 0xd0580192E98eA6CEB9c7b6191Ed2E27560911697 \
  "hasRole(bytes32,address)" 0x5f58e3a2316349923ce3780f8d587db2d72378aed66a8261c916544fa6846ca5 0xcd3c66e73abF927EAAF1238aEB5F251b4f2f667b \
  --block 26451608 --rpc-url "$ETH_RPC_URL"
cast block 26451608 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0x0266af5bcad519d93b3be78e41b76a62985e22fbe4feef043ac3225f6f217a17

Control-plane badge: Parameter Delta

Pacta Control Plane: Parameter Delta

This badge is amber because at least one Base-EAS-attested surface of Tori Finance differs from what the protocol documents. It turns to the neutral Aligned · Base EAS shield only when the on-chain state or the documentation changes and the two match at a new finalized block, whoever requests the re-check.

Submit updated docs

Embed this badge (it updates when the status changes):

Markdown
[![Pacta Control Plane](https://pacta.wtf/badges/tori-finance.svg)](https://pacta.wtf/protocols/tori-finance/)
HTML
<a href="https://pacta.wtf/protocols/tori-finance/"><img src="https://pacta.wtf/badges/tori-finance.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>

Badge: https://pacta.wtf/badges/tori-finance.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/tori-finance.svg.

For maintainers and issuers

Fixed this gap? 24h mainnet re-verification ($99 intro)

A maintainer and an independent verifier re-check Tori Finance on mainnet within 24h and attest the result on Base. The fee pays for the 24-hour mainnet re-verification work, never the grade: your attestation reads Aligned when on-chain controls match the published documentation, and Delta when they do not.

Maintaining Tori Finance? Verify and reconcile the record

Two paths, both public. A free doc-update notice asks the maintainers to correct the documentation or the onchain parameter; anyone can send it. A Full Control-Plane Dossier ($2,500–$5,000 USDC, 24h SLA) re-reads the multisig and timelock control planes on archive RPCs and prepares an upstream docs reconciliation PR. Either way the classification changes only when the onchain state or the documentation aligns at a new finalized block.

Need procurement paperwork? Request a commercial invoice (PDF).

Read-only onchain analysis. Not investment advice. Exploit-sensitive vulnerabilities are never published here; they go through Immunefi or Cantina bounty programmes.Request a dossier (24h SLA)