Umia: control-plane safety record
2 indexed control-plane surfaces for Umia, each pinned to a canonical Base block and compared with what the protocol documents. Contracts: 0x55975E430Cc54C63dff03B1E6d27Be574Ce229F6, 0xD0193fFAF565B6E530C1a6bbBb2FB13243f29177.
Control-plane scorecard
Aligned Docs and chain match
- Upgradeability
- Not determined · Upgradeable; the delay gating the upgrade path is not in the published recordsEvidence: umia-upgradeability-s27: UmiaMarketCore proxy 0x55975E430Cc54C63dff03B1E6d27Be574Ce229F6 (Base): EIP-1967 implementation slot = 0xBc35cB6cCc4BE46AA491960EBf5281cD5310c653
- Timelock floor
- Strong · 2d minimum enforced delay across control surfacesEvidence: controller fact: getMinDelay() = 172800s
- Signer quorum
- Not determined · No signer quorum in the published records
- Emergency / freeze scope
- Not determined · No pause / freeze authority in the published records
- Docs-vs-chain parity
- Strong · Chain matches or is stronger than the documentation
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 -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=base&address=0xD0193fFAF565B6E530C1a6bbBb2FB13243f29177"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "base", "address": "0xD0193fFAF565B6E530C1a6bbBb2FB13243f29177"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "base", "address": "0xD0193fFAF565B6E530C1a6bbBb2FB13243f29177"})Umia timelock: 2-day minimum delay, as documented
Observed onchain. Umia timelock 0xD0193fFAF565B6E530C1a6bbBb2FB13243f29177 (Base): getMinDelay() = 172800s (2 d).
Documented. 'The protocol owner is a timelock with a two-day public delay.' (umia.finance/llms-full.txt)
cast call 0xD0193fFAF565B6E530C1a6bbBb2FB13243f29177 \ "getMinDelay()" \ --block 58956515 --rpc-url "$BASE_RPC_URL" cast block 58956515 --field hash --rpc-url "$BASE_RPC_URL" # expect 0x82af637fd7a689f4ea41c0ecd1a84a407ea93f2622b8e9c06184327d957129d0
UmiaMarketCore proxy: upgradeable (UUPS), as documented
Observed onchain. UmiaMarketCore proxy 0x55975E430Cc54C63dff03B1E6d27Be574Ce229F6 (Base): EIP-1967 implementation slot = 0xBc35cB6cCc4BE46AA491960EBf5281cD5310c653; upgradeable (EIP-1967 implementation exposing upgradeToAndCall (UUPS)).
Documented. 'Our stance is that the core contracts stay upgradeable while the protocol is still being built.' (umia.finance/llms-full.txt)
cast storage 0x55975E430Cc54C63dff03B1E6d27Be574Ce229F6 \ 0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc \ --block 58956515 --rpc-url "$BASE_RPC_URL" cast block 58956515 --field hash --rpc-url "$BASE_RPC_URL" # expect 0x82af637fd7a689f4ea41c0ecd1a84a407ea93f2622b8e9c06184327d957129d0
Embed Live Control-Plane Badge
Show Umia's Base-EAS-attested Aligned control-plane status in a README, docs page or forum post. The badge links back to this record.
[](https://pacta.wtf/protocols/umia/)
<a href="https://pacta.wtf/protocols/umia/"><img src="https://pacta.wtf/badges/umia.svg" alt="Pacta Control Plane: Aligned · Base EAS" height="20"></a>
Static badge: https://pacta.wtf/badges/umia.svg (rebuilt with the site). Live edge badge: https://pacta-x402.pacta.workers.dev/v1/badges/umia.svg (5-minute cache).
Operating Umia? Add Continuous Control-Plane Monitoring
Continuous Control-Plane Monitoring ($1,500 USDC / month) re-checks your control plane after governance proposals, signer rotations and timelock upgrades, and refreshes the dossier and attestation. It does not buy a status: the result can still be Delta whenever docs and chain diverge.