Researchers at Alloc Init have proposed, in a September 24 paper, private Bitcoin transfers using zero-knowledge proofs without requiring a soft fork.

Alloc Init’s researchers Clara Shikhelman, Mikhail Komarov and Aleksei Moskvin published Shielded Bitcoin as a metaprotocol that uses Bitcoin to publish and order encrypted transaction data. Bitcoin nodes would not need to understand or enforce the privacy system’s rules.

Called Shielded Bitcoin, the proposed system borrows core ideas from Zcash, including encrypted notes, nullifiers and zero-knowledge proofs. It would conceal shielded senders, receivers, transferred amounts and links to earlier notes while leaving Bitcoin’s existing consensus rules unchanged.

The proposal remains research, not deployed Bitcoin software. Alloc Init has not announced a mainnet launch date, while a separate mechanism for moving BTC into and out of the shielded system remains under development. Founder Misha Komarov described the underlying technique as experimental during an interview published September 24.

Shielded Bitcoin moves privacy checks outside consensus

Under the proposed architecture, Bitcoin would function as what the researchers describe as a neutral publication and ordering layer. A shielded transaction would place encrypted notes, nullifiers and a zero-knowledge proof into data carried by an ordinary Bitcoin transaction.

Separate programs called indexers would read the data in Bitcoin’s established transaction order. An indexer would verify the zero-knowledge proof, check whether each nullifier had appeared before and update its view of the shielded system when the transaction passes those checks. Invalid shielded data could still enter the Bitcoin blockchain because Bitcoin itself would not enforce the metaprotocol. The indexer would simply reject it from Shielded Bitcoin’s state.

A sender would consume encrypted notes representing previously received value and create new notes for recipients. The proof would establish that the sender controls valid notes, has not created value from nothing and has balanced transaction inputs and outputs without exposing the underlying amounts or notes.

As crypto.news explained in its recent guide to zero-knowledge proofs, ZK systems can prove that a computation followed specified rules without revealing the private information used in that computation. Shielded Bitcoin applies that model to Bitcoin transfers, while its indexers handle verification outside Bitcoin consensus.

A dishonest indexer could provide stale information, omit transfers or delay wallet updates, the researchers said. Such an indexer would not gain control of a user’s spending key. Users could switch indexers or independently replay the shielded transaction history from Bitcoin.

How the Zcash-style design hides transaction links

Shielded Bitcoin closely follows the note model used by Zcash. Nullifiers identify when a note has been spent without publicly revealing which encrypted note produced the nullifier, allowing an indexer to reject double spending while keeping the transaction link hidden.

Komarov characterized the concept more simply in his September interview: “It’s basically Zcash.” He said users would place bitcoin into a private pool, receive encrypted notes and later spend, split or use those notes when withdrawing. Alloc Init intends to connect that system to Bitcoin through its PIPEs research.

Privacy would not make every part of the activity invisible. Public observers could still see when a Shielded Bitcoin transaction occurred, its timing, transaction fee, data size, number of notes consumed and created, and the Bitcoin transaction carrying the encrypted information. A recognizable Bitcoin wallet used to publish those transactions could reveal further information about the publisher.

The researchers provide separate read-only keys for viewing incoming or outgoing activity. Users could disclose selected transaction information to an accountant or counterparty without surrendering spending authority, though Alloc Init cautions that sharing a complete viewing key would reveal everything covered by that key.

In related coverage, crypto.news reported this week on expanding demand for privacy-focused crypto systems. The report cited ZecStats data showing 4.91 million ZEC in Zcash shielded pools, representing 29% of issued supply at the time.

Anonymity and quantum resistance remain contested

The proposal has drawn questions over how much privacy a new shielded pool could provide at launch. Developer Vadim Zavodil argued that Zcash already has years of shielded activity behind its anonymity set, while a new Bitcoin metaprotocol would begin with few participants.

“Privacy is a function of the crowd,” Zavodil wrote, arguing that an early Shielded Bitcoin user could have very few comparable transactions to blend into. His criticism focuses on practical anonymity from user behavior and pool size, not whether the cryptographic proof itself conceals its private inputs.

Alloc Init’s own explanation acknowledges the same general limitation. A large quantity of bitcoin entering a shielded system does not by itself create a strong anonymity set if only a few actors generate most notes or if individual wallets follow recognizable deposit, withdrawal or timing patterns.

Research on Zcash has documented similar behavioral problems. A peer-reviewed 2018 study found that transaction patterns could shrink the effective anonymity set even when the underlying shielded cryptography remained intact. The study examined an older Zcash implementation and predates several later upgrades.

Post-quantum researcher Pierre-Luc Dallaire-Demers raised a separate cryptographic concern. He described the construction as interesting but “not quantum resistant at all.” In a follow-up, he said he was examining what a fully post-quantum version could require if Bitcoin eventually adopts post-quantum signatures.

Komarov has given a more conditional account. His interview with Unchained said the shielded pool’s eventual route to quantum resistance would depend partly on Bitcoin’s own signature system. Alloc Init has not presented Shielded Bitcoin as a finished post-quantum implementation.

Zerocash co-author and StarkWare CEO Eli Ben-Sasson responded more favorably to the project’s direction, while noting that he had not yet reviewed the full paper. His support therefore represented an initial reaction, not a technical endorsement of the construction.

Shielded Bitcoin still needs its Bitcoin entry and exit system

A major unfinished component is the movement of actual BTC into and out of the shielded metaprotocol. Alloc Init’s September 24 explanation says the current paper specifies shielded transfers after value is inside the system, while a forthcoming paper will describe peg-ins and peg-outs using PIPEs.

PIPEs relies on witness encryption to make access to a Bitcoin signing key conditional on proof that specified rules were followed. Komarov explained to the Bitcoin Development Mailing List in February that PIPEs v2 could emulate certain covenant and zero-knowledge verification functions without requiring a Bitcoin soft fork.

The cryptographic machinery remains computationally heavy. Komarov’s February disclosure put a PIPEs v2 ciphertext at roughly 330 TB of storage, while stating that researchers knew a route that could eventually reduce the figure toward 100 GB. The smaller target had not been achieved in that publication.

Shielded transfers would consume more Bitcoin block space as well. Komarov told Unchained that an encrypted shielded payload would run around 700 virtual bytes, compared with roughly 100 to 200 virtual bytes for a typical Bitcoin transaction. He estimated the resulting miner fee could be approximately four times higher.

No launch date has been set. Komarov said the team is gathering technical feedback while continuing work on the experimental construction, including open attempts to find faults in the design and work with witness-encryption researcher Sanjam Garg.

The next publicly scheduled presentation is set for September 28, 2026. The Bitcoin Treasuries Conference agenda lists Alloc Init researcher Clara Shikhelman for a five-minute session titled “Shielded Bitcoin: Private Transfers on Bitcoin L1” in New York.

Alloc Init researchers have outlined a new approach they say could bring Zcash-style shielded transfers to Bitcoin without requiring a soft fork of the base protocol. The proposal, titled Shielded Bitcoin, aims to hide transaction amounts, senders, receivers, and linkages to previously spent funds by relying on encrypted “notes” and zero-knowledge proofs.

Published on Thursday by Clara Shikhelman, Mikhail Komarov, and Aleksei Moskvin, the design is intended to use Bitcoin as a kind of settlement and ordering layer—while separate software handles verification and state reconstruction for the privacy system. The result is a privacy overlay that, in theory, avoids asking miners or the wider network to enforce new rules.

Key takeaways

• Shielded Bitcoin proposes private transfers on top of Bitcoin without a soft fork by treating Bitcoin as an “ordering layer” rather than enforcing privacy rules at consensus.
• The system mirrors core Zcash components—encrypted notes, nullifiers to prevent double-spending, and zero-knowledge proofs for transaction validity.
• Privacy quality would depend on how quickly a meaningful anonymity set forms; critics argue early deposits may provide limited crowd-mixing.
• Commentators also raised open questions about cryptographic robustness and the practicality of the scheme.

How the proposal avoids a soft fork

In traditional privacy upgrades, hiding transaction details often requires changes that the network enforces. Shielded Bitcoin instead reframes the problem: rather than embedding privacy checks into Bitcoin’s mining and validation rules, the researchers propose using Bitcoin as “a neutral publication and ordering layer.”

Under this model, indexers—separate software components—would verify zero-knowledge proofs, confirm that the underlying funds have not been double-spent, and then reconstruct the evolving state of the shielded system. The encrypted notes and proofs would be published using Bitcoin transactions, but the privacy logic would be validated externally.

The paper’s key architectural point is that shielded validity does not have to be enforced by consensus for users to benefit from a private transfer—at least within the constraints of what other parties (wallets, relayers, and indexers) choose to accept and verify.

Why the Zcash-style design matters

The proposal explicitly draws from Zcash’s architecture. According to the paper, Shielded Bitcoin would use:

• Encrypted notes to conceal who owns funds and how much value is being moved.
• Public nullifiers that mark notes as spent, preventing double-spending without revealing note contents.
• Zero-knowledge proofs that demonstrate transaction validity while keeping sensitive details hidden.

However, Shielded Bitcoin differs from Zcash in one fundamental way: it is not presented as a separate shielded blockchain with its own consensus mechanism. Instead, it aims to plug a Zcash-like privacy system into Bitcoin’s existing infrastructure, using encrypted transaction artifacts and proof verification performed by external components.

For Bitcoin users and developers, the practical implication is clear: a privacy layer that can be deployed without consensus changes could lower the friction associated with privacy tooling. It also shifts the engineering burden toward wallets and verification infrastructure rather than requiring network-wide upgrades.

Early privacy may be weaker than Zcash’s anonymity set

Developer Vadim Zavodil was among the most pointed critics. Posting on X, Zavodil argued that a large share of the privacy “stack” already exists in Zcash and questioned how much privacy a newly launched shielded system could deliver immediately.

“Privacy is a function of the crowd. Zcash has a real shielded pool built over years of use. A brand new metaprotocol starts at zero, so your first private transfer hides in a crowd of one.”

In response, the Shielded Bitcoin researchers acknowledged the same concern. In a companion explanation published alongside the proposal on Notion, they said that large deposits do not automatically translate into a large anonymity set. They also warned that observers might still be able to infer relationships between transfers if a small number of actors create most notes or if wallets produce distinctive behavior.

This tension highlights a common theme for privacy systems: cryptographic soundness does not automatically guarantee anonymity. Shielded designs often depend on how users actually use them—how many participants join, how uniformly transactions behave, and whether patterns can be linked over time.

Questions extend beyond privacy: post-quantum concerns and intent

Another line of critique came from Pierre-Luc Dallaire-Demers, founder of post-quantum cryptography firm Pauli Group. He said the construction was “not quantum resistant at all,” framing the proposal as interesting while still leaving cryptographic assumptions in question.

Dallaire-Demers later indicated he was exploring what a fully post-quantum version could look like, contingent on Bitcoin eventually adopting a post-quantum signature scheme.

Supporters, meanwhile, emphasized the broader goal of bringing privacy to Bitcoin. Eli Ben-Sasson, a Zerocash co-author and CEO of StarkWare, responded more positively to the announcement. Although he said he had not yet read the full paper, Ben-Sasson argued that the intent behind Zerocash—preceding Zcash—was to bring privacy to Bitcoin. He said he would like to see the vision of privacy and scalability through zero-knowledge proofs materialize on Bitcoin’s base layer.

Taken together, these reactions underscore that Shielded Bitcoin is not being debated only on whether it “works” on paper. It’s also being evaluated on longer-term assumptions—particularly around anonymity set formation and the resilience of the cryptography to future threats.

As the proposal circulates among developers, investors and builders will likely watch for two practical follow-ups: whether any wallet or indexer implementation demonstrates credible usability and whether the system’s privacy properties improve as more independent users participate and diversify their behavior.

Ondo Finance has denied a report based on three anonymous sources that the tokenization company was offered to prospective buyers after founder Nathan Allman died on May 25, 2026.

CoinDesk reported that outreach to prospective buyers took place sometime after Allman’s death, citing three people familiar with the matter. Two sources placed the outreach after May 25, but the report said it could not establish who initiated the effort or what valuation may have been discussed.

Ondo rejected the account. A company spokesperson called reports of a possible sale “wholly untrue” and said nobody at the company had sought buyers or authorized another party to do so. Allman’s estate declined to comment to CoinDesk.

She described the breach as the digital version of slipping forged withdrawal slips through a bank’s own teller window. The vault keys never left the building. Someone got into the office that prepares the slips, created paperwork that looked official, and sent it through the same approval window the bank uses every day. To the system doing the approving, it looked like a normal payout.

The outflow, however, has been stopped, Chen confirmed.

“Loss containment is confirmed. No further unauthorized transfers are possible. The specific method of system intrusion remains under active investigation. A full technical report will follow once confirmed,” she said.

The breach

The breach surfaced when Bitget’s systems flagged unauthorized transfers from some exchange hot wallets at 18:31 UTC on Sept. 24. A hot wallet stays connected to the internet so funds can move quickly. For an exchange, it is a temporary liquidity hub, analogous to an online cash drawer that handles instant trades, deposits, and withdrawals.

Chen said the hack also reached the warm-wallet layer. That is a semi-connected buffer between the automated hot wallets and fully offline cold storage. It tops up the hot wallet when balances run low and pulls excess deposits off the internet so too much capital is not left exposed.

Brazil’s central bank has required covered institutions to report virtual-asset transfers worth at least $10,000 to or from self-custody wallets beginning October 1, 2026.

The Central Bank of Brazil published Resolution BCB No. 588 on September 23, amending Circular No. 3,978, the anti-money-laundering and counter-terrorist-financing framework for institutions under its supervision. The new item added to Article 49 covers transfers of virtual assets to or from self-custodied wallets when the value equals or exceeds the equivalent of $10,000.

Brazil’s $10K self-custody rule starts October 1

Resolution 588 places qualifying self-custody transfers inside the category of specific operations that covered institutions must communicate to the Financial Activities Control Council, known as Coaf. The rule applies in both directions, covering transfers sent to a self-custody wallet and transfers received from one.

The resolution does not prohibit self-custody, cap the amount a user can transfer, or state that a qualifying transaction must be blocked. B3 reported that the $10,000 figure is a mandatory reporting threshold instead of a transaction limit. The central bank has said self-custody can reduce information available for monitoring because users directly control the private keys.

By amending Article 49 of Circular 3,978, the new provision sits alongside mandatory reports for certain large cash operations and foreign-currency cash transactions. Resolution 588 adds foreign-exchange transactions involving at least $10,000 in physical foreign currency and virtual-asset transfers involving self-custody wallets at the same dollar threshold.

Resolution 588 differs from Brazil’s 24-hour hold

The October reporting requirement is separate from Resolution BCB No. 584, an anti-fraud rule published in August. Resolution 584 covers certain outbound virtual-asset transfers to foreign service providers or self-custody wallets and permits a temporary retention period of up to 24 hours under defined risk controls from January 1, 2027. Brazil’s Finance Ministry explained the measure after the central bank adopted it.

As crypto.news previously reported, Brazil’s 24-hour hold on qualifying $10,000 crypto transfers uses a different threshold calculation. Resolution 584 can apply when one transfer exceeds the threshold or when the same customer’s transfers reach the threshold in aggregate during one day. Providers can release a transfer before the full 24 hours after completing the required risk review.

Resolution 588 contains no equivalent same-day aggregation language for its automatic reporting trigger. Its text refers to a transfer with a value equal to or above $10,000. A Brazilian regulatory analysis published after the September rules found the same distinction: Resolution 584 expressly aggregates same-day transfers, while Resolution 588 does not state such a formula.

The absence of an automatic aggregation clause does not remove separate suspicious-activity monitoring obligations. Circular 3,978 requires covered institutions to assess transactions or situations that may indicate money laundering or terrorist financing, with suspicious cases subject to a separate reporting process.

Covered institutions must send reports through AML controls

Article 49 of Circular 3,978 requires institutions within its scope to communicate listed transactions to Coaf. The circular’s existing timing rule requires Article 49 communications by the next business day after the transaction or relevant provision occurs, placing the new self-custody category inside an established compliance process.

The same circular prevents institutions from informing customers or third parties that a Coaf communication has been made. Resolution 588 does not create a direct filing obligation for an individual simply because the person controls a self-custody wallet; the reporting duty operates through institutions covered by the central bank’s AML framework when they handle a qualifying transfer.

In its public explanation, the central bank said self-custody can “reduce the availability of information for monitoring and risk assessment purposes.” The statement distinguished user-controlled wallets from assets held by an institution authorized by the central bank, where customer and transaction records remain inside a supervised entity.

Resolution 588 itself does not create a new crypto tax rate, fee, or transaction levy. The measure amends Brazil’s AML/CFT reporting framework, while crypto taxation operates under separate tax rules. Crypto.news has previously covered Brazil’s separate crypto tax framework, including rules affecting gains from assets held in self-custody.

Brazil is rolling out crypto supervision in stages

Resolution 588 arrives within a series of virtual-asset rules introduced since 2025. As crypto.news reported, Brazil’s capital requirements for crypto service providers now sit alongside licensing, governance, security and compliance requirements. A separate 2026 rule has restricted virtual assets from settling payments inside regulated cross-border electronic foreign-exchange channels. Brazil’s cross-border crypto payment restrictions cover the supervised eFX system without banning ordinary crypto transfers outside that channel.

A separate central bank measure, Resolution BCB No. 589, was issued on September 23 alongside Resolution 588. It changes rules for virtual-asset service providers, including supervisory information covering customer balances, custody positions, proof of reserves and customer assets committed to staking. Provisions governing those data submissions take effect on January 1, 2027.

Resolution 589 changes another operational deadline for institutions dealing with crypto service providers. From November 6, 2026, financial institutions, payment institutions and other entities authorized by the central bank face restrictions on carrying out or facilitating virtual-asset market operations with counterparties that are not authorized to operate in Brazil, subject to the exceptions in the applicable regulation.

Researchers at the cryptography research firm Alloc Init have proposed a system for bringing Zcash-style private transfers to Bitcoin without requiring a soft fork. 

The proposal, called Shielded Bitcoin, would conceal transaction amounts, senders, receivers and links to previously spent funds using encrypted notes and zero-knowledge proofs. The paper was published on Thursday by Clara Shikhelman, Mikhail Komarov and Aleksei Moskvin.

The proposal offers a potential path to stronger privacy for Bitcoin users without requiring consensus changes to the base protocol.

Instead of having miners enforce the privacy protocol, Shielded Bitcoin would use Bitcoin as “a neutral publication and ordering layer,” the researchers wrote. Separate software called indexers would then verify zero-knowledge proofs, check that funds haven’t been double-spent, and reconstruct the state of the shielded system.

Shielded Bitcoin’s design explicitly draws from Zcash’s architecture. The researchers said it similarly uses encrypted notes, public nullifiers that mark notes as spent, and zero-knowledge proofs that show transactions are valid. Unlike Zcash, Shielded Bitcoin would not operate its own blockchain or consensus mechanism.

Shielded Bitcoin draws mixed reactions 

Developer Vadim Zavodil criticized the proposal on X, arguing that much of its privacy stack had already been implemented by Zcash. He questioned how much privacy a newly launched system could initially provide, arguing that a new shielded pool would start without the anonymity set Zcash has accumulated over years of use. 

“Privacy is a function of the crowd. Zcash has a real shielded pool built over years,” he wrote. “A brand new metaprotocol starts at zero, so your first private transfer hides in a crowd of one.”

In a companion post explaining the proposal, the Shielded Bitcoin researchers acknowledged a similar limitation, saying that large deposits do not automatically create a large anonymity set. They said observers may still be able to narrow down relationships between transfers if a small number of actors create most notes or wallets exhibit distinctive behavior.

Related: Zcash’s November upgrade could freeze funds in legacy Sprout pool

Pierre-Luc Dallaire-Demers, founder of post-quantum cryptography firm Pauli Group, raised a separate issue, describing the construction as interesting but “not quantum resistant at all.” Dallaire-Demers later said he was exploring what a fully post-quantum version could look like, assuming Bitcoin eventually adopts a post-quantum signature scheme.

Zerocash co-author and StarkWare CEO Eli Ben-Sasson was more supportive of the proposal’s direction. In response to Alloc Init’s announcement, Ben-Sasson said the original intent behind the Zerocash paper, which preceded Zcash, was to bring privacy to Bitcoin.

Ben-Sasson said he had not yet read the Shielded Bitcoin paper but would like to see the vision of privacy and scalability through zero-knowledge proofs materialize on Bitcoin’s base layer.

Magazine: Winners and losers of the SEC’s new tokenized stocks rules

Bitget has said its preliminary probe into a $351.6 million wallet breach found no private-key leak, while withdrawals remain suspended after unauthorized transfers on September 24, 2026.

Bitget’s official security notice states that its systems detected the transfers at 18:31 UTC and activated emergency procedures within minutes. The exchange estimated that approximately $351.6 million in assets were affected and said the incident reached portions of its hot and warm wallet layers. Cold wallets remained secure under Bitget’s internal three-tier classification, the company said.

The exchange temporarily stopped withdrawals while leaving deposits and trading open. Bitget said customer account balances remained accurate and its User Protection Fund, valued at more than $464 million, could cover the estimated loss. Law enforcement agencies and on-chain security firms have been notified, while addresses tied to the abnormal transfers have been flagged.

Bitget says private keys were not exposed

During a live Q&A after the breach, CEO Gracy Chen said investigators had ruled out a leak of private keys used by Bitget’s cold, warm and hot wallets. Chen said attackers entered Bitget’s systems and transferred funds directly, without using customer withdrawal requests. Investigators were still working to determine the precise entry point.

A report on the same live session said Bitget’s security team had identified part of the attack route. The preliminary finding described a compromise of a core backend wallet service, where false transfer data reached the exchange’s approval-signature process. Bitget has not yet published the technical evidence behind that finding, leaving the exact intrusion method under review.

Chen said measures intended to prevent further outflows had been completed. Engineering teams were still repairing systems, strengthening security controls and preparing withdrawal services for reopening. No fixed restart time had been announced by early September 25.

The first public notice had avoided naming an attack method. Bitget wrote, “We will not speculate on the attack vector until the investigation is complete.” Its subsequent backend-system finding therefore remains preliminary until the promised root-cause report is released.

As crypto.news reported after the $1.4 billion Bybit theft in 2025, forensic investigators traced that attack to compromised Safe infrastructure. Investigators said Bybit’s own security systems remained intact during that incident.

On-chain tracking puts XRP at the top of stolen assets

On-chain estimates have continued changing as researchers identify more addresses and assets. Lookonchain placed the stolen portfolio at roughly $356.8 million using token prices when it published its update, slightly above Bitget’s approximately $351.6 million internal estimate. The figures come from separate accounting methods and should not be treated as identical measurements.

Lookonchain listed 102.93 million XRP worth $157.48 million as the largest component. Its breakdown included 31,890 ETH valued near $85.75 million, 34.75 million USDT, 21.05 million USDC, 19.67 million USD₮0, 3,000 XAUt, 12,719 BNB, 821,012 AVAX and 20.59 million TRX. The figures remain an external on-chain estimate, not Bitget’s final transaction-level accounting.

The Federal Reserve has released proposed rules aimed at tightening oversight of stablecoin issuers as the U.S. works to implement the GENIUS Act. The proposals set out how Fed-supervised entities would be required to hold reserves, manage risk, handle redemptions, and report key information about their stablecoins.

While the GENIUS Act already mandates that stablecoins be backed on a one-to-one basis with specified reserve assets, the Fed’s plan would add more granular requirements—especially around capital levels tied to operational risk, credit-related risks, and standardized reporting and assurance.

Key takeaways

• The Fed’s proposal would require operational-risk capital charges for stablecoin issuers, scaling based on the amount of stablecoins outstanding.
• Issuers would generally need to process redemptions within two business days and notify the Fed if reserves fall below required one-to-one backing.
• Monthly reserve and outstanding stablecoin reporting would be required, with disclosures examined by a registered public accounting firm and certified by the issuer’s CEO and CFO.
• A separate Fed proposal would create a pathway for Fed-supervised banks to seek approval to issue payment stablecoins through subsidiaries.
• Fed Governor Michael Barr supports the direction of the framework but says stablecoin reliability during market stress still needs further work.

What the GENIUS Act already requires—and what the Fed is adding

Under the GENIUS Act, stablecoin issuers must maintain reserves backing their tokens on a one-to-one basis and can only hold certain types of assets. These include cash, bank deposits, and short-term U.S. Treasurys, among other permitted instruments. The law also assigns federal regulators the task of writing the more detailed capital, reserve-diversification, and risk-management rules.

According to the Fed’s published documents, the agency’s proposals are intended to translate those statutory requirements into day-to-day supervisory expectations for issuers under Fed oversight.

Operational-risk capital, redemptions, and reserve shortfalls

One central piece of the Fed’s proposal is a capital framework tied to operational risk. As outlined in the Fed’s plan, issuers would face an operational-risk capital charge calculated as follows: 2% of the first $20 billion in stablecoins outstanding, 1.5% of the next $30 billion, and 1% of amounts above $50 billion. In addition to that operational-risk charge, the proposal contemplates further capital requirements linked to credit and operational risks.

On liquidity and redemption mechanics, the proposal would generally require issuers to process redemptions within two business days. If an issuer’s reserves drop below the one-to-one backing threshold, the issuer would have to notify the Fed. The issuer would then need to either restore reserves under a remediation plan or liquidate the reserves and redeem outstanding stablecoins.

For investors and traders, these elements matter because they directly affect the feasibility of exiting a stablecoin position when market conditions deteriorate or when an issuer faces stress on its reserve composition and operational controls.

Monthly disclosures and external verification

The Fed’s proposal also emphasizes transparency and accountability. Issuers would be expected to publish monthly reports covering their outstanding stablecoin balances as well as the value and composition of reserves backing those tokens.

Those disclosures would not be limited to internal attestations. The proposals call for the disclosures to be examined by a registered public accounting firm, and for certification by the issuer’s CEO and CFO.

This structure—audited examination plus senior executive sign-off—could create stronger compliance incentives for issuers, while giving market participants more consistent and comparable information to evaluate reserve backing over time.

Bank participation through subsidiaries: a separate application framework

In addition to rules for stablecoin issuers, the Fed also released a separate proposal intended to establish an application process for Fed-supervised banks that want approval to issue payment stablecoins through subsidiaries.

As described in the Fed’s second proposal, banks would be required to submit a business plan and financial information as part of the approval process. The separate track suggests the Fed is attempting to clarify how regulated banks can participate in the stablecoin ecosystem while remaining within a defined supervisory structure.

Barr’s support, and the remaining reliability questions

Fed Governor Michael Barr backed the proposals on Thursday but argued that more work is needed before stablecoins can be considered reliable payment instruments. Barr said that “stablecoins will only be stable if they can be reliably and promptly redeemed at par in a range of conditions,” including during market stress, situations where even liquid government debt may come under pressure, and episodes of strain affecting a specific issuer or related entities.

In remarks tied to the Fed’s announcement, Barr indicated he was encouraged by proposed limits on reserve assets and by standardized capital requirements. At the same time, he urged public feedback on whether the framework adequately addresses interest-rate and foreign-currency risks.

Barr also raised questions about how universal redemption rights should be established in the final rule. He highlighted concern about an approach that could limit the Fed’s ability to take supervisory or enforcement action over an anti-money laundering deficiency unless the problem is deemed “significant or systemic.”

For market participants, Barr’s comments underscore a key tension: the rules aim to formalize backing and capital adequacy, but the final design will be judged on whether it holds up under real-world stress scenarios, not only in normal periods.

Public comment period and GENIUS Act implementation timing

The Fed’s proposals are open for public comment for 60 days after publication in the Federal Register, according to the Fed’s announcements. That comment window may determine how the capital formulas, redemption expectations, reporting requirements, and risk treatment ultimately look in final form.

The GENIUS Act is scheduled to take effect on Jan. 18, 2027, or 120 days after federal regulators issue final implementing rules, whichever comes first. As the rulemaking process advances, readers should watch how regulators refine stress-testing expectations, define the final contours of redemption rights, and decide how operational and financial risk controls translate into practical reliability for users.