Staking and funded protocol services

The reference staking profile uses actual JOLT, share-based positions and explicitly configured penalties. These are development rules, not a public staking product or promised return.

Stake positions

The reserved service at 0x101c authenticates operators, delegators and reporters. Validator registration uses distinct BLS keys with proof of possession. Bonded positions provide eligible committee weight; unbonding positions no longer contribute weight but remain subject to the profile's accountability window.

Double-sign evidence binds conflicting authorized votes to the same consensus context. A successful evidence claim can slash stake and bar the validator under the configured profile. Delegators share the economic loss. Missing a slot is not the same evidence as signing conflicting votes.

Consensus membership is established by authenticated assignments/transitions, not merely by receiving stake or connecting a TLS peer. Production committee randomness and economic calibration remain open.

Funded services

SAFU (0x101d) accepts funded JOLT reserves and committee-authorized claims. Quorum is strictly more than two-thirds of the configured committee. Payout authority is limited to the fund's reserves. This is not blanket insurance or a promise that every loss will be compensated.

Vesting (0x101b) locks an exact funded JOLT amount for a fixed beneficiary under a linear schedule with a cliff. It does not define total supply or a launch allocation.

LP farm (0x101f) distributes rewards from its funded budget to eligible LP stake. A configured emission rate is not a guaranteed market yield.

Match service encodings, limits, replay protection and genesis configuration to the deployed protocol version before integration. No published token figure grants minting authority. See tokenomics and vesting.