Appearance
Verity in two pages
The problem
Games, raffles, NFT mints and tournaments on blockchains need random numbers that nobody can predict or rig. The usual tricks (block timestamps, block hashes, a server) can be gamed by validators, predicted by players, or have to be taken on trust. PulseChain has had no verifiable randomness service.
What Verity does
Your contract asks Verity for random numbers. About 45 seconds later it receives them, together with a mathematical proof that the blockchain itself checks before your contract sees the numbers.
- Nobody can choose the result. For each request there is exactly one valid answer, fixed by the oracle's public key and a seed that includes a block hash that didn't exist yet when you asked.
- Nobody can fake the result. A wrong number fails the on-chain check and is rejected.
- Everyone can verify it. Every request and its proof transaction is public. The Verity explorer lists them.
What the oracle can do is delay. Verity limits that with backup nodes, refunds after a timeout, and (planned) multiple independent operators.
How you use it
- Create a subscription and fund it with PLS (in the web app or with one CLI command).
- Make your contract inherit
VerityConsumerBaseand implement one function that receives the numbers. - Add your contract to the subscription and call
requestRandomWords.
Ready-made examples cover a raffle, NFTs with random traits, and tournament seeding.
What it costs
You pay the gas the oracle spent, plus a premium and a small flat fee, from your subscription. Each request reserves its worst-case cost and is charged the actual cost; the rest is released. On testnet a dice roll costs about 0.0012 tPLS. Fees are capped in the contract, and changes are announced through a timelock before they apply.
Why trust it
- Proven cryptography: the same ECVRF construction as the most widely used oracle on Ethereum, checked on-chain.
- Tested against itself: the off-chain prover and on-chain verifier are tested against each other, and a million outputs pass standard statistical randomness tests.
- Tested under stress: crashes, flaky RPC providers, reorganisations, dropped transactions, fee spikes, and a 300-request burst, with every request fulfilled exactly once.
- Governed in the open: a multisig behind a timelock, with an emergency pause that can only stop new requests.
Status and roadmap
Live on PulseChain testnet v4. Next: independent security audits, a public testnet beta with partner projects, a bug bounty, then a mainnet beta. Verity has no token.
Read the white paper for the full design, or start with the Quickstart.