Smart contracts

BashardToken, Staking and the Bashard core contract. No deployed addresses exist.

Three Solidity contracts form the control plane. They hold no file data, only commitments, balances and membership.

BashardToken (BSHD)

The ERC-20 used to pay for tapes and to stake. Under mainnet rules there is no faucet, and supply and ownership move to the treasury address. Contract deployment is deferred until the original token exists.

Staking

Holds one share-based pool per node. Functions used by clients include delegate, requestUnstake, withdraw and claimCommission. Applies reward compounding, 2-epoch unbonding and slashes.

Bashard core

The coordination contract. Responsibilities:

• Node registration with endpoint, signer and commission.
• Tapes: reserve, quote, extend, expand.
• Tracks: registerTrack, certifyTrack, delete, lookup by tape and key.
• advanceEpoch, fee distribution, committee selection.
• slash with a two-thirds quorum of committee signatures: 5% burned, 2 epochs jailed.

Owner and treasury roles

For a mainnet deployment the deployment tooling refuses to run without explicit OWNER and TREASURY addresses and an explicit EPOCH_SECONDS. It validates that these are addresses; it does not enforce that they are multisig wallets. Ownership of all three contracts moves to the owner address. Using a multisig for both roles is recommended to reduce single-key risk, but it is the deployer's choice. A timelock in front of the owner and a decision on upgradeability are open items. Those values are configured by the deployer; this documentation does not publish or request them.