OUTCRY answers the same JSON-RPC as Solana. The stock solana CLI and @solana/web3.js work against it unchanged: only the URL changes.
Point the CLI at the public RPC for one command with -u; nothing global changes.
solana cluster-version -u https://rpc.outcry.networksolana slot -u https://rpc.outcry.networkMake a key, restore that file on /trade (Restore from file) and take test money there, then send a transfer with it:
solana-keygen new --no-bip39-passphrase -o outcry-key.jsonsolana transfer <to address> 0.001 -k outcry-key.json --allow-unfunded-recipient -u https://rpc.outcry.networkThe order book program sits in genesis at a fixed address. Nobody can replace it.
solana program show PhoeNiXZ8ByJGLkxNfZRnkUfjvmuYqLR89jjFHGqdXY -k outcry-key.json -u https://rpc.outcry.networkThe output lists Authority: none and the owner BPFLoaderUpgradeab1e11111111111111111111111.
The program is Phoenix v1 (Ellipsis Labs, MIT licence), the executable read from Solana mainnet, unchanged. Dump it here and compare its hash with the same program dumped from Solana mainnet:
solana program dump PhoeNiXZ8ByJGLkxNfZRnkUfjvmuYqLR89jjFHGqdXY phoenix.so -k outcry-key.json -u https://rpc.outcry.network
sha256sum phoenix.soEvery block's transactions are listed in the order they executed. Read any block and look at the position of each transaction to the book.
solana block <slot> -u https://rpc.outcry.network --output json > block.jsonA book transaction has a top-level instruction to the book program. Its kind comes from that instruction's first data byte (and the second when the first is 2 or 3): 4 to 11 cancel; 16, 17, or 2 or 3 followed by 0 post-only quote; anything else take or other.
For one pair from the line test page, confirm both signatures and compare their slots:
solana confirm -v <take signature> -u https://rpc.outcry.network
solana confirm -v <cancel signature> -u https://rpc.outcry.networkWhich block a transaction lands in is decided by the block builder; every block builder on this chain is a validator this project runs.
curl -s https://rpc.outcry.network -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"getBlock","params":[<slot>,{"maxSupportedTransactionVersion":0,"transactionDetails":"full"}]}'Cancels, then post-only quotes, then everything else; ties by arrival slot, then signature hash.
Book transactions are scheduled by class, then by the slot in which the leader received them (earlier first), then by SHA-256 of the first signature (lowest first). Fee priority plays no part among them.
A take becomes schedulable 50 ms after the leader received it. A cancel or quote that reaches the leader no later than 50 ms after a take is executed before that take; one that arrives later can land after it, in the same block or a later one.
import { Connection } from "@solana/web3.js";
const conn = new Connection("https://rpc.outcry.network", "confirmed");
const slot = await conn.getSlot();
const block = await conn.getBlock(slot, { maxSupportedTransactionVersion: 0 });
block?.transactions.forEach((tx, i) => console.log(i, tx.transaction.signatures[0]));