Solver bonding & $OCLU

What $OCLU is for, who needs it, and how slashing works.

$OCLU is the protocol's native token. It has two independent roles: collateral for solvers, and a separate staking pool where any holder earns a share of protocol revenue. Trading never requires it. The token contract is live; bonding and staking are not yet active and will be switched on separately.

bonding & slashing
Solver stakes $OCLU→Registry→Audit
within toleranceRouting priority maintained
deviation flaggedBond slashed→Paid to trader

Registering

To operate, a solver posts an $OCLU bond to the Solver Registry contract.

Priority

Routing priority is weighted by integrity_score × √bond. The square root is on purpose: doubling a bond does not double a solver's allocation, so size alone does not win.

Unbonding

A withdrawal timelock stops a solver from leaving before any pending audit resolves.

Slashing

A confirmed audit failure slashes part of the bond. The slashed amount goes to the affected trader, and the rest goes to the protocol treasury. The system is only secure while the stake a colluding majority would lose is larger than what an undetected leak could earn. Setting bond sizes and slash rates to keep it that way is an ongoing operating task.

$OCLU staking pool

A second, entirely separate pool lets any holder stake $OCLU and earn a share of protocol revenue: a small routing fee taken on each shielded trade, plus the treasury's portion of slashed solver bonds.

Separate from bonds
Staking in this pool has no effect on solver routing priority or accountability, and is never slashed by the audit. It is purely revenue sharing for holders who want exposure to protocol activity without running a solver.