Methodology
One vocabulary for every label on the site: what each status, rosette slice and live-check verdict means.
How it works
- Read the docs. Pacta records what each protocol publishes about who can upgrade, pause or change its contracts, and how long changes must wait.
- Read the chain at a finalized block. The same controls are read at a finalized block on two independent RPC providers.
- Attest the difference on Base. Each result is attested with EAS on Base, so anyone can re-check it later with
cast.
Docs vs chain
One status per protocol, used in every table, badge and feed:
| Status | Meaning | Protocols |
|---|---|---|
| Aligned | The published documentation matches the sampled onchain controls. It says the docs are accurate, not that the protocol is low-risk. | 50 |
| Delta | Docs and chain differ: the live controls are looser than, or different from, what the protocol documents. | 28 |
| Protective | Docs and chain differ in the safe direction: the live controls are stricter than documented. | 8 |
| Observed | The onchain control plane is pinned at a finalized block over RPC; the documentation has not been compared yet. | 4 |
Record-level classifications in the JSON feeds map onto the same words: parameter_delta = Delta, protective_delta = Protective, aligned_baseline = Aligned, rpc_observed = Observed. The embeddable badges read "Aligned · Base EAS", "Parameter Delta" or "RPC-Observed" for the same three cases. A protocol is Delta if any of its records is Delta; "Reconciled" marks a Delta that was fixed and re-attested as Aligned.
The control-plane rosette
Five factors, clockwise from the top. Colour, slice length and a letter carry the same information, so the rosette never relies on colour alone; hover or focus a slice to read it.
| Factor | What it measures |
|---|---|
| Upgradeability | Who can replace the contract code, and through what path (immutable, timelocked, multisig, single key). |
| Timelock floor | The shortest enforced delay before a privileged change can execute. |
| Signer quorum | The signer threshold of the multisigs that control the contracts. |
| Emergency / freeze scope | Who can pause, freeze or blacklist, and how broad that power is. |
| Docs-vs-chain parity | Whether the documented controls match the chain (uncompared for Observed protocols). |
| State | How it looks |
|---|---|
| Strong | Long green slice: the control meets a strong standard (for example a multi-day timelock). |
| Moderate | Medium yellow slice: partial protection. |
| Weak | Short red slice: weak or no protection. |
| Not determined | Hollow dashed slice: the published evidence does not decide it. Pacta never guesses. |
| Uncompared | Hollow dashed slice: docs-vs-chain parity is not compared (Observed protocols). |
The live contract check
The checker on the homepage and /v1/check/preflight read one contract address at the latest block. Its verdict and its 0–100 risk score rate that single address, not the whole protocol: a protocol can be Delta while one of its token contracts has no admin at all. Confidence says whether the address is an indexed, verified record or a bytecode heuristic.
| Verdict | Meaning |
|---|---|
| No standard upgrade or admin authority detected | Neutral. No proxy admin, owner or role with upgrade power was found at this address. |
| Changes wait behind a timelock | Neutral. Privileged changes go through an enforced delay. |
| A multisig can change it with no delay | Warning. A Safe can change the contract without a waiting period. |
| A single key can change it instantly | Warning. One externally owned account controls it. |
| Timelock with a zero delay | Warning. A timelock exists but enforces no delay. |
| Controller needs further review | Warning. An unclassified contract controls it. |
| No contract code at this address | Neutral. The address is an EOA or not deployed. |
Amber is reserved for warnings everywhere on the site. Neutral and good results are never amber.
Evidence and reproducibility
Every record names its block number and block hash, the contract and the call. 183 attested checks are anchored in 25 Base EAS batch attestations; the 4 Observed protocols are pinned over RPC and reproducible with cast, but not attested yet. Machine-readable: scorecards.json, index.json, rpc-pinned.json.
Glossary
- Control plane
- The set of keys, multisigs, timelocks and roles that can change a protocol.
- Finalized block
- A block the chain will not reorganize; reads pinned to it are reproducible.
- EAS
- Ethereum Attestation Service: Pacta signs each result onchain on Base.
- Timelock
- A contract that forces a delay between queuing and executing a change.
- x402
- An HTTP payment protocol for metered API calls; Pacta's free tier needs no payment.
- MCP
- Model Context Protocol: how AI agents call Pacta's tools.