OUTCRYApp
GuideTradeThe lineBlocksBoardNetworkWhitepaperDocsToken
Places
GuideTradeThe lineBlocksBoardNetworkWhitepaperDocsToken
Reading the chainSlot -TEST MONEYKey none yet
Docs | OUTCRY
League
Count
League
Count
X

Check it yourself

OUTCRY answers the same JSON-RPC as Solana. The stock solana CLI and @solana/web3.js work against it unchanged: only the URL changes.

The stock CLI

Point the CLI at the public RPC for one command with -u; nothing global changes.

solana cluster-version -u https://rpc.outcry.network
solana slot -u https://rpc.outcry.network

Make 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.json
solana transfer <to address> 0.001 -k outcry-key.json --allow-unfunded-recipient -u https://rpc.outcry.network

The book has no upgrade authority

The 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.network

The 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.so

Read the order inside a block

Every 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.json

A 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.network

Which 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.

  • cancel: a transaction whose instructions to the book are all cancels
  • quote: a transaction whose instructions to the book are only cancels and post-only quotes, at least one quote
  • take: anything else that calls the book
  • The rule orders transactions inside one block. Which block a transaction lands in is decided by the block builder, and every block builder is our validator.
  • The rule is enforced by the leader's block-building scheduler. Replay does not check the order; every validator here runs the patched build.
  • Transactions that reach the book only through another program are not book transactions for the rule.
  • The token is not this chain's gas at launch. The chain runs on faucet test gas.

web3.js

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]));

Limits and faucet rules

  • TEST MONEY: Test money from a faucet. It has no value.
  • Faucet: up to 10,000 test USD per account per UTC day, refilled up to that amount at 00:00 UTC.
  • Trading fee, in test money: taker 0.05%, maker 0.00%.
  • Markets: SOL / USD (test SOL against test USD).
  • The faucet and order sending are limited per IP; a refusal says why and when to come back.