Dokumentasi/Whitepaper
Security
Contract properties and how to check them yourself.
Every contract is publicly verified and its properties were checked directly on-chain. The table below is the result of that check, not a claim.
Contract properties
| Property | Token | Curve | Vesting factory |
|---|---|---|---|
| Owner | None | None | None |
| Proxy / upgrade | None | None | None |
| Withdraw / rescue | — | None | None |
| Pause / blacklist | None | None | None |
| Transfer tax | None | — | — |
| Additional minting | None | — | — |
What nobody can do
- Change the contract code after deployment.
- Freeze or block token transfers.
- Take tokens from somebody else's wallet.
- Issue new tokens beyond the 1 billion supply.
- Withdraw assets from a vesting vault.
- Cancel a vesting schedule that has been created.
Checking it yourself
# token: no owner, no pause, no tax
cast call <token> "owner()(address)" # must revert
cast call <token> "paused()(bool)" # must revert
# curve: no owner, no withdraw
cast call <curve> "owner()(address)" # must revert
cast call <curve> "withdraw()" # must revert
# vesting vault: no owner
cast call <vault> "owner()(address)" # must revert
Beyond that, the bytecode deployed on-chain can be disassembled to confirm there is no
DELEGATECALL, SELFDESTRUCT or CREATE — meaning no proxy, no
self-destruct and no hidden contract inside.
ℹ️
Source verification was done through Sourcify,
so the code shown in a block explorer can be matched byte-for-byte with what runs on-chain.
Apakah halaman ini membantu?