ParmetonPMN
MasterNode: offline

The DAG blockchain mined on graphics cards

Parmeton Network (PMN) is a UTXO testnet organised as a DAG: blocks produced in parallel are ordered by GHOSTDAG, while the PoM work runs on the GPU and is then re-verified by the node.

Read the API documentation Discover 0.2.52 RC2 Join our Discord
Parmeton logo: a P in brushed metal, a red trail on the left and cyan glows below
Blocks
—
Seed peers
—
Virtual DAA score
—
Finalized DAA score
—

Waiting for a recent seed snapshot.

Testnet 0.2.52 RC2

The 0.2.52 RC2 release candidate uses a new genesis, parmeton-testnet-v5, and keeps monetary version 4. The testnet is reset: no compatibility with 0.2.51 or its balances. The code, the addresses (prefix tpmn) and the test ticker (tPMN) are now fully PMN.

Monetary policy 3.1

Network fees and the tax on the first spend of a miner reward are burned. The tax decreases with the age of the output.

See the emission rules

Validation and storage

CPU workers replay the Phi PoM. The node applies state in DAG order and publishes paged storage in batches from the journal. An optional coin index speeds up wallet reads.

See the architecture

Monitoring

VPSmon tells block admission apart from PoM replay. The PARMETON MCP compares catch-up, state roots and counters through read-only local RPCs.

See testnet tracking

Project status. PoI and the Solana bridge are still under development. The test measurements published on this site are dated. The public table shows a timestamped snapshot from the seed, which describes the version the seed is running: 0.2.51 until the V5 genesis is launched.

Network basics

Four design choices that explain the rest of the site.

DAG
Blocks do not form a single chain. A block can reference up to 16 parents. GHOSTDAG selects one parent and orders competing branches into a common canonical view.
UTXO
Funds are unspent outputs, as on Bitcoin. Each output belongs to an Ed25519 public key and can be spent only once: the state stays simple to verify.
GPU mining
PoM (Proof of Matrix) is computed by graphics cards. The miner asks the node for a block template, searches for a solution, then submits its block. The node re-verifies everything on the CPU before accepting it.
Explicit finality
A canonical block can still be reorganised; a finalized block cannot. The network publishes both markers: the virtual DAA score and the finalized DAA score.

From miner to confirmed block

The path of a block inside a Parmeton node, from the graphics card to the database.

Canonical does not mean final. An accepted block first enters the DAG order; finality is announced later.

  1. The miner prepares a candidate

    A graphics card searches for a PoM solution for the block template provided by the node. As soon as it finds one, the miner submits the candidate block.

  2. The node receives and organises blocks

    Blocks coming from a local miner or a peer enter bounded queues, which protect the node during traffic spikes. Each block is attached to its parents in the DAG.

  3. CPU workers re-verify the PoM

    Several workers replay the mining proof without touching network state. A block whose proof does not hold is rejected at this step.

  4. A single owner applies the rules

    A single component owns the state. It checks signatures, difficulty, parents and consensus, applies transactions, creates the new unspent outputs and computes the state root.

  5. Journal, then batched writes

    The accepted block is first written to a journal, then grouped with others into a batch and saved to the database. After a hard stop, the node resumes from the journal.

The current architecture

Three distinct components in version 0.2.52 RC2.

Consensus node

ait-node maintains the DAG, the UTXO state, emission, the P2P network, the journal and the checkpoints.

It remains the validation authority.

GPU miner

The NVIDIA and Intel kits compute PoM candidates on the GPU. The AMD Vulkan Linux kit is experimental. The node replays the proof on the CPU before any durable admission.

The GPU proposes, the node decides.

Read interface

The JSON-RPC API exposes node state, the DAG, the network, mining and UTXOs. It is local and has no write method.

The site publishes a network snapshot over HTTPS.

A JSON-RPC 2.0 API over HTTP

The node exposes its state, the DAG, the network, mining, balances and unspent outputs. One request, one response, in JSON.

See all methods
RequestPOST, Content-Type : application/json
// Ask for the DAG state
{ "jsonrpc": "2.0", "id": 1, "method": "dag.getInfo" }

// Shape of the response
{ "jsonrpc": "2.0", "id": 1, "result": {
    "blockCount": <integer>,
    "tipCount": <integer>,
    "virtualDaaScore": <integer>,
    "finalizedDaaScore": <integer>
    // …
} }

Explore the protocol

The information below describes testnet 0.2.52 RC2. Public snapshot values are displayed as long as the snapshot is recent.