PIKO | Wallet Console

Browser-generated wallet | MetaMask claim | Direct node submit

Turn the landing page into a real control surface for claim, transfer, and block confirmation.

This console now focuses on operations, not only presentation. Generate a native Lamport wallet in the browser, connect the founder EVM wallet through MetaMask, sign the claim message, submit transfers directly to the node, and confirm the next block from the same UI.

Open Console Inspect Network

Founder reserve address

0x30514237625b9e4206c728ff551725b4bf9d4a85

Quick action

Production note: the deployed HTTPS site can only call an https:// node endpoint. If your node runs on http://127.0.0.1:8080, open the site locally during development or expose the node over HTTPS.

Native wallet in browser

Generate Lamport keys locally with Web Crypto, persist them in local storage, and export the JSON wallet file on demand.

Founder claim via MetaMask

Request the exact claim message from your node, sign it with the founder EVM wallet, then submit it back as an on-chain claim.

Direct transaction submit

Sign native transfers client-side and post the full transaction to /tx/submit without sending private keys to the node.

Interactive Console

Wallet, claim, transfer, and block controls

The current prototype still uses one-time Lamport addresses. Treat every sender wallet as disposable and avoid partial sends from important balances until we move to a production-grade signature and account model.

Node API endpoint

Start by loading the static genesis snapshot or connect a live node API. Wallet, claim, and transfer actions require a live node.

Native PIKO Wallet

offline

Keys are generated in-browser and never sent to the node. Download the wallet JSON if you want an external backup.

Import Wallet JSON

Lamport sender addresses are single-use in this prototype. After you spend from one wallet, rotate to a fresh wallet for the next send.

Founder Claim Bridge

metamask

Only the founder wallet 0x3051...4a85 can sign the checked-in genesis claim. Connect MetaMask before submitting.

Claim message preview

Transfer PIKO

native tx

Transfers are signed client-side and submitted to /tx/submit. This is safer than passing the private key to the node.

Recipient address Amount Note

Prototype warning: because Lamport wallets are treated as one-time senders here, avoid partial sends from long-term holdings.

Block Confirmation

operator

Use your active native wallet as the miner or proposer to include pending claim and transfer transactions in the next block.

In validator mode the node will only accept the selected proposer for the current height.

Activity Log

0 events

Network View

Chain state and consensus snapshot

This section combines the static genesis snapshot with live node metadata when available. It is meant to help the operator see current height, pending transactions, validator thresholds, and founder-claim status at a glance.

Chain Metadata

snapshot

{}

Consensus and Status

snapshot

{}

Genesis Tokenomics

Genesis allocation and founder reserve tracking

The current checked-in plan distributes 1,000,000,000 PIKO across founder treasury, ecosystem, community, validator rewards, liquidity, AI and privacy research, and operations.

Founder Claim Status

Genesis bridge state for the founder address

This panel tracks whether the founder allocation is still available, already pending in the mempool, or fully claimed into a native piko1 address.

Create or import a native wallet in the browser.
Connect the founder EVM wallet in MetaMask.
Request the claim message from a live node endpoint.
Sign, submit, and confirm the next block to finalize the claim.

Claim Snapshot

snapshot