Deploy Yano X
Start with a local demonstration, rehearse a shared application on one machine, then set it up for real with the other operators.
| Your goal | Start here | What you get |
|---|---|---|
| See Yano X working | Local showcase | Three nodes, useful data, proofs, and a console |
| Rehearse a shared application | ./yano.sh appchain try | Every real setup step, on one machine, with three simulated operators |
| Run an application with other operators | Set up an application | Each operator runs their own node; everyone checks they have the same chain |
| Add or remove a member, or add another application | Grow and change it | One command per operator, without resetting anything |
| Run your node on a server | Run your node on a server | A systemd service, open ports, and the cloud route for the showcase |
Yano X is JVM-only and requires Java 25. Yano’s tooling calls an app ledger an
app chain, so commands and files say appchain.
Who does what
Section titled “Who does what”A real app ledger is run by several organizations. Each one is an operator: it runs one member node and holds that node’s private key, which never leaves its machine. One person, the coordinator, defines the application and collects everyone’s public member card. The coordinator is usually also an operator. The first operator listed is the lead.
Only public files travel between people: the draft, the member cards, and the
sealed .chain file. Send them however you like, or let
join links carry them. Everyone
checks they have the same chain by comparing a short chain fingerprint on
a call.
An application can hold several chains. Each chain keeps its own genesis, state, and finality history, and all of them run on the same member nodes.
Nodes, chains, and ports
Section titled “Nodes, chains, and ports”Each node has one HTTP port and one node-to-node (n2n) port, however many chains it hosts.
- Local showcase: node 0, node 1, node 2.
- appchain try, one machine: alice, bob, carol.
- One node per operator: alice, bob, carol.
Select a node to see its port rule.
- node 0
- The showcase puts node i on HTTP 7070 + i and node-to-node port 13337 + i, listening on 127.0.0.1. It passes these ports to
requestfor every node, so a busy port stops it instead of moving. Change the bases with--http-baseand--server-base; a retained instance remembers them. Node 0 also produces the private devnet. - node 1
- The showcase puts node i on HTTP 7070 + i and node-to-node port 13337 + i, listening on 127.0.0.1. It passes these ports to
requestfor every node, so a busy port stops it instead of moving. Change the bases with--http-baseand--server-base; a retained instance remembers them. - node 2
- The showcase puts node i on HTTP 7070 + i and node-to-node port 13337 + i, listening on 127.0.0.1. It passes these ports to
requestfor every node, so a busy port stops it instead of moving. Change the bases with--http-baseand--server-base; a retained instance remembers them. - alice
./yano.sh appchain trygives alice, bob and carol the first free ports from 8080 (HTTP) and 13337 (node-to-node), listening on 127.0.0.1, and prints every command it runs. A showcase already holding 13337 just moves the rehearsal up. Alice is the lead and produces the devnet.- bob
./yano.sh appchain trygives alice, bob and carol the first free ports from 8080 (HTTP) and 13337 (node-to-node), listening on 127.0.0.1, and prints every command it runs. A showcase already holding 13337 just moves the rehearsal up.- carol
./yano.sh appchain trygives alice, bob and carol the first free ports from 8080 (HTTP) and 13337 (node-to-node), listening on 127.0.0.1, and prints every command it runs. A showcase already holding 13337 just moves the rehearsal up.- alice
- In a real application each operator chooses their ports at
request; the defaults are HTTP 8080 and node-to-node 13337. With a public host name, the node listens on all interfaces. Other members connect to the node-to-node port;statusand later members use the HTTP port. Open both only to the machines that need them. - bob
- In a real application each operator chooses their ports at
request; the defaults are HTTP 8080 and node-to-node 13337. With a public host name, the node listens on all interfaces. Other members connect to the node-to-node port;statusand later members use the HTTP port. Open both only to the machines that need them. - carol
- In a real application each operator chooses their ports at
request; the defaults are HTTP 8080 and node-to-node 13337. With a public host name, the node listens on all interfaces. Other members connect to the node-to-node port;statusand later members use the HTTP port. Open both only to the machines that need them. - Every chain on a node shares its two ports
- A node has one HTTP API for all its chains; the path carries the chain id, for example
/api/v1/app-chain/chains/orders/messages. By default, chain traffic between members also shares one node-to-node connection per pair of nodes.
- also produces the devnet
- member node
| How you run it | HTTP | Node-to-node | Change it with |
|---|---|---|---|
Local showcase (showcase.sh) | 7070 + node index | 13337 + node index | --http-base, --server-base |
./yano.sh appchain try | first free from 8080 | first free from 13337 | chosen for you and printed |
| One node per operator | 8080 on each host | 13337 on each host | request --http-port, --node-port |
try skips busy ports and prints the ones it chose. The showcase passes its
ports explicitly, so it stops instead. While the
coordinator hands out join links, invite --serve also listens on port 7099
(--port changes it), which the operators must be able to reach.
Where to start
Section titled “Where to start”The supported evaluation posture is a local devnet. Public networks follow the same steps, but anchoring and settlement there are explicit operations that spend real test ADA; easier setup does not change the release-readiness assessment.
Next: start the local showcase, or rehearse a shared application.