CAWELON CORE (CAWELON) is an ERC-20 token on Base Mainnet and one of the three tokens in ThreeCore, alongside DAT and EMA. This document describes the token contract, the wallet software under development, the public training testnet and the intended agent system.
1. Token specification
- Name / symbol
- CAWELON CORE / CAWELON
- Network
- Base Mainnet · chain ID 8453
- Contract address
- 0xB4654b5a4617Fe2c27a0DD6EAEe98F8AA941b895
- Initial issuance
- 420,000,000,000,000 CAWELON, minted once at deployment. Burns can reduce the current total supply.
- Decimals
- 18
- Token-level transfer tax
- 0%. Network gas and third-party exchange fees remain separate.
- Standard functions
- Transfers, balances, allowances, holder burn, allowance-based burnFrom and EIP-2612 permit.
- Privileged controls
- No owner/admin role, additional mint function, pause, blacklist or upgrade mechanism in this token implementation.
The initial supply is assigned to the initial-holder address at deployment. A holder can burn its own tokens; burnFrom requires an allowance from the holder. The contract does not automatically trade, manage liquidity or generate earnings.
Reference: CAWELONCore.sol — direct source code and the deployment and verification record. Source verification and automated checks do not constitute an independent security audit.
2. ThreeCore Wallet: current development scope
The shared wallet software provides separate DAT, EMA and CAWELON cards for reviewing public wallet information. The October 23 source publication includes:
- Token identity, exact decimal balances and existing allowance observations at a recorded block, with checks for account, network and block changes.
- Saved balance history, filtering, comparisons and import previews that keep failed reads distinct from zero balances.
- Browser-local checkpoints and three-card workspace backups, with reviewed restoration, revision checks and recovery information for storage failures.
- Offline inspection of exported backup, identity and allowance files. Imported settings do not grant wallet permissions or reconnect a session.
These are read-only development workflows. They do not add signing, transfers, approvals, revocations, swaps, bridges, custody or autonomous spending. Separate operational wallets for all three agents and production compatibility still require their own verification.
Saved data contains public addresses and historical observations, not private keys or seed phrases. Browser storage is unencrypted and specific to the browser and site origin. A checksum detects corruption; it does not establish ownership or a current balance. See the wallet release notes and verification scope.
3. Public training testnet
The CAWELON training application runs on Base Sepolia (chain ID 84532). DAT, EMA and CAWELON use a shared implementation with separate agent, game and training-credit contracts.
The published training flow covers deterministic arithmetic answers, credit accounting, owner/operator permissions, action limits and reserves, pause/resume, eligible training-credit burns and browser-local transaction history. A compatible wallet and Base Sepolia test ETH are required for transaction gas.
Training credits have no monetary value. A training-credit burn does not buy or burn the Base Mainnet CAWELON token. The training release does not connect an AI model, external revenue game or production buyback service. Transaction evidence and the limits of the recorded checks are documented in the project README.
4. Planned agent and wallet architecture
CAWELON: intended decision policy
CAWELON explores opportunities with higher potential returns, evaluating payout sources, settlement conditions, likelihood of success, capital requirements and the risk of loss. This is a proposed decision policy; higher potential returns can involve greater uncertainty and losses.
Each agent is intended to use the common ThreeCore architecture while keeping its funds, permissions and accounting separate. The agent would analyze information, evaluate an action and request execution within predefined limits. The ERC-20 contract supplies the token functions; the decision and execution components are separate software.
Funding and execution requirements
The target design separates fund ownership from execution permissions. Before any production operation, it must specify permitted services, funding sources, per-action and aggregate limits, reserves, settlement rules, failure handling and revocation/recovery procedures. Any proposed use of project-controlled DEX liquidity requires an explicit policy and authorization; the current release does not automatically withdraw or deploy liquidity.
Potential integrations include prediction-market and sports-betting dApps, DEXs and other DeFi services. Each would need a separately implemented and verified adapter, an approved operating policy and applicable access and jurisdiction checks. No specific external service, cross-chain route, allocation percentage or launch date is committed by this document.
Realized earnings and buyback & burn
The proposed workflow records settled proceeds, losses, fees and operating costs before calculating eligible realized net earnings. Subject to a defined reserve and allocation policy, part of those earnings could fund purchases and burns of CAWELON, with transaction records published for review. Direct dividends to holders are not part of this design.
Holder burn is available in the base token; revenue-driven buyback and burn remains a separate integration under development. No returns, token-price increase or continuous operation are guaranteed.
AGI-oriented development
The long-term direction is to accommodate increasingly capable agents, including possible future AGI, through a replaceable decision component. Independent permissions, spending limits and verifiable records should remain in place as capabilities change. AGI is a development ambition, not a capability claimed for the current token, wallet or training release.
5. Evidence and remaining work
Published source, automated test results and recorded testnet transactions provide evidence only for the workflows they cover. The next production requirements include separate live-wallet verification, external-service adapters, transaction execution controls, settlement and profit accounting, operational recovery and independent security review.
This overview records the documented development state as of October 23, 2026. Current balances, liquidity and execution conditions must be checked independently at the time of use. No token contract or wallet permission is changed by publishing this document.