Mainnet deployment
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 template | ae13cead…ef9c (opens the indexer record) |
| Fee-config template | b3628ed0…9f45 (opens the indexer record) |
| Fee config | 37df6af5…0bb5 (opens the indexer record) |
| Network tag | 0 |
| Indexers | https://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
| Transaction | Hash |
|---|---|
| Publish the fee-config template | 651aff42…3983 (opens the indexer record) |
| Create the fee config | 1fdbb909…1fd9 (opens the indexer record) |
| Publish the channel template | 3ff0500c…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
| Parameter | Value |
|---|---|
| Protocol fee | 1% of the service payout, paid once at settle |
| Price step | Prices and cumulative totals are multiples of 100 µT |
| Reserve | At least 1 µT of payer change on every settlement |
| Maximum settleable payout | floor((D − 1) / 101) × 100 µT for a deposit D |
| Outputs per settlement | Three: 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.