Portal Community
What it does: The Centrifuge node (centrifuge) exposes read operations against a Centrifuge-family Substrate chain via plain JSON-RPC over HTTP, plus local address, unit, and interest-rate conversion utilities. No signing credential or third-party SDK is required for any operation on this page — every network call is a read, and sr25519 extrinsic signing is not yet available for this node.

Quick Start

  1. Add a Centrifuge node to your workflow
  2. Set resource to account and operation to getBalance
  3. Enter an address (an SS58-encoded Centrifuge account, e.g. an address you control)
  4. Set network explicitly — centrifuge, altair, or development (there is no default network for this node)
  5. Run the workflow — the node returns the account's free/reserved/frozen balance and nonce
Tip: Every operation on this node shares the same two top-level config keys — resource, operation — but network is only required for the two operations that actually call the chain (account.getBalance and utility.chainInfo). Learn the full pattern once on Input & Output.

Pages in This Guide

Configuration

Registration, project layout, and why there's no appsettings.json section.

Networks

Centrifuge, Altair, and Development — plus conversion-only Polkadot/Substrate prefixes.

Account Operations

getBalance — free, reserved, and frozen balance plus nonce.

Chain Info

Chain identity, runtime version, head block, and how to detect a stalled chain.

Address Operations

validateAddress and convertAddress — SS58 checksum and re-encoding.

Conversion Operations

convertUnits and convertRate — base/display units and APR ↔ RAY.

Currencies & Units

Why decimals are never assumed — CFG, AIR, USDC, USDT, and more.

Input & Output

The shared config-key pattern and how errors surface.

Examples

Worked workflow patterns using this node.

Troubleshooting

Common errors and how to fix them.

Roadmap

Signed writes, pools/loans/tranches, IPFS — what's coming and what it needs.

Core Concepts

Substrate JSON-RPC Reads

Every network call this node makes is a plain HTTP JSON-RPC request to a Centrifuge-family Substrate node — system_chain, system_version, state_getRuntimeVersion, chain_getHeader, chain_getBlockHash, and state_getStorage. There is no WebSocket subscription and no signing key involved in any operation shipped today.

Resources

Operations are grouped by resource:

Networks Are Fixed, Not Configured

Unlike some other chain nodes, Centrifuge's networks and RPC endpoints are compiled-in constants (CentrifugeNetworks), not read from an appsettings section. There is no DefaultNetwork fallback either — network must be supplied explicitly wherever it's required. See Networks.

Decimals Are Never Assumed

Pool amounts on Centrifuge are usually denominated in a stablecoin (USDC/USDT at 6 decimals), not the 18-decimal native CFG token. Every amount-bearing operation on this node takes decimals explicitly — there is no default and no silent 18. See Currencies & Units.

Operation Summary

Resource Operation Guide Page
accountgetBalanceAccount Operations
utilitychainInfoChain Info
utilityvalidateAddress, convertAddressAddress Operations
utilityconvertUnits, convertRateConversion Operations