Chains

Octra

oct and a fixed 44 base58 characters, the one chain here where decoding would be wrong. No coin type, no CAIP-2 namespace, and the class says so.
IDoctra26 / 36octra · OCT
Chain / Octra

Octra

"octra""oct""Octra"

Symbol
OCT · 6 decimals
Coin type
none
CAIP-2
none
Checks
address · txid
fields set 4 / 9

Network

CAIP-2none
Magicnone
PoWnone
RPCoctra.network/rpc
Exploreroctrascan.io

Access

Createcreate("octra")
ResolvegetChain("oct")
CLIchains info oct
Tryplayground with a sample address

Address format

oct and exactly 44 base58 characters, and that's the whole format. Octra is the one base58 chain here where decoding would be a mistake: a contract address is cut out of a base58 string rather than encoded from a payload, so its value runs past 32 bytes and a decoder that expected a payload would throw real contracts away. The node takes that width and nothing else, so an address one character short isn't a near miss, it's a different string.

No BIP-44 coin type and no CAIP-2 namespace are registered, so bip44 and caip2 are undefined and the tools print none. Inventing either would be worse than admitting it.

ts
import { getChain } from "@agntn/chains";

const chain = getChain("oct");
chain.assertAddress("oct7xCozDD9JEsbeVpo5C7HXp2BJbKqfmNUHmDDCCTtWcGb"); // returned unchanged
chain.type; // "octra"
chain.caip2; // undefined

Spellings

octra, oct, Octra. The key is octra, the rest resolve through getChain.