Shavez's BitcoinCode:
the promise,
and the ledger

Not a two-hop check on one wallet

A Reality Check follows one wallet for a hop or two. BitcoinCode needed more than that: the creator's complete transaction list, full histories of the wallets its money moved through, the pool's own records for as far as the explorer would give them up, and every mint read down to who signed it. Every figure in this report traces back to the bytes it came from.

  const check = (rows, req) => {
    if (!Array.isArray(rows)) throw new Deterministic(`page ${req.page} is not an array`);
    if (rows.length > req.offset) throw new Deterministic(`explorer returned ${rows.length} rows for offset ${req.offset}: offset not applied`);
    let prev = -1;
    for (const r of rows) {
      const b = blockOf(r);
      if (b === null) throw new Deterministic(`row without a block number: ${JSON.stringify(r).slice(0, 200)}`);
      if (b < prev) throw new Deterministic(`rows out of ascending block order (${prev} then ${b}) on page ${req.page}: sort not applied`);
      if (!involves(r, target)) throw new Deterministic(`row does not involve ${target}: filter not applied: ${JSON.stringify(r).slice(0, 240)}`);
      prev = b;
    }
  };
  // Does this page continue the list? No row below the last block consumed; at that block, no repeat of a row
  // already consumed (where the key is unique by construction). Changes nothing. Returns null or a problem.
  const validate = (rows, pageNo) => {
    let lb = lastListBlock, t = tail;
    for (const r of rows) {
      const b = blockOf(r), k = key(r);
      if (lb !== null && b < lb)
        return { fatal: true, msg: `page ${pageNo} has a row at block ${b}, below the last block already consumed (${lb}): page not applied, or the list moved under the pull` };
      if (lb !== null && b === lb && unique(r) && t.get(k))
        return { fatal: false, block: b, msg: `page ${pageNo} repeats a row already consumed at block ${b} (${String(k).slice(0, 90)}): page not applied, or rows in that block moved across the page boundary` };
      if (lb === null || b > lb) { lb = b; t = new Map(); }
      else if (t === tail) t = new Map(tail);
      t.set(k, (t.get(k) || 0) + 1);
    }
    return null;
  };

  const check = (rows, req) => {
    if (!Array.isArray(rows)) throw new Deterministic(`page ${req.page} is not an array`);
    if (rows.length > req.offset) throw new Deterministic(`explorer returned ${rows.length} rows for offset ${req.offset}: offset not applied`);
    let prev = -1;
    for (const r of rows) {
      const b = blockOf(r);
      if (b === null) throw new Deterministic(`row without a block number: ${JSON.stringify(r).slice(0, 200)}`);
      if (b < prev) throw new Deterministic(`rows out of ascending block order (${prev} then ${b}) on page ${req.page}: sort not applied`);
      if (!involves(r, target)) throw new Deterministic(`row does not involve ${target}: filter not applied: ${JSON.stringify(r).slice(0, 240)}`);
      prev = b;
    }
  };
  // Does this page continue the list? No row below the last block consumed; at that block, no repeat of a row
  // already consumed (where the key is unique by construction). Changes nothing. Returns null or a problem.
  const validate = (rows, pageNo) => {
    let lb = lastListBlock, t = tail;
    for (const r of rows) {
      const b = blockOf(r), k = key(r);
      if (lb !== null && b < lb)
        return { fatal: true, msg: `page ${pageNo} has a row at block ${b}, below the last block already consumed (${lb}): page not applied, or the list moved under the pull` };
      if (lb !== null && b === lb && unique(r) && t.get(k))
        return { fatal: false, block: b, msg: `page ${pageNo} repeats a row already consumed at block ${b} (${String(k).slice(0, 90)}): page not applied, or rows in that block moved across the page boundary` };
      if (lb === null || b > lb) { lb = b; t = new Map(); }
      else if (t === tail) t = new Map(tail);
      t.set(k, (t.get(k) || 0) + 1);
    }
    return null;
  };

Six kinds of source, and each statement says which it rests on:

The name borrows Bitcoin's. Nothing else does

BitcoinCode ("BTCC", the "BTC20 Smart Chain") is a separate chain with its own coin. It isn't part of Bitcoin, it doesn't run on Bitcoin, and no code read in this investigation converts BTCC into bitcoin. Even its presenter drew the line at launch:

"21 million supply, [built] like Bitcoin blockchain. Don't ever say it's better than Bitcoin. We are really inspired by Bitcoin."22 Sep 2023 · 02:55–03:11

In full, as shortened in the table above
0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599
0xcd9c88bdbe0ae6e8b20ed87c70c1af5f5f816b18363c4970d5cfd13f745f67f1

What a public blockchain gives you, and what BitcoinCode gives you

A public blockchain is worth trusting for a handful of practical reasons: anyone can read it, anyone can check it, nobody alone decides who keeps it, and nobody alone prints its money. Here is BitcoinCode against each of them, with the section that shows it.

The training of 5 September 2023, in the presenter’s words

The recording “WAAS Affiliate Marketing Training Sept. 5th 2023” is first in a YouTube playlist titled “BTCC Training by Shavez”, published by the channel “Crypto Tech SXM”. It is a recorded Zoom call. Three things on screen identify the presenter as Shavez:

• the Zoom label “SHAVEZ (BTC…)”;
• the opening slide, signed “-SHAVEZ”;
• the playlist title.

The channel is a third party’s. The label and the slide are the presenter’s own.

The NFT miners were the product. These are the five promises made about them. Read each one, then turn it over to see what the ledger shows.

Three possible sources, and a contract isn’t one of them

BitcoinCode works like Ethereum. BTCC is the chain’s own coin, the way ether is Ethereum’s. On a chain of that kind, a coin can come into existence in only three ways, and all three are in the hands of whoever runs the chain:

1. The starting allocation, written into the chain’s first block (the “genesis” block).
2. Block rewards, if the chain’s rules pay any.
3. A change to the chain’s rules, made by those who run the node software.

A smart contract can’t do any of these. It can hold coins and pass them on, and nothing more. So a contract that “mines” BTCC can only be paying out BTCC that someone first put into it.

The "Meeting Close Out" call of 22 September 2023

The recording "Meeting Close Out Sept 22nd" is published on the same YouTube channel as the training, "Crypto Tech SXM". The speaker's Zoom tile is labelled "shavez". He spoke the night before launch ("it's already 11:15 my time"):

"Today the chain is live, tomorrow the product is going to be live. In 24 hours the minting will start, and on 29th we will start mining."01:16–01:31

"21 million supply, [built] like Bitcoin blockchain."02:55–03:01

"We have created everything according to the numerology … that's why we are not minting today, we are minting tomorrow."14:06–14:15

• 22 Sep 2023, the call's own screenThe operator's explorer shows 21,789 blocks and 10 transactions in total, with a block every 3 seconds. Those 10 transactions came before the creator's first. Who sent them is not established.
• 23 Sep 2023 13:30:29Z · block 43,737The creator, [0x]34cCC8, sends its first transaction (nonce 0). That first transaction creates the ZEON GT1X miner contract. Within 24 seconds it has also created GT10X, GT100X and the "property" contract, and a fifth contract follows at 13:31:02Z. The miner contracts: on time. When the first miner was minted is not established.
• at block 43,736That same address already holds exactly 21,000,000 BTCC (§2.2).
• 29 Sep 2023Mining was promised for today. The pool that pays "mining" doesn't exist yet.
• 2 Oct 2023The pool is created at 03:42:17Z and started at 04:00:08Z, with 20 BTCC sent in. It is paused at 04:25:47Z, filled with 20,998,712.96 BTCC at 18:26:11Z, and unpaused at 18:40:44Z. Mining: three days late. It is the only payer of "mining" found (§2.4).

The supply was already there at the start

At block 43,736, this address held exactly 21,000,000 BTCC. It had not yet sent or received a single transaction. Its first transaction (nonce 0) is in the next block, 43,737, on 23 Sep 2023 at 13:30Z. So no ordinary transaction delivered those coins to it. Transfers made inside contract calls weren’t checked.

No mining code, no output and no reward

The ZEON “miners” are four NFT contracts. Three have published source. The explorer says the fourth is byte-for-byte the same code as the GT100X.

RIFT:CURIO:428638-dd821B:CG  ZEON GT1X
  0x4286388ad684515627464dF221b59Cc5C2dd821B
RIFT:CURIO:c4256C-8A3A26:CG  ZEON GT1X (unverified)
  0xc4256CeE90c418DDE89163606532Ea6Ed98A3A26
RIFT:CURIO:371d9C-E9e054:CG  ZEON GT10X
  0x371d9C99aBC64d90356B488f2b9Be56350E9e054
RIFT:CURIO:286F43-0AcA80:CG  ZEON GT100X
  0x286F4310551D634Ef485a9bEE962f19cbb0AcA80

Only addresses on a list the owner keeps can create these NFTs. Creating one costs nothing at the contract, so whatever a buyer paid was paid somewhere else.

Filled by the creator in one transfer, and paid out of its own balance

Members deposit (“stake”) their NFT miners in this pool. Under its published code, it paid BTCC at a fixed rate, shared between stakers according to a “hash rate” number. The code it has run since 22 Nov 2023 is unpublished (§4.3). The rate copies Bitcoin’s: 50 BTCC every ten minutes, which is 7,200 a day, for four years, then half that. Over all the periods together it comes to about 21 million.

RIFT:CURIO:b116db-B0d0c2:CG  "property" contract (unpublished)
  0xb116dbC19873a6d8Dec92e960ef229ffbBB0d0c2
RIFT:CURIO:700F05-4759f0:CG  StakingV1, the pool's first code
  0x700F05b0c90DCdd5d75ae7106fed7B7ed44759f0
RIFT:CURIO:3558e7-6807eD:CG  StakingV1 v2 (from 16 Oct 2023)
  0x3558e707f29f589c99585B17bB217267B56807eD
RIFT:CURIO:e99aD6-EA1B35:CG  BFUEL
  0xe99aD64420A20aF4d02806e2cCEBe693d4EA1B35

In full, as shortened in the table above
0x6db54866bedbfd39757ebf5fd88f62367254b25c92d3cc9fb79fe3c6e278b787
0xae8fa84f23c4fe19459456336ebd74f66cd4b576a9dcdf77037484e1fc4410c6

How BTCC got a dollar value on day one

"3,000 [BTCC] we will keep it for airdrop, and against that I will on call deposit wrapped Bitcoin in the liquidity … so now you can determine the price of BTCC even before mining. So it will be three dollars. It will not start from zero, it will be from three dollars, because I am putting in liquidity."22 Sep 2023 · 12:03–12:41

Every contract of the market read here, except the swap pool [0x]2C06D9, was created by [0x]34cCC8, the address that held all 21 million BTCC:

RIFT:CURIO:445465-0ED98E:CG  wrapped BTCC; created by [0x]34cCC8, 2 Oct 2023 04:09:59Z
  0x44546571729D1CC8c8DD680A36D80aD8E30ED98E
RIFT:CURIO:6F8FC8-865e29:CG  swap router; created by [0x]34cCC8, 2 Oct 2023 04:20:17Z
  0x6F8FC88C42E829a6F7eE8B823E043CB1d4865e29
RIFT:CURIO:9C80AF-d6001F:CG  "USDT" no. 1, 6 decimals; created by [0x]34cCC8, 3 Oct 2023 16:56:05Z
  0x9C80AF130278c14DB04A0bB2Cc9a0F0466d6001F

• 3 Oct 2023 17:43:11Z[0x]34cCC8 receives exactly 290 BTCC from [0x]c6aFd2, the wallet later minted 67 million "USDT" (§5.2; tx 0x5b151f7e4faaf88ae83ea0409b540e95785289ddadc83af2386371e110384711).
• 3 Oct 2023 17:48:26Z[0x]34cCC8 calls the router's addLiquidityETH with 290 BTCC and 870 of "USDT" no. 1. The minimums equal the amounts, so the ratio is exact: $3.00 per BTCC.
• 3 Oct 18:12 and 18:13It buys from its own pool with 1 BTCC (for at least 2.965922 of the "USDT"), then sells 1 "USDT" back.
• 5 Oct 04:55:26ZIt withdraws that liquidity. The call sets minimums of 134.80 BTCC and 1,856.98 "USDT" back, which puts the pool at about $13.78 per BTCC by then.
• 5 Oct 05:23:56Z and 07:54:38ZIt creates "USDT" no. 2, then pairs 1 BTCC with 15.70 of it.
• 5 Oct 12:17:23ZIt creates "USDT" no. 3 ([0x]aB472A). This is the token later minted in round millions (§5.2).
• 22 Nov 2023 12:29:58ZIt adds 1 BTCC to a pool against "USDT" no. 3 at the pool's ratio then: about $74.31 per BTCC.
• 3 Nov 2024 13:46:03Z"Wrapped Bitcoin" finally enters the creator's liquidity, 13 months late: 85,665 BTCC against 100 "WBTC". That "WBTC" is a token [0x]34cCC8 created the same day. Five hours earlier, [0x]34cCC8 had received 99,999.99 BTCC from [0x]c6aFd2 (tx 0xc3952f423eece9fb3896222748faf5df77445a814a221cefbaa668770b5c4d24) (§9.1, claim 8).

RIFT:CURIO:7bB89C-ff3B0c:CG  "USDT" no. 2, 6 decimals; created by [0x]34cCC8, 5 Oct 2023
  0x7bB89Cb9184749888c718F99eC64D674Ccff3B0c
RIFT:CPTY:aB472A-E7878A:CG  "USDT" no. 3, 6 decimals; created by [0x]34cCC8, 5 Oct 2023
  0xaB472AE141Cc0abE698Be3df227513367EE7878A

In full, as shortened in the table above
0x1dbc44f853fbbb53ad2131f3b0858306f953152e8e70e84fdb5b09a52c37de44
0xd9056cb544f159c01063f19b715df3db21333d79a2929203bbd722087505dc90
0xcd9c88bdbe0ae6e8b20ed87c70c1af5f5f816b18363c4970d5cfd13f745f67f1

What "connect your miner to the node" meant in code

"Imagine you having a node and validating … you will make a lot of money. So what I have planned is I will not sell nodes [for] less than half a million dollars, because [nodes] will make [a] massive chunk of gas [fee] every 10 minutes."22 Sep 2023 · 07:57–08:23

"Initially for our people we will give nodes like this … but the goal is to decentralize it."08:32–08:52

"If you have the node you have the control, you have the power … I will have zero control."09:36–09:49

"You and me, we will connect our miner to the node, and we will hit connect to the node together."13:07–13:18

"This is how validator will look like … you will validate your address in one click."17:31–18:24

BNB's toolkit for private, BSC-compatible chains, and how it differs from BSC itself

BitcoinCode presents itself as the "BTC20 Smart Chain". Its records carry the fingerprints of a specific kit: the one BNB Chain's ecosystem offers for building separate, BSC-compatible networks (documented by Ankr as "BNB Sidechain"). In that kit, the chain's own management contracts sit at fixed addresses:

0x0000000000000000000000000000000000001000  Staking       (validator registration and stake)
0x0000000000000000000000000000000000001002  SystemReward
0x0000000000000000000000000000000000007003  ChainConfig

(no tag yet)  registered as a validator by [0x]34cCC8, 3 Oct 2023
  0x5fB621DE3407a8C7B6b2B02746BC65930cDa014A

In full, as shortened in the table above
0x5fB621DE3407a8C7B6b2B02746BC65930cDa014A
0xbab415c8456da1518daabf69d27fa6aff566b630217b6815740e4bb220a635ef

Three code changes, the last two unpublished; 21 calls naming 358 staked miners, and those read sent miners to [0x]34cCC8

Every change was sent by [0x]34cCC8, the pool’s owner from its creation. None of [0x]34cCC8’s 7,832 transactions hands ownership of the pool to anyone else.

RIFT:CURIO:960a62-c7D550:CG  unpublished, from 21 Nov 2023
  0x960a6279E55C6E0635fea61CFa268376Dcc7D550
RIFT:CURIO:978a93-2EE710:CG  unpublished, from 22 Nov 2023
  0x978a93FBFf996d5C87bE5D5616354327be2EE710

Anyone could send transactions; one address, [0x]34cCC8, held the BTCC, minted the "USDT" read, and changed the pool's rules

In the first 175,000 pool transactions (2 Oct to 14 Dec 2023, a stopped pull, so a floor), 11,075 addresses other than the creator sent transactions to the staking pool, and 11,061 of them had at least one succeed. At least 1,314 different addresses used the chain's "bridge", [0x]556Da7 (§5.4), between 9 Oct 2023 and 7 Jan 2024. It worked as a withdrawal request, not a bridge: it burned the chain-"USDT" and recorded the TRON address typed in. Any real USDT paid on TRON had to come from whoever runs the TRON side, on a different chain entirely. Even that route closed on 7 Jan 2024, when [0x]34cCC8 removed "USDT" from it. What came from one address, [0x]34cCC8, was the money members used and the pool's rules (§2.2 to §4.3).

Taken together, most of what reached the two largest chain-"USDT" wallets read was created there, by the creator

RIFT:CPTY:aB472A-E7878A:CG  the chain's "USDT" token (source unpublished)
  0xaB472AE141Cc0abE698Be3df227513367EE7878A
RIFT:CPTY:c6aFd2-36e27C:CG  the largest chain-USDT wallet read
  0xc6aFd23A13d420828d424E327A7de4d5bA36e27C
RIFT:CPTY:06aCe6-3dCAA0:CG  the second largest read
  0x06aCe60b5D5cC887a79AC111dEeF88B5453dCAA0

A token named "USDT" on this chain is not Tether's USDT. It is a contract on BitcoinCode whose source isn't published. When the token's records show a transfer from the zero address, that is new tokens being created (minted). The two largest chain-USDT wallets read in full received:

RIFT:CURIO:2C06D9-833d5b:CG  a swap pool on the chain; label "UNI-V2", token pair not established
  0x2C06D97870Ea6931D49A130544B012Db5D833d5b
(no tag yet)                 21.5M from [0x]c6aFd2 and 0.36M from [0x]06aCe6
  0x73985398366F13A5440689c5079ec61853dc1c8e

(no tag yet)  allowed to mint by [0x]34cCC8, 6-24 Oct 2023; signed 4 small mints
  0xD6C3b1a1b70F1b10d886f4B6964cD225d861dDE0

In full, as shortened in the table above
0xD6C3b1a1b70F1b10d886f4B6964cD225d861dDE0

The creator buys BTCC with its own "USDT"

"On 30th this reward that we mine, BTCC that we [mine], will be accepted … will not be given in withdrawals, will be accepted in deposits."22 Sep 2023 · 01:31–01:49

"My only job will be to collect as much [BTCC] as possible from you guys, because I have to force you all to sell, and mostly sell it to me, so that we can … go for listings."09:49–10:09

In full, as shortened in the table above
0x6ca4d06ad0009c84226f56375512e16f819b83b9122f292779e6ed0211b0f6ab
0xbb8c7782a9bc6b438524f080c9a28b76472f86aa1701c2eb1868c2de573edccf
0xb2a283c738a0c6f2cec45063cca724f023112dbb4b1dddef4a7fc9d0b47c7834

In May 2025, [0x]34cCC8 made three purchases of BTCC, listed in the table under Tech detail above. How much BTCC each swap actually delivered hasn't been read, but each swap instruction named the least BTCC [0x]34cCC8 would accept. So it received at least those amounts, and paid at most about $120 to $155 per BTCC. Where its "USDT" came from isn't established, since all 39 of its mints that we read from the BitcoinCode explorer went to two other wallets (§5.2), but it already held at least 1,000,000 of it on 31 Jan 2025, when it put that sum into a pool against another token it had created and took the liquidity back out 48 minutes later. Whether the listings promised in September 2023 ever happened was not tested.

In full, as shortened in the table above
0x4f8815933cE09c9F2c9435414b3dbeF423Fd3fa5
0x217ec7d93a446194cdf1ef7f888655238b43268b50448d77693d41ea03527a04
0x4dfde7484a1f612c037400e62fc7024326867ae761ded45969a9585ed830cc3b

Assets one address could create, and no established route to value off the chain

For a token on this chain to be worth something outside it, there has to be a way out: a bridge that pays real money on another chain, or an exchange that takes it. This is every route out that the investigation has read.

A withdrawal request, not a bridge. The chain's "bridge", [0x]556Da7, moves nothing between chains. A member sent it chain-"USDT" and typed in a TRON address; the contract burned the "USDT" and recorded the address. Any real USDT paid on TRON had to come from whoever runs the TRON side, on a different chain entirely. Whether it was paid, to whom and how much is traced in a later part of this audit, from the burn list filed with this one. This route closed on 7 Jan 2024.

RIFT:CPTY:556Da7-fA82f1:CG  the "bridge" contract ("bridgeToken")
  0x556Da75f8b248DDb9b133Dd71bc2CAB7BbfA82f1

(TRON; no tag)  TRON USDT deposit address on a WAAS deposit screen, 14 Sep 2023 (recording)
  TSrzRHrUeRBgfiJDx49VCS98QB6XLgLGFU

Valentine's Day 2024, UK prime time

"We are going to … unveil the Affiliate Marketing 3.0 [DAO], which is registered in United States. It is going to be a decentralized autonomous organization."26:49–27:03

"Every member of [We Are All Satoshi] is going to have one vote, a governance token of our own on [BTC20] Smart Chain."28:51–29:07

"We are going to unveil the governance token, the smart contract, in our event."30:16–30:23

"I will also have one vote. We all will be equal in this organization."31:06–31:16

RIFT:CURIO:8E421B-f8B9B9:CG  created by [0x]34cCC8, 22 Feb 2024 09:21:13Z; purpose not established
  0x8E421B92A26721C46332D063b883a4e8e1f8B9B9
RIFT:CURIO:c582da-42DF0e:CG  created by [0x]34cCC8, 22 Feb 2024 09:21:22Z; purpose not established
  0xc582da428B307991771046cbFEda909f5642DF0e

In full, as shortened in the table above
0x15bd9ba98353e908c8a9bc003f395ac684cebd405bcab3b6d2d893b63f99223e
0x56b54fbd87c57d96e2fd89206186d5a266d8e661ffc08561ae051bed5b2f815f

"Harvest Party 9.16.24", published by Crypto Tech SXM

Crypto Tech, whose channel published the training and the launch call, runs a weekly "Harvest Party". The spreadsheet heading on his screen reads "Once a week, on Monday @ 3pm. Let's drive BTCC price up." He shares his screen throughout, and his wallets are public:

RIFT:CPTY:810b17-8306Bb:CG  Crypto Tech's harvest wallet ("Account 4")
  0x810b1777f8F091fb0B9D65FcC0986067908306Bb
RIFT:CPTY:50Faf8-596e19:CG  Crypto Tech's "BTCC Assets Saving Wallet"
  0x50Faf81B6D35CdcE6c362a206721FA085D596e19

1 · The dashboard's numbers were clocks

• "Circulating supply 2,521,050" is exactly 50 BTCC for every 10 minutes since 18:40:44Z on 2 Oct 2023, the moment [0x]34cCC8 unpaused the pool. "Next halving: 1110 days 21 hours" matches four calendar years from the same moment, to the nearest hour. Both fit if his clock read UTC−4, which the screen doesn't show. Counted from start(), neither matches.
• "Total market cap $1,410,969,000" is 21,000,000 × $67.189. "Circulating market cap $169,386,828.45" is 2,521,050 × $67.189. Both are exact to the cent.
• So the dashboard showed a payout timetable multiplied by a quoted price, not coins actually paid out. Two years later, on 24 Sep 2026, the pool still held 18,979,696.67 of the 20,998,732.96 BTCC that [0x]34cCC8 put into it. That means about 2.02 million BTCC had left the pool in total, fewer than the 2.52 million the dashboard called "circulating" back in Sep 2024. The one assumption is that no other BTCC was paid into the pool along the way, which hasn't been checked (§2.4).

2 · Harvesting cost more than it paid

• He swaps 1.48832 BTCC for 100 "USDT" on swap.bitcoincode.technology: $67.19 a coin. The router on his MetaMask screen matches the first and last characters of [0x]34cCC8's router (§3.1), and the fee is 0.30%, to the precision shown.
• He buys 8,000 BFuel with the 100 "USDT" at a fixed $0.0125, on the purchase page shown on his screen. The BFuel contract in his wallet is [0x]e99aD6 (§2.4).
• He spends 6,748 BFuel ($84.35) to claim 0.99648 BTCC, worth about $67 at the dashboard's price.
• His swap sold BTCC. In a pool of this kind, a sale pushes the price down: the opposite of the party's stated aim.

3 · Who the pool paid

His explorer screen shows the pool (the explorer labels it "COD20Proxy") paying his harvest wallet 0.99648 BTCC at block 10,307,670 (tx 0xf5cf1a6d…d55b7189) and 1.00655 BTCC a week earlier at block 10,103,810 (tx 0xd59e3150…3509d12f). That wallet is already in the pool's own records: between 28 Oct and 12 Dec 2023 it called stake 25 times, batchStake 3 times, withdrawMiner 10 times and batchWithdrawMiners 3 times. It is the first recipient of the pool's BTCC named in this report other than [0x]34cCC8 itself.

4 · In his own words

"People sold everything to buy Boomerang and stopped harvesting, because the price dropped and stagnated around in the 60s."46:47–46:56

Every fault the operator's explorer showed when this investigation tried to read it whole

On a public chain, an investigator, an auditor or a member can pull the complete history of any address, check it against a second source, and get the same answer every time. Over 11 and 12 October 2026, this investigation tried to do exactly that on BitcoinCode, through the only window there is. This is what it found:

Transparency was part of the pitch. Introducing the chain on 22 Sep 2023, the presenter said it would become "more transparent" as it gained "more nodes" (08:53–09:00). The wrapped Bitcoin he would put into liquidity was there "to make sure that there is absolute enough transparency" (12:20–12:25), and the airdropped supply "will be transparent with the community, you all can see … on chain" (12:54–13:00). The only window onto that chain refuses or garbles a complete reading of any large account, and has shown nothing new since 24 Sep 2026, as read on 12 Oct 2026.

The explorer stopped five minutes after the node’s certificate expired

The operator runs the only public explorer found for this chain, scan.bitcoincode.technology. Its newest block is 30,834,158, timestamped 24 Sep 2026 06:21:32Z, and there is no block after it. Until then, blocks had been arriving about every three seconds.

• 26 Jun 2026 · 06:16:20ZThe node’s 90-day certificate becomes valid (its “Not Before” time).
• 24 Sep 2026 · 06:16:19ZThe node’s certificate expires.
• 24 Sep 2026 · 06:21:32ZThe explorer records its last block, 5 minutes 13 seconds later.
• 25 Sep 2026Two new certificates are issued for swap.bitcoincode.technology.
• 12 Oct 2026 · 00:48ZThe node still presents the expired certificate, and the public Certificate Transparency logs show no newer one for it. A valid wildcard certificate that would cover it exists: Let’s Encrypt to 23 Oct 2026, and Google Trust Services to 4 Nov 2026.

Eighteen statements, from the training of 5 Sep 2023 to the DAO of 14 Feb 2024

Each verdict describes what the code and the records show. None is a verdict on the speaker’s intent. Where the records can’t settle a claim, the verdict says so.

The test, applied, so readers can judge for themselves

"Blockchain" isn't a legal term, and software alone doesn't settle it. What people rely on when they trust a public blockchain is a short list of properties. Here is the list, with BitcoinCode's answer to each:

Self-published roles and public registers only

• "Shavez's BitcoinCode." The headline uses his name because he presented the chain as his own: "we will make a lot of money as a blockchain" (22 Sep 2023, 07:50–07:57) and "our own blockchain" (14 Feb 2024, 32:17–32:21). It does not mean he is shown to control [0x]34cCC8. That is not established.
• Shavez is named as the presenter of the 5 Sep 2023 training. The basis is his own presentation: the Zoom label and the signed slide (§1.1).
• The creator address, [0x]34cCC8, isn't linked to any person in this section. Who controls it is not established.
• The four holders in §4.3 are not characterised, and their addresses are held back. Nor is the registered validator 0x5fB621, or [0x]c6aFd2 and [0x]06aCe6, characterised beyond what their records show.
• Crypto Tech is named by his own channel's handle (Crypto Tech SXM), and his wallets are given in full: he published them on screen himself (§7.1).
• Nobody else is named, apart from the LLP's designated members as the public register records them (box below). That excludes the promoters and members named in the training's captions.

Three questions bigger than this chain

Every section marks its own limits in its "How we know" box. Three questions reach beyond any one section, and the next parts of this audit take them up:

• Who controls [0x]34cCC8. This report shows what that address did. It does not name who holds it, and nothing here should be read as doing so (Who is named).
• What happened on TRON, and what members paid for nodes. The "bridge" burned 1,437,295.80 chain-"USDT" (§5.4). Whether anyone was paid on TRON in return, and what members paid for nodes there, are being traced alongside the HyperFund investigation.
• Who the staking pool paid. One recipient is named from his own screen (§7.1). The full pull was stopped by the explorer faults in §8.1 and is parked until the records can be read in full.

Addresses and files behind every statement

Addresses. How to read a tag is set out at the start. Each tag was checked against its full address, with its EIP-55 checksum computed, and run through a lookalike-collision check across the case evidence set. None collided. The three untagged addresses have been submitted to the Hashbook register as candidates.

Links. Addresses, transactions and blocks on this chain link to the operator's explorer, scan.bitcoincode.technology. Checked by hand on the afternoon of 12 Oct 2026, its front page opened but could not load blocks or transactions, so a link may open without data. The full value is printed beside every link so it can be checked without the explorer. Two transactions read from Crypto Tech's screen are shown as his screen showed them, shortened; they link to their blocks instead.

Recordings. Every quoted timestamp links to that moment in the recording. Each recording was matched on YouTube on 12 Oct 2026 by its title, channel and length against the transcript filed for it:

• "WAAS Affiliate Marketing Training Sept. 5th 2023", Crypto Tech SXM, 25:59. Transcript 0034_input_yt-transcript_waas-affiliate-marketing-training-2023-09-05.txt.
• "WAAS Funding Sept. 14th", Crypto Tech SXM, 6:54. Screenshot 1233_input_screenshot-yt-waas-funding-2023-09-14.png.
• "Meeting Close Out Sept 22nd", Crypto Tech SXM, 24:56. Transcript 1233_input_yt-transcript_meeting-close-out-2023-09-22.txt.
• "CEO Shavez Session English on 14 Feb 2024, UK Primetime", Affiliate Marketing 3.0 BTCC, 35:36. Transcript 1233_input_yt-transcript_ceo-shavez-session-2024-02-14.txt.
• "Harvest Party 9.16.24", Crypto Tech SXM, 1:14:05. Transcript 1221_input_yt-transcript_harvest-party-2024-09-16.txt.

A recording can be taken down or edited after this date. The transcripts and screenshots filed under Files are the record this report rests on; the links are there for convenience.

Marks: the Bitcoin logo is in the public domain; the Ethereum logo is by the Ethereum Foundation, used under CC BY 3.0. BitcoinCode and its "WBTC" are shown by a "?" coin in the purple of the operator's own explorer (#5A43A4), sampled from 1233_input_screenshot-yt-meeting-close-out-2023-09-22_01.png.

RIFT:CPTY:34cCC8-1Bb8Ba:CG   creator of every contract here except [0x]2C06D9
  0x34cCC892b67C873853D7a7050f5Df5B2781Bb8Ba
RIFT:CURIO:8e3C84-8C92aE:CG  staking ("mining") pool
  0x8e3C843104e155A90fcB0CF0deb6756D688C92aE
RIFT:CURIO:700F05-4759f0:CG  StakingV1, first code
  0x700F05b0c90DCdd5d75ae7106fed7B7ed44759f0
RIFT:CURIO:3558e7-6807eD:CG  StakingV1 v2
  0x3558e707f29f589c99585B17bB217267B56807eD
RIFT:CURIO:960a62-c7D550:CG  unpublished, 21 Nov 2023
  0x960a6279E55C6E0635fea61CFa268376Dcc7D550
RIFT:CURIO:978a93-2EE710:CG  unpublished, 22 Nov 2023
  0x978a93FBFf996d5C87bE5D5616354327be2EE710
RIFT:CURIO:b116db-B0d0c2:CG  "property" contract
  0xb116dbC19873a6d8Dec92e960ef229ffbBB0d0c2
RIFT:CURIO:e99aD6-EA1B35:CG  BFUEL
  0xe99aD64420A20aF4d02806e2cCEBe693d4EA1B35
RIFT:CURIO:53b71E-642f09:CG  the chain's "WBTC"
  0x53b71Ed5900f035d775638115f54681c86642f09
RIFT:CURIO:428638-dd821B:CG  ZEON GT1X
  0x4286388ad684515627464dF221b59Cc5C2dd821B
RIFT:CURIO:c4256C-8A3A26:CG  ZEON GT1X (unverified)
  0xc4256CeE90c418DDE89163606532Ea6Ed98A3A26
RIFT:CURIO:371d9C-E9e054:CG  ZEON GT10X
  0x371d9C99aBC64d90356B488f2b9Be56350E9e054
RIFT:CURIO:286F43-0AcA80:CG  ZEON GT100X
  0x286F4310551D634Ef485a9bEE962f19cbb0AcA80
RIFT:CPTY:aB472A-E7878A:CG   "USDT" no. 3
  0xaB472AE141Cc0abE698Be3df227513367EE7878A
RIFT:CPTY:c6aFd2-36e27C:CG   largest chain-USDT wallet read
  0xc6aFd23A13d420828d424E327A7de4d5bA36e27C
RIFT:CPTY:06aCe6-3dCAA0:CG   second largest read
  0x06aCe60b5D5cC887a79AC111dEeF88B5453dCAA0
RIFT:CPTY:556Da7-fA82f1:CG   the bridge contract
  0x556Da75f8b248DDb9b133Dd71bc2CAB7BbfA82f1
RIFT:CURIO:2C06D9-833d5b:CG  swap pool "UNI-V2"
  0x2C06D97870Ea6931D49A130544B012Db5D833d5b
RIFT:CURIO:445465-0ED98E:CG  wrapped BTCC; by [0x]34cCC8, 2 Oct 2023
  0x44546571729D1CC8c8DD680A36D80aD8E30ED98E
RIFT:CURIO:6F8FC8-865e29:CG  swap router; by [0x]34cCC8, 2 Oct 2023
  0x6F8FC88C42E829a6F7eE8B823E043CB1d4865e29
RIFT:CURIO:9C80AF-d6001F:CG  "USDT" no. 1; by [0x]34cCC8, 3 Oct 2023
  0x9C80AF130278c14DB04A0bB2Cc9a0F0466d6001F
RIFT:CURIO:7bB89C-ff3B0c:CG  "USDT" no. 2; by [0x]34cCC8, 5 Oct 2023
  0x7bB89Cb9184749888c718F99eC64D674Ccff3B0c
RIFT:CURIO:8E421B-f8B9B9:CG  by [0x]34cCC8, 22 Feb 2024; not read
  0x8E421B92A26721C46332D063b883a4e8e1f8B9B9
RIFT:CURIO:c582da-42DF0e:CG  by [0x]34cCC8, 22 Feb 2024; not read
  0xc582da428B307991771046cbFEda909f5642DF0e
RIFT:CPTY:810b17-8306Bb:CG   Crypto Tech harvest wallet
  0x810b1777f8F091fb0B9D65FcC0986067908306Bb
RIFT:CPTY:50Faf8-596e19:CG   Crypto Tech saving wallet
  0x50Faf81B6D35CdcE6c362a206721FA085D596e19
(no tag yet)                 validator registered by [0x]34cCC8
  0x5fB621DE3407a8C7B6b2B02746BC65930cDa014A
(no tag yet)                 21.8M chain-USDT from [0x]c6aFd2 and [0x]06aCe6
  0x73985398366F13A5440689c5079ec61853dc1c8e
(no tag yet)                 allowed to mint chain-USDT, 6-24 Oct 2023
  0xD6C3b1a1b70F1b10d886f4B6964cD225d861dDE0

Files. Paths are under Reality Check FORENSIC Reports/, onchain-rpc/out/ or RC_CANON/handovers/. Files already in the case manifest, or in a save run's .sha256 list, matched when hashed again for this report. The pulls and diagnostic written on 12 Oct 2026 are registered in the case manifest.

session_inputs/2026-10-12/0034_input_yt-transcript_waas-affiliate-marketing-training-2023-09-05.txt
  0a5ea7cfb6f28ef39298d87b45db4382f2e7a8f5a426e67089ae963211998003
session_inputs/2026-10-12/0034_input_screenshot-yt-btcc-training-by-shavez-2023-09-05.png
  a4f4f169131f4b35e1d0410d810406b923f97760351b93693f86583b119b3575
session_inputs/2026-10-12/0034_input_screenshot-explorer-blocks-head_2026-10-12-0030Z.png
  6bd83e84a072b443a6f4e31860e0f552d7cd9fdcd8a7c9447a5ce7fd588ed615
session_inputs/2026-10-12/0040_RIFT_btcc-shavez-claims-vs-chain.md
  78b412f69da490d42d63a357036473dafb38e1d81f1b84b5dcae5da64092c9aa
session_inputs/2026-10-11/2355_RIFT_btcc-chain-mining-findings.md
  1281132c708916af6553a8f553bb7312558b3e6ca98ec351f4160848aa88002f
session_inputs/2026-10-11/2357_RIFT_btcc-mining-questions-for-readers.md
  1e40b9996ebae46d16e7ef0fd5b798e925bffc5d8c072b3340c73a578fc88519
session_inputs/2026-10-12/0006_RIFT_btcc-issuance-test.md
  73b1f223b21a6ad53edf5f583197f9435b2343939f39a91580f0aa28460efafe
session_inputs/2026-10-12/0015_RIFT_btcc-pool-funding-and-control.md
  b62351cf08273edc4a407e491b801db0cdc1bf1357bcdcc7e4a491614be33bc8
session_inputs/2026-10-12/0024_RIFT_btcc-explorer-head-frozen-and-corrections.md
  a0f54dc8c2d98de440d48848135ec76bb603745ed61c8c23b1170f6f0165caf8
session_inputs/2026-10-12/0047_RIFT_btcc-rpc-certificate-expiry.md
  a8ff4a307003058afa85eba53b7aeda7b941f956ffbc99ba1657f0495e74c592
session_inputs/2026-10-12/0050_RIFT_btcc-rpc-certificate-exhibit.md
  1106dae73311cb52e3086c741f764ee119735af8dfab52e120f50ecb12d706b0
session_inputs/2026-10-12/0055_input_companies-house-OC458239-llin01-2025-09-24.pdf
  d250ea31acbb1f1f8cec31d68a40cfc6aeb8b0e474cda34b9823c5d0de9dea91
session_inputs/2026-10-12/0048_input_rpc-cert_leaf-decoded.txt
  db1ef01a52f64483344d68c159b98d216b91a6cb6a80647d5bc981907b69eb27
session_inputs/2026-10-12/0048_input_crtsh_rpc-bitcoincode-technology.json
  0e68dec59f3455c90e3ccfd53628015644e48a335ae5492a2e724e305378186a
session_inputs/2026-10-12/0048_input_crtsh_all-bitcoincode-technology.json
  86f942609cd6f9ad6fdc6d827d7e3ed7e5c381ba59beec0f7e91cf39ea819718
session_inputs/2026-10-12/0028_input_rpc-bitcoincode-head-test.txt
  33ca2a074dcf7a0b4628b34e6c503b45ff2265baff22b839d59f93d4c0956aa3
session_inputs/2026-10-12/0009_RIFT_btcc-ethgetbalance-34cCC8-43736.json
  51801a5f8031bab613345c39914446dfa22c86d2ca1071b058fd248b15c1726d
session_inputs/2026-10-12/0029_RIFT_btcc-balance-8e3c84.json
  4bc13d07708db470a43ebff1cef041c8e69e27f8c053e45e4a502856cc5b9040
session_inputs/2026-10-12/0029_RIFT_btcc-stats-coinsupply.json
  a5b2e8f417c7a840733bdd8ccb94243d35d630d1133eb8cb98a1891ac9bcabc3
session_inputs/2026-10-12/0029_RIFT_btcc-stats-ethsupply.json
  0d41bbeaf2c80497ce62354fa3f3aa6af0c65a0977565512f54fd6eff55453eb
session_inputs/2026-10-12/0033_RIFT_btcc-eth_block_number-1.json
  59b2f2b94be3a2aafd25cf8b55ae5bbcfa9d1ccfa1cc8cf7c83d9792221b0c9a
session_inputs/2026-10-12/0033_RIFT_btcc-eth_block_number-2.json
  59b2f2b94be3a2aafd25cf8b55ae5bbcfa9d1ccfa1cc8cf7c83d9792221b0c9a
session_inputs/2026-10-12/0033_RIFT_btcc-page-block-30834158-ts.html
  e1b6fd533e31ca75f0acf4eae87f9af59de613e1652b25b69bf3e4218104313a
session_inputs/2026-10-12/0033_RIFT_btcc-page-block-30834157-ts.html
  eef9c40db8d8a476c2eeb410156335a45e44e641eabe882bf213c7e8c1dbae2b
session_inputs/2026-10-12/0029_RIFT_btcc-txinfo-create-8e3c84.json
  e1eb4254eaede47d269fb92455a992b8dbc050c552aec1b07e7c1af18d658085
session_inputs/2026-10-12/0028_RIFT_btcc-txinfo-create-e99aD6.json
  5dab87765aa5ab4fd19b3526058bdbb14dfd671601f7f84bc9ef71b60965738b
session_inputs/2026-10-12/0028_RIFT_btcc-txinfo-create-53b71E.json
  52ccb0a683c80f0ec3d3d349a5cb2e7af961a85dcabce59a309563e0aa1bfba5
session_inputs/2026-10-12/0029_RIFT_btcc-src-700f05-StakingV1.json
  2b4442956efc2d00200c292256851a2f5635be4b3fa7818dc54f245c5430212b
session_inputs/2026-10-12/0029_RIFT_btcc-src-3558e7-StakingV1.json
  be4511bf8fc5b7bebbabe7a4bdde0bd602250ef641cf1404967021767e9b298d
session_inputs/2026-10-12/0028_RIFT_btcc-src-428638-zeon-gt1x.json
  dce3471f7ef651ad7fb3988c0e587f55ddc88cc1600b8c698455f6bb2620b87a
session_inputs/2026-10-12/0029_RIFT_btcc-txlist-34cCC8-asc-p1-o1000.json
  81454e9067850ae9ec5f8148a662cffb2aa588d183de2f8d003c9e3da958703e
session_inputs/2026-10-12/0032_RIFT_btcc-txlist-34cCC8-asc-p2-o1000.json
  94759125fe0705d0a1dcde07d1780374b6505bc0bdf48f390e16312ba9df2fdb
session_inputs/2026-10-12/0032_RIFT_btcc-txlist-34cCC8-asc-p3-o1000.json
  c056ebc7dbfaf157f1e2a05d4740a58626ecb418bf898aaaf08903d9e39981f1
session_inputs/2026-10-12/0032_RIFT_btcc-txlist-34cCC8-asc-p4-o1000.json
  53fe1a352aca337263a3197e2de30d7089474d9f699368ab8dc47e89707c4be2
session_inputs/2026-10-12/0032_RIFT_btcc-txlist-34cCC8-asc-p5-o1000.json
  730ed3b323bcd93d66af0dcf163bca5846d878d93f8e67545b9194d749876ac6
session_inputs/2026-10-12/0032_RIFT_btcc-txlist-34cCC8-asc-p6-o1000.json
  c9877777f6d3d8201ed0303935fa61359d54db9bfe30f154c75c47fd7c571395
session_inputs/2026-10-12/0032_RIFT_btcc-txlist-34cCC8-asc-p7-o1000.json
  eae4f999d7f86aac1827e9ad494f765c31a8359bdf4e3bad42f21d52e4b9665f
session_inputs/2026-10-12/0032_RIFT_btcc-txlist-34cCC8-asc-p8-o1000.json
  cde056f0cc803c565f848493a37ec068e20c65e30bfbf2c653d4a9d3a7a2c2ce
session_inputs/2026-10-12/0032_RIFT_btcc-txinfo-0xffc2a7a0.json
  b62f3730cbfbaa241c817c8ee0a42903a4cffa5da258868b82821b1f1f043459
session_inputs/2026-10-12/0032_RIFT_btcc-txinfo-0x0278d07a.json
  8af1abf353d694a8e9de3167bcde17601304fc76e6b928e4822e05c28cfc3333
session_inputs/2026-10-12/0032_RIFT_btcc-tokentx-8b74dc-428638.json
  d66db96c14efafa4601d6d764ad867377f56ceb2cde4ef088c90b135381dafa7
session_inputs/2026-10-12/1221_input_yt-transcript_harvest-party-2024-09-16.txt
  4cfed7914a56c30e04456424765b016165b4af80b632bc5aad098e26c7845d0d
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_01.png
  3e05c2dc4ddb0ae284571304c6b2b78b7f2b13b0f18c38c8f5785920d5f33a73
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_02.png
  15303b29f1f9f26a10001dd9656905b548d7c78eaeea6585b44fa1be8ea84dd9
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_03.png
  f90e47da4e43a88f1306ea6873b66639259e2951276ac485f065af78912d2ce1
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_04.png
  73467db7491ddc620f2cca327074c12076a1c2c371e47d020a8d8a03dcacb974
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_05.png
  b3e58c1d366a07b218a14fc98022cf1e66a74a2a04722369e73ee85a42d0ef8d
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_06.png
  5c85b04a4c79562f378d10507c9a4c0a3fab040eae94c0be7689856cada205c5
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_07.png
  913f425a60146ea3242c6437664cf5d91fe7f9279133887daf18d91e7f1dc296
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_08.png
  118ad2dfb6b283d7471fbad915d42172d4df3c4f8cec6962ab0b2b16f3ca447d
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_09.png
  c738f9b94bfaf5cfb659cc29758322df6521b4a218ab4ae79fbb8d5d11a26c03
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_10.png
  02e5f61d011879b17d50ce17efc3639f850be032e288549571f34705967118a3
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_11.png
  f6f5726014bd2b1818a065bb328fd2e2b065599fae3d3731796d41945bbe3e2b
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_12.png
  cce5d2fcfa7ed2824bd4a8b661f0f0e321ca1b721c1d628d63eded37e94fa845
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_13.png
  117f2eedc05e3b3f04e2422fcab28a7cd3ee653555c5b67eb4dcca966cb8dee7
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_14.png
  c90cec3202748be1b931440e46fa4cf710f557d21ec6f74309f85dbd9cbdc112
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_15.png
  77203937dfa7ba30e94745935891c1944b6282c701ebaf7c9e35fb0cf06ecca8
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_16.png
  e8b58691f78370a5576c9632897f3c889b7d7eea6e9d24e3c0bbf2fb30cec6b4
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_17.png
  030be3983c789d45b3a794ea00461025cf04d4fa0347eff4a9fc2bfc26c80e44
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_18.png
  c5e6484b4ae213deed75973bb5c8be1d53f39aa64acb2eb96e65e0f02a7407a2
session_inputs/2026-10-12/1221_input_screenshot-yt-harvest-party-2024-09-16_19.png
  f777ea42133f631677e7bbdac96f05e319baa213b06444ed57a30db7ab714ef8
session_inputs/2026-10-12/1233_input_yt-transcript_meeting-close-out-2023-09-22.txt
  906055413e791faf2424fbee37b85cd9459ccfbd4c7f2c124a5d4230aecb3db8
session_inputs/2026-10-12/1233_input_yt-transcript_ceo-shavez-session-2024-02-14.txt
  7041cdefe3b20466931986581291b4e4e986aef08c1e72ea3b0c0581b20ffcc2
session_inputs/2026-10-12/1233_input_screenshot-yt-meeting-close-out-2023-09-22_01.png
  8cc24fefe131c566cd8d4629fbbdaa40336df4c4463498151a0f5490d70bfc01
session_inputs/2026-10-12/1233_input_screenshot-yt-meeting-close-out-2023-09-22_02.png
  ab49e1c1087f558a8131d4aa6a3054f3789c55683c0e868b3d63a2f37ff84ecb
session_inputs/2026-10-12/1233_input_screenshot-yt-waas-funding-2023-09-14.png
  33f48a51da16b8ef873a8c096be3f087b1da1bc63f2f7e67274bb9e519ac48f9
session_inputs/2026-10-12/0032_RIFT_btcc-txlist-34cCC8-asc-p8-o1000.json
  cde056f0cc803c565f848493a37ec068e20c65e30bfbf2c653d4a9d3a7a2c2ce
session_inputs/2026-10-12/1200_RIFT_btcc-usdt-mint-txinfo.mjs
  46e635f61d4f3ce398abb2af089d141e8a5fb91e5217d79c15ea6ea8d29e0f6f
session_inputs/2026-10-12/1135_RIFT_t7-btcc-pull.mjs
  1b37ec218e2f40d9f1215a3f2ce1192088a0f425bb47da5d7ffefff034d3e8bb
session_inputs/2026-10-12/1125_RIFT_t7-internal-paging-diag.mjs
  95996d6ca6826bd79d0273317392454cfb6be2ab74704220ce75ac0ec142091e
session_inputs/2026-10-12/0029_RIFT_btcc-listaccounts-p1.json
  45098bc581441255832813c90697fdf2295269879059a652102b5698220efdfd
session_inputs/2026-10-12/0029_RIFT_btcc-page-block-0.html
  bab5a13dfa7a1895dc1b892afe9abadc0d4af1a129779a92c9aca596c4b14ea6
session_inputs/2026-10-12/0029_RIFT_btcc-page-block-1.html
  3a6439d5e12471d3da3568db584b229118d96fd9ed92cb943328b5e4e2fa0612
session_inputs/2026-10-12/0029_RIFT_btcc-page-block-2.html
  9fe4017859cb6412bcd1068cc66a6684f804d5cfc20f3d2d0e61ab3e77aa6e7c
session_inputs/2026-10-12/0029_RIFT_btcc-page-block-43742.html
  64b5482e7126c16ce062b9152f11e3ee635ca25d24b287e1f7fb9c075e9eee1e
session_inputs/2026-10-12/0029_RIFT_btcc-page-block-43743.html
  b167fc874c56ee16d81aac624bd81bbae901b83a06e83de502dd152175c8d8ca
session_inputs/2026-10-12/0029_RIFT_btcc-page-block-3052335.html
  73d0d72329ffb913b4b91f633944ae988e21c55e7bdd14d065017a44ad87a077
session_inputs/2026-10-12/0029_RIFT_btcc-page-block-3052336.html
  8bc00e248d9c9ee113d0936d8c0a3b1dcfa3107a97c290e4673474aa6f4756c3
session_inputs/2026-10-12/0029_RIFT_btcc-page-block-30800000.html
  0cc969a6df7f2113fc865974aae7b2cae9bb0763d08cf2c887fcd5057cb1c26f
session_inputs/2026-10-12/0029_RIFT_btcc-page-block-30800001.html
  b83dba3d9b1840a56bd7ba2df14245e0b57d2321fcc01ac430b71c8805ba39a2
session_inputs/2026-10-12/0029_RIFT_btcc-page-block-30800002.html
  72da6e51db9f81163d2741625a480e0fc965ba86a1c8597432110a4fe6bfd681
session_inputs/2026-10-12/0029_RIFT_btcc-page-block-30800003.html
  daf500388d892fec2b82d752974a051a299767ba25ef6a1cd4d892d1198e3d79
session_inputs/2026-10-12/0029_RIFT_btcc-page-block-30800004.html
  c09f7ddb2f951fa1a50eae90d1504ac1285134e224143c68363d6afaf6f440a7
onchain-rpc/out/address-btcc-c6afd23a-20261011T221241Z.json
  258cc145b950d702c4cf15bb506f926c01e3ad1cda721bc6ab8294858d471ff7
onchain-rpc/out/address-btcc-06ace60b-20261011T221304Z.json
  8288d6d548decfcf68c1401ed962fc15ee22478ac44e5dbce071e15aae491dce
onchain-rpc/out/address-btcc-8e3c8431-20261012T012214Z.json.rows.partial
  9bf587ed855647b6ed59cd6aeb6ea8478dc1ae708e57fc27c0f79874e7279537
onchain-rpc/out/address-btcc-8e3c8431-20261012T103221Z.json.rows.partial
  b8871c769d3315a284f4fe4c4607d9f2df5221ffc85a14697ad982f7e08a75d3
onchain-rpc/out/paging-diag-internal-btcc-20261012T102613Z.json
  69f08344797196f6fe7841ac59ee3602aeda7678af6a89bcebb9f37d56342acd
onchain-rpc/out/probe-btcc-20261011T210224Z.json
  c7087bdc6f989c84300f7484be05a678fe05da47e437209725e82a38ecea20a6
onchain-rpc/out/paging-diag-btcc-20261011T220338Z.json
  be9b5d4b7e0a8c5bc3deaa7c56432d694a7a171202656c7358f0c63cd1c6b399
onchain-rpc/out/address-btcc-556da75f-20261011T222233Z.json
  506a46c9a3fe4ce8e163b6b96a050898568a725b408927880bd8315813e87af6
onchain-rpc/out/btcc-usdt-mint-txinfo-20261012T105758Z.json
  c2087327ed0df4ee62fd7deeaaeb60f2355ac32a7868c23d4aafb4c6f93f0654
session_inputs/2026-10-11/2250_RIFT_556da7-bridgeToken-decode.py
  a34a62e91d05a1f67d5b34a5a9e9cb73d5031c78e7270ceec022efff3efe6173
RC_CANON/inbox/HYPERFUND/BURNLIST_btcc-556da7-bridgeToken_2026-10-11_2250Z.csv
  732ce2ffd683aa2ee05b6ad4edb1b10132f9b3ff07eea5b7de40e842d3950e01
RC_CANON/handovers/SESSION_HANDOVER_RIFT_2026-10-11_2235Z.md
  381b2b54b3b34c477570c1b9d2a9f1b30ac20bb7b7357acfdff2f03c52051a3a
RC_CANON/handovers/SESSION_HANDOVER_RIFT_2026-10-11_2320Z.md
  c2d83d96cd9d5f17587113f9db17946fcfcd4e8ea199dd589044048019e104d4
RC_CANON/handovers/SESSION_HANDOVER_RIFT_2026-10-12_0105Z.md
  1f1a285f1daa3b8895fea04a9cbe8fa71044435f46db8a3e93b4d10ce3ed76f5

Source of every on-chain record: scan.bitcoincode.technology, the operator’s own explorer, read between 11 and 12 Oct 2026. Its state is as at its last block, 24 Sep 2026 06:21:32Z.