CoinDesk reports that Brazil's securities regulator has set up a task force with a 60-day deadline to produce a tokenization proposal. The headline is the deadline, but the substance is the list of unresolved questions the task force actually has to answer: who owns a tokenized asset on paper, who custodies the private keys, what happens when a transaction needs to be reversed, and who is liable when the system fails. Those four questions show up in every serious tokenization framework, and they're harder than the technology itself.
This article covers why tokenization keeps stalling on the same set of questions regardless of jurisdiction, what each of Brazil's four focus areas actually requires regulators to decide, and why a compressed 60-day timeline is either a sign of confidence or a sign the hard parts are getting rushed.
Tokenization's technology problem was solved years ago
Tokenization — representing ownership of a real asset (a bond, a share, a fund unit) as a digital token on a blockchain — is not blocked by missing technology. Issuing a token that represents a claim on an asset has been straightforward since early smart contract platforms matured. What has consistently stalled tokenization at the regulatory level is a narrower, harder problem: making that token's ownership legally equivalent to the traditional security it represents.
Think of it like translating a legal contract into a new language. The words can be translated in an afternoon. Making sure the translated version holds up in a court in a different country — with different legal traditions, different definitions of ownership, different remedies when something goes wrong — is the part that takes years and involves lawyers, not engineers.
The four questions Brazil's task force has to answer
Official ownership records. Traditional securities have a registrar — a legally recognized entity whose records determine who owns what. A blockchain ledger can track token transfers perfectly, but the regulator has to decide whether that ledger is the official record, or whether it needs to be reconciled against a separate legal registrar. Get this wrong and you have two competing sources of truth for who owns an asset.
Custody standards for private keys. In traditional finance, custody rules (who can hold client assets, under what capital and insurance requirements) are well established for cash and paper securities. Applying those same protections to private keys — the cryptographic credentials that control a token — requires new standards, because losing a private key isn't like losing a paper certificate; there's often no reissuance process.
Transaction reversibility. Blockchain transactions are designed to be final. Traditional securities markets have established processes for reversing erroneous trades, fixing settlement failures, or complying with a court order to freeze or claw back assets. A tokenization framework has to decide how — or whether — those legal remedies can be exercised against something engineered to resist exactly that kind of intervention.
System liability. When a tokenized security transaction fails — a smart contract bug, an oracle error, a custody breach — someone has to be legally on the hook. Traditional finance has decades of precedent for allocating liability between exchanges, custodians, and clearing houses. None of that precedent maps cleanly onto a system where the "exchange" might be a smart contract with no legal personhood.
Tokenization frameworks don't stall on cryptography. They stall on deciding which legal tradition's answers to the ownership, custody, reversibility, and liability questions get imported into a new medium.
What a 60-day deadline signals
A tight, self-imposed 60-day deadline for a proposal (not final rules) reads two ways. It could signal that Brazil's regulator has already done enough groundwork on these four questions that a first proposal is achievable quickly — treating this as an accelerant on work already in motion. Or it could signal a race to produce something concrete before market pressure builds further, with the understanding that a first draft will iterate significantly before final rules land.
Either reading is consistent with the broader pattern in tokenization regulation globally: jurisdictions that move first on a proposal aren't necessarily moving first on quality. The IMF's own analysis of tokenization flagged that policy choices — not technology choices — determine whether tokenization strengthens or fragments financial markets, and those policy choices are exactly the four questions above.
What this means for builders
If you're building tokenization infrastructure with an eye on the Brazilian market, don't wait for final rules to start designing around the four open questions — build with a pluggable registrar interface, custody architecture that supports institutional-grade key management (not just self-custody), and transaction logic that can accommodate a legally mandated reversal path even if you don't expect to use it. Frameworks that get finalized quickly tend to reward infrastructure that anticipated the eventual answer rather than assumed the most permissive one.
Conclusion
Brazil's 60-day task force deadline is a proposal deadline, not a final-rules deadline, and the substance of what it needs to produce is the same four-question set every serious tokenization framework eventually confronts: ownership records, custody, reversibility, and liability. Watching how Brazil answers those questions will tell you more about where tokenization regulation is heading globally than the existence of the task force itself.