Interactive source-and-use record

Two pools of value.
The same exits.

Follow BOS Origins sale receipts and Sovryn Exchequer assets from their source, through shared custody and payment infrastructure, to exact exchange-style destinations on Bitcoin and Ethereum.

The significant fact is exact infrastructure reuse

On Bitcoin, a high-confidence BOS Origins collector candidate and all three later Exchequer pegout routes used one exact destination address. On Ethereum, BOS-bounded funds and Exchequer-derived DD funds reused the exact same forwarding proxy and terminal; another Exchequer route used a sibling proxy from the same deployment family and reached that same terminal.

Candidate BOS to Bitcoin terminal
≥ 20.01114355 BTC
Exchequer to the same Bitcoin terminal
23.13948498 BTC
Exchequer to recurring recipients or common ETH terminal
≥ 411,750.640097 units

The route sequence, in order

Sale collection came first. The same terminal infrastructure then reappeared in later Exchequer routes.

  1. Origins sale opens

    Unique-deposit collection begins on the reconstructed stablecoin, Bitcoin, and Cardano infrastructure.

  2. Collectors rotate together

    Bitcoin and Cardano collector succession occurs within minutes across independent chains, one fingerprint supporting the high-confidence Origins attribution.

  3. Candidate BOS Bitcoin reaches the terminal

    Eight deposits totaling 20.09750539 BTC arrive; conservation assigns at least 20.01114355 BTC to sale-window value.

    Inspect the Bitcoin record
  4. BOS-bounded Ethereum value uses e1d4

    0x509201 sends 200,000 USDT through e1d4 to the common public Gemini-labeled terminal.

    Inspect the Ethereum record
  5. Exchequer BTC reaches the exact same address

    Three treasury routes produce 23.13948498 BTC at the previously used Bitcoin terminal.

    Compare both pools
  6. Exchequer-derived DD funds reuse the Ethereum route

    DD uses the exact e1d4 path in January and the sibling f6c8 proxy plus the same terminal in March.

    Compare both routes

Choose a route, then inspect each address

Blue paths are BOS-linked. Rust paths begin with Sovryn’s Exchequer. Black relationship paths show custody or deployment—not money movement.

Recorded directly on-chainFirst-party off-chain platform recordForced minimum from balance conservationMultiple independent infrastructure fingerprintsPublic service label; account owner unresolvedDocumented organizational role; no wallet attribution

BOS Origins candidate · Bitcoin

A high-confidence Origins-style deposit cohort moved through rotating collectors into the exact terminal later used by the Exchequer routes.

≥ 20.01114355 BTCMultiple independent infrastructure fingerprints
  1. source Origins sale counter $4,888,380.30 in first-party usdCollected; 609,509,366.81051 BOS in tokensSold.
  2. Counter benchmark Bitcoin Aggregated BTC deposit cohort 297 clean sweeps from 927 UTXOs and 699 unique input addresses.
  3. Deposit sweeps to Bitcoin Origins-style BTC collectors A → B 20.01527801 BTC gross; 20.01262609 BTC after sweep fees.
  4. Collector deposits to Bitcoin Exact common Bitcoin terminal 20.01114355 BTC candidate BOS lower bound and 23.13948498 BTC from Exchequer routes reached this exact address.

Sovryn Exchequer · Bitcoin

Three independent Exchequer pegout routes arrived at the exact same Bitcoin address used by the candidate BOS collector.

23.13948498 BTCRecorded directly on-chain
  1. Rootstock Sovryn Exchequer The 0x924f multisig held the treasury assets whose downstream paths are reconstructed here.
  2. Treasury transfer to Rootstock / Bitcoin D9 → PowPeg → far side 23.146420437622064715 RBTC left the Exchequer route; 23.13948498 BTC reached the terminal after bridge and transaction fees.
  3. Pegout and deposit to Bitcoin Exact common Bitcoin terminal 20.01114355 BTC candidate BOS lower bound and 23.13948498 BTC from Exchequer routes reached this exact address.

BOS collectors · Ethereum

After BOS collectors funded 0x509201, at least this amount entered e1d4 and the common public Gemini-labeled terminal.

≥ 150463.919739 USDTForced minimum from balance conservation
  1. source Origins sale counter $4,888,380.30 in first-party usdCollected; 609,509,366.81051 BOS in tokensSold.
  2. Counter benchmark Ethereum / BNB Chain Ethereum BOS collectors BB55, FeD3, 1160, and the smaller 60c branch used participant-specific deposit sweeps; FeD3 and 1160 later funded 0x509201.
  3. Deposit sweeps to Ethereum / BNB Chain / Rootstock 0x509201…AbD6 Long-running Sovryn and BitcoinOS treasury-linked operations address; DD signer, DD payee, BOS Safe owner, and recipient of collector funds.
  4. Collector consolidation to Ethereum e1d4 forwarding proxy The exact proxy accepted the BOS-bounded 200,000-USDT route and later DD’s 100,000-USDT route, forwarding each to the same terminal.
  5. Terminal forwarding to Ethereum Common Ethereum terminal 133809.640217 Exchequer-attributed units reached the same public Gemini-labeled terminal infrastructure used after BOS collector receipts.

Exchequer-derived DD funds · January

DD reused the exact e1d4 proxy and terminal previously used by the BOS-bounded route.

≥ 66644.658655 USDTForced minimum from balance conservation
  1. Rootstock Sovryn Exchequer The 0x924f multisig held the treasury assets whose downstream paths are reconstructed here.
  2. Treasury route to Ethereum / BNB Chain DD cross-chain Safe 508947.877906 USDT reconciled to Exchequer-origin assets entered DD. DD uses the same five-owner set as official BOS administration Safes.
  3. DD payment to Ethereum e1d4 forwarding proxy The exact proxy accepted the BOS-bounded 200,000-USDT route and later DD’s 100,000-USDT route, forwarding each to the same terminal.
  4. Terminal forwarding to Ethereum Common Ethereum terminal 133809.640217 Exchequer-attributed units reached the same public Gemini-labeled terminal infrastructure used after BOS collector receipts.

Exchequer-derived DD funds · March

DD paid 0x509201, which swapped the funds and used a sibling proxy from the same deployment family to reach the same terminal.

≥ 33809.640217 unitsForced minimum from balance conservation
  1. Rootstock Sovryn Exchequer The 0x924f multisig held the treasury assets whose downstream paths are reconstructed here.
  2. Treasury route to Ethereum / BNB Chain DD cross-chain Safe 508947.877906 USDT reconciled to Exchequer-origin assets entered DD. DD uses the same five-owner set as official BOS administration Safes.
  3. DD payment to Ethereum / BNB Chain / Rootstock 0x509201…AbD6 Long-running Sovryn and BitcoinOS treasury-linked operations address; DD signer, DD payee, BOS Safe owner, and recipient of collector funds.
  4. Swap and payment to Ethereum f6c8 sibling proxy Same creator, implementation, and terminal as e1d4; received 122,000 USDC from 0x509201 after the March DD transfer and Curve swap.
  5. Terminal forwarding to Ethereum Common Ethereum terminal 133809.640217 Exchequer-attributed units reached the same public Gemini-labeled terminal infrastructure used after BOS collector receipts.

Exchequer-derived DD funds · recurring network

All 24 DD recipients also appeared in genuine 0x509201 payments; 23 were in that network before DD first paid them.

≥ 244585.603045 USDTForced minimum from balance conservation
  1. Rootstock Sovryn Exchequer The 0x924f multisig held the treasury assets whose downstream paths are reconstructed here.
  2. Treasury route to Ethereum / BNB Chain DD cross-chain Safe 508947.877906 USDT reconciled to Exchequer-origin assets entered DD. DD uses the same five-owner set as official BOS administration Safes.
  3. DD payments to Ethereum 24 recurring recipients 37 DD transfers totaling 277941 USDT; all 24 recipients also received genuine USDT payments initiated by 0x509201.
  4. Same payee set Ethereum / BNB Chain / Rootstock 0x509201…AbD6 Long-running Sovryn and BitcoinOS treasury-linked operations address; DD signer, DD payee, BOS Safe owner, and recipient of collector funds.

BOS Origins candidate · Cardano exchange route

The first two pooled collectors repeatedly used one enterprise relay to the Cardanoscan-labeled Binance 1 terminal.

2155639.685101 ADAMultiple independent infrastructure fingerprints
  1. source Origins sale counter $4,888,380.30 in first-party usdCollected; 609,509,366.81051 BOS in tokensSold.
  2. Counter benchmark Cardano Three aggregated Cardano cohorts 2440904.338471 ADA across 1,834 UTXOs and 1,254 unique deposit addresses.
  3. Deposit sweeps to Cardano Rotating Cardano collectors Three shared-stake pools followed sale dates, unique-address sweeps, collector succession, and official BOS recipient records.
  4. Pooled withdrawals to Cardano Cardanoscan-labeled Binance 1 2155639.685101 ADA reached the labeled terminal through a one-use enterprise relay.

BOS Origins candidate · Cardano public use

The post-cutover collector funded the official distributor and a large BOS/ADA Minswap position whose LP capability remained at one unidentified controller at cutoff.

277394.921276 ADA + 36652194.91 BOSMultiple independent infrastructure fingerprints
  1. source Origins sale counter $4,888,380.30 in first-party usdCollected; 609,509,366.81051 BOS in tokensSold.
  2. Counter benchmark Cardano Three aggregated Cardano cohorts 2440904.338471 ADA across 1,834 UTXOs and 1,254 unique deposit addresses.
  3. Deposit sweeps to Cardano Rotating Cardano collectors Three shared-stake pools followed sale dates, unique-address sweeps, collector succession, and official BOS recipient records.
  4. Liquidity funding to Cardano BOS/ADA liquidity controller 277394.921276 ADA and 36652194.91 BOS entered a Minswap order; the full LP-unit position remained at the controller at cutoff.

Cross-project custody and deployment

8C deployed DD and the BOS Safe family. DD and the official BOS Safes use one exact five-address owner set; 0x509201 and cD900 approved all 14 reviewed Ethereum DD executions.

Same five owner addressesRecorded directly on-chain
  1. Ethereum / BNB Chain DD cross-chain Safe 508947.877906 USDT reconciled to Exchequer-origin assets entered DD. DD uses the same five-owner set as official BOS administration Safes.
  2. Deployed by Ethereum / BNB Chain / Rootstock 8C deployer and routing address 8C deployed DD on Ethereum and BNB Chain and the official BOS token-owner and allocation Safe family.
  3. Also deployed Ethereum / BNB Chain Official BOS Safe family The official BOS token-owner and allocation Safes use the exact five owner addresses also installed on DD.
  4. Owner in both families Ethereum / BNB Chain / Rootstock 0x509201…AbD6 Long-running Sovryn and BitcoinOS treasury-linked operations address; DD signer, DD payee, BOS Safe owner, and recipient of collector funds.

This reconstruction traces $4,169,986.84 of the $4.888 million sale counter

Stablecoin receipts are direct token records. The Bitcoin and Cardano collector assignments are supported by sale timing, unique-deposit architecture, collector succession, official recipient corroboration, and synchronized rotations.

Canonical stablecoins

$432,623.93

Ethereum, BNB Chain, and Polygon receipts; downstream movements are not counted again.

Cardano

2,440,904.338471 ADA

$1,873,923.65 at the funding-day daily-VWAP benchmark.

Bitcoin

20.015278 BTC

$1,863,439.26 at the funding-day daily-VWAP benchmark.

Reconstructed sale value

$4,169,986.84

85.30% of Origins’ first-party counter. Origins, Fireblocks, exchange, and banking records can reconcile the remaining approximately $718,393.46.

Measurement method: the range is $3,974,628.13–$4,368,551.68, using each funding day’s Kraken low and high for BTC and ADA. Issuer order records, vault assignments, exchange statements, and bank records supply the final audited reconciliation and loss accounting.

The two strongest convergence records

Exact destination-address reuse and transaction conservation establish both convergence records. Exchange account files identify the customers and beneficial owners behind the destinations.

On-chain recordDossier conclusionRecords authorities should compel

One exact Bitcoin address received both routes

bc1qccy9mn9h2ed6sjf7pvx7af6zc7zax0qaegadw5
High-confidence BOS Origins candidate ≥ 20.01114355 BTC

297 clean sweeps, 927 UTXOs, and 699 unique input addresses fed rotating collectors before the terminal deposits.

Sovryn Exchequer routes 23.13948498 BTC

Three independently reconciled Rootstock-to-Bitcoin routes reached the exact same address in December 2025 and January 2026.

Exchequer-derived arrivals at the common Bitcoin terminal
DateSource executionTerminal amountBitcoin transaction
0xf09e5dde… 11.99899103 BTC 45f6e40a5c…
0xc9f566be… 6.72047426 BTC f753d78eba…
0x336a6d72… 4.42001969 BTC dd5b45fe83…
Inspect the candidate BOS terminal deposits
Candidate BOS collector deposits to the common Bitcoin terminal
UTCAmountBitcoin transaction
2025-08-27T22:06:11Z0.0001 BTC e4faced1e265…
2025-08-29T21:24:51Z0.0001 BTC 000bd5e261d5…
2025-08-29T21:44:04Z0.05 BTC 3bcc7b77ba77…
2025-08-29T21:55:42Z0.05 BTC ffea2edfcc52…
2025-08-29T22:05:58Z4.9 BTC 7a34ee57da9d…
2025-09-29T20:55:50Z3 BTC 2d692c8da2a9…
2025-10-21T22:37:17Z6 BTC bdc52b93074d…
2025-10-23T19:19:55Z6.09730539 BTC 5ec4894d397e…

Endpoint record: OKLink labels the terminal Gemini, while another public label conflicts farther downstream. The exact shared destination is visible in the transactions. Exchange address-assignment, KYC, trade, withdrawal, and bank records identify the venue, credited account, and beneficial owner.

On-chain recordDossier conclusionRecords authorities should compel

The same Ethereum proxy and terminal handled both pools

0x5f65f7b609678448494De4C87521CdF6cEf1e932
  1. BOS-bounded route0x509201 → e1d4 → terminal · 200,000 USDT gross · ≥ 150463.919739 USDT from the designated collector lot
  2. Exact proxy reuseDD → the same e1d4 → the same terminal · 100,000 USDT gross · ≥ 66644.658655 Exchequer-derived
  3. Sibling proxy, same terminalDD → 0x509201 → Curve → f6c8 → the same terminal · ≥ 33809.640217 Exchequer-derived

Using the shared unrelated-funds pool only once, at least 133809.640217 nominal stablecoin units attributable to the Exchequer lot reached the common terminal across the January and March deposits.

Inspect the exact Ethereum transaction sequence
BOS-bounded and Exchequer-derived Ethereum terminal routes
UTCRouteAsset and amountTransaction
2025-11-20T16:00:11Zoperations509 → proxyE1d4200000 USDT 0xb270e61594…
2025-11-25T01:59:59ZproxyE1d4 → commonTerminal200000 USDT 0xe07b22ee1d…
2026-01-12T17:55:47Zdd → proxyE1d4100000 USDT 0xb7d54da940…
2026-01-13T13:36:23ZproxyE1d4 → commonTerminal100000 USDT 0xdbeb7a9ec7…
2026-03-30T15:55:23Zdd → operations509120000 USDT 0x893dad3add…
2026-03-30T15:57:59Zoperations509 → curveRouter120000 USDT → 119923.264180 USDC USDT to USDC 0x495ba532fe…
2026-03-30T15:59:47Zoperations509 → proxyF6c8122000 USDC 0xb0c2733f77…
2026-03-30T18:07:59ZproxyF6c8 → commonTerminal122000 USDC 0xf2e6892b32…

The public control and responsibility record

The record distinguishes cryptographic authority, documented project-account activity, and executive responsibility while connecting each to its source.

DD and BOS share one owner set

DD and the official BOS token-owner and allocation Safes use the exact same five owner addresses. The same 8C address deployed both families.

Exact on-chain configuration

Two addresses repeatedly operated DD

0x509201… and 0xcD900… supplied every approval on all 14 reviewed Ethereum DD executions. 0x509201 also approved DD’s payment to itself.

Exact signatures; custody records identify the people

One recurring payment network

DD paid 24 recipients. All 24 also received real USDT transfers initiated by 0x509201; at least 244585.603045 USDT of the DD group was Exchequer-derived.

Invoices and payee records identify purpose and recipients
Documented organizational role; no wallet attribution

Edan Yago

BitcoinOS co-founder and CEO; Sovryn identified him as project lead at launch, and he authored the approved SIP-0015 executive-treasury framework.

Documented leadership and treasury-design context.

Natural-person control behind DD, 0x509201, the shared owner keys, and the common terminals remains unidentified.

Actor attribution record · BitcoinOS leadership record (opens in a new tab) · Sovryn project-lead record (opens in a new tab) · SIP-0015 treasury framework (opens in a new tab)

Documented organizational role; no wallet attribution

Elan Nahari

BitcoinOS co-founder and COO; founder and Exchequer records place him in Sovryn’s founding and treasury process, and his public Armando account published the financial report and supplied the FastBTC explanation.

Documented leadership, treasury, reporting, and explanation context.

Natural-person control behind DD, 0x509201, the shared owner keys, and the common terminals remains unidentified.

Actor attribution record · BitcoinOS leadership record (opens in a new tab) · Sovryn founder record (opens in a new tab) · Exchequer meeting record (opens in a new tab) · Published financial report (opens in a new tab) · FastBTC explanation (opens in a new tab)

Multiple independent infrastructure fingerprints

Public Tyrone project identity

Sovryn identified Tyrone as Circle of Order Team Lead; a displayed Tyrone project account supplied 8C during a May 2024 BOB bridge session reproduced by public transactions.

Corroborated project-account link to 8C.

Continuous personal custody and natural-person ownership of 8C remain unresolved; 8C is not a DD owner.

Actor attribution record · Official Sovryn technical-role record (opens in a new tab) · 8C public BOB address (opens in a new tab) · Matching May 2024 bridge transaction (opens in a new tab)

Attribution record: public records link Yago and Nahari through leadership, treasury, reporting, and public-explanation roles. A preserved, on-chain-matched session links the public Tyrone project identity to 8C. Signer-custody, exchange KYC, device, and instruction records identify the people controlling DD, 0x509201, cD900, the common terminals, and the exchange accounts at each relevant time.

Address and infrastructure records

Open the complete register to inspect every address, role, confidence level, source link, and attribution record represented in the map.

Inspect the complete address register 19 source-linked infrastructure records
sourceFirst-party off-chain platform record

Origins sale counter

$4,888,380.30 in first-party usdCollected; 609,509,366.81051 BOS in tokensSold.

Scope: This is an off-chain platform counter, not one wallet balance or audited net proceeds.

BitcoinMultiple independent infrastructure fingerprints

Aggregated BTC deposit cohort

297 clean sweeps from 927 UTXOs and 699 unique input addresses.

Scope: Sale-window timing, 297 one-output sweeps from 927 external UTXOs and 699 unique input addresses, a Fireblocks-style unique-deposit sweep pattern, collector succession, and a May 2025 rollover synchronized within minutes of independently reconstructed Cardano BOS collectors.

BitcoinMultiple independent infrastructure fingerprints

Origins-style BTC collectors A → B

20.01527801 BTC gross; 20.01262609 BTC after sweep fees.

bc1qe3wasll7p4xy8tmrw64ept5xmmqn2rv602unh6 → bc1qspmy5dn0mk83k6grsaqcjd7lxqh7pwtwg3n6r4 → bc1qzxczrnp9383a7gc98mf08a29535ragp8de55z3

Scope: The topology is strongly attributable to BOS Origins; first-party Fireblocks mapping remains required.

BitcoinPublic service label; account owner unresolved

Exact common Bitcoin terminal

20.01114355 BTC candidate BOS lower bound and 23.13948498 BTC from Exchequer routes reached this exact address.

bc1qccy9mn9h2ed6sjf7pvx7af6zc7zax0qaegadw5

Scope: Origins or Fireblocks must produce the private vault-to-address inventory to make the candidate collector mapping first-party-confirmed. The terminal address is publicly labeled Gemini by one explorer, while another public label conflicts downstream. The exact address reuse is established; venue, customer, beneficial owner, authorization, purpose, and final disposition remain unresolved.

RootstockRecorded directly on-chain

Sovryn Exchequer

The 0x924f multisig held the treasury assets whose downstream paths are reconstructed here.

0x924f5Ad34698fD20C90fe5D5A8A0ABD3b42dC711

Scope: Registered-owner approvals are on-chain; natural-person signer custody and instructions require production records.

Rootstock / BitcoinRecorded directly on-chain

D9 → PowPeg → far side

23.146420437622064715 RBTC left the Exchequer route; 23.13948498 BTC reached the terminal after bridge and transaction fees.

Scope: Each hop is reconciled in native units; the final three terminal deposits are listed in the source record.

Ethereum / BNB ChainRecorded directly on-chain

Ethereum BOS collectors

BB55, FeD3, 1160, and the smaller 60c branch used participant-specific deposit sweeps; FeD3 and 1160 later funded 0x509201.

Scope: Wallet function is established by exact payment-and-sweep paths; matching every pooled unit to an order still requires Origins records.

Ethereum / BNB Chain / RootstockRecorded directly on-chain

0x509201…AbD6

Long-running Sovryn and BitcoinOS treasury-linked operations address; DD signer, DD payee, BOS Safe owner, and recipient of collector funds.

0x5092019A3E0334586273A21a701F1BD859ECAbD6

Scope: The address role is documented; its natural-person controller is unidentified.

Ethereum / BNB ChainRecorded directly on-chain

DD cross-chain Safe

508947.877906 USDT reconciled to Exchequer-origin assets entered DD. DD uses the same five-owner set as official BOS administration Safes.

0xDd2311ecEB6Ec8A83C027FDe4aa04eA455ee3FC4

Scope: Five owner addresses and threshold are public. The people controlling those keys are not.

EthereumRecorded directly on-chain

e1d4 forwarding proxy

The exact proxy accepted the BOS-bounded 200,000-USDT route and later DD’s 100,000-USDT route, forwarding each to the same terminal.

0xe1D4a15C1115c5f6F111311A89cb5C3b045DCd0A

Scope: Exact route reuse strongly supports a common account relationship; exchange records identify the credited account.

EthereumRecorded directly on-chain

f6c8 sibling proxy

Same creator, implementation, and terminal as e1d4; received 122,000 USDC from 0x509201 after the March DD transfer and Curve swap.

0xF6c8e0B7858bA96896B2bE771f3e42ecBf56933e

Scope: Same proxy family is an infrastructure relation, not a transfer between the proxies.

EthereumPublic service label; account owner unresolved

Common Ethereum terminal

133809.640217 Exchequer-attributed units reached the same public Gemini-labeled terminal infrastructure used after BOS collector receipts.

0x5f65f7b609678448494De4C87521CdF6cEf1e932

Scope: The service label identifies destination infrastructure, not the credited customer, subaccount, beneficial owner, trades, withdrawals, or final use.

EthereumForced minimum from balance conservation

24 recurring recipients

37 DD transfers totaling 277941 USDT; all 24 recipients also received genuine USDT payments initiated by 0x509201.

Scope: No recipient was publicly identified as a natural person, BitcoinOS developer, employee, vendor, or project payee. The supported label is recurring recipient/payment network.

CardanoMultiple independent infrastructure fingerprints

Three aggregated Cardano cohorts

2440904.338471 ADA across 1,834 UTXOs and 1,254 unique deposit addresses.

Scope: The private Fireblocks vault-to-address inventory remains required for first-party confirmation. Pooled collector balances include small opening or other funds, so the public record does not assign every identified ADA unit to an exchange credit or purchaser order. No natural-person controller is identified.

CardanoMultiple independent infrastructure fingerprints

Rotating Cardano collectors

Three shared-stake pools followed sale dates, unique-address sweeps, collector succession, and official BOS recipient records.

addr1q8e6yenct3hhxl0y4xd75atug25n2ph3mk6vxh9453vmuufdwcaxxwxuyh7enr57pa0ekp2ltfv8hydufkrzz8xq0kzsyh4ey4 · addr1qydpeegtjrfc9n9z3k0vtcdp0n4rax7dwl0dqenlnle4vrsw5jlwsq5y60jch6a859e4w7wdgfrv59szf0pt07rza6qsclds2s · addr1qxh0lghfqekh8q3p5078xgp8xs6wrjg2z95k965mm34pqfequyxu6rm97tsx9p2pmd00r9swyzmysxj7s6p6gntgam8scr9xan

Scope: The third collector is a high-confidence public candidate for private Fireblocks vault 58, not a first-party-confirmed mapping.

CardanoPublic service label; account owner unresolved

Cardanoscan-labeled Binance 1

2155639.685101 ADA reached the labeled terminal through a one-use enterprise relay.

addr1vx7j284mqe59w2mka36gf5xq0hvu8ms2989553fk5qh3prcapfpj3

Scope: Pooled/opening funds exceeded identified roots by 167.822746 ADA; Binance records identify the credited account.

Ethereum / BNB ChainRecorded directly on-chain

Official BOS Safe family

The official BOS token-owner and allocation Safes use the exact five owner addresses also installed on DD.

0x4F7265EAE3b538eD1816919076Bd22aE282C017F

Scope: Addresses are cryptographic authorities, not five independently identified people.

Ethereum / BNB Chain / RootstockRecorded directly on-chain

8C deployer and routing address

8C deployed DD on Ethereum and BNB Chain and the official BOS token-owner and allocation Safe family.

0x8C9143221F2b72Fcef391893c3a02Cf0fE84f50b

Scope: 8C is not a listed DD owner. The Tyrone project-account link is corroborated for a May 2024 session; continuous personal custody is unresolved.

Why investigators should test for misappropriation or embezzlement

The public record establishes more than overlapping personnel. Exchequer assets entered custody and payment infrastructure controlled by the same owner-address set used for official BOS administration; BOS-linked value and Exchequer-derived assets converged at exact exchange routes; and 0x509201 both received and authorized payments from DD.

These facts establish shared custody, wallet-level commingling, common payment rails, and related-party-control concerns. They support investigation of whether Sovryn property was diverted to BitcoinOS, related parties, or personal benefit without valid authority, fair consideration, complete disclosure, or reimbursement.

The decisive legal records cover: ownership and duties, authority, intent, purchased work, accounting treatment, reimbursement, and ultimate benefit. Those facts sit in the company, exchange, payee, and key-custody files identified below.

The records that can identify owners, purpose, and benefit

The public chain gets the inquiry to specific accounts, wallets, signers, recipients, and transactions. Compulsory records finish it.

  1. Origins and Fireblocks: every order, rate, vault, generated deposit address, customer reference, sweep, policy approval, signer, and audit log.
  2. Gemini, Binance, and any conflicting venue: address assignment, customer and subaccount, KYC and beneficial owner, credits, trades, internal transfers, withdrawals, and bank wires.
  3. Sovryn and BTC OS Limited: approved budgets, general ledgers, intercompany accounts, invoices, reimbursements, journal entries, cost allocation, tax records, and source-and-use schedules.
  4. DD, 0x509201, and the 24 recipients: signer and device logs, key custody, instructions, contracts, invoices, payroll/vendor identity, service periods, project codes, and subsequent disposition.
  5. Safe and actor attribution: who selected and controlled each of the five owner keys, who controlled 8C at each relevant date, and who approved every cross-project payment.