flaunch: control-plane safety record
1 indexed control-plane surface for flaunch, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0x6c4c…27b0
Control-plane scorecard
Aligned Docs and chain match
- Upgradeability
- Not determined · Upgrade path not in the published records
- 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=ethereum&address=0x6c4c0CD7E0E5eeFfbd77AAfe1820d3b9B1ef27b0"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x6c4c0CD7E0E5eeFfbd77AAfe1820d3b9B1ef27b0"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x6c4c0CD7E0E5eeFfbd77AAfe1820d3b9B1ef27b0"})flaunch timelock: 2-day minimum delay, as documented
Observed onchain. flaunch TimelockController 0x6c4c0CD7E0E5eeFfbd77AAfe1820d3b9B1ef27b0 (Ethereum): getMinDelay() = 172800s (2 d).
Documented. 'a two day timelock will follow before the proposed code is executed' (docs.flaunch.gg/community/governance/proposals-and-voting.md)
cast call 0x6c4c0CD7E0E5eeFfbd77AAfe1820d3b9B1ef27b0 \ "getMinDelay()" \ --block 26448221 --rpc-url "$ETH_RPC_URL" cast block 26448221 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa7818c0e1b8807aac0c999c2dc9aeeea40b91b4f19b1b76a62ad02d8d17607c8
Embed Live Control-Plane Badge
Show flaunch'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/flaunch/)
<a href="https://pacta.wtf/protocols/flaunch/"><img src="https://pacta.wtf/badges/flaunch.svg" alt="Pacta Control Plane: Aligned · Base EAS" height="20"></a>
Static badge: https://pacta.wtf/badges/flaunch.svg (rebuilt with the site). Live edge badge: https://pacta-x402.pacta.workers.dev/v1/badges/flaunch.svg (5-minute cache).
Operating flaunch? 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.