D. Together

Connection profiles

Every account beyond the activation trees that any kind of record connects to them — token flow, XRP flow, creation, shared destination tags, shared behaviour — scored by how many independent kinds, the strongest first.

Published

October 2, 2026

Ledger index

107030551

Contents

• What counts
• Every scenario, by strength
• Under either tracing rule
• Every connection profile

Accounts marked “flow-connected to” an activation tree are those the CULT and OBEY token flow reaches from it at its widest flow threshold, 10 CULT paid in total one way; the token-flow article sets out how it is followed, and the groups at every other threshold. Accounts flow-connected to both activation trees: 17 at 10 CULT, 0 at 30 CULT, 0 at 50 CULT. Being flow-connected does not make an account the activation tree's.

A connection profile sets the token flow beside every other kind of record the ledger keeps between an account and the activation trees. The token flow follows CULT and OBEY payments, and a single payment can bring an account in; a profile asks how many separate kinds of record connect the account, out of five. That number is its connection score. The scores are grouped in four bands: strong, two or more kinds; token flow only, the token flow by more than one payment and nothing else; token flow on one payment, a single payment and nothing else; and one other kind only. An account with two or more kinds is connected by more than one route; an account with one is listed apart, so nothing is dropped and nothing rests on a single record. None of it says who holds an account.

What counts

Table 1. The kinds of record a connection profile counts. Each kind counts once, however much of it there is.

every row: download connection-kinds.csv.

Of the 134 accounts with the token-flow kind, 79 are flow-connected by payments, and 55 have it only because most of the CULT they hold came through an activation tree account under both tracing rules; those 55 are not on the token-flow page, which follows payments alone.

Every scenario, by strength

Table 2. The activation trees, then each band of connected accounts added in turn, strongest first: how much CULT they would hold between them, and the pool price left if all of it were sold into the CULT/XRP pool at once. The ledger does not say any of these accounts are the activation trees'; each row is only the arithmetic of that set of accounts taken together.

every row: download connection-scenarios.csv.

Under either tracing rule

Which units leave an account when it pays or sells is a rule, not a fact the ledger records. First in, first out sends the oldest units first; last in, first out sends the newest. The CULT held outside the activation trees that came through an activation tree account, under each:

Table 3. The CULT held by connected accounts that came through an activation tree account, first in, first out and last in, first out.

every row: download connection-rules.csv.

Every connection profile

Table 4. Every account beyond the activation trees with at least one kind of connection: its band and score, the kinds, what it moved with the activation trees each way, and how much of what it holds came through them under each rule. The strongest first.

every row: download connection-profiles.csv.

A connection is a recorded fact between two accounts: a payment, a creation, a shared destination tag, a shared pattern. Several of them together say more than one; none of them shows who holds an account.

← Previous: The CULT and OBEY token flow
Next: Sellers among flow-connected accounts →