Section · AVAT — Nasdaq: AVAT · CIK 0002092446
Avalanche Treasury Corp.
The treasury that borrowed. It holds roughly 3.5% of all circulating AVAX, has drawn $33M against it, and disclosed a going-concern note in its first 10-Q — withdrawn in its second. Its paper trail stops one inch short of the chain. Its twin, AVAX One, is covered separately.
02 — The Fleet
A pattern is not a fingerprint
AVAT’s filings describe its staking in detail: private validator nodes, run by named operators, on contractual terms of 14 to 365 days. That is a description an outsider can search for on-chain. I searched, and found a set of validators that fits it closely. The fit means less than it looks, for a reason the ladder’s own history supplies.
Each bar is one validator that was active on 7 August 2026, the date of the scan, with a six-figure stake and a 100% delegation fee, which leaves nothing for outside delegators. It runs from the validator’s start date to its end date, and bar thickness is stake size. Sorted by start date, 16 of them, highlighted, resolve into a series of steps: one new node every day, each for the same term of about 16 days. Regularity of that kind is what a scheduled staking program produces. How many of the 70 are still validating has not been re-checked since that scan.
Sixteen of seventy validators start one a day for the same 16-day term, while the other 54 show no such rhythm
One bar per validator, from its start to its end date, in four groups: the 16-node daily ladder (teal), the winter stakes clipped at the left edge, the short-term crowd whose starts bunch and skip days, and the long bets. Bar thickness is stake (linear; the largest is 2.5M AVAX) on a hairline that marks every term; clipped bars wear arrowheads. Dashed line is the Aug 7 scan. Hover or tap any row for that validator’s NodeID, dates and uptime, with a link to the official explorer; rows sharing its reward owner light up.
Hover or tap any row for that validator’s NodeID, stake, dates and uptime, with a link to it on the official explorer; validators sharing its reward owner light up in teal. Click to pin. All 70 rows are real validators from the Aug 7 2026 scan.
Source: Avalanche P-Chain, platform.getCurrentValidators, scanned 2026-08-07: 70 validators with a 100% delegation fee and a six-figure stake, 42.0M AVAX, 48 distinct reward-owner addresses.
The same sixteen validators as a staircase: one step per day, each block as tall as its stake
Isometric view of the 16-node daily ladder from the timeline above. Each step is one day later; block height is AVAX staked.
Hover or tap a block for its NodeID, stake, dates and uptime, with a link to the validator on the official explorer. Click to pin. Every block is a real validator from the 2026-08-07 scan; each one pays to the same reward address.
Source: Avalanche P-Chain, platform.getCurrentValidators, scanned 2026-08-07: the 16 ladder validators, from the same 70-validator scan as the timeline above.
The trace
Every validator in the marked ladder pays to one reward address. I followed it. Its P-Chain history runs to 600 transactions: 329 stakes, 271 exports and 0 imports. It never brings new capital in. Matured stake is re-staked directly, and only the yield is skimmed off to a single C-Chain address.
| Reward owner (P-Chain) | P-avax13rs52le7yllu3fcgpgvn75elpzqvk79g269frk |
| Yield skim endpoint (C-Chain) | 0x3bddcc3c88170a931dfa07e9660bbe02741ef635 |
| Skim address state | nonce 0 · balance 0 · no code · 0 EVM transactions |
| Ladder cadence | 1 new node/day · term of about 16 days · 100% fee · 0 delegators |
The skim address is a dedicated collection point with no other activity. Everything about it says institutional staking operation. The temptation to name it is strong: 8 million AVAX, laddered on the cadence a treasury would use, matching the behaviour the S-1 describes. Writing “this is AVAT” would be easy.
Before attributing anything, I paged the ladder’s history back to its first transaction. It has been staking since April 2024. That is sixteen months before AVAT came into existence, and over two years before it listed. The pattern cannot be the company, because the pattern is older than the company.
The ladder's reward address was staking sixteen months before AVAT existed, and over two years before it listed
One bar from the address's first stake (24 Apr 2024) to the 7 Aug 2026 scan, still running; markers below the axis show AVAT's inception (20 Aug 2025) and its Nasdaq listing (11 Jun 2026).
Source: Avalanche P-Chain: the full transaction history of the ladder's reward-owner address, paged back to its first stake; AVAT inception and listing dates as used across the AVAT tabs.
The profile of private nodes, a 100% fee and laddered terms is what institutional staking looks like in general. It is not unique to any one company. Matching it on-chain narrows nothing. It is the on-chain equivalent of trusting a hand-typed wallet label.
What survives
The refutation is the result. It teaches the same lesson the filings do: a public blockchain records addresses; it does not record owners. You can map every validator and trace every flow and still fail to reach a legal entity. The mapping from address to owner is private, and these companies keep it that way by design.
The next tab turns to what is established: the operators AVAT names itself, in filings it signed.
Since the scan · 28 Aug 2026
Two validators that did not exist when this page’s 70 were scanned started on 28 Aug, funded by 4,000,000 AVAX exported from the second Anchorage-custodied wallet of The Wallets. One of them wears this page’s ladder uniform exactly, a 100% fee on a 15-day term, under a different reward address. Per the blockquote above, that matches a pattern, not an owner. The difference this time is that the funding is traced, transaction by transaction, back to the wallets the filed quantities pinned.
Since the scan · 9 Sep 2026
The same wallet funded two more. At 16:17 and 16:18 UTC on 9 September it exported 1,134,000 AVAX twice, to two P-Chain keys with no prior history. Both imported at 16:20 and staked 1,133,999 AVAX each within eight minutes: P-avax1xnywps55r3tsssxklsj6039l9e67t3h2qxedps on NodeID-…Ej4R8ukp until 24 September, and P-avax1qjukw4p93pyygk0zdgw2zqsyspatw829d5gtqn on NodeID-…itWckyPD until 29 September. Neither key was in the 7 August scan. Both exports are traced; who operates the nodes is not filed anywhere.
Since the scan · 13 Sep 2026
The second of the 28 August pair reached the end of its term on 13 September. Its owner key P-avax1pgjtvez2rr7yf9yejs6pkr7kpu4xnw76uynl9n read 2,004,596 AVAX unlocked and zero staked that evening, the returned stake plus its reward, with nothing done with it at the read. The first of the pair still had 1,999,999 AVAX staked until 21 September. Four positions funded by that wallet across the record, three of them staked at the 13 September read. That count covers those four positions only. It says nothing about the 70 scanned above, whose present state has not been re-checked.
Since the scan · 16 Sep 2026
A block walk enumerated the staking the company’s other named custodian runs for it, and it looks nothing like this page’s ladder. Nine single-key P-Chain vaults, each staking its whole balance on its own node at a 100% fee, each ending at an exact month end and exporting to the C-Chain minutes after midnight, on a monthly clock rather than a 16-day one. Their stakes come to 8,284,248 AVAX against the 8,329,871 the Q2 10-Q puts at Coinbase Custody at 31 December 2025, and six of them to 4,458,518 against the 4,510,207 filed at 30 June. The uniform is the custodian’s, and the filed sums are what name the customer; the full account is on Custody. Four of the nine vault keys are already rows in the 70-validator scan: NodeID-DVh35F3R with 2,500,060 AVAX, NodeID-8QDaNCzY with 1,158,985, NodeID-DQdJGdg9 with 166,676 and NodeID-CS2Rnk3P with 149,493, all four staked on 2 and 3 July to 25 September. The scan counted them by fingerprint and named nobody, and that stands: what the Custody chapter adds is the custodian the four belong to, not a customer for the other 66. Two nodes are shared between that batch and the keys traced here, which is corroboration and not a tie of its own, because a node identifies the provider rather than the customer. That is this page’s own lesson applied to a second set of validators.