D. Together

Where the two activation trees meet

Every place the record brings the two activation trees together: payments between them, accounts that paid each other, shared destination tags, and things their accounts did alike.

Published

October 2, 2026

Ledger index

107030551

Contents

• Every group, in one diagram
• Payments between the two activation trees
• Trades between the two activation trees
• Accounts that paid each other
• The same destination tags
• Things their accounts did alike

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.

Pheanor's activation tree and Hodler's activation tree share no account: no account in one was created by an account in the other. This article sets out every other place the record brings them together — the CULT that moved between the groups, the payments between the two activation trees, accounts that paid each other, destination tags they both paid, and things their accounts did alike.

Every group, in one diagram

Every CULT payment between the groups this series is about, every pool deposit and withdrawal, and every swap and offer, summed over the whole history. The table under the diagram gives every route exactly.

Table 1. Every route CULT took between the groups, by payment, over the whole history.

every row: download group-routes.csv.

Payments between the two activation trees

Table 2. Every payment between an account of Pheanor's activation tree and an account of Hodler's activation tree, by pair of accounts and asset.

every row: download between-the-trees.csv.

Table 3. The same, added up by direction.

every row: download between-the-trees-totals.csv.

Trades between the two activation trees

Table 4. Every standing offer of one activation tree's account that an account of the other activation tree filled, read from the offer owner's own balance changes.

every row: download trades-between-the-trees.csv.

Accounts that paid each other

Table 5. Pairs of accounts, at least one of them in an activation tree and the other in an activation tree or flow-connected, that each paid the other CULT.

every row: download paid-each-other.csv.

The same destination tags

A service gives each customer a number — a destination tag — and a payment to that service carries it so the service knows whose balance to credit. Two accounts paying the same number to the same receiver are paying into the same place there. Every tagged payment is checked, in XRP and in tokens, to named exchanges and to receivers with no public name, among the 1,877 accounts whose full histories were read. The numbers 0 and 1 are left out: many wallets send them by default.

Table 6. Every destination tag an activation tree account paid that another activation tree account, or another account in the series, paid too, the numbers fewest outsiders paid first.

every row: download shared-numbers.csv.

The strongest are the numbers no one else paid — the first rows. A number paid by dozens or hundreds of other accounts is a shared reference at that receiver, such as a marketplace listing or a platform's own tag, and says little about who paid it. Two accounts paying the same number does not say they are the same person: people share numbers, pass them on, and use the same service.

Things their accounts did alike

Two accounts doing the same unusual thing may share a reason, or may simply have been watching the same market. The test is how often the same thing happens between accounts with no connection at all — measured over every comparable pair in this market, not a sample. None of it shows who controls an account.

Table 7. What each kind of shared behaviour means.

every row: download alike-kinds.csv.

Table 8. Every pair of activation tree accounts measured for doing the same thing, the most unusual first.

every row: download alike-pairs.csv.

Table 9. Ledgers in which two or more activation tree accounts moved CULT. One ledger closes every three to five seconds.

every row: download same-ledger.csv.

Both activation trees acting in one ledger is expected when both trade the same market, and is a count, not a finding. A pattern is a shape: repeating an amount, trading in a circle or keeping a steady rhythm are all things software does for ordinary reasons.

← Previous: Hodler's activation tree: in and out
Next: The CULT and OBEY token flow →