Smart Contracts

Standard token, upgradeable under timelock. Spend splits 50% burn, 50% treasury. Narrow roles.

• Standard token. YAP follows a widely supported token standard on our chain. Transfers, approvals, and burns work as people expect.

• Upgradeability with guardrails. Code can be upgraded under a public timelock by a multisig. No surprise changes.

• Spend logic on chain. When an approved app wallet “spends” its own tokens, the contract burns 50 percent and sends 50 percent to the treasury. This is the sink that powers the economy.

• Gasless approvals. Users can sign an approval so the app can move tokens they authorized, without forcing them to hold gas.

Roles and limits

• Admin. Manages roles and the treasury address, under multisig control.

• Upgrader. Authorizes software upgrades, under timelock.

• Spender. Limited permission for vetted app wallets to call the onchain spend function on their own balances.

• No post-launch mint. Total supply is fixed at launch. There is no function to mint more.

• No seizure. The contract cannot move user funds without the user’s own transaction or signature.

Transfer lock for new rewards

• Cooling-off period. Newly earned tokens have a short transfer lock for off-app transfers, currently 24 hours.

• Use in app. You can spend locked tokens inside YAP immediately.

• Why this exists. It blocks instant farm and dump behavior and keeps rewards meaningful. The lock is enforced by the contract.

Parameters that can change

All changes use a public timelock and onchain events.

• Treasury address.

• List of approved spender wallets.

• Duration of the transfer lock for newly earned tokens.

• Allowlisted spending targets used by the app.

We publish a “parameters that can change” table with current values and maximum single-step adjustments.

Transparency

• Verified code. Contract source is verified on the explorer.

• Public addresses. Token, treasury, and multisig addresses are listed in the docs.

• Onchain events. Every burn and treasury receipt emits an event. Dashboards show circulating supply and total burned.

Security posture

• Multisig and role separation. Different keys for admin and upgrades.

• Timelocks. Non-emergency changes queue before execution.

• Audits and tests. Independent audits before token launch, with reports published. Property tests cover mint, burn, and spend invariants.

• Key hygiene. Hardware backed keys, rotation, and monitored access. Bug bounty at launch.

Bottom line: clear rights for users, predictable sinks for the economy, and tightly scoped powers under a timelocked multisig.