BLVCK MINDZ × NEAR / Interoperability
A Solana foundation. A NEAR integration.
The current portal connects evidence from two networks. Settlement of the same obligation across networks remains planned.
What works today
| Network | Demonstrated scope |
|---|---|
| Solana · devnet | Earlier split-payment program and an archived, independently rechecked test payment. |
| NEAR · testnet | Interactive fixed-sample invoice, approval, distribution and recipient-level proof. |
Open the demo’s network portal →. Expand Interoperability to inspect both references. They use different ledgers and agreements and are not two legs of one payment.
What carries over from Solana
The integration reuses earlier catalog allocation rules, shared calculation vectors and the batch/hash receipt format. Consistent calculation does not synchronize ownership or balances between networks.
Inspect the baseline ↗ · Solana devnet program ↗
NEAR’s role
Today NEAR executes the test payment and exposes its distribution evidence. The proposed next role is coordination of an approved obligation and its settlement destination. No bridge, Intents conversion or destination-chain adapter is implemented in this demo.
Planned: receive on another network
- Bind the revenue obligation to its agreement version and each participant’s share.
- Let the participant authorize a supported destination, asset and acceptable fees.
- Execute through a tested adapter, with durable tracking that prevents paying the same obligation under another chain or batch ID.
- Verify the delivered amount, finality and any refund or recovery path.
This is a proposed workflow, not an available payout option. Custody, liquidity, fees and failure handling require validation. Multiple participant destinations must not duplicate an individual obligation.
What would prove the connection
A completed cross-network test must link source and destination transactions to the same approved obligation and verify delivered amounts and costs. Until then, two explorer links prove separate executions only.
Documentation maintenance · 16 November 2026 · Source and scope