• What a signed article can and cannot prove: ARMCP Token as a provenance example
  • Layer 1: the signature
  • Layer 2: the identity record
  • Layer 3: the arithmetic record
  • Layer 4: the purpose statement
  • A reader’s provenance checklist

§What a signed article can and cannot prove: ARMCP Token as a provenance example

A long-form Nostr article has a useful property: its event signature lets a reader verify which public key signed the exact content. That is evidence of authorship and integrity, but it is not a substitute for evidence about every statement inside the article. ARMCP Token offers a practical example of keeping those layers separate.

This article is published by the ARMCP Team. ARMCP Token is described by the Armenian Crypto Project as a Solana SPL utility token. The official ARMCP Token profile is the canonical project source used for the token fields below; the wider Armenian Crypto Project portal provides project context. These are first-party sources, not independent audits.

§Layer 1: the signature

The Nostr event signature supports two narrow conclusions. First, the event was signed by the public key shown by the reader. Second, changing the content would invalidate that signature. A signature does not prove that a token has a particular market value, that a wallet belongs to a named party, or that a stated allocation matches current on-chain distribution.

That boundary matters. Cryptographic provenance answers “who signed this exact record?” It does not automatically answer “is every claim current and independently verified?”

§Layer 2: the identity record

The project profile states the following identifiers:

• symbol: ARMCP;
• network and standard: Solana SPL;
• decimals: 8;
• mint: CxN4zmEB6unBKAfz6jHgoQ5BWHiCeWDTT8wkr3K2YHRt;
• stated total: 21,000,000 ARMCP.

The mint is the decisive comparison field. Names, tickers and logos can be reused, while a character-for-character mint match identifies the specific Solana token referenced by the project. Even a correct match does not establish wallet ownership, endorsement of a venue, liquidity or price.

§Layer 3: the arithmetic record

The published allocation is 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.

Two checks are reproducible from those numbers. The percentage column totals 100%. The amount column totals 21,000,000. Each amount also agrees with its stated percentage of the total.

This proves internal consistency in the published table. It does not prove current holder balances, custody, locks, vesting, release dates, circulating supply or the present contents of category wallets.

§Layer 4: the purpose statement

The project describes intended utility within supported ARMCP features and participating products. A careful summary keeps the qualifiers “intended,” “supported” and “participating.” The statement does not guarantee integration, adoption, universal acceptance, an exchange listing, demand, liquidity, price performance or future returns.

§A reader’s provenance checklist

For any signed token article, record five items separately:

1. the signer and event identifier;
2. the cited source and observation date;
3. the exact token identifier;
4. calculations that can be reproduced from the source;
5. claims that still require current independent evidence.

This layered approach preserves the real value of signed publishing without asking the signature to prove more than it can. For ARMCP, the signed record establishes authorship; the project profile establishes what the project states; arithmetic establishes internal consistency; and separate dated records are still needed for changing external conditions.

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.