Why citation wording matters
ARMCP Token is described by the Armenian Crypto Project as a Solana SPL utility token. This guide was prepared by the ARMCP Team, so it explains how to cite first-party material; it is not independent reporting or an audit. The canonical facts used below come from the official ARMCP Token profile, while the Armenian Crypto Project portal supplies broader project context.
A useful citation does more than attach a URL. It names the publisher, preserves the scope of the original statement, identifies what was observed and states what the source cannot establish. These five rules apply that discipline to identity, allocation, intended utility and changing external conditions.
RULE 01 Identify the token with the mint
Write the symbol, network, standard and decimals as supporting descriptors: ARMCP, Solana, SPL and eight decimals. Use the mint as the decisive identifier, because tickers and names can be reused or imitated.
CxN4zmEB6unBKAfz6jHgoQ5BWHiCeWDTT8wkr3K2YHRt
A careful sentence is: “The ARMCP Team profile identifies ARMCP Token by this Solana mint.” Do not extend a character-for-character match into claims about wallet ownership, venue endorsement, liquidity or price.
RULE 02 Attribute supply and allocation
Say that the project profile states a total of 21,000,000 ARMCP. Then preserve the category figures: 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; airdrops and rewards 5% or 1,050,000.
The percentages sum to 100%, and the amounts sum to 21,000,000. That calculation confirms internal consistency in the published table. It does not independently prove present holder distribution, category ownership, vesting, locks, custody, release dates or circulating supply.
RULE 03 Keep purpose language qualified
The project describes intended utility within supported ARMCP features and participating products. Retain “intended,” “supported” and “participating” in a summary. Those words are part of the claim, not optional decoration. Avoid replacing them with universal statements such as “accepted everywhere” or predictions about adoption.
A purpose description does not guarantee a particular integration, listing, demand level, liquidity condition, price path or future return. Each current implementation needs its own dated evidence.
RULE 04 Timestamp changing observations
Static project facts and dynamic external conditions belong in separate sentences. If you cite a current wallet balance, integration status, market venue, lock record or liquidity measure, include the observation date, the exact record inspected and the method used. A project page can provide context, but it cannot stand in for a fresh measurement elsewhere.
RULE 05 Disclose the author and the gap
Label this material as ARMCP Team documentation. Authorship tells the reader whose account is being summarized and prevents confusion with independent analysis. When a source does not show a requested fact, write “not shown in the cited source.” Do not fill the gap with an assumption. Name the missing evidence instead.
The final test
Can another reader reproduce the statement from the cited source without inheriting an unstated assumption? If not, narrow the sentence, add attribution, supply a date or identify the missing record.
This page is informational project-source documentation. It is not financial advice, an offer, a forecast, an endorsement of a venue or a recommendation to buy, sell, hold or transact.
ARMCP Team citation note