A static source card for checking ARMCP Token claims

A compact, reproducible way to separate token identity, published arithmetic, intended utility and still-unanswered questions.

What this page introduces

ARMCP Token is described by the Armenian Crypto Project as a Solana SPL utility token. This page was prepared by the ARMCP Team from project materials, so it is a first-party explanation rather than independent coverage. It is designed as a static source card: the essential claims are kept on one page, in plain language, with the exact identifier and arithmetic visible.

The starting source is the official ARMCP Token profile. It states the symbol ARMCP, eight decimals, a total of 21,000,000 tokens and this Solana mint:

CxN4zmEB6unBKAfz6jHgoQ5BWHiCeWDTT8wkr3K2YHRt

A ticker is not a unique identifier. Readers should compare every character of the mint with a current independent Solana record before associating a wallet, balance, transaction or market with ARMCP. Matching the mint answers the identity question only; it does not prove ownership, liquidity, circulating supply or current activity.

Check the published allocation as two totals

The profile assigns the stated 21,000,000 ARMCP supply across five categories. The percentages should total 100%, and the corresponding token amounts should separately total 21,000,000.

Category	Share	Amount
Reserve	60%	12,600,000
Investors	15%	3,150,000
Marketing	10%	2,100,000
DEX liquidity	10%	2,100,000
Airdrops and rewards	5%	1,050,000

Both totals reconcile. That demonstrates internal arithmetic consistency in the published table. It is not evidence of present wallet distribution, custody, vesting, locks, release dates, circulating supply or market depth. Each of those is a separate, time-sensitive question requiring dated evidence.

Keep intended utility qualified

The Armenian Crypto Project portal presents broader project context around crypto information, market data, social features, functions, tools and games. The token profile describes ARMCP as intended for utility within supported ARMCP features and participating products.

That wording should stay attributed and conditional. “Supported” and “participating” do not mean universal acceptance, guaranteed adoption, an exchange listing, demand, liquidity, price performance or future returns. A responsible summary preserves those limits instead of turning an intended use into a promise.

This material is informational project-source documentation. It is not financial advice, an offer, a forecast or a recommendation to buy, sell, hold or transact.

What the static format proves—and what it does not

This nsite is published as content-addressed files referenced by a signed Nostr site manifest. A reader or gateway can compare file hashes with that manifest and verify which Nostr public key authorized the version. This improves portability and makes silent file substitution easier to detect.

Transport integrity is not claim validation. A matching signature and file hash establish authorship and file consistency; they do not independently verify token economics, wallets, adoption or external market conditions. The defensible reading sequence is therefore: confirm the mint, reproduce the two allocation totals, preserve the qualified utility statement, identify the author and list the facts that still need independent, dated evidence.