Real usage evidence

NimCarry separates human registration from wallet linking and protocol participation. These live counts come from production aggregate endpoints. No names, emails, invite tokens, target wallets, or raw wallet lists are exposed.

Evidence boundary

Registration is acquisition, not activation. A profile can be created with name + email and explicit privacy consent without Nimiq. We therefore do not use registration count as the strongest real-usage claim.

Nimiq verification requires a valid wallet signature. Activation requires that verified wallet to create a mission, accept an invitation, or participate in a FINAL hop after the wallet was verified. Finalized requires independently verified on-chain finality after verification.

This time ordering prevents pre-registry development/test activity from becoming real-user traction later just because an old wallet is linked. Screenshots containing user emails are not published as evidence.

Protocol runtime evidence

Mission/runtime counts can include controlled development or test activity and must not be interpreted as unique human users. Rate limits reduce abuse but are not treated as proof of humanity. NimCarry continues to state the stronger boundary: registration ≠ verification ≠ activation ≠ FINAL.