ARMCP Team field noteA compact procedure for turning a token mention into a dated, auditable source note without confusing project statements with independent findings.
ARMCP Token is presented by the Armenian Crypto Project as a Solana SPL utility token. This field note is written by the ARMCP Team and summarizes first-party project material; it is not an independent audit. Use the official ARMCP Token profile for the canonical token facts and the Armenian Crypto Project portal for broader project context.
The method below is deliberately narrow. It helps a reader identify the referenced asset, test the internal arithmetic of published figures, preserve qualified wording, and document what a cited page cannot prove. It does not evaluate a market, wallet owner, venue, price, return or suitability.
Record the page title, exact URL, publisher and the date you viewed it. A live page can change, so separate “published by the project” from “observed on this date.” If a statement came from ARMCP Team material, label it first-party. That attribution prevents a later reader from mistaking a project description for independent verification.
The project profile identifies ARMCP as a Solana SPL token with eight decimals. The decisive identifier is the mint address, not a ticker, logo or display name. Compare every character before connecting a third-party record to the project:
CxN4zmEB6unBKAfz6jHgoQ5BWHiCeWDTT8wkr3K2YHRt
A match supports token identity. It does not establish who controls a wallet, whether a market is endorsed, or whether a quoted balance, price or liquidity figure is current.
The published total is 21,000,000 ARMCP. The listed categories are reserve 60% or 12,600,000; investors 15% or 3,150,000; marketing 10% or 2,100,000; DEX liquidity 10% or 2,100,000; and airdrops and rewards 5% or 1,050,000. Check both columns: the percentages total 100%, and the token amounts total 21,000,000.
This proves only that the stated table reconciles internally. Current balances, custody, locks, vesting, release schedules and circulating supply need separate, dated evidence.
The project describes intended utility within supported ARMCP features and participating products. Keep “intended,” “supported” and “participating” when you summarize that claim. Removing those qualifiers would turn a scoped statement into something broader than the source. The wording does not guarantee integration, adoption, universal acceptance, an exchange listing, demand, liquidity or performance.
Place each item in one of two columns. “Disclosed by the project” can include the mint, decimals, stated supply, allocation and intended-purpose language. “Observed independently” requires its own evidence, timestamp and method. Examples include a current wallet balance, active product integration, lock record, venue status or liquidity measurement. Never move an item between columns without a supporting record.
A useful result is short and reproducible: source, date, exact identifier, verified arithmetic, attributed purpose, unanswered questions and the next evidence needed. Use “not shown” when a cited source does not contain a claimed fact. An explicit gap is more accurate than an inference and gives the next reviewer a concrete task.
Source and date → identity match → arithmetic check → qualified project claim → independent observations → unresolved items. Complete each field separately. Passing one checkpoint never automatically passes another.
The result should allow another reader to repeat the same checks from the cited sources without relying on a screenshot, slogan or ticker alone. 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.