BOR requires only a Reticulum connection - no internet, no account,

no ID - meaning it can reach people conventional banking

infrastructure cannot.

Bank of Reticulum (BOR) is a self-describing replicated state machine.

This network currently runs across independently operated machines,

with both fully participating nodes and newer nodes still building

history. New nodes are welcome to join through the onboarding process

below.

A new BOR node begins in a CHILD role.

A child node keeps up with the ledger and independently verifies it,

holding a complete, verified copy the network can rely on.

A child does not take part in finality decisions.

Each day a child is present and current, it records a signed

attestation against the finalized ledger. Those attestations:

build node maturity

earn 0.05 BOR for that node

Every node has a permanently associated owner.

BOR earned by the node can be moved to its owner's account through

the ledger's protected payout process.

After enough sustained presence over time, a child node can be

promoted to an ADULT role through protected ADULT_PROMOTION.

An adult node continues normal service and can also participate in

verification and finality.

A valid adult consensus challenge earns 1 BOR.

BOR runs on a network where many links are slow, shared, or

battery-powered, so its traffic is kept proportional to actual

banking activity rather than to how long the ledger has existed.

Earlier releases advertised a node's entire history on every sync -

around 200 KB every 15 seconds, growing forever whether or not

anything had happened. From RC18 a node exchanges only what has

changed since the last finalized height: roughly 8 KB every 20

seconds, and it stays that size as the ledger grows.

A node that has fallen far behind fetches a snapshot rather than

replaying the difference. Sync intervals are set to the slowest rate

that still lets finality complete on time, not the fastest the

network would tolerate.

Reticulum carries the messages.

LXMF proves who is sending them.

BOR nodes independently check the ledger rules.

Finality determines what becomes part of the accepted history.

Sustained presence and useful participation earn BOR.

No node can simply invent a balance or rewrite accepted history.

BOR does not create units simply because someone requests them.

Units enter the ledger through specific, authenticated ledger events

defined by the protocol.

Presence rewards are created when a child node records a valid

attestation proving it held current ledger state. Under the current

rules, a qualifying day earns 0.05 BOR.

Consensus rewards are created through eligible adult consensus

participation. The current adult challenge reward is 1 BOR.

Faucet funding is another explicitly defined source used for

controlled testing and onboarding. Faucet-created units retain their

provenance in the ledger rather than becoming indistinguishable from

other units.

These are protocol-defined issuance events. A normal transfer does

not create new units; it only moves existing units between accounts.

Every issuance is therefore part of the ledger history and can be

validated against the rules that allowed it.

BOR is the ledger's native unit, created only through the issuance

events described above and moved between accounts through ordinary

transfers.

This is experimental software and this page makes no claim about

investment value, market value or external monetary value.

The main Bank of Reticulum LXMF address is:

Send:

to see the currently available public operations.

A BOR node runs on your own computer and uses your existing

Reticulum connection.

Every newly admitted node begins in the CHILD role.

Python 3.11 or newer

Reticulum

LXMF

rngit

Python, Reticulum, LXMF and rngit must be available from the same

Python 3.11+ environment.

rngit release rns://3bd054e4ab5b089ca44c5c54c421fcbc/public/bor_master fetch 0.21.0-master-enhanced-rc21-starter-20260913b:BOR_BRANCH_STARTER_RC21_20260913B.tar.gz --signer 35f354aa923d9e509e336456d638ec94

sha256sum BOR_BRANCH_STARTER_RC21_20260913B.tar.gz

The SHA-256 must be:

848e3099f613d000e9121114c6f9f126b273a9d6d6cf31e754ae2b34551bdee9

If it does not match, do not run the archive.

tar -xzf BOR_BRANCH_STARTER_RC21_20260913B.tar.gz

./BOR_BRANCH_BOOTSTRAP/bor-start

The Starter handles node creation, release verification,

BRANCH START and activation.

Do not regard the node as active until it finishes with:

Once active, the node automatically begins its CHILD role and

records presence against the finalized ledger.