The Missing Link in Real-World Asset Tokenization: Security and Trust
Tokenization can unlock new opportunities, but without security and trust, the value remains at risk.
By Jenny Tseliou, Serenity Technology
At 23:47 UTC on May 23, 2026, someone began printing euros on Ethereum. They were not counterfeits in the usual sense. Every token came out of StablR’s own minting contract, carried StablR’s own name and passed every check a blockchain knows how to run.
StablR is a Malta-licensed electronic money institution that presents its EURR and USDR stablecoins as compliant with the EU’s MiCA rules, with Tether and Kraken among its investors. Its minting authority sat in a multisig wallet with three signers and a threshold of one, The Block reported, citing the security firm Blockaid. One signer’s private key was enough. The attacker added a new owner, removed the other two, and minted about 8.35 million USDR and 4.5 million EURR, roughly $13.5 million with nothing behind it. The same admin powers were then used to burn about 2.7 million EURR from a wallet that had been processing customer redemptions. USDR traded as low as 40 cents.
Blockaid called it “a governance and key-management issue.” The license was real and the smart contract code worked as written. Every one of those transactions was valid.
Real-world asset tokenization security depends on three links a blockchain cannot verify on its own: that the underlying asset exists in custody, that only authorized people can create or destroy tokens, and that each transfer was approved by its rightful owner. RWA.xyz tracked $38.95 billion in distributed tokenized real-world assets on October 21, 2026, held by about 5.27 million holders.
Most writing on tokenization worries about the first link, whether the gold, the bond or the building is really there. That worry is justified, and we have looked closely at what “backed by gold” actually promises. StablR failed somewhere else, and so did several of the most instructive incidents of the past year. They failed at the point where a person, through a key, tells the chain what is true.
what a blockchain can and cannot verify about a tokenized asset
A blockchain is very good at one question: was this transaction signed by a key that is allowed to sign it? It answers that question for every block, permanently, without asking anyone’s permission. It cannot answer three others. Does the asset exist? Was the key used by the person it belongs to? Did that person mean to do it?
The first is answered off-chain, by custodians, auditors and reserve reports, and even that answer has a legal layer underneath it. IOSCO, the global body of securities regulators, warned in its November 2025 report on tokenization that some structures “could leave investors uncertain about whether they own the underlying asset or just the crypto token,” according to Reuters.
The other two questions are answered by whoever controls the keys. A tokenized asset usually depends on at least three kinds: the key that creates and destroys tokens, the key that reports prices or reserves to the contract, and the key the holder uses to move what they own. Each one is a place where a real-world promise becomes an on-chain fact, and each one can be wrong while the chain stays perfectly consistent.
the key that prints the asset
On October 15, 2025, Paxos minted 300 trillion PYUSD, the stablecoin it issues for PayPal. The intended amount was $300 million. Paxos called it an internal error and sent the excess to a burn address, but not before Aave and other protocols froze PYUSD trading. Halborn’s analysis located the root cause in the architecture: PYUSD supply was managed by “a single externally owned account (EOA) with unlimited mint privileges.”
Nobody stole anything at Paxos, and that is what makes the case useful. The design that let a typo create 300 trillion dollars of tokens would have let a stolen key do the same, and seven months later at StablR a stolen key did. The difference between the two stories is intent. The chain could see neither.
Get Serenity Technology’s stories in your inbox
Join Medium for free to get updates from this writer.
For a tokenized gold product, the mint key is the link between the vault and the token supply. A proof-of-reserve feed can show that the bars are in the vault. It cannot show that the person who signed the last mint was the person entitled to sign it.
the key that reads the price
Oracles are the second bridge between the world and the contract, and they sign too. In July 2026 Ostium, a perpetuals exchange on Arbitrum, lost an estimated $18 million in a few minutes after price reports dated in the future were fed into its system. Halborn’s write-up says the attack reportedly relied on a compromised oracle private key, a root cause Ostium had not publicly confirmed at the time. The contract accepted a bitcoin price of $5,000 while the market sat near $60,000, because the report carried a valid signature. A gold token priced through an oracle inherits the same dependency.
the owner at the other end
The last key belongs to the holder. For almost all of those 5.27 million holders, ownership on the chain means control of an address. A smart contract does not know who its holder is. It knows which key signed. If that key is phished, copied from a cloud backup or used by someone else in the household, the contract will transfer a tokenized bond or a gram of gold exactly as it would for the owner. The question of who legally owns the asset afterward lands back in courts and paperwork, the world the token was supposed to make simpler.
real-world asset tokenization security starts with who signs
So the missing link in the title is not a missing technology. It is a missing fact: the identity of the person behind a signature, captured at the moment of signing. Higher multisig thresholds help, and at StablR a two-of-three threshold would have forced the attacker to compromise a second signer. Mint caps and timelocks help. None of them tells the contract which human approved the action.
That missing fact is the problem sGold is designed around. sGold is Serenity Technology’s dual-token framework for tokenized gold, pairing an audited, redeemable gold token with a separate utility layer. The gold is to be held as allocated metal with approved custodians, separate from sGold itself, and the framework is designed to publish reserve data through Chainlink Proof of Reserve, with Zoniqx and C-Gold Technologies handling lifecycle compliance and vaulting. What separates it from a plain gold token is the identity layer. sGold ties user access, ownership-related actions and transaction authorization to biometric identity, which the sGold whitepaper anchors in sAxess Pro, Serenity Technology’s biometric access control card, so that a fingerprint checked on the card stands behind each authorization. The intent is that a stolen key on its own should not be enough to move gold.
That design has not yet been tested by money. sGold says on its own site that the core platform and enterprise architecture are complete, that commercial implementation is underway, and that it has “intentionally not accepted client assets” before its operating framework is in place. Until that changes, everything above is architecture, not track record. A fingerprint also proves presence, not judgment. A person who approves the wrong transaction on purpose, or under pressure, still approves it. Biometrics close the gap between a key and a person. They do not close the gap between a person and a sound decision, and they do nothing for the first link, which still depends on custodians and auditors doing their jobs.
the link that stays human
The tokenization pitch usually ends with the asset: gold, bonds, buildings, finally on-chain. The incidents of the past year end somewhere else. At Paxos nobody attacked anything. At StablR the code did exactly what it was told. In both cases the token supply was wrong, because one key could change it and nothing asked who was holding that key.
StablR acknowledged the exploit about eight hours after the on-chain activity had stopped. The chain had recorded every step in real time, block by block, with perfect accuracy. It simply had no way of knowing who was taking them.
Jenny Tseliou is a contributor at Serenity Technology, covering digital asset security, tokenization, and real-world assets.
Serenity Technology (s.technology, formerly Serenity Shield) builds biometric security and recovery infrastructure for digital assets, including sGold, a dual-token framework for tokenized gold.
Related reading: Gold Entered the Digital Era. Four Promises Came With It. | The World Has $450 Trillion in Real Assets. Less Than $30 Billion Is on a Blockchain. | Serenity Presents: sAxess Pro
Common questions
What are the main security risks in real-world asset tokenization? The main risks sit where off-chain facts enter the chain: custody of the underlying asset, the keys that mint and burn tokens, the oracles that report prices and reserves, and the holder’s own keys. IOSCO’s 2025 report also flags legal uncertainty over whether investors own the asset or only the token. Recent losses, including StablR in May 2026, came from compromised or overpowered keys rather than broken smart contract code.
What happened in the StablR exploit? On May 23 and 24, 2026, an attacker used one compromised signer key on StablR’s one-of-three minting multisig to take control of the contract, mint about $13.5 million in unbacked USDR and EURR, and sell them on decentralized exchanges. USDR fell as low as $0.40. Blockaid described it as a governance and key-management failure, not a bug in the code.
How can I check whether a tokenized gold token is really backed? Look for four things: a named custodian holding allocated metal, independent attestations or proof-of-reserve data you can verify, published redemption terms, and a clear statement of what legal claim the token gives you. Proof of reserve shows that the gold exists. It does not show how many claims exist against it, or who controls minting.
How can a token issuer control who is allowed to mint or move tokens? Several approaches are used, often together. Multisig wallets such as Safe require several signers, and the threshold matters as much as the number of signers. MPC custody platforms such as Fireblocks and Copper split key material and enforce policy rules. Timelocks and mint caps limit what a single action can do. Permissioned token standards such as ERC-3643 tie holder addresses to verified identities. Biometric authorization, the approach behind Serenity Technology’s sGold and sAxess Pro, ties each approval to a fingerprint checked on dedicated hardware.
Is sGold live? Not commercially yet. sGold says its core platform and enterprise architecture are built, commercial implementation is underway, and it has deliberately not accepted client assets before its operating framework is complete. No launch date has been announced. The design pairs allocated gold in approved custody with biometric authorization of ownership actions and transactions.
