Reference

RPC Reference

The Morana node (moranad) is built on Bitcoin Core 31.1, so the familiar commands — getblockchaininfo, getblock, sendrawtransaction and the rest — work as they do in Bitcoin. RPC is the interface through which programs and the command line send commands to the node.

Networks and ports

Network P2P RPC
mainnet (not launched yet) 49331 49332
testnet tmor 39233 39232
regtest 49233 49232

Address formats

Kind Mainnet Testnet Regtest
transparent (SegWit v0 P2WPKH, BIP84) mor1q… tmor1q… morrt1q…
private (Sapling) morp1… tmorp1… morrtp1…
unified mu1… tmu1… murt1…

A unified address always contains a private receiver and may also contain a transparent one. Payment links use morana:, modeled on ZIP-321.

A transparent transaction is signed as in Bitcoin (BIP143). If a transaction has a private part, its transparent inputs sign the ZIP-243 digest, as in Zcash.

1 XMOR = 100,000,000 atoms.

Morana commands

On top of the Bitcoin Core commands, the node answers:

  • getnetworkparams — network parameters;
  • listrelays — the relay registry and a summary of the swarm economy (the swarm is all relays together): epoch, pool, income cap, stake;
  • getrelayinfo — details of a single relay;
  • getrelaypayouts — relay payouts;
  • getmrstcommitment — computes the relay-set commitment from the current registry, by default for the next block. A past height does not reconstruct the historical registry, so the result may differ from that block’s commitment;
  • getmnstproof — a proof that a MORID name (a readable name that stands for an address) exists, that it does not, or that it has expired.

Keep RPC bound to localhost (127.0.0.1:39232 on testnet). Never expose it to the internet: from

the outside, a node only needs its P2P port.