The Impactivism Wallet

The Impactivism Wallet is where you exist on Impactium: where you come into being on-chain, turn your contributions into verified impact, and help shape the Universal Constitution.

What it does

The wallet is built around three verbs:

• Identity — hold the keys that are your on-chain Entity, and act as any Entity, Product, or organization you're a keyholder of.
• Contribution — submit impact claims, watch them move through attestation, and hold the capsules they mint.
• Voice — propose, advance, and vote on Constitution articles, and on the ActionCatalog.

On the word "wallet". A conventional wallet is built around one verb: transfer. This one has no such verb for Impactium, because the impact you hold cannot be moved (see Impact as Value). The name is kept because the thing it protects — your keys, your identity — is the same.

Keys, kept safe and conventional

The wallet uses standard, audited cryptography — hierarchical-deterministic keys derived from a recovery phrase, encrypted at rest so a wrong password fails rather than leaking anything. This is a deliberate choice: there is no philosophical reason to reinvent key handling, and every reason to use the battle-tested standards. Your keys never leave your device unencrypted.

One wallet can hold many named accounts — your personal Entity, an organization whose key you custody, an agent Product — and act as any of them. A single secured device can facilitate actions on behalf of everything you're responsible for.

Onboarding by referral

Because referral is the only door, onboarding has two sides:

• Joining. A new member installs the wallet and generates their keys locally — no chain involved yet. The wallet shows a join code (their public key), which they send to a member who is inviting them.
• Inviting. An existing member pastes that join code and signs the spawn. They are the door the new member enters through — and the new member joins their Chain of Impact.

The invitee's on-chain identity is known the moment their keys exist; their confirmed lineage — parent, root, depth — appears once the chain records the spawn.

Starting a network (operators)

Referral is the door for members — but the very first Entity on a brand-new chain has no one to refer it. On sim-nets and rehearsal networks, the wallet's Start page handles this: an operator points it at a running chain, and — only when that chain reports a sim/rehearsal identity and is still unbootstrapped — it plants the founding lineage in one atomic act. The first Spore is a human Entity at depth 0, the root the rest of the network germinates from; the founding organization is spawned beneath it. Each founding key is offered as a downloadable, password-encrypted file. On any live or already-bootstrapped network the action never appears; the page shows the command-line hand-off instead.

This is a safety rail, not just convenience: planting the roots of the live network is a deliberate command-line ceremony with out-of-band verification, never a browser click. The same principle extends to every privileged bootstrap role as those roles come to exist.

Contributions, honestly shown

When you submit a claim, the wallet shows its whole life: pending, attested, and then either minted into a capsule or failed — and failed claims are shown, with their scores, never hidden. The wallet renders exactly what the chain returns, because "you cannot hide -$IMP" is a property of the system, not a setting.

You can also self-log personal impact directly — gateless, permanent, labeled, and residual-inert — for the impact that no third party will ever notarize.

Reads from Karma, writes to the chain

The wallet keeps no private notion of truth. It signs actions locally and submits them to the chain, and it reads confirmed state from Karma, the public ledger. What you did is what the network recorded — nothing the wallet shows you is its own bookkeeping.