OP_DATA_32(32) c5095c0fc16905bf467a8be4dee6416412725e665922e50b10892ee2481865a9

OP_CHECKSIG(172)

OP_0(0)

OP_IF(99)

OP_DATA_3(3) ord

OP_DATA_1(1)

OP_DATA_24(24) text/plain;charset=utf-8

OP_0(0)

OP_PUSHDATA2(77) `ord` makes RPC calls to `bitcoind`, which usually requires a username and password. By default, `ord` looks a username and password in the cookie file created by `bitcoind`. The cookie file path can be configured using `--cookie-file`: ``` ord --cookie-file /path/to/cookie/file server ``` Alternatively, `ord` can be supplied with a username and password on the command line: ``` ord --bitcoin-rpc-user foo --bitcoin-rpc-pass bar server ``` Using environment variables: ``` export ORD_BITCOIN_RPC_USER=foo expo

OP_PUSHDATA2(77) rt ORD_BITCOIN_RPC_PASS=bar ord server ``` Or in the config file: ```yaml bitcoin_rpc_user: foo bitcoin_rpc_pass: bar ``` Logging -------- `ord` uses [env_logger](https://docs.rs/env_logger/latest/env_logger/). Set the `RUST_LOG` environment variable in order to turn on logging. For example, run the server and show `info`-level log messages and above: ``` $ RUST_LOG=info cargo run server ``` New Releases ------------ Release commit messages use the following template: ``` Release x.y.z - Bump version: x.y.

OP_DATA_12(12) z → x.y.z

OP_ENDIF(104)