Threshold Network (tBTC): control-plane safety record
1 indexed control-plane surface for Threshold Network (tBTC), pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0x92f2d8b72a7F6a551Be60b9aa4194248E9B4913D.
Control-plane scorecard
Aligned Docs and chain match
- Upgradeability
- Not determined · Upgradeable; the delay gating the upgrade path is not in the published recordsEvidence: threshold-tbtc-timelock-1d-walletregistry-op-0xb667: getMinDelay() = 86400s (1d). Operation 0xb6671bbbedf818d7232a4006d4a85b21e3f3055d17244188f244c1da8263e0c7: isOperationPending() = true, getTimestamp() = …
- Timelock floor
- Moderate · 1d minimum enforced delay across control surfacesEvidence: controller fact: getMinDelay() = 86400s
- 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=0x92f2d8b72a7F6a551Be60b9aa4194248E9B4913D"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x92f2d8b72a7F6a551Be60b9aa4194248E9B4913D"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x92f2d8b72a7F6a551Be60b9aa4194248E9B4913D"})tBTC TimelockController 1d delay — public WalletRegistry upgradeAndCall schedule
Observed onchain. getMinDelay() = 86400s (1d). Operation 0xb6671b…63e0c7: isOperationPending() = true, getTimestamp() = 1794604955 (2026-11-13 21:22:35 UTC). It is a public CallScheduled upgradeAndCall (0x9623609d) on ProxyAdmin (0x7Affa05f726D293eB1193807A91617318292008e) for WalletRegistry (0x46d52E41C2F300BC82217Ce22b920c34995204eb) to implementation 0x14fAD0C11C83AC736e5929D5661bbA7E6BB9c0D6.
Documented. docs.threshold.network contract addresses (Mainnet, tBTC application contracts) list 0x92f2d8b72a7F6a551Be60b9aa4194248E9B4913D as the tBTC 'Timelock Controller'; the docs state no delay for it. The '2-day' timelock in the Governance Process page belongs to the separate Governor Bravo Timelock Controller (0x87F005317692D05BAA4193AB0c961c69e175f45f, getMinDelay() = 172800s at the same block).
cast call 0x92f2d8b72a7F6a551Be60b9aa4194248E9B4913D \ "getMinDelay()" \ --block 26407707 --rpc-url "$ETH_RPC_URL" cast block 26407707 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x9030abf37638c14a5f9c145f298a0f4cd74b247a99f3dddd119b9c6b09f5dced
Embed Live Control-Plane Badge
Show Threshold Network (tBTC)'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/threshold-network-tbtc/)
<a href="https://pacta.wtf/protocols/threshold-network-tbtc/"><img src="https://pacta.wtf/badges/threshold-network-tbtc.svg" alt="Pacta Control Plane: Aligned · Base EAS" height="20"></a>
Static badge: https://pacta.wtf/badges/threshold-network-tbtc.svg (rebuilt with the site). Live edge badge: https://pacta-x402.pacta.workers.dev/v1/badges/threshold-network-tbtc.svg (5-minute cache).
Operating Threshold Network (tBTC)? Add Continuous Monitoring
Continuous 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.