Forum Post Maps Who Can Upgrade 7 Tokenized Treasury, Gold Tokens
A read-only Ethereum Magicians post examined upgrade control for seven tokenized treasury and gold tokens, finding no delay on six of them.

A post published on the Ethereum Magicians forum on November 9, 2026, mapped the upgrade-control setup of seven tokenized treasury and gold fund tokens on Ethereum, reading the control structure directly from on-chain data rather than from issuer disclosures.
The author described the exercise as a snapshot taken on 9 Nov 2026 and said the check was read-only, with nothing tested against the live contracts.
What the On-Chain Snapshot Found
Per the post, of the seven tokens examined, three had upgrade control held by a single externally owned address — meaning no contract code, no multisig, and no on-chain delay standing between that one key and a contract upgrade. Two tokens used a Safe multisig configured 4-of-7, also without any on-chain delay found. One token used an older multisig arrangement configured 3-of-6, again with no delay identified. Only one of the seven tokens had a timelock in place, with a minimum delay of 24 hours before an upgrade could execute.
The author was explicit about the limits of the method. The post states plainly that the findings do not mean any private key is stored insecurely — keys could sit behind hardware security modules or multi-party computation setups that are invisible to someone reading the chain from outside. The post also does not claim that user assets are currently at risk, or that any of the seven issuers have done anything improper. It frames itself strictly as a structural read of who holds upgrade authority and how fast they could act, not an assessment of custody practices or issuer intent.
This distinction matters for how the findings should be read. A single externally owned address controlling an upgrade function is a different risk profile from a 4-of-7 multisig, even though both showed no on-chain delay in the post's snapshot. A multisig requires coordinated signing from multiple parties before an upgrade can be pushed; a single key does not. Neither configuration found in this snapshot includes a timelock, meaning token holders would have no advance public notice window before a contract change executes, beyond whatever private notice issuers might choose to give.
Tokenized treasuries and gold-backed tokens have expanded on Ethereum as issuers seek on-chain representations of traditional assets, a trend that sits adjacent to the broader growth of DeFi infrastructure built on upgradeable smart contracts. Upgradeability gives issuers a way to patch bugs or respond to regulatory change, but it also concentrates power over the contract in whoever holds the upgrade key, a tradeoff this post set out to document rather than resolve.
The post does not name the seven tokens or their issuers, and CoinsCipher has not independently verified the on-chain findings beyond what the forum post describes. What the public record does not yet show is whether any of the seven issuers maintain off-chain controls — such as HSM- or MPC-based key custody — that would meaningfully change the practical risk picture the post's structural snapshot implies.