★ Sudden admin-rescue/ACL change without discussion
Spiko's assessment for RD-F-123 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Spiko is a corporate-governed no-DAO RWA issuer (PD-042 class). No public governance forum exists. Admin changes executed via 2-of-5 super-admin Safe (0xEBB418e1f8E8F26BdF7816A2cD25bE87c040E425) as routine corporate operations. USTBL proxy upgraded 2024-04-19; EUTBL Arbitrum upgraded 2024-10-25; no public pre-discussion for either. GitHub PR#23 (admin sanity-check config, April 2024) minimal discussion. No sudden unannounced emergency-rescue or ACL escalation detected in 180-day trailing window. Scored yellow per PD-042: absence of forum is structural to corporate governance model, not a red departure from stated norms. No Drift-class insider-implant signal detected.
Sources #
- TxUSTBL proxy deploy/upgrade tx — EtherscanUSTBL proxy initial upgrade tx 0x728d46f23e31b485d1a803dc6cc7b98196f2e59fab0d81d7e21a729435acb69b on 2024-04-19 — no public pre-discussionretrieved 2026-05-16
- Spiko 00-profile.md §6 governance topology00-profile.md §6 confirming no governance forum, no Snapshot space, no Governor contract — PD-042 corporate RWA classretrieved 2026-05-16
- spiko-tech/contracts closed PRs — GitHubspiko-tech/contracts PR#23 admin sanity-check April 2024 — minimal pre-discussion; no governance forum threadretrieved 2026-05-16
Methodology #
Determine whether any admin-rescue function or ACL change was committed to the repo or executed on-chain without corresponding public discussion in issues, PRs, or governance forum.
See the full factor methodology and distribution across all protocols →