ARCP is the prospective ARCHCOIN Payable token. It has not launched. The Payable concept is part of the planned four-token ARCHCOIN architecture.
ARCP
Launch statusProspective · Not launched
Concept
Contract constructed
Compiled
Tested
Local EVM deployed
Signed transaction qualified
Not launched
Plane 01 · Identity
Outgoing obligation becomes a bounded protocol unit.
ARCP / Overview
Domain role
ARCP identifies the Payable domain inside the four-asset architecture. It is associated with what must leave, how an obligation moves toward execution, and how settlement is constrained.
Asset identity
Name: ARCHCOIN Payable. Symbol: ARCP. Standard: ERC-20 on the Ethereum EVM family, using 18 decimal places.
Not launched
ARCP remains prospective. Local implementation and transfer qualification do not establish a public launch. No public contract address or deployment transaction is announced for this token.
Plane 02 · Construction
Transferable behavior without an administrative back door.
ARCP / Engineering
Implementation
ARCP is instantiated by the shared Solidity 0.8.28 ArchcoinFixedSupply.sol contract, built on OpenZeppelin Contracts 5.4.0 ERC20.
Fixed-supply behavior
The constructor mints once to a nonzero recipient. No callable mint, public burn, ownership role, pause switch, or privileged mutation function survives deployment.
Qualification
Hardhat 2.28.0 and Toolbox 6.1.0 compile and test ARCP. Local EVM qualification deploys the contract and signs a transfer while proving total supply remains fixed.
Supply boundary
The 1,000,000-unit test fixture is engineering evidence, not an authorized issuance decision. Network supply and recipient wallet remain unfrozen.
Plane 03 · Traversal
Local settlement behavior precedes public-network evidence.
ARCP / Platform
Current surface
The repository contains ARCP’s shared source, compiler setup, tests, local deployment, and signed-transfer qualification. That establishes a working local implementation.
Before a public launch
A public launch requires a separately qualified release, confirmed network and supply, a recipient, and explicit deployment authorization. No launch date is announced.
Evidence after deployment
The platform will expose a contract address and transaction evidence only after on-chain bytecode and ERC-20 behavior can be independently retrieved and checked.
Launch status
ARCP is not deployed on Ethereum mainnet. ARCC and ARCR have launched; their deployments do not establish a launch for ARCP.
Plane 04 · Constraint
A token name cannot authorize a payment.
ARCP / Governance
Immutable token constraints
No post-deployment mint.
No public burn in version one.
No privileged token mutation.
Public launch requires separate release qualification and authorization.
Holder-rights boundary
ARCP creates no legal payment obligation, settlement guarantee, redemption right, creditor status, equity position, governance power, or ownership claim.
Public status
ARCP is a prospective token with a locally qualified implementation. It is not a launched cryptocurrency. Any future launch will need its own verifiable contract address and transaction record.