For the complete documentation index, see llms.txt. This page is also available as Markdown.

Evidence — an investor

The Investing screenshots are a real buyer, twice over — once from an EVM wallet and once from a Solana wallet, buying the same Solidity asset (Mineral Vault I, ARCV) on Hadrian (chain 200010). Every action is a transaction you can open. The link is the claim.

The EVM lane — a wallet buys at its own address

An EVM wallet holds the asset at its own address, and a buy is the ordinary two-step approve-then-buy. The eligibility gate is checked on the token first — the buyer is allowlisted, then buys.

Buyer: 0x5667b3700b4a021Cc475157cbf3dE2d756Fae597

#
What it did
Transaction

1

Allowlist the buyer (the test-wiring stand-in for the issuer's approval)

2

Approve wUSDC to the storefront

3

Buy the asset

After the buy, the eligibility card reads Permitted and the holding shows in Positions — the invest-permitted and positions screenshots in the guide are this buyer, after these transactions.

The Solana lane — a wallet buys at its derived address

This is the one that carries the whole thesis: a Solana wallet buys the same Solidity asset, with no bridge and no second token. There is no EVM key anywhere — the buyer signs with their Solana key, and the asset is held at the EVM address derived from it.

Each step is a DoTxUnsigned: an EVM transaction executed inside one Solana transaction, authorised by the Solana signature. The buy is the same two legs, each its own Solana transaction:

#
What it did
Solana transaction
Compute

1

Approve wUSDC to the storefront (from the derived address)

~191K CU

2

Buy the asset

~737K CU

The buyer paid the transaction fee in lamports from their own Solana wallet; the derived address never held SOL. The positions-solana screenshot in the guide — "Held for your Solana key", the custody chain, and the ARCV holding — is this signer, after these transactions.

The same asset, the same allowlist, either wallet world. The EVM buyer and the Solana buyer bought the identical Solidity token, gated by the identical on-chain allowlist, priced in the identical wUSDC. The only difference is which key signed and which address holds — which is the entire point of the two lanes, proven here rather than asserted. The mechanics are in LANES.md; the compliance model is in COMPLIANCE.md.

Last updated

Was this helpful?