Skip to content
Ghostline

These are the Ghostline contracts on Tari Ootle mainnet, published on 13 Nov 2026. Check each one against the indexer yourself: GET /substates/<address> should return HTTP 200.

Addresses

Value
Channel templateae13cead…ef9c (opens the indexer record)
Fee-config templateb3628ed0…9f45 (opens the indexer record)
Fee config37df6af5…0bb5 (opens the indexer record)
Network tag0
Indexershttps://indexer-a.ootle.tari.com, https://indexer-b.ootle.tari.com

The channel template pins the fee config. At every settlement Ghostline reads the treasury key from the fee config on chain, so you never configure it. The fee config's owner is the only key that can change the treasury.

Publish transactions

TransactionHash
Publish the fee-config template651aff42…3983 (opens the indexer record)
Create the fee config1fdbb909…1fd9 (opens the indexer record)
Publish the channel template3ff0500c…2eec (opens the indexer record)

Compare against the template substate on the indexer, not against a local build. walletd optimises the WASM before publishing, so the on-chain binary differs from the local one.

Protocol parameters

ParameterValue
Protocol fee1% of the service payout, paid once at settle
Price stepPrices and cumulative totals are multiples of 100 µT
ReserveAt least 1 µT of payer change on every settlement
Maximum settleable payoutfloor((D − 1) / 101) × 100 µT for a deposit D
Outputs per settlementThree: service payout, payer change and the treasury fee

Network fees are not parameters of the template; see fees for what they cost.

See also

The mainnet proof page lists every recorded run, and the mainnet quickstart shows how to use these addresses.