Session keys are used for block production. Only needed if you're running a validator node.
Validator Keys0 keys
No keys found. Click CHECK KEYSTORE or GENERATE NEW KEY.
Key Injection (Advanced)
Note: Dev seeds (Alice, Bob) generate random test keys.
For production, use GENERATE NEW KEY and register the public key with the network.
Enter dev account name or SPHINCS+ secret key (128 bytes / 256 hex chars)
Console Output
Keys console ready
Quantum Services
Entropy Source
QKD Client
Checking...
Device---
Keys Available---
Entropy Hub
Checking...
Active Sources---
Pool Size---
Crypto4A HSM (QRNG/RNG Entropy)
DescriptionHardware entropy source (does not store keys)
Endpoint
StatusNot Tested
Last Entropy---
Network Topology
Connected Peers
0
Best Block
---
Finalized
---
Network Health
---
Toroidal Mesh Topology
Validator Nodes
Peer Connections
Fetching peers...
Quantum-Secured Signals
SIGNAL API
LIVE
SIGNAL SOURCES
32
X402 PROTOCOL
ENABLED
ATTESTATION
SPHINCS+
Live Signal Feed
SN8 (Taoshi)LONG BTC (87%)
SN18 (Cortex)HOLD ETH (72%)
SN19 (Inference)SHORT SOL (65%)
SN8 (Taoshi)LONG TAO (91%)
Top Subnets by Emission
SN8 Taoshi
18.2%
SN1 Apex
12.4%
SN18 Cortex
8.7%
SN19 Inference
6.1%
X402 Agent Payments
ProtocolX-402-Payment, X-402-Signature
Payment ChainsTAO, Base, Polygon, Solana
API Endpointhttp://209.38.225.4/api
LOCAL ENTROPY
ACTIVE
SOURCE
Crypto4A Sim
NETWORK SHARES
0/3
THRESHOLD
2-of-3
Network Entropy Shares
Alice32 bytes (QBER: 0.8%)
Bob32 bytes (QBER: 1.1%)
CharlieWaiting...
Combined Output
Combined Entropy0x7f3a...9b2c
Proof StatusValid STARK
Last UpdateBlock #71,234
KEYS AVAILABLE
48
SOURCE
Threshold QRNG
LAST EXCHANGE
#71,234
NEXT REFRESH
~6 blocks
Routing Status
ConsensusActive - 12 keys used
MessagingActive - 8 keys used
Custom PoolIdle - 0 keys used
Route Keys To
ACTIVE FEEDS
2
MY FEEDS
1
EARNED
142 QMHY
SLA SCORE
99.3%
Request New Feed
Active Requests (from network)
#1 Weather APIACTIVE
api.openweather.com/...
Reward: 10 QMHY | SLA: 99% / 5s | Reporters: 2/3
#2 BTC/USD PricePENDING
api.coingecko.com/...
Reward: 5 QMHY | SLA: 99.5% / 2s | Reporters: 1/2
My Active Feeds (providing)
#1 Weather API142 reports
Earned: 1,420 QMHY
SLA: 99.3% uptime | Avg latency: 2.1s
Next report in: 3 blocks
Recent Reports
#71,230Weather: 22.5C | 3/3 agree | Used
#71,220Weather: 22.4C | 3/3 agree | Unused
#71,210Weather: 22.6C | 2/3 agree | Used
External Signals
Loading available signals...
Reporter Approval
Pending Proposals
Loading...
Approved Reporters
Loading...
Settings
Cryptographic Proofs & Tests
PALLET TESTS
164
PALLETS COVERED
8
PEDERSEN PROOFS
21
STATUS
VERIFIED
Active Proof Systems by Pallet
pallet-ricardian-contracts32 tests
pallet-academic-vouch32 tests
pallet-notarial29 tests
pallet-pedersen-commitment21 tests
pallet-fideicommis18 tests
pallet-stablecoin14 tests
pallet-relay-coordination11 tests
pallet-validator-entropy7 tests
Pedersen Commitment Scheme - Technical Details
What is a Pedersen Commitment?
A Pedersen commitment is a cryptographic primitive that allows you to commit to a value while keeping it hidden, with the ability to reveal it later. It provides two critical security properties:
Information-Theoretic Hiding
Even with unlimited computational power, an attacker cannot determine the committed value from the commitment alone. The blinding factor makes every possible value equally likely.
Computational Binding
Once committed, you cannot open the commitment to a different value. Breaking this requires solving the discrete logarithm problem on the elliptic curve.
Mathematical Foundation
// BLS12-381 Curve Parameters
Curve: BLS12-381 (Barreto-Lynn-Scott)
Group: G1 (381-bit prime field)
Order: r = 0x73eda753299d7d483339d80809a1d80553bda402fffe5bfeffffffff00000001
// Commitment Formula
C = gentropy × hblinding
where:
g = G1 generator (standard)
h = hash_to_curve("qh_pedersen_h") // Nothing-up-my-sleeve point
entropy = 32 bytes of quantum randomness
blinding = 32 bytes of secret randomness
// Output
Commitment size: 48 bytes (compressed G1 point)
Protocol Flow in QuantumHarmony
1
COMMIT
Block N: Validator computes C and submits on-chain. Entropy is HIDDEN.
2
WAIT
At least 1 block must pass. Prevents same-block reveal attacks.
3
REVEAL
Block N+1: Submit (entropy, blinding). Network verifies C' = C.
Pedersen Commitment Use Cases
Quantum Entropy AggregationValidators commit entropy before revealing, preventing front-running
MEV ProtectionTransaction ordering hidden during mempool validation phase
Confidential VotingGovernance votes committed before reveal to prevent bandwagoning
Sealed-Bid AuctionsBid amounts hidden until reveal phase in NFT/asset auctions