Security & permissions

Permanently locked principal #

The current deployed liquidity adapters expose no Admin rescue or LP-principal withdrawal path. Token supply and creator fee selection are immutable. Campaign contribution escrow and backer claims are governed by each campaign’s state machine.

Locking cannot guarantee profitable trading or recover liquidity after an immutable dependency failure. The official V4 manager retains its external protocol-fee authority; the integration accounts for the separately approved venue fee rather than representing it as RUKUS revenue.

Administrative and emergency controls #

Contract Admin configures authorized integrations and factory permissions. Pauser/Emergency roles can exercise the pause controls defined by each contract. Application administration is a separate signed-session allowlist and does not grant contract or treasury authority.

Pausing new activity is not an asset seizure or a forced migration. Curve sells and accrued fee claims have dedicated protections; campaign refunds and backer claims remain subject to their immutable eligibility rules. Always inspect the particular deployed contract when integrating.

Immutable contracts and future versions #

These deployed contracts are not upgradeable proxies. A new factory or adapter version can apply to future launches; it does not rewrite existing tokens, escrow or locked positions. Old assets cannot be forcibly migrated through a dashboard.

Verification is not an audit #

Contract source reproduction and Sourcify verification link source to deployed bytecode. They do not establish that the code is free of vulnerabilities. No published independent security audit is claimed in this documentation.

Use the public source repository and deployed manifest to inspect exact implementations. Report suspected issues privately through the project’s official contact channels; never send private keys or recovery phrases.