Publicly traded companies held 1,264,867 BTC as of July 3, 2026, roughly 6.02% of Bitcoin's maximum supply and about $79 billion in value (Source: BitcoinTreasuries.net data reported by Wu Blockchain). 

Hinkal provides privacy infrastructure for stablecoin payments and on-chain financial operations, letting businesses settle, pay out, and manage treasury across public chains while balances, counterparties, and amounts stay confidential, without changing wallets, chains, custody, or compliance controls. 

Corporate treasury has moved on-chain faster than corporate disclosure practice has adapted, and the gap is now measurable: every balance, every rebalance, every payroll run, every vendor settlement, and every reserve drawdown is written to a permanent public ledger that competitors, counterparties, and attackers read for free. 

The exposure is not limited to holdings, and extends to compensation structure, commercial relationships, burn rate, and runway. 

This report maps the full exposure surface of a public corporate wallet in 2026, quantifies what each layer reveals, shows how an analyst reconstructs a treasury from public data, explains why the common workarounds fail, and sets out how to keep settlement verifiable and auditable without publishing the underlying business.

[[KEY_TAKEAWAYS]]

Report Scope and Method

This report covers exposure created by corporate use of public blockchains, across four categories: balances, flows, payroll and vendor payouts, and liquidity or runway indicators. 

It draws on 2026 holdings data from BitcoinTreasuries.net, The Block, DefiLlama, and the CEBE tracker, SEC filings from Strive and BitMine Immersion Technologies, on-chain attribution published by Arkham Intelligence, stablecoin payment research from McKinsey and Artemis, BCG, and Bessemer, and security incident reporting from CertiK.

Two boundaries are worth stating up front:

1. This is not an argument against on-chain treasury operations. The rails are faster, cheaper, and more programmable than correspondent banking, and adoption data settled that argument. 
2. Exposure is treated here as an operational cost category rather than an ideological objection. 

Where sources disagree on a figure, both are given. Where a number is derived rather than reported, the inputs are shown.

The 2026 Baseline: How Much Corporate Capital Is Publicly Readable

Corporate crypto treasury stopped being a curiosity and became a balance sheet category.

• Public company Bitcoin holdings: 1,264,867 BTC, approximately 6.02% of the 21 million supply, valued near $79 billion as of July 3, 2026 (Source: BitcoinTreasuries.net via Wu Blockchain). A separate tracker put the figure at 1,267,251 BTC across roughly 85 companies with a Bitcoin NAV near $82.2 billion in the same window (Source: The Block, July 2026).
• Year-to-date accumulation: a net 166,984 BTC added by public companies through early July 2026, against approximately 81,153 BTC mined over the same stretch, with around 110,000 BTC bought in Q2 2026 alone (Source: Cryptobriefing citing BitcoinTreasuries.net).
• Total digital asset treasury value: $134 billion held by Digital Asset Treasury Companies as of January 1, 2026, up 137.2% year over year from $56.5 billion (Source: Hinkal, 2026 analysis).
• Ethereum: approximately 7.67 million ETH in tracked institutional and public company holdings, about 6.35% of circulating supply and $13.8 billion to $14.7 billion in value (Source: DefiLlama, July 2026).
• Solana: approximately 16.8 million SOL across about six public companies, with a combined NAV near $1.3 billion as of July 23, 2026 (Source: The Block).

Every figure above describes capital sitting in wallets that publish their own activity. Filings report these positions quarterly. The chains report them continuously, and they report far more than the position.

Exposure Layer 1: Balances

The first thing a public wallet publishes is how much you have, and concentration makes that unusually legible.

Strategy holds between 843,775 and 847,363 BTC depending on the reporting date, roughly two thirds of all public company Bitcoin and about 4% of total supply, with an aggregate cost basis near $63.7 billion and an average purchase price around $75,500 (Source: Cryptobriefing, July 2026). Twenty One Capital holds approximately 43,514 BTC, Metaplanet approximately 43,000 BTC, and MARA Holdings approximately 36,303 BTC (Source: BitcoinTreasuries.net via Wu Blockchain). 

The top 20 firms account for more than 90% of public corporate Bitcoin in most 2026 rankings.

Attribution turns that concentration into a live feed. Arkham Intelligence verified approximately 83% of Strategy's Bitcoin position directly on-chain in mid-July 2026, with roughly 184,000 BTC identified as sitting with a custodian (Source: Arkham Intelligence). That is the number that matters for this report. Attribution is not theoretical. It is a commercial product, and it works.

On-chain balance visibility differs from filed disclosure in three ways that matter operationally. 

• Frequency: a filing is a snapshot on a schedule you control, while a wallet is a live feed you do not. 
• Granularity: filings report aggregate positions, while chains report individual address clusters, custody splits, and the exact composition of every wallet in the cluster. 
• Scope: filings report the treasury asset, while wallets report everything the same cluster touches, including operating stablecoin balances, gas wallets, bridge positions, staking deposits, and DeFi collateral.

BitMine Immersion Technologies disclosed 5,777,468 ETH with approximately 85% staked, alongside $385 million in cash and marketable securities and 207 BTC (Source: BitMine 8-K, July 20, 2026). The staking position, the validator relationships, and the reward flows are all independently observable regardless of what the filing says.

For companies that are not treasury vehicles, and this is the larger group, balance exposure is pure downside. A payments company, an exchange, a fintech, or an iGaming operator gains nothing from publishing its float, and loses leverage in every negotiation where the counterparty can read it.

Exposure Layer 2: Flows and Timing

Balances are a photograph. Flows are the film, and they are more revealing.

Every acquisition publishes size, price band, timing, and often the venue. Digital asset treasury companies deployed at least $49.7 billion on crypto purchases in activity carrying into 2026 tracking, each creating a permanent record of when, how much, and through whom (Source: Hinkal, 2026 analysis). Q3 2025 alone accounted for roughly $25 billion of deployment, while early 2026 monthly inflows slowed sharply, to around $555 million in one reported low period. 

Anyone tracking those wallets watched the slowdown in real time, before it appeared in commentary.

Sales are more sensitive still, because a sale by a self-described permanent holder is a signal about liquidity, not about price.

• Bitdeer emptied its corporate Bitcoin treasury entirely by February 20, 2026, liquidating a remaining 943 BTC to fund an AI data centre pivot.
• MARA Holdings sold approximately 15,133 BTC between March 4 and March 25, 2026 for around $1.1 billion, associated with debt retirement.
• Nakamoto Inc. sold approximately 284 BTC for $20 million in March 2026 for working capital, with a significant portion of remaining holdings pledged as collateral.
• Strategy sold roughly 3,588 BTC around late June and early July 2026, plus a smaller 32 BTC tranche in late May, primarily to fund preferred distributions and replenish USD reserves (Source: Cryptobriefing, July 2026).
• Satsuma Technology shareholders approved full liquidation of the remaining 668 BTC, around $43.5 million, on July 21, 2026.
• Smarter Web Company sold 178 BTC on July 23, 2026 at an average near $65,762 to repay a convertible instrument ahead of maturity.

Read as a set, those events describe a sector rotating from accumulation to liquidity management. Each company published that rotation itself, in advance of explaining it. The timing gap between the on-chain movement and the press release is the exact window in which the information is worth the most to someone else.

Flow exposure also covers what a company never intends to announce: the treasury desk testing a new venue with a small transfer before a large one, the bridge route chosen for a cross-chain rebalance, the market maker whose address receives the block, and the pattern of splitting a large order across days. Execution strategy is a competitive asset. On a public chain it is a public document.

Exposure Layer 3: Payroll and Compensation

Payroll is the clearest illustration that exposure, not cost or speed, is the binding constraint on on-chain finance.

Fewer than 1% of businesses run payroll on public-chain crypto in 2026, and the reason cited consistently is that doing so permanently publishes every salary, every bonus, every contractor rate, and the treasury balance funding them (Source: Paxos Labs, 2026). The rails are not the problem. Stablecoin transfers settle in seconds at sub-cent cost across most networks, against two to five days and 2% to 5% for traditional cross-border rails (Source: Chainalysis, 2026). The disclosure model is the problem.

A single payroll batch publishes four things at once:

1. Individual compensatio:, because each transfer pairs an address with an amount and a timestamp, with recurring transfers identifying salaried staff and off-cycle transfers identifying bonuses, retention packages, and severance. 
2. Headcount and org shape: because the number of recipients per batch, the distribution of amounts, and the appearance or disappearance of addresses map hiring, attrition, and seniority structure month over month. 
3. Retroactive de-anonymization: because once one address is attributed to a person through an exchange deposit, a name service record, a donation, or a social post, that individual's entire compensation history becomes readable backwards. 
4. Burn rate: because batch size multiplied by cadence gives monthly operating outflow, which combined with the funding wallet's balance gives runway.

The market response in 2026 has been to build confidential payroll rails rather than accept the disclosure. Private stablecoin payroll deployments, including work by Toku with Aleo and Paxos Labs, exist specifically to process compensation without exposing salaries or treasury flows on-chain, and Toku alone has handled more than $1 billion in prior token payroll volume (Source: Paxos Labs, 2026). That volume is a useful measure of how much compensation data would otherwise have been public.

Exposure Layer 4: Vendor, Contractor, and Counterparty Flows

Business-to-business settlement is the largest genuine stablecoin payment category, at roughly $226 billion annually and close to 58% of real payment volume out of a $390 billion total (Source: McKinsey and Artemis Analytics, February 2026). B2B stablecoin payments grew 733% year over year in 2025, and real-world stablecoin payment volume doubled to around $400 billion (Source: Bessemer Venture Partners, April 2026).

Adoption at that scale is now visible in ordinary corporate operations. Ramp launched Solana-based stablecoin business accounts in July 2026, letting companies pay vendors and contractors in USDC and USDT across more than 140 countries, with over 1,000 organisations already using comparable Ramp stablecoin rails for international supplier payments (Source: Blockonomi, July 2026). 

Tokyo-listed logistics firm AZ-COM Maruwa announced plans to pay approximately 2,300 business partners, including subcontractors and truck drivers, in the yen-pegged JPYC stablecoin, described as Japan's first large-scale corporate use of a local-currency stablecoin for contractor pay. Wirex pivoted toward stablecoin banking-as-a-service for corporate clients in July 2026, targeting B2B, e-commerce, and supply chain settlement.

Each of those flows writes a counterparty graph to a public ledger, and that graph is a commercially sensitive document. 

• Supplier identity lets competitors learn your sourcing and approach your vendors directly. 
• Payment size per vendor reveals negotiated pricing and volume commitments. 
• Payment cadence reveals contract terms, net payment periods, and dependency. 
• New addresses appearing signal a partnership, integration, or market entry before you announce it. 
• Addresses disappearing signal a lost contract, a churned client, or a supplier dispute. 
• Concentration reveals single-supplier or single-client dependency to acquirers and lenders.

The asymmetry is what makes this expensive. A competitor operating on traditional rails reads your entire counterparty graph while publishing none of their own. Institutional stablecoin playbooks acknowledge the tension directly, promoting on-chain B2B invoicing and settlement for speed and cost while noting that transmissions, balances, and counterparties are fully visible, and that transaction screening is required precisely because of that visibility.

Exposure Layer 5: Runway, Reserves, and Solvency Signals

The most sensitive number in any company is how long it can keep operating. On-chain, that number is derivable.

Strategy's USD reserve reached $3.225 billion as of July 19, 2026, built through equity sales, with holdings held steady at 843,775 BTC that week (Source: CoinDesk, July 2026). Earlier June 2026 figures put the reserve near $2.55 billion, providing roughly 17.4 months of coverage against approximately $1.76 billion in annual expected preferred dividends and interest, against a board minimum policy of 12 months. 

Later July commentary referenced roughly 20 to 22 months of coverage, and combined with authorised Bitcoin monetisation capacity of up to $1.25 billion, total coverage approached 26 months under that framework.

Filing-verified cash runway across tracked treasury firms sits in a narrow, readable band as of July 23, 2026 (Source: CEBE tracker):

• Twenty One Capital: 2.3 years
• Capital B: 2.0 years
• Strategy: 1.8 years
• Strive: 1.5 years
• OranjeBTC: 1.4 years
• H100 Group: 1.2 years
• ProCap: 0.8 years

Average sector claims percentage, meaning senior claims diluting common equity exposure to the underlying Bitcoin, ran around 23%, rising to roughly 34% for Strategy and 45% for Strive (Source: CEBE tracker, July 23, 2026).

Filings supply part of this picture and wallets supply the rest, continuously. Strive disclosed cash and cash equivalents rising from $141.7 million to $153.4 million between June 26 and July 2, 2026 alongside a purchase of 17.76 BTC at approximately $59,850 (Source: Strive 8-K, July 6, 2026). For any company whose operating stablecoin balances sit in attributable wallets, the equivalent movement is visible daily rather than quarterly, and without the framing a filing provides.

For private companies the exposure is worse, because there is no filing to contextualise it. A venture-backed business paying its team and vendors from a public wallet publishes its burn rate and its runway to every competitor, every acquirer, and every prospective investor, continuously, on the worst possible schedule, which is the one where a bad month is visible before the recovery is.

How an Analyst Rebuilds Your Treasury in an Afternoon

The reconstruction is not exotic. It follows a repeatable sequence, and commercial tooling automates most of it.

1. Find one address: A published donation wallet, an exchange deposit, a contract deployment, a name service record, a grant disbursement, a public invoice, or a partner's disclosure.
2. Cluster it: Common spending heuristics, gas funding patterns, and shared change addresses expand one address into a wallet set.
3. Attribute it: Platforms including Arkham, Chainalysis, and Elliptic label entities and publish or sell those labels, and attribution of public companies to on-chain positions is a shipped feature rather than a research project.
4. Classify the wallets: Treasury, operating, payroll, gas, and bridge wallets have distinct behavioural signatures in batch size, recipient count, cadence, and asset mix.
5. Extract the metrics: Balance history gives position and rebalancing, outflow cadence gives burn, recipient sets give the counterparty graph and headcount, and inflow sources give revenue concentration and funding events.
6. Cross-reference filings: Where a company files, the filed numbers calibrate the on-chain estimate. Where it does not, the on-chain estimate stands alone.
7. Follow it across chains: Bridge transactions link identities across Ethereum, Solana, Tron, and EVM networks, so multi-chain operations multiply exposure points rather than dividing them.

The whole sequence is cheap, and that is the point. Financial intelligence that once required a subpoena, an insider, or an investigative team is now a subscription.

Who Is Actually Reading Your Wallet

• Competitors: Sourcing, pricing, client concentration, hiring pace, and market entry timing, all before announcement.
• Counterparties: A vendor who can see your treasury negotiates differently, and so does a lender, a landlord, and an acquirer reading your runway during diligence.
• Traders: Large, predictable treasury movements are front-runnable, so publishing execution intent is a direct cost measured in slippage.
• Employees and candidates: Visible pay bands turn every compensation conversation into a negotiation against a public spreadsheet.
• Journalists and activists: A liquidation, a payout to a controversial counterparty, or a treasury drawdown becomes a story on the ledger's timeline, not yours.
• Attackers: Covered below, because this one has a body count.

The Physical Security Dimension

CertiK recorded 52 wrench attacks worldwide in H1 2026, meaning physical violence or robbery tied to crypto holdings, a 33% increase year over year, with $124.1 million in associated financial exposure (Source: CertiK H1 2026 report). Home invasions became the dominant vector, frequently enabled by leaked personal data that links an identity and a location to visible on-chain wealth.

For corporate treasuries the relevant risk is that a wallet identifies the people with access to it. Signers on a multisig, finance staff receiving payroll, and executives holding company tokens all become targets once holdings are visible and attribution is possible. Confidentiality at the settlement layer is a personnel safety control as much as a commercial one.

Why the Standard Workarounds Fail

Most treasury teams have tried some version of the following, and none of them hold.

Rotating wallets

New addresses are linked by the transaction that funds them, and clustering heuristics resolve rotation in seconds. Rotation raises operational overhead and reconciliation burden while providing negligible privacy.

Routing through an exchange

A centralized venue breaks the on-chain link but replaces it with counterparty and compliance risk, adds settlement delay, forfeits custody during transit, and creates a complete record with a third party. It also does not work for recurring payouts to counterparties who need to be paid directly.

Splitting transactions

Chunking a large movement into smaller ones creates a distinctive pattern that clustering tools flag rather than miss. It increases fee cost and reconciliation complexity while making the wallet set easier to identify, not harder.

Using an OTC desk for everything

Effective for entry and exit, useless for ongoing operations. Payroll, vendor settlement, and treasury rebalancing still have to touch the chain.

Migrating to a private chain or privacy rollup

The most common proposal and the most expensive. It requires moving custody, integrations, liquidity, compliance tooling, and counterparties to a new environment, imposes a two-sided adoption problem because your vendors and clients must also migrate, and strands you on a network with thinner liquidity and fewer stablecoin options than the ones you left.

Mixers and obfuscation tools

Non-starters for any regulated business. They provide no screening at the entry point, no selective disclosure for auditors, and they carry sanctions exposure that no treasury committee will accept.

The pattern across all six is the same. Each either fails technically or forces the business to change something it cannot change. What treasury teams need is confidentiality that fits into the stack that already exists.

The Treasury Exposure Audit: 12 Questions

Run this against your own operations before assuming your exposure is limited.

1. Can any of your treasury or operating wallets be linked to your company by a third party today?
2. Has any wallet in your cluster ever received funds from an exchange account in your company's name?
3. Do you pay contractors, vendors, or employees from a wallet that also holds treasury balance?
4. Would your monthly outflow cadence reveal your burn rate to someone watching the funding wallet?
5. Can a competitor derive your supplier list from your outbound transaction history?
6. Would a new counterparty relationship be visible on-chain before your announcement?
7. Are your treasury rebalances large enough and regular enough to be predictable?
8. Do bridge transactions link your identity across networks?
9. Are any individual employees identifiable from payout addresses?
10. Would a lender or acquirer reading your wallets learn something you would not put in a data room?
11. If your reserve balance dropped 40% in a quarter, who would see it first, your board or the internet?
12. Do you have selective disclosure available for auditors that does not require making everything public?

Any single yes on questions one through nine means the rest of the list applies.

What Confidential Treasury Operations Look Like

Hinkal is a smart contract deployed on the public chains you already use, letting users hold private balances controlled by their existing wallet keys. It is not a mixer, not a private L1 or L2, and not a privacy rollup. There is no network to migrate to and no new custody model to approve.

How it works

Instead of a direct wallet-to-wallet transfer, funds are held in and moved from a private account inside the Hinkal smart contract. Zero-knowledge proofs, specifically zkSNARKs using Groth16, prove each transaction is valid without revealing its contents. 

• A UTXO-style commitment and nullifier model stores state in a canonical on-chain contract state. 
• A relayer broadcasts the transaction, so the user's own wallet never appears as the transaction origin. 

On-chain, an observer sees the Hinkal smart contract and the relayer address, and does not see sender, recipient, or amount.

There are four flows:

• Public to Private: Funds move from a wallet balance into a confidential balance, and all subsequent activity from that balance stops being publicly visible.
• Private to Private: Funds move between confidential balances, and sender, recipient, asset, and amount all stay confidential on-chain.
• Private to Public: Funds move from a confidential balance to a public address, so the recipient address is public but the sender stays confidential.
• Public to Public: Funds move from a public wallet through Hinkal to a public address, and the direct sender-to-recipient link is removed on-chain.

The Public to Public flow removes the two-sided adoption problem. Funds start in an ordinary wallet and arrive at an ordinary wallet, while the deposit into the contract and the withdrawal out of it are cryptographically unlinkable. 

Your vendor, contractor, or client needs no shielded address, no new wallet, and no onboarding, and gets paid the way they always do.

Mapped back to the five exposure layers, balances are held privately and controlled by existing keys, flows stop publishing accumulation and rebalancing timing, payroll settles without publishing amounts or recipients, the vendor and B2B counterparty graph leaves the public ledger, and runway is no longer derivable from wallet activity.

Hinkal has operated in production for more than three and a half years, has completed 6 security audits, and has processed over $500 million in cumulative private volume across Ethereum, Polygon, Arbitrum, Optimism, Base, Solana, TRON, Arc, and Tempo (Source: Hinkal). Enterprise settlement is priced at 10 basis points, or 0.10% per transaction. 

The company is backed by Draper Associates, SALT, SNZ Capital, and NGC Ventures, and was incubated at Stanford and through Binance MVB.

Compliance Without Disclosure

Privacy at the settlement layer means opacity to the public ledger, not opacity to your auditor, your regulator, or your compliance team. That distinction is structural, and it is what separates confidential settlement infrastructure from sanctioned obfuscation tools.

• Chainalysis KYT screening runs on wallet addresses before execution, preventing high-risk funds from entering the smart contract. Screening happens at the entry point rather than after the fact.
• Viewing keys let a user decrypt their own transaction history and share it selectively. Disclosure can be scoped to specific transactions or time ranges, time-bounded, and revoked, so an auditor sees exactly what they need and nothing on the public ledger changes.
• Downloadable transaction history is available out of the box, ready to hand to a third party.
• Non-custodial by design: Hinkal never holds funds. The private balance is controlled by the same wallet keys the treasury already uses, so there are no new credentials to issue, rotate, or lose.

For a regulated institution the practical test is whether an examiner can be satisfied without a public disclosure. Scoped viewing keys plus pre-transaction screening plus exportable history is a stronger audit posture than a public explorer link, because it produces a complete, decrypted, attributable record rather than a set of addresses an examiner has to interpret.

Where Each Hinkal Product Fits

1. Hinkal Pay

End-to-end confidential settlements and payouts across Solana, TRON, Ethereum, and major EVM networks. Connect an existing wallet, move funds to a private balance, and settle privately or out to any public address. Suited to teams that need confidential settlement without an engineering project.

2. Hinkal Prime

The enterprise control surface for confidential treasury and payouts, with permissioned multi-user access so a finance or treasury team operates together with defined roles, pending payouts queued and reviewed before execution, batch payouts that settle many recipients in one confidential operation for payroll, vendor, and contractor runs, and compliance controls on high-value transactions with viewing-key audit access.

3. Hinkal Integrations

The same protocol is exposed as an API and an SDK for products that want privacy embedded underneath their existing stack. 

• The API is language-agnostic, callable from Python, Go, Java, .NET, Rust, or Node.js, with requests signed by the caller's wallet so user-level access is authorised without passwords or custodial key handling. Private balance reads, UTXO handling, proof generation, and transaction building run inside Hinkal's secure enclave, where raw key material is never exposed. 
• The SDK gives frontend-level control for teams embedding private balances and private sends directly into their own interface, with 2 teams running SDK integrations in production today and a forward-deployed Hinkal engineer supporting the integration throughout 

4. Hinkal Wallet

A multichain wallet that shields balances and transaction history while supporting swaps, transfers, and DeFi execution from a private account.

For custodians, institutional wallets, embedded wallet providers, payroll platforms, PSPs, merchants, exchanges, on-ramps, stablecoin card issuers, iGaming operators, and fintechs, the highest-leverage path is Hinkal Integrations: a private balance sitting next to the regular balance in your product, and a private send sitting next to the regular send.

A 30-Day Path to a Confidential Treasury

• Days 1 to 5 - Map exposure: Inventory every wallet, identify which are attributable, and run the 12-question audit above. Most teams discover more linkage than they expected.
• Days 6 to 10 - Classify flows: Separate treasury, payroll, vendor settlement, and operating float, then rank by sensitivity. Payroll and vendor flows usually rank highest because they expose third parties who did not choose the exposure.
• Days 11 to 20 - Pilot one flow: Run a single recurring payout batch through a confidential flow end to end, including reconciliation and audit export. Batch payouts through Hinkal Prime are the usual starting point because they concentrate the most exposure into the smallest change.
• Days 21 to 30 - Extend and instrument: Move treasury rebalancing and vendor settlement onto the same path, issue scoped viewing keys to finance and audit, and document the disclosure procedure so it exists before anyone asks for it.

Nothing in that sequence requires changing chains, wallets, stablecoins, custody arrangements, or compliance vendors. That is the design constraint the entire product is built around.

Conclusion

Hinkal is the privacy infrastructure that lets businesses run treasury, settlement, and payouts on public chains while balances, counterparties, and amounts stay confidential, with existing wallets, existing chains, and existing compliance controls fully intact. 

The evidence in this report is consistent across every source: more than 1.26 million BTC and roughly $134 billion in corporate digital asset value now sit on ledgers that publish every balance change, every payout, every counterparty, and every reserve drawdown in real time. 

That exposure compounds across five layers, from holdings to flows to compensation to vendor relationships to runway, and commercial attribution tooling has made reading it cheap enough that anyone can. 

Migration to a private chain is not the answer, because the cost is the business itself. Adding a confidential settlement layer on the chains you already operate on, with Chainalysis KYT screening at the entry point and scoped viewing keys for auditors, closes the exposure without touching anything else. 

Book a demo with the Hinkal team to map your treasury exposure and see a confidential batch payout run end to end.

Read Next:

• The Hidden Cost of Public Crypto Payroll: A 2026 Exposure Report
• Confidential Stablecoin Settlement Under MiCA, the Travel Rule, and GENIUS
• Confidential Settlement for Stablecoin Issuers: How Issuers Keep Vault Positions and Holder Balances Private

FAQs:

1. What do public corporate wallets reveal about a company's treasury?

Public corporate wallets reveal a company's treasury balances, accumulation and sale timing, rebalancing strategy, payout cadence, counterparty relationships, individual compensation, and derivable burn rate and runway. Because public blockchains record every transaction permanently, this information is available continuously rather than on the company's disclosure schedule, and commercial attribution platforms including Arkham, Chainalysis, and Elliptic cluster and label wallets so a single identified address expands into a full operational picture. Arkham verified approximately 83% of one public company's Bitcoin position directly on-chain in mid-July 2026, which illustrates how complete that picture can be.

2. How much corporate crypto is publicly visible on-chain in 2026?

The amount of corporate crypto publicly visible on-chain in 2026 exceeds 1.26 million BTC held by public companies, about 6.02% of Bitcoin's maximum supply and roughly $79 billion in value as of July 3, 2026, plus approximately 7.67 million ETH in tracked institutional and public company holdings and around 16.8 million SOL across about six public companies. Digital Asset Treasury Companies collectively held $134 billion in crypto as of January 1, 2026, up 137.2% year over year. Every one of those positions, and every movement in or out of them, is recorded on a public ledger.

3. Can competitors see corporate payroll and vendor payments on-chain?

Competitors can see corporate payroll and vendor payments on-chain whenever those payments settle on a transparent public network, because each transfer permanently records the recipient address, the amount, and the timestamp. Recurring transfers identify salaried staff, off-cycle transfers identify bonuses and severance, and outbound vendor payments reveal supplier identity, negotiated pricing, contract cadence, and client concentration. This is the primary reason fewer than 1% of businesses run payroll on public chains in 2026, despite stablecoin rails being faster and cheaper than correspondent banking.

4. How can a company hide its treasury balance without breaking compliance?

A company can hide its treasury balance without breaking compliance by settling from a confidential balance on the chain it already uses, with screening at the entry point and selective disclosure for auditors. Hinkal holds private balances inside a smart contract on public chains, controlled by the company's existing wallet keys, and proves every transaction valid with zkSNARKs while keeping sender, recipient, and amount off the public ledger. Chainalysis KYT screens wallet addresses before execution, scoped and revocable viewing keys let auditors and regulators decrypt exactly what they need, and transaction history is downloadable out of the box, which is a stronger audit posture than a public explorer link.

5. What is the best way to prevent on-chain treasury exposure in 2026?

The best way to prevent on-chain treasury exposure in 2026 is to add a confidential settlement layer to the chains, wallets, and stablecoins already in use rather than migrating to a private network. Hinkal Pay and Hinkal Prime execute treasury movements, batch payouts, and vendor settlements from private accounts controlled by existing wallet keys, with a relayer broadcasting so the company's wallet never appears as transaction origin. The Public to Public flow means recipients need no new wallet and no shielded address, which removes the two-sided adoption problem that makes migration-based privacy approaches fail in practice, and Hinkal Integrations lets wallets, PSPs, payroll platforms, and custodians embed the same privacy underneath their own product.