Proof of Stake Testnet

Clore.ai Migration from Proof‑of‑Work to Proof‑of‑Stake

This page outlines our progress in migrating the Clore network from Proof‑of‑Work to Proof‑of‑Stake, and explains how you can join the public test‑net and help us find potential bugs.


Key Milestones


How to Try Staking

  1. Download the wallet. Use the link above and install the latest version for your OS.

  2. Switch to Testnet. At the top of the wallet window choose Testnet.

  3. Request test Clore coins. Open the support chat widget on https://clore.ai/ (bottom‑right corner) and ask for test coins.

  4. Start staking. Move the coins to any address in your wallet and keep the wallet online — there is no minimum amount.

💡 Rewards start after ≈100 block confirmations (about 1 hour 40 minutes).


Test‑Net Parameters

Parameter
Value

Minimum staking amount

None

Average block interval

≈ 1 minute

Rewards begin

After 100 blocks


Main‑Net Cut‑Over

  • Mode: one‑shot (all‑in PoS).

  • Condition: the public test‑net must pass without critical issues.

  • Exact block height: to be announced later.

We initially considered a hybrid 50 % PoW / 50 % PoS phase, but decided on a full PoS switch to:

  • maximize rewards for long‑term holders who stake and believe in the project;

  • remove constant sell pressure from miners covering electricity and hardware costs.


Frequently Asked Questions (FAQ)

Q: Do I need to send my coins to a special address to stake? A: No. Just hold them in a wallet that is synced to the network.

Q: What happens if my wallet goes offline? A: Your coins continue staking while the wallet is closed. When you reopen the wallet and it catches up to the latest blocks, any earned rewards will appear automatically.

Q: Will there be a “coin swap” or migration? A: No. Existing Clore coins will continue to work in the PoS chain; addresses and balances stay intact.



How You Can Help

  1. Run the wallet and stake coins. The more active nodes, the better.

  2. Report bugs. Use GitHub issues or the chats above.

  3. Submit pull‑requests. Every contribution matters — from docs to code optimizations.

  4. Spread the word. Invite developer and validator friends to the test‑net.


Feedback

For any questions or suggestions, reach us via:


Last updated