← intents/minerintents/miner / chains

chains

the three chains the machine touches and what it does on each.
value
1h
24h
liquidity
mode
rung
shares
pending
orchard
monero

solana

program
state account
intake
coin

on solana the machine is one anchor program and one coin. the program accepts shares, keeps the anchor mirror, keeps the commitment and output accounts, keeps the tree, and holds the rung. it has no instruction that moves coins or sol except the reward buy, which is a cpi into the curve from the buffer.

the program's name shows on explorers because its idl is published on chain with the deploy, and the deploy is a verified build so the source hash matches the executable. the links above resolve to the program and its state account.


zcash

address
viewing key
balance
notes
last block
mirror lag

zcash is the even side. the machine receives orchard notes at a unified address and never spends them. the full viewing key is published so the notes can be listed by anyone with a view only wallet. the anchors the program mirrors are the orchard tree roots zcash itself publishes in its block headers.

a zcash fill is grade 1 by the direct route and grade 3 by the two hop route. its share proves a merkle path from the note commitment to a mirrored anchor, which is the same proof a zcash spend would make, minus the spend.


monero

address
view key
balance
outputs
last block

monero is the odd side. the machine receives outputs at a primary address and never spends them. the view key is published so incoming outputs can be listed by anyone with a view only wallet. the key images are never produced, so the outputs are provably unspent for as long as the machine exists.

a monero fill is grade 2 by the direct route and grade 3 by the two hop route. its share proves the output's global index and transaction hash after ten confirmations, which is monero's own unlock depth.


near

near intents is the road between solana and the two far chains. an intent names what goes in and what must come out, and a solver that can deliver takes it. the machine's solver is one of those solvers, bound to the machine's own addresses as the only allowed destinations. the near transaction on every fill is the receipt.

the machine holds nothing on near. the intermediate asset of a two hop route exists only inside the intent's settlement.