Use
Use
Token, transactions, wallet, and inscriptions on ire-1. This is a public testnet with one validator — not mainnet. Operators broadcast with local ired.
Token
1 IRE = 1,000,000 uire. The base denom on chain is uire (6 decimals). Send with ired tx bank send, chain-id ire-1, gas-prices 0.001uire.
ired tx bank send <from> <to> 1000000uire \
--chain-id ire-1 \
--from <key> \
--gas-prices 0.001uire \
--home "$HOME/.ire" \
--yes
The transaction sits in the mempool, then a block (~5s). Watch it on Mempool.
Transactions
The human view of sends, receives, inscriptions, stakes, and bets is Wallet — look up an ire1 address, then scan the last blocks plus the mempool. Cubes of the same traffic live on Mempool. Empty blocks are normal on a quiet testnet.
There is no faucet. You need uire already in a local key. This docs host reverse-proxies read-only GET named routes such as /rpc/status and /api/cosmos/bank/v1beta1/supply/by_denom?denom=uire. It will not relay broadcast_tx. Signing and broadcast stay on your machine with ired.
Wallet
IRE is a Cosmos chain. It is not Solana and not Bitcoin. Do not use Phantom. Do not use a Bitcoin wallet. Use Keplr or Leap as a custom/experimental chain, or just ired keys.
Copy-paste experimental chain JSON:
{
"chainId": "ire-1",
"chainName": "IRE Testnet",
"rpc": "https://boomer250.com/rpc",
"rest": "https://boomer250.com/api",
"bip44": { "coinType": 118 },
"bech32Config": {
"bech32PrefixAccAddr": "ire",
"bech32PrefixAccPub": "irepub",
"bech32PrefixValAddr": "irevaloper",
"bech32PrefixValPub": "irevaloperpub",
"bech32PrefixConsAddr": "irevalcons",
"bech32PrefixConsPub": "irevalconspub"
},
"currencies": [{
"coinDenom": "IRE",
"coinMinimalDenom": "uire",
"coinDecimals": 6
}],
"feeCurrencies": [{
"coinDenom": "IRE",
"coinMinimalDenom": "uire",
"coinDecimals": 6,
"gasPriceStep": { "low": 0.001, "average": 0.001, "high": 0.0025 }
}],
"stakeCurrency": {
"coinDenom": "IRE",
"coinMinimalDenom": "uire",
"coinDecimals": 6
}
}
Honest: that proxy is read-only GET, so Keplr cannot broadcast through it yet. Balances and chain status may load; sends will fail until there is a public write RPC. Operators broadcast with local ired against 127.0.0.1:26657. A custom IRE wallet app is optional later, not required.
Inscriptions (not IPFS)
NFTs on IRE are not IPFS and not Arweave. You inscribe the payload into the transaction so every full node stores it. The id is {txid}i0 for the first message (lowercase hex + i + index). See docs/INSCRIPTIONS.md.
The current binary has no dedicated inscription module. The path is a memo convention: the memo starts with IREINSCRIBE1. Cosmos’s default memo is small (256 characters), so the current path is text, JSON, or small SVG. Large images need a later chain upgrade. Never pin to IPFS for IRE inscriptions — that would put the bytes off this chain.
CLI inscribe
Self-send 1uire with a memo. The send is only the carrier.
ired tx bank send <from> <from> 1uire --chain-id ire-1 --from <key> --gas-prices 0.001uire --memo 'IREINSCRIBE1 application/json {"p":"ire-insc","op":"deploy","tick":"IRE","name":"example"}' --home $HOME/.ire --yes
Then open Mempool. The cube should be magenta→violet and show {txhash}i0.
Prediction markets
Prediction markets are inscribed bets (ire-bet memos), not an escrow module. Protocol fee is 0% — gas only (0.001uire). Cosmos gas currently pays the validator; the chain wallet is the community pool. See Markets.
More
- Source: github.com/kenyahewitt/ire-blockchain
- Join a node or validator: Join
- Public seed and genesis: Network
- Live cubes and blocks: Mempool
- Inscribed prediction markets: Markets