CO45T C45 · BASE · PRE-LAUNCH
PRE-LAUNCH · BASE · RC5 TOKENOMICS IN FINALIZATION
TOKEN IDENTITY CO45T C45

Security engineered.
Fixed by design.

CO45T is a fixed-supply Base token created by a solo security researcher to support real vulnerability research, CTF competitions, open-source tooling and security education—without hidden minting, upgrade controls or single-person treasury authority.

Explore RC5 tokenomics Coming soon
No official contract address yet. Only trust the contract address eventually published on this official website and BaseScan.
Maximum genesis supply
45,000,000 C45
Maximum unlocked at launch
3% 1.35M C45
Token admin
None by design
CO45T artwork featuring Mount Taranaki, ocean waves and CO45T branding
FIXED SUPPLY
BASE / 8453
SECURITY RESEARCH
PROJECT ARTWORK Original CO45T visual identity
01 / WHAT CO45T IS

A token with a deliberately small control surface.

CO45T is being designed as a simple fixed-supply ERC-20 on Base. The token contract is intended to minimize privileged control and common token attack surfaces rather than depend on an administrator to intervene after launch.

The project is currently pre-launch. There is no deployed C45 contract, no official contract address and no claim that the final production code has completed external review.

01

Minimal privilege

No token owner, administrator, proxy upgrade authority, pause switch or blacklist role.

02

Fixed issuance

Exactly 45,000,000 C45 maximum genesis supply with no future minting path.

03

Transparent treasury

Proposed allocations are separated across six Safes with a 2-of-3 signing threshold.

04

Research purpose

Designed to support vulnerability research, CTFs, open-source security tooling, education and research grants.

Full original CO45T project artwork

ORIGINAL PROJECT ART Used here without redesign or distortion.

02 / WHY IT EXISTS

Put security work at the center, not the edge.

CO45T is intended to create a long-duration pool of resources for practical security work. The emphasis is on real research output rather than artificial activity metrics.

Vulnerability researchIndependent investigation of real software and smart-contract attack surfaces.
CTF competitionsHands-on adversarial challenges that reward useful security skills.
Open-source toolingUtilities, PoCs, test harnesses and defensive research made available to others.
Education & grantsSecurity learning material and research grants where treasury policy permits.
03 / SECURITY BY DESIGN

Remove powers the token does not need.

The design goal is not “unhackable.” It is to minimize privileged control and common token attack surfaces with a smaller, easier-to-reason-about contract model.

c45 / proposed-control-surface
MINT_AFTER_GENESISDISABLEDNo future minting
TOKEN_OWNERNONENo owner or token administrator
PROXY_UPGRADESDISABLEDNo implementation replacement
PAUSEDISABLEDNo privileged global transfer halt
BLACKLISTDISABLEDNo privileged address blocking
TRANSFER_TAX0%No token transfer tax
BALANCE_SEIZUREDISABLEDNo arbitrary forced balance removal
BURN_FROMDISABLEDNo allowance-based burnFrom
SELF_BURNENABLEDHolders can burn only their own C45
!

Security engineering is risk reduction, not a guarantee. A smaller privilege surface can reduce certain classes of risk, but it cannot prove the absence of implementation bugs, ecosystem failures, signer compromise, liquidity risks or every future attack technique.

04 / PROPOSED RC5 TOKENOMICS

45 million C45. Fixed at genesis.

RC5 is still being finalized. The table below is a proposed pre-launch allocation, not an on-chain state claim.

Proposed RC5 allocation schedule
AllocationC45ShareSchedule
Total45,000,000100%Fixed supply
MAXIMUM PROPOSED UNLOCKED AT GENESIS 1,350,000 C45
3%

Maximum unlocked is not the same as circulating supply. Unlocked tokens can still remain in Safes, liquidity positions, project wallets or otherwise unmoved. Circulation depends on actual distribution and use.

05 / MAXIMUM PROPOSED UNLOCK

Inspect every milestone.

This is a maximum unlock schedule. It does not forecast market supply, sales, liquidity or price.

MilestoneLaunch
Maximum unlocked1,350,000 C45
Share of supply3%
Maximum proposed C45 unlock schedule Launch 3 percent, Year 1 20.55 percent, Year 2 38.10 percent, Year 3 55.65 percent, Year 4 73.20 percent, Year 5 85 percent, Year 8 100 percent.
Maximum unlocked ≠ circulating supplyActual circulating supply can be lower at every milestone.
06 / SECURITY RESEARCH & CTFs

Funding is intended to follow useful security work.

The proposed security allocation is split between a small launch reserve and a long-term reserve so the entire security budget is not immediately available at genesis.

Security launch reserve450,000 C451% · available at genesis through Rewards Safe
Security long-term reserve15,300,000 C4534% · five years linear · no cliff
01

Bug rewards

Reward reproducible, useful security findings under published program rules.

02

CTF competitions

Run adversarial technical challenges with transparent rules and outcomes.

03

Open-source work

Support tools, public PoCs, test infrastructure and defensive research.

04

Research grants

Longer-horizon support for technically useful security work where approved.

07 / TREASURY & SAFE TRANSPARENCY

Six allocations. Six separate Safes.

Token immutability and treasury governance are separate things. The C45 token is designed without a token administrator; treasury allocations are proposed to be managed through distinct Safe accounts.

2-of-3 signer threshold
01Rewards Safesecurity launch + long-term
02Liquidity Safeliquidity growth
03Ecosystem Safeecosystem allocation
04Community Safecommunity & CTFs
05Development Safedevelopment allocation
06Founder Safefounder allocation
SAFE COUNT6
THRESHOLD2 / 3
SINGLE-SIGNER TRANSFERNO

Under the proposed policy, no single signer can authorize a treasury transfer alone. This reduces single-key risk, but it does not eliminate governance risk: signer compromise, collusion, operational errors and malicious approvals remain possible.

Pre-launch transparency items
  • Safe addresses: coming soon
  • Signer addresses: coming soon
  • Vesting contracts: coming soon
  • On-chain allocation verification: after deployment
08 / ROADMAP

Publish evidence as each step becomes real.

  1. NOW
    Finalize RC5

    Lock the final allocation, vesting and Safe deployment parameters.

  2. NEXT
    Freeze production contracts

    Complete testing and review of the exact deployment code and scripts.

  3. THEN
    Deploy to Base

    Create the fixed genesis supply and treasury infrastructure.

  4. VERIFY
    Publish and verify

    Verify source on BaseScan and publish the official contract and Safe addresses here.

  5. LAUNCH
    Initialize public launch state

    Publish final documentation and clearly identify official liquidity information.

09 / AUDIT & VERIFICATION

Trust the deployed code, not a badge.

CO45T is pre-launch and has no official deployed contract yet. No external audit badge is displayed because there is no final public production audit report to point to here.

At deployment, the goal is to make verification practical: publish the exact official address, verify source on BaseScan, disclose final supply and treasury addresses, and link the code repository and documentation.

DEPLOYMENT_VERIFICATION
NETWORKBASEPLANNED
CHAIN_ID8453KNOWN
CONTRACT_ADDRESSNOT DEPLOYEDPENDING
BASESCAN_SOURCENOT AVAILABLEPENDING
GITHUBPLACEHOLDERPENDING
DOCSPLACEHOLDERPENDING
EXTERNAL_AUDIT_REPORTNONE PUBLISHEDDISCLOSED
10 / RISKS & LIMITATIONS

Security design does not remove market or operational risk.

01

Software risk

Security engineering does not guarantee the absence of every vulnerability.

02

Market risk

C45 has no guaranteed price, return, liquidity depth or future market demand.

03

Unlock risk

Token unlocks may increase available supply and can affect market value.

04

Liquidity risk

Cryptocurrency and liquidity pools can be highly volatile and may experience severe slippage.

05

Signer risk

Two signatures are required for proposed treasury Safes, but compromise or collusion remains a governance risk.

06

Information only

Website content is informational and is not financial, investment, legal or tax advice.

11 / FAQ

Pre-launch questions.

Anything that depends on deployment is marked as pending rather than guessed.

Is C45 live yet?

No. CO45T is pre-launch and the final production token has not been deployed.

What is the official contract address?

There is no official contract address yet. Do not trust addresses sent through DMs, replies, ads or unofficial websites. The final address should be checked here and on BaseScan after deployment.

Can more than 45,000,000 C45 be minted?

The proposed design has exactly 45,000,000 C45 maximum genesis supply and no future minting function.

Can an owner pause transfers or blacklist wallets?

The proposed token design has no token owner or administrator, no pause control and no blacklist control.

Does 3% unlocked at launch mean 3% is circulating?

No. It is the maximum proposed amount technically available at genesis. Actual circulating supply depends on distribution, liquidity, Safe balances and other real on-chain activity.

Who controls treasury funds?

RC5 proposes six separate Safe accounts using a 2-of-3 threshold. No single signer can approve a transfer alone, but signer compromise or collusion remains a governance risk.

Has CO45T been audited?

No final external production audit report is published on this site. Any future audit or review will be linked directly rather than represented by an unsupported badge.

Is C45 designed to go up in price?

No price or return is guaranteed. C45 is a volatile crypto asset if and when it launches, and the project purpose does not guarantee market value.

C45
OFFICIAL LINKS

Nothing is live until it is published here.

Contract and project links remain placeholders until real destinations are available.

Contract Coming soon BaseScan Coming soon GitHub Coming soon Documentation Coming soon X Coming soon Discord Coming soon