• A portable verification note for ARMCP Token readers
  • 1. Start with the identifier, not the ticker
  • 2. Recompute the published allocation
  • 3. Keep purpose attributed
  • 4. Record what the signed article establishes

§A portable verification note for ARMCP Token readers

Long-form Nostr publishing is useful when an article should remain attributable to its author while being readable through more than one client. That portability does not make every claim true; it simply makes the signed source easier to inspect. The same distinction matters when documenting a token.

This note introduces ARMCP Token, the Solana SPL utility token described by the Armenian Crypto Project, and gives Habla readers a compact verification routine. It was prepared by the ARMCP Team from project materials. That affiliation is disclosed because provenance is part of the evidence. The note is informational, not independent research, financial advice, or a prediction.

§1. Start with the identifier, not the ticker

The canonical ARMCP Token profile states the symbol ARMCP, the Solana network, eight decimals, and this mint:

CxN4zmEB6unBKAfz6jHgoQ5BWHiCeWDTT8wkr3K2YHRt

A ticker can be reused by unrelated assets, while the full mint identifies a specific token on Solana. A careful reader should compare every character with a current independent on-chain record before treating any wallet, market, or transaction as related to ARMCP.

§2. Recompute the published allocation

The project profile gives a total of 21,000,000 ARMCP and the following allocation:

• 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 add to 100%, and the token amounts add to 21,000,000. Each amount also matches its stated percentage of the total. This proves that the displayed table is internally consistent. It does not prove current wallet balances, circulating supply, custody, vesting, trading depth, or distribution timing.

§3. Keep purpose attributed

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

That wording should remain attributed to the project. Intended utility is not evidence of guaranteed adoption, exchange availability, demand, price performance, or future returns. Those are separate questions requiring current and independent sources.

§4. Record what the signed article establishes

The Nostr signature establishes which public key authored this version of the article. Habla provides a readable public presentation, while compatible clients can retrieve the same kind 30023 event from relays. Neither the signature nor the reader interface validates the token’s market status.

The defensible conclusions are deliberately narrow:

1. the ARMCP Team published this explanation under its Nostr identity;
2. the project-source identity fields and allocation are reproduced here;
3. the arithmetic of the stated allocation checks out;
4. current market and on-chain conditions remain outside this note.

That boundary is the useful part. It lets readers separate authorship, source claims, reproducible calculations, and unanswered questions instead of treating them as one undifferentiated promotional statement.