Dassie docs

How Dassie works, how to run a node and use its wallet, how to build an app on it, and how it is built. Pick the door that fits you, or search.

Where do you start?

Newest release

Dassie 0.4.0

A node's place in the network now follows the core it works out from the signed link states, not just whether it has a hostname. Every node starts in the periphery, a node with a hostname too, and becomes a core node once its uplinks have checked it: how long it has been in good standing, its heartbeats and its clock, and that it answers at its URL over QUIC and over HTTPS with a publicly issued certificate. The bootstrap nodes are core from the start. A node being promoted is paid beneath its core peers until it has been core for a while, and keeps taking packets at those addresses afterwards.

All release notes

Every section

  • Start here

    What Dassie is, which setup fits you, a first node and a first payment.

  • Concepts

    How Dassie works, in plain words. Each page links to the spec for the full reasons.

  • Use your wallet

    The owner's tasks in the web wallet, one page each, in the order a new owner meets them.

  • Desktop app

    Your node in a window on your own computer: no server, no domain.

  • Run a node

    For a server's operator: install, configure, watch, update, back up.

  • Run network services

    Roles beyond a node: hub validators and founders, market makers, front doors.

  • Build on Dassie

    For app developers: pay and get paid through a node with standard Interledger tools.

  • Reference

    Facts to look up: commands, variables, files, schemes and releases, checked against the code.

  • Project

    How Dassie is built and looks, and where to get help.

A kopje of granite blocks against the sun, in veld grass; one dassie climbs its slab, one keeps lookout on top inside the sun, and one sleeps on the next rock; on a wide screen, a pair sits on a kopje to the left