Argentina just turned the lights on for tokenized securities. Not hype, but actual plumbing that tells you who owns what, who can vote, and how those rights get exercised without breaking company law. If you’re an issuer eyeing blockchain rails or an investor wondering if a wallet address equals shareholder, this is for you.
The new regime sits inside the securities rulebook, not outside of it. Which means the old questions still matter: who is on the official register, how do instructions get to the meeting, and what happens if platforms don’t sync. Let’s break it down so you can make decisions without guessing.
| Aspect | What to Know |
|---|---|
| Regulatory runway | The CNV extended the tokenization sandbox through 31 Dec 2027 under RG 1150, keeping experimentation under supervision (Argentina.gob.ar / Resolución General 1150/2026). |
| Ownership proof | Investors can obtain certificates of holding with the legal effects of registered book entries, on request via the PSAV and ADCVN (Boletín Oficial — RG 1150/2026). |
| Voting mechanics | Tokens must be blocked once investors submit voting instructions, and instructions must reach the registral holder at least 5 days before the meeting (RG 1150, Art. 18). |
| PSAV limits | No more than 5 PSAVs per issuance, with mandatory interoperability and real time synchronization for traceability between on chain and registral records (RG 1150, Art. 5). |
| AML expectations | The CNV flagged new AML guidance in late July 2026, signaling updated obligations for PSAVs during the sandbox period (CNV regulatory list). |
| Record equivalence | Digital representations must remain equivalent to traditional book entry records, with the ADCVN as registral anchor. |
Core concepts you need to lock in
Argentina’s framework does not replace the company register with a blockchain. It connects them. Tokenized securities represent positions that must remain fully traceable to the official book entry system, typically anchored by the ADCVN, which is the collective depositary and registral reference for negotiable securities. PSAVs operate the tokenization rails, but the legal status of ownership still ties back to recognized records and procedures.
In practical terms, that means your wallet can hold a token that represents a share or bond, but legal effects hinge on registral equivalence. The regime pushes PSAVs to sync data in real time so the token and the official register never drift. It also forces clear workflows for corporate actions like votes and distributions. When investors give voting instructions, the tokens get locked, and the instructions follow a formal path up to the registral holder before the assembly cutoff.
For investors, the key change is access to verifiable proof. You can ask for a certificate of holding routed through the PSAV and issued by the ADCVN. That document lives in traditional law, not just on chain. For issuers, the message is clarity: pick a small set of interoperable PSAVs, map your data flows, and prove to the CNV that your smart contracts do what the corporate code expects.
Quick glossary
- RG 1150/2026 — The CNV’s resolution that expands tokenization rules and extends the sandbox to 31 Dec 2027, laying out voting, custody, and interoperability requirements.
- PSAV — A virtual asset service provider running tokenization infrastructure for an issuance, subject to limits and sync requirements, and key to AML/KYC controls.
- ADCVN — The collective securities depositary and registral node for book entry records. It issues certificates of holding that carry legal weight.
- Certificate of holding — A formal document that proves an investor’s position in a tokenized security, requestable via the PSAV and enforceable like a registered holding.
- Voting instruction lock — A rule that blocks tokens from the moment an investor submits voting instructions until the assembly ends, avoiding double voting or transfers during the process.
- Interoperability and sync — Mandatory real time reconciliation among PSAVs so token balances and the registral register match at all times.
Step by step playbook
- Define the security and rights precisely. Map the instrument’s rights in plain language first, then align token logic and off chain registers so there is one unambiguous source of truth.
- Select up to five PSAVs intentionally. The rule caps you at five. Choose for uptime, audited smart contracts, AML readiness, and native support for ADCVN workflows.
- Design the data bridge to the ADCVN. Set up event driven sync so every token mint, burn, transfer, and lock updates the registral records without lag.
- Codify the voting workflow. Bake in the lock on instruction, the five day delivery window to the registral holder, and confirmation receipts to investors.
- Stand up AML and KYC controls. Mirror CNV’s fresh AML expectations, including risk scoring for wallets and ongoing monitoring tied to PSAV onboarding.
- Publish investor facing docs. Explain how ownership is evidenced, how to request a certificate, how votes are submitted, and what happens if a platform outage occurs.
- Test failure modes. Simulate a PSAV going offline, a chain reorg, or an out of sync event. Document who can pause transfers, who must notify the ADCVN, and how to resume safely.
- Keep an audit trail. Store tamper evident logs of every balance change and instruction, linking on chain events with registral timestamps.
Who owns what, and how you prove it
Let’s start with the uncomfortable truth in tokenization: legal systems care about registers and documents. Argentina leans into that. RG 1150 lets investors request a certificate of holding, issued by the ADCVN at a PSAV’s request. Those certificates have the same legal effect as standard anotational records. That bridges the gap between a token balance and the courtroom or a corporate action desk. If you need to prove you owned 10,000 units on the record date, the certificate is the artifact that settles arguments.
Operationally, issuers should build a clear path inside the PSAV dashboard where investors can request a certificate tied to a specific date and time. On the back end, the PSAV queries the synchronized ledger, locks any pending movements if needed, and requests the certificate from the ADCVN. The document comes back with identifiers the company secretary and transfer agent will recognize.
Why this matters: token positions move faster than traditional settlement windows. If your corporate action has a Friday record date and tokens are still trading at T instant, the PSAV to ADCVN sync needs to prove holdings without ambiguity. Certificates of holding are how you anchor that proof in the legal system while keeping the token rails humming.
Voting rules and corporate actions that won’t trip you up
Voting is the stress test for any tokenized security because rights meet timing. Argentina’s rule forces discipline. Once an investor submits voting instructions, the tokens get blocked until the meeting ends. That eliminates last minute transfers that could break quorum or cause double counting. There is also a hard deadline in the chain of custody for those instructions. PSAVs must deliver the investor’s instructions to the registral holder at least five days before the assembly. That buffer lets the company finalize the roll without reconciling in real time on the day of the vote.
Issuers should treat that five day window as a stop sign. Anything that comes in late needs an explicit policy, which you should publish ahead of the meeting. Investors should plan around the lock. If you rely on those tokens for liquidity, get your trades done before sending instructions, or you’ll be stuck until the meeting closes.
Pro tip: run a dry run a month before your first assembly. Ask a few investors to submit dummy instructions, verify the lock triggers instantly, and confirm that the registral holder receives the file five business days before the test date. Document the timestamps.
Dividends and other actions ride the same infrastructure. If there is a cash distribution, the ADCVN register and the PSAV subledgers must agree on who is entitled as of the record date. If there’s a tokenized rights issue, your smart contract should prevent entitlement from moving after the ex date, mirroring how traditional depositories operate. Keep a single calendar of record dates, ex dates, payment dates, and voting dates, then make the PSAVs consume that calendar automatically.
Choosing an architecture that won’t box you in
There is no one size fits all architecture here. You need something compliant, but also something your ops team can actually run. Here’s a simple way to think about the options.
| Option | Pros | Cons | Best for |
|---|---|---|---|
| Single PSAV on a permissioned chain | Simplest sync, clean change control, tight latency | Single point of failure, vendor lock in, less market reach | Pilot issuances, small cap equities, private debt |
| Two to five interoperable PSAVs | Resilience, broader distribution, redundancy | Complex sync, harder incident response, more vendor management | Larger issuances that need multiple distribution channels |
| Public chain with permissioned token | Transparency, composability, potential secondary liquidity | KYC gating complexity, MEV considerations, education load for investors | Issuers seeking on chain ecosystem features and visibility |
Remember, RG 1150 caps you at five PSAVs per issuance and expects real time synchronization and traceability among them. If you spread too thin, your ops team will struggle to keep the registral records aligned. Start small, prove the loop from wallet to ADCVN, then scale distribution if the data bridge holds.
Regulatory anchors you can point to
This framework is not a policy speech, it’s written down. The CNV’s RG 1150, published in the Boletín Oficial, extends the sandbox and codifies the plumbing investors care about: certificates of holding, vote locks, timing rules, and PSAV coordination. The sandbox itself now runs until 31 December 2027, which buys time for real issuances to shake out bugs while staying under supervision. You can point your board or legal counsel at the text when they ask for the basis.
There’s also a live compliance angle. Within the last month on the CNV’s regulatory list, a new AML item appeared, indicating that PSAVs and tokenization participants should expect updated requirements on customer due diligence and monitoring while they operate under the sandbox. If you run a platform, sync your compliance roadmap to those signals, not just the tech roadmap.
Key references at first launch or diligence time: the sandbox extension and tokenization rules in RG 1150 on the government’s site, Article 18 on voting, Article 28 on certificates, and the AML update listed on the CNV timetable. These are the pegs you hang your procedures on. Link them in your policies and in your investor materials so everyone is reading from the same script: Argentina.gob.ar / Resolución General 1150/2026, Boletín Oficial — RG 1150/2026, and the CNV regulatory list.
Pitfalls and red flags
- Late voting instructions. If your PSAV cannot guarantee delivery to the registral holder five days in advance, you risk disenfranchising investors or delaying the meeting.
- Not implementing token locks. Skipping the lock on voting instructions opens the door to transfers that break quorum math and exposes you to challenges.
- Overlapping PSAV roles. More providers than you need means more sync points. Each is a potential source of reconciliation drift if monitoring is weak.
- Unclear proof of title. If investors don’t know how to request a certificate of holding, disputes will escalate quickly when money or votes are on the line.
- AML blind spots. Treat the new AML item as a living requirement. If your KYC is static and your wallet screening is one off, you’ll fall behind expectations.
- Poor incident playbooks. If a PSAV goes offline or the chain hiccups, who pauses transfers, who calls the ADCVN, and who signs the resumption notice. Write it down now.
If you want ongoing coverage of how these rules are playing out in the market and what other regulators are copying, keep an eye on Bitzo. We track the plumbing, not just the price charts.
Frequently Asked Questions
Does a wallet balance alone make me the legal owner under Argentine law?
No. The token represents your position, but legal effects ride on equivalence with the registral records anchored by the ADCVN. You can request a certificate of holding to evidence title for meetings or disputes.
How exactly does the voting lock work for tokenized shares?
Once you submit voting instructions through the PSAV, the corresponding tokens are blocked until the assembly ends. The PSAV must forward your instructions so the registral holder receives them at least five days before the meeting.
Can an issuance use unlimited platforms to distribute tokens?
No. RG 1150 caps designated PSAVs at five per issuance and requires those platforms to interoperate and synchronize in real time to keep traceability intact.
What happens if my PSAV goes down during a vote?
Your tokens should already be locked if you sent instructions. A good incident plan lets another PSAV, or the issuer under defined controls, coordinate with the ADCVN to complete the roll. Read the issuer’s contingency policy before you invest.
Are tokenized securities on public chains allowed?
The rule focuses on traceability and registral equivalence, not a single chain choice. Public chains with permissioned tokens can work if the PSAVs maintain KYC gates and keep the ADCVN sync tight.
How do I prove my holdings on a specific record date?
Request a certificate of holding via your PSAV. It’s issued by the ADCVN and carries the legal effects of a registered book entry at that date.
What AML checks apply to investors using PSAVs?
Expect full KYC and ongoing monitoring. The CNV recently posted a new AML item on its regulatory timetable, a signal that expectations for PSAVs are being updated during the sandbox.
