Skip to content
pVAULT
devnetSimulation only · assets have no value

This build is connected to Solana’s devnet cluster, a public test network. It is not Solana mainnet.

Tokens on a test network are issued freely and have no market and no value. Nothing shown here is a balance you own, a reward you have earned, or an amount you could sell. Any transaction you sign here moves test tokens only.

Figures on this build come from whatever the program and indexer report on that cluster. Where a figure is missing, the page says so rather than substituting one.

Proof

Nothing here asks to be believed

Every figure derives from program events and transaction signatures, and every entry links to a block explorer this project does not operate. The index is rebuildable from chain state alone.

Launch progress

0 / 10

steps recorded complete

Index status

Where these figures come from

Indexed through slot
No index is running
Finalized through slot
No index is running
Cluster
devnet

Figures below carry the label of the strongest evidence behind them. On-chain. Read directly from chain state in this request. This is the authoritative value. means the value was read from chain state while building this page. Finalized. Indexed from a finalized slot. It cannot be reversed by a reorg, but it was read from the index rather than from chain state. means it came from an indexed event in a slot that can no longer be reorganised. Pending. Indexed from a slot that is not yet finalized. A chain reorganisation could still remove it. means a reorg could still remove it, and Estimated. Calculated from indexed inputs rather than read from the chain. The protocol settles on its own figures, which may differ. means this page calculated it rather than reading it.

Warning: No on-chain figures can be shown on devnet: the pVAULT program and token are not deployed, and no indexer is configured for this build. Nothing on this page is a balance, an estimate, or a projection.

Addresses

Every account this protocol runs on

pVAULT has not launched. No program is deployed, no coin exists, and no creator-fee route has been configured — so there is nothing here to check yet. 0 of 10 launch steps are recorded complete.

When it does launch, every address below will arrive with the signature of the transaction that created it. An address on its own is a claim; this page is here so that nothing has to be taken on trust.

These come from config/launch-record.json, which is committed to the repository and reviewed. This page compares them against what the running deployment is configured with, and says so above when the two disagree.

BurnedpVAULT permanently destroyed
Total burnedUnavailable. No value is known. Nothing is being shown in its place.

Not deployed on devnet.

By the protocolUnavailable. No value is known. Nothing is being shown in its place.

Not deployed on devnet.

Half of every processed creator reward buys pVAULT on the market and burns it.

By early exitsUnavailable. No value is known. Nothing is being shown in its place.

Not deployed on devnet.

Penalties from unstaking inside the 30-day window.

Burns reduce the mint’s supply directly. pVAULT does not send tokens to a dead address and describe it as burning.

RewardsPUMP acquired for stakers
PUMP in the reward vaultUnavailable. No value is known. Nothing is being shown in its place.

Not deployed on devnet.

Committed to open epochsUnavailable. No value is known. Nothing is being shown in its place.

Not deployed on devnet.

Creator rewards booked, lifetimeUnavailable. No value is known. Nothing is being shown in its place.

Not deployed on devnet.

Recent activity

Every entry links to the transaction

No protocol activity has been indexed. Burns, creator-fee batches and epoch funding will appear here, each with the signature of the transaction that produced it.

Reproduce this yourselfThe index rebuilds from chain state

The index is rebuildable from chain state alone. Every figure on this page derives from program events and transaction signatures, so an independent party can replay the same history and arrive at the same numbers without trusting this deployment’s database.

The database is a cache. It is never authoritative for token custody, stake balances, or reward entitlement — the program is.