Hinkal has supported Solana and TRON as native networks for confidential operations. Users on either chain could run private transfers, settlements, and payouts with the same properties as on any EVM network. Deposits, withdrawals, internal transfers, payment execution - all of it running through the shielded pool with ZK verification and KYT screening.
What was missing was the bridge between them. Users could bridge from EVM networks to Solana inside Hinkal. The reverse - Solana back to EVM - was not available. And TRON had no bridging at all, in either direction. That meant any operation that needed to move assets between Solana and an EVM chain, or touch TRON in any cross-chain capacity, had to leave the Hinkal interface and bridge publicly.
NEAR fills those gaps. Bridging from Solana and TRON is now live inside Hinkal Pay and Prime, and both-way bridging is active across all supported networks. Every direction, every supported chain. The bridge runs inside the same interface, through the same shielded pool, with the same compliance properties.
NEAR is a cross-chain infrastructure protocol built for routing assets between networks. Hinkal integrates NEAR as a bridge provider, routing cross-chain transactions through Hinkal's shielded pool. As a result, all cross-chain movements carry the same privacy and compliance properties as single-chain or other cross-chain operations inside Hinkal.
The integration adds two capabilities that did not exist before:
Solana as a bridge source network, not just a destination
Users holding assets on Solana can now bridge into any supported destination network directly from the Hinkal interface. Previously, Solana could only receive bridged assets from EVM chains. Now the reverse works. Solana to Ethereum, Solana to Polygon, Solana to Arbitrum, Solana to any supported EVM chain - all live. Assets enter the shielded pool on arrival and carry the same properties as any native Hinkal operation: sender, recipient, and amount hidden on-chain, ZK-verified, Chainalysis KYT-screened, non-custodial.
TRON as a bridge source and destination network
TRON had zero bridging capability inside Hinkal before this update. Users could operate privately on TRON itself, but could not move assets to or from other networks through the Hinkal interface. Now TRON is a full participant in the bridge. TRON to Ethereum, TRON to Solana, TRON to Polygon - any supported destination. Same shielded pool entry, same privacy properties, same compliance posture.
Together, these unlock both-way bridging across all supported networks. Solana to Polygon. TRON to Ethereum. Arbitrum to Solana. Ethereum to TRON. Any supported source to any supported destination. Select source chain, destination, asset, amount. NEAR handles the route from TRON and Solana. No separate bridging tool, no manual token approvals on a third-party site, no leaving the interface.
Stablecoin volume spans multiple chains. TRON carries over $60B in USDT and processes the highest volume of stablecoin transfers globally. Solana runs high-speed payment and DeFi volume with sub-second finality. EVM networks handle the bulk of institutional settlement and DeFi composability. Any operation running at scale - payment service providers, treasuries, payroll operations, OTC desks - holds positions across multiple networks and needs to move between them regularly.
Both-way bridging through NEAR removes that limitation entirely. A treasury on TRON that needs to settle on an EVM chain can bridge inside Hinkal and maintain privacy on both legs. A PSP on Solana rebalancing to Polygon can do the same. Payroll operations spanning multiple chains can batch across networks without exposing the cross-chain movement pattern. OTC desks filling orders across chains can move capital without broadcasting the flow. The privacy posture holds at the bridge instead of breaking at it.
This also simplifies operations. Before, a user who wanted to move assets from TRON to Polygon privately had to find an external bridge, execute a public transaction, deposit into Hinkal on Polygon, and then operate privately. Now it is one step. The operational overhead drops and the privacy gap disappears.
NEAR operates as a bridge provider inside the Hinkal interface. The user selects source chain, destination chain, asset, and amount. The transaction is routed through NEAR and settled through Hinkal's shielded pool on both sides.
Both sides of the bridge run through Hinkal's shielded pool. The on-chain link between source chain activity and destination chain activity is severed. An observer on Solana cannot link an outbound transfer to an inbound position on Polygon. An observer on TRON cannot trace where bridged assets landed on an EVM chain. The bridge does not create a public record connecting the two addresses.
Every operation carries the same compliance posture as any other Hinkal transaction: Chainalysis KYT screening before settlement, viewing keys for selective disclosure to auditors or counterparties when required. The bridge does not create a compliance gap - it carries the same screening and disclosure mechanisms as native operations on any single chain.
Non-custodial throughout. Users retain control of assets on both sides of the bridge. No intermediary custody, no pooled holding period, no third-party risk.
Payment service providers processing cross-chain stablecoin volume. PSPs that hold USDT on TRON and need to settle in USDC on an EVM chain can now bridge inside Hinkal without exposing the settlement flow.
Treasuries managing multi-chain positions. Corporate treasuries holding assets across Solana, TRON, and EVM networks can rebalance without public bridge transactions linking their addresses across chains.
Payroll operations spanning multiple networks. Organizations paying contractors or employees across different chains can batch cross-chain movements without creating a visible pattern of which addresses are connected.
OTC desks filling cross-chain orders. Capital can move between networks without broadcasting the flow direction or volume to observers on either chain.
Hinkal is a privacy infrastructure for stablecoin payments and settlements. Confidential, compliant, non-custodial. Live across EVM, Solana, and TRON.
Both-way bridging turns the supported chain set into one privacy environment. Capital moves across chains inside Hinkal without creating public links between addresses on different networks. The privacy posture holds at the bridge - the one point where most operations are forced to go public.
