Chains Features Desktop App Status Apply to Launch
Browser + Native Proof-of-Work

Launch Your Own
Privacy Blockchain

Generate a complete CryptoNote chain, native-mining pool, and independently runnable node source. Privacy and consensus claims remain test-gated.

Public beta: launches are experimental, valueless test chains. PowPad does not endorse a coin, promise privacy, investment returns, continued hosting, or exchange access.
Apply to Launch View Chains
0
Chains
--
Miners
--
Hashrate
--
Blocks

Launches

Live and building chains show up here as they go through review and deployment.

Testnet Launch Stack

Reviewed components for disposable, explicitly valueless beta networks

⛏️

Real PoW Mining

Choose browser-compatible or native-only proof-of-work. Every pool share is daemon-verified, and every launch has a unique network and genesis.

🔒

Privacy-Capable Protocol

Built from CryptoNote primitives including ring signatures and stealth addresses; each production fork still requires independent review.

⚙️

Custom Economics

Configure block time, rewards, halving schedule, tail emission, and fee burning.

🌐

Mobile Wallet + Pool Dashboard

Create or restore a self-custody address and monitor pool rewards on a phone. Phones never hash. The current universal app supports full-node solo mining only where a signed engine package exists; a public native pool miner remains a release gate.

Future Network Tooling

Trading and exchange services are not part of the public beta. Discovery and node health come first.

⇄

No Custody

PowPad does not hold user funds or private keys. Any future settlement feature needs separate security and regulatory approval.

🧭

Discovery Layer

Listings, explorers, liquidity maps, and chain comparisons can ship before trading so launches have a useful network surface early.

🏗️

Separate Launch Gate

Listings, swaps or exchange access will not be implied by launching a chain and are outside this beta.

Launch in 3 Steps

From idea to live blockchain in minutes

1

Apply

Submit your application with chain details and custom parameters.

2

Deploy

Once approved, your blockchain compiles and deploys automatically.

3

Hand Off

Share the checksummed source archive or Git bundle so independent operators can run nodes before the temporary seed expires.

Apply to Launch a Chain

Submit the chain name, ticker, economics, and any optional contact details you want to leave. Approved applications are provisioned from the admin dashboard.

The public name shown in wallets, miners and the explorer. This is branding; changing it does not make the chain more private or secure.

The short code shown beside balances, such as BTC. Pick something distinctive: it becomes part of the node, wallet and service names.

A private application contact, not a chain setting. It is not placed in the public launch queue or blockchain.

Another private way to contact you about the application. It has no effect on the chain.

Use this for your purpose, audience or special requirements. It is application information, not data written into the chain.

Used in the launch page, wallet and miner interface. It only changes appearance, never consensus or privacy.

Design your chain

These choices become rules that every node follows. The defaults are a sensible test-chain starting point. Each explanation tells you what the setting changes and the trade-off if you move it.

Block rhythmA block about every minute
Mining accessMobile, browser and native apps
First reward reductionAbout 160 days after launch
Mined funds unlockAbout 1 hour after mining
PowPad seed nodeStops after 24 hours
Supply and miner rewards
Allowed: 1–900 coins

The number of new coins paid to miners for each block when the chain begins.Higher: faster early supply and larger mining rewards. Lower: scarcer early supply and smaller rewards.

Allowed: 10,000–230,584 blocks for the selected reward

After this many blocks, the block reward is cut in half. Its safe maximum depends on the early reward so the consensus supply counter cannot overflow; PowPad rejects an unsafe combination instead of silently changing it.Higher: the original reward lasts longer. Lower: new supply slows sooner.

Allowed: 0.01–1 coin per block

Halvings stop reducing rewards when they reach this amount. New coins then continue forever to keep miners incentivised.Higher: stronger long-term miner income, with more inflation. Lower: less inflation, with less mining income.

Allowed: 0–100%

This percentage of every transaction fee is permanently removed. The rest goes to the block miner.Higher: more coins are burned, but miners keep less. Lower: miners keep more of each fee.

Allowed: 10–720 blocks

A newly mined reward stays locked for this many blocks before its owner can spend it.Higher: more protection from short chain reorganisations, but miners wait longer. Lower: quicker access with less buffer.

Block speed and network stability
Choose: 60, 120, 180, 240 or 300 seconds

How often the network aims to add a block and confirm transactions.Higher: slower confirmations and fewer blocks to process. Lower: faster confirmations, with more network and storage overhead.

Allowed: 60–720 blocks

The network looks at this many recent blocks when deciding how hard the next block should be to mine.Higher: smoother but slower reaction to miner changes. Lower: faster reaction, but block times can swing more.

Allowed: 5–60 blocks

Difficulty calculations leave out this many newest blocks, reducing the influence of very recent timestamp manipulation.Higher: more cautious but slower to react. Lower: more responsive to sudden hashrate changes.

Allowed: 5–60; safely limited by window size

The most unusual fast and slow block timestamps are discarded before calculating difficulty.Higher: ignores more outliers. Lower: uses more of the observed timing data.

Allowed: 300 KB–5 MB

Blocks up to this size can earn the full miner reward. Larger blocks are penalised, which discourages uncontrolled growth.Higher: more transaction capacity with more storage and bandwidth. Lower: lighter nodes, with less capacity.

Mining pool and community hand-off

Browser-compatible lets opted-in phones and desktop browsers join the same verified pool, while desktop apps can still pool mine, solo mine and run nodes. RandomX-native is more memory-heavy and CPU-focused, but browsers and phones cannot calculate its proof reliably. This is a permanent consensus choice for the chain.

Allowed: 0–5%

The hosted pool keeps this percentage of rewards before distributing the rest to miners.Higher: more pool funding and lower miner payouts. Lower: more goes directly to miners.

Allowed: 0.01–1,000 chain coins

The pool sends a miner's balance to their wallet after it reaches this amount.Higher: fewer transactions, but miners wait longer. Lower: quicker payouts and more pool transactions.

Pool accounting only: 1–1,000,000,000

How much proof a mobile browser does before reporting one pool-accounting share. This does not change the chain difficulty or create extra rewards.Higher: fewer visible updates and less server traffic. Lower: more frequent share updates and more verification work.

Pool accounting only: 1–1,000,000,000,000

The same accounting target for faster desktop miners. It is normally higher because desktops calculate more hashes.Higher: less pool traffic and fewer share updates. Lower: more frequent updates and more server traffic.

Allowed: 1–48 hours

PowPad keeps the first peer online for this long after launch. Then it stops; community nodes must already be running for the chain to continue.Higher: more time for node operators to join. Lower: earlier hand-off and a greater risk the chain stops if nobody joins.

Leave X, Telegram, or a message if you want a reply attached to the application. Otherwise just submit the chain.