DigiStamp Permanent Storage Pool

A Permanent Storage Pool (PSP) for the DigiByte / DigiAsset network.

This server is a Permanent Storage Pool: it keeps the files behind DigiAssets alive on IPFS, and pays node operators DigiByte (DGB) to help. Here is how that works — and where your own asset fits in.

How your DigiAsset stays alive — live

Watch what flows where. Every dot is real activity on the network: your files being stored and pinned, the pool publishing + checking, and DigiByte flowing to the operators who keep it all online.

You mint & retrieve DigiByte blockchain record + CID (permanent) IPFS the files This pool server publishes · verifies · pays Node operators worldwide pin your files, prove it, get paid — the pins on the map below
Your files — uploaded to IPFS, then pinned by every node so copies stay online.
Record & list — the CID goes on-chain; the pool publishes which files to keep alive.
Verification — the pool keeps checking each node still holds the content.
DGB payments — verified nodes get paid from the treasury, on-chain.
Why it never disappears: your files live on many paid, checked nodes at once, so even if some go offline there is always another copy to serve them — and retrieval pulls straight from the network, not through this server.

How it works — and where your DigiAsset lives

A DigiAsset is stored in two places at once. Knowing which part lives where is the key to understanding why this pool exists — and how you get your files back.

  1. Step 1

    You mint a DigiAsset

    You create an asset — art, a certificate, a collectible — from your wallet. Right away it splits into two parts that live in two different places.

  2. Step 2

    It lives in two places at once

    The proof of ownership and the pointer to your files go on-chain. The files themselves are too big for a blockchain, so they go on IPFS instead.

    DigiByte blockchain

    The ownership record — who owns it, its asset ID, and the CID pointing at the files.

    ✓ Permanent by design
    IPFS

    The actual files — the image and metadata — addressed by a CID, a fingerprint of the content.

    ⚠ Only kept while pinned
  3. The problem

    IPFS forgets files nobody keeps

    IPFS only holds a file while at least one node pins it. If every node drops your CID, the files vanish — even though the on-chain record still points to where they used to be. Your asset would show a broken image.

  4. What this pool does

    It pays a worldwide network to keep your files pinned

    This pool publishes your CID on its permanent list, then pays a network of verified node operators — on the map below — to pin those files and prove they still have them. Many redundant copies, always online. That is the gap this pool closes: the blockchain keeps the record forever, and the pool keeps the content alive to match.

Getting your content back

Because IPFS is content-addressed, the CID is the address. Anyone, anywhere can fetch the exact same file with it — no account, no login — for as long as it stays pinned.

From any IPFS gateway

Take the CID from your asset and open it in a browser through any public gateway:

https://ipfs.io/ipfs/<YOUR-CID>

From your wallet

A DigiAsset wallet or explorer reads the CID from the chain and loads your image automatically — you never touch the CID by hand.

Your ownership is never at risk. The record on the DigiByte blockchain is permanent no matter what. This pool exists to keep the files that record points to online and instantly retrievable, so your DigiAsset always shows more than a broken link.

What this server does

It is not a wallet or an explorer. It talks to DigiAsset Core nodes, not to browsers.

The network — pools & nodes worldwide

—

Each pin is a node hosting DigiAsset content. Nearby nodes group into a count.

Support the pool — donate DGB

Donations to the address below fund the DGB paid out to the operators who keep DigiAsset content alive. The treasury total, current balance, and every payout below are live and on-chain — fully auditable.

—
Donated in
—
In treasury
—
Paid to hosts
—
Verified / active nodes

Recent payouts (on-chain, newest first)

WhenAmountToTx
loading…

Run a node and get paid

One installer sets up everything — DigiAsset for Windows, DigiByte Core and IPFS. Paste this into an Administrator PowerShell on Windows 10 or 11, approve the one Windows prompt, and it runs to the end on its own: 

iwr https://raw.githubusercontent.com/chopperbriano/DigiAssetWindows/master/setup-digiasset.ps1 -OutFile "$env:TEMP\setup-digiasset.ps1" -UseBasicParsing; powershell -ExecutionPolicy Bypass -File "$env:TEMP\setup-digiasset.ps1"

It asks you nothing. You do not need a DigiByte address — the installer creates your payout address in the DigiByte wallet it sets up on your own PC, so your earnings arrive in a wallet only you hold the keys to. It also opens your firewall, registers everything to start at login, and keeps itself updated. Back up wallet.dat once it is done.

Manual setup

Only needed if you are not using the installer above — it already does all of this. Requires DigiByte Core v9.26.5 or newer: earlier releases cannot validate DigiDollar, and the node refuses to start against them.

  1. Install and sync DigiAsset for Windows (see the repo).
  2. Point it at this pool — add to your config.cfg: 
    psp0subscribe=1
psp0payout=YOUR_DGB_ADDRESS
psp2server=https://pool.digistamp.co
psp2subscribe=1
psp2payout=YOUR_DGB_ADDRESS
    Pool 0 is your local pool (no server); pool 2 is this pool (DigiStamp). Both need a payout address or the node errors with “Could not generate new PSP payout address”.
  3. For reliable verification, forward IPFS port 4001 on your router (nodes behind NAT can still qualify via a fallback check, but forwarding is faster and more reliable).
  4. Restart. Your node registers automatically and the dashboard's Payment row shows your status.
View on GitHub →