Re Protocol (reUSD / reUSDe): control-plane safety record
3 indexed control-plane surfaces for Re Protocol (reUSD / reUSDe), each pinned to a canonical Ethereum block and compared with what the protocol documents. Contracts: 0x4691C475bE804Fa85f91c2D6D0aDf03114de3093, 0x5086bf358635B81D8C47C66d1C8b9E567Db70c72, 0x69dDEa332723cF5407151aAF68B9b076557FCA93.
What differs
Changed / discrepant
- Deposit vault role admin held behind the delay; multisig lacks it: ICL 0x4691C475bE804Fa85f91c2D6D0aDf03114de3093 (shareToken() = reUSD): hasRole(DEFAULT_ADMIN_ROLE, Safe 0x8eec10616802Ef639CA55c98ac856553fAdEfBaD) = false; observed vs docs.re.xyz (ICL permissions note): 'The Safe holds DEFAULT_ADMIN_ROLE on every ICL (Ethereum reUSD and reUSDe, Avalanche, Arbitrum, Base), alongside the chain's timelock.' documented
Show the full onchain evidence
ICL 0x4691C475bE804Fa85f91c2D6D0aDf03114de3093 (shareToken() = reUSD): hasRole(DEFAULT_ADMIN_ROLE, Safe 0x8eec10616802Ef639CA55c98ac856553fAdEfBaD) = false; the Timelock 0x69dDEa332723cF5407151aAF68B9b076557FCA93 holds DEFAULT_ADMIN_ROLE and UPGRADER_ROLE; getRoleAdmin(UPGRADER_ROLE) = DEFAULT_ADMIN_ROLE, so granting UPGRADER_ROLE on this ICL waits the 48-hour delay.
Show the full documented text
docs.re.xyz (ICL permissions note): 'The Safe holds DEFAULT_ADMIN_ROLE on every ICL (Ethereum reUSD and reUSDe, Avalanche, Arbitrum, Base), alongside the chain's timelock.' and '... so the Safe can grant itself ICL UPGRADER_ROLE with no delay'
Matched
- reUSD and reUSDe tokens: admin and upgrades wait 48 hours: matches the documentation
- Scheduling rights: one 3-of-5 multisig proposes, executes, cancels: matches the documentation
Control-plane scorecard
Protective Chain stronger than documented
- 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
- Strong · Lowest controlling quorum: 3-of-5Evidence: re-safe-sole-timelock-proposer-s21: … timelock is its own admin; the Safe is 3-of-5 (v1.4.1, no modules).
- 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=0x5086bf358635B81D8C47C66d1C8b9E567Db70c72"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x5086bf358635B81D8C47C66d1C8b9E567Db70c72"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x5086bf358635B81D8C47C66d1C8b9E567Db70c72"})reUSD and reUSDe tokens: admin and upgrades wait 48 hours
Observed onchain. reUSD 0x5086bf358635B81D8C47C66d1C8b9E567Db70c72 and reUSDe 0xdDC0f880ff6e4e22E4B74632fBb43Ce4DF6cCC5a: DEFAULT_ADMIN_ROLE and UPGRADER_ROLE held by TimelockController 0x69dDEa332723cF5407151aAF68B9b076557FCA93 (getMinDelay() = 172800s); the Safe 0x8eec10616802Ef639CA55c98ac856553fAdEfBaD holds neither; the ICL 0x4691C475bE804Fa85f91c2D6D0aDf03114de3093 holds MINTER_ROLE on reUSD.
Documented. docs.re.xyz (governance and access control): 'a 48-hour TimelockController holds DEFAULT_ADMIN_ROLE and UPGRADER_ROLE on the ShareToken' and 'OpenZeppelin TimelockController enforcing a 2-day (172,800 second) delay between scheduling and executing privileged actions.'
cast call 0x5086bf358635B81D8C47C66d1C8b9E567Db70c72 \ "hasRole(bytes32,address)" 0x0000000000000000000000000000000000000000000000000000000000000000 0x69dDEa332723cF5407151aAF68B9b076557FCA93 \ --block 26427612 --rpc-url "$ETH_RPC_URL" cast block 26427612 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x1c5ef52eb0b586e49da2a11dc9f905cae4125008dc814d6781f53a142f6555ac
Deposit vault role admin held behind the delay; multisig lacks it
Observed onchain. ICL 0x4691C475bE804Fa85f91c2D6D0aDf03114de3093 (shareToken() = reUSD): hasRole(DEFAULT_ADMIN_ROLE, Safe 0x8eec10616802Ef639CA55c98ac856553fAdEfBaD) = false; the Timelock 0x69dDEa332723cF5407151aAF68B9b076557FCA93 holds DEFAULT_ADMIN_ROLE and UPGRADER_ROLE; getRoleAdmin(UPGRADER_ROLE) = DEFAULT_ADMIN_ROLE, so granting UPGRADER_ROLE on this ICL waits the 48-hour delay.
Documented. docs.re.xyz (ICL permissions note): 'The Safe holds DEFAULT_ADMIN_ROLE on every ICL (Ethereum reUSD and reUSDe, Avalanche, Arbitrum, Base), alongside the chain's timelock.' and '... so the Safe can grant itself ICL UPGRADER_ROLE with no delay'
cast call 0x4691C475bE804Fa85f91c2D6D0aDf03114de3093 \ "hasRole(bytes32,address)" 0x0000000000000000000000000000000000000000000000000000000000000000 0x8eec10616802Ef639CA55c98ac856553fAdEfBaD \ --block 26427612 --rpc-url "$ETH_RPC_URL" cast block 26427612 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x1c5ef52eb0b586e49da2a11dc9f905cae4125008dc814d6781f53a142f6555ac
Scheduling rights: one 3-of-5 multisig proposes, executes, cancels
Observed onchain. TimelockController 0x69dDEa332723cF5407151aAF68B9b076557FCA93: hasRole(PROPOSER_ROLE / EXECUTOR_ROLE / CANCELLER_ROLE, Safe 0x8eec10616802Ef639CA55c98ac856553fAdEfBaD) = true; the timelock is its own admin; the Safe is 3-of-5 (v1.4.1, no modules).
Documented. docs.re.xyz (proposer roles): 'A Gnosis Safe ( 0x8eec10616802Ef639CA55c98ac856553fAdEfBaD) is the sole proposer, executor, and canceller on those timelocks'
cast call 0x69dDEa332723cF5407151aAF68B9b076557FCA93 \ "hasRole(bytes32,address)" 0xb09aa5aeb3702cfd50b6b62bc4532604938f21248a27a1d5ca736082b6819cc1 0x8eec10616802Ef639CA55c98ac856553fAdEfBaD \ --block 26427612 --rpc-url "$ETH_RPC_URL" cast block 26427612 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x1c5ef52eb0b586e49da2a11dc9f905cae4125008dc814d6781f53a142f6555ac
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of Re Protocol (reUSD / reUSDe) differs from what the protocol documents. It turns to the emerald 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.
Embed this badge (it updates when the status changes):
[](https://pacta.wtf/protocols/re/)
<a href="https://pacta.wtf/protocols/re/"><img src="https://pacta.wtf/badges/re.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/re.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/re.svg.
Maintaining Re Protocol (reUSD / reUSDe)? 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).