wurrly

Treasury companyProven

AVAX One (AVX)

42 registry addresses

Observed portfolio value

Reading balances

No successful balance read yet.

Seven BitGo-template vaults operated by one signer since November 2025, single-use pass-throughs that export straight to the P-Chain, ten validator owner keys, and the tAVAX wallet the filed 829,989 gave away. The full account is on the research pages.

Holdings

AVAX and the listed tokens, across the addresses in scopeThe price read has not finished. The quantities below are measured; USD values follow.24 h value change unavailable. No read returns a second valued endpoint 24 hours earlier.

Reading balances

Requested: Registered AVAX and liquid-staking balances. Returned coverage unavailable. Chains requested: C, P. 42 eligible addresses; none read yet.

Source: Avalanche C-Chain RPC, Wurrly Intel registry. No successful read yet.

Read method

Every figure is summed in exact decimal over one asset key at a time. A chain figure adds the priced holdings measured on that chain; an asset the price read could not answer for is left out of the sum, and the cell says how many were left out. A share is that chain figure over the summed priced holdings in the selected scope, divided at 60 decimal places and shown at two.

The P-Chain balance is one measurement for the whole owner group, so an address row on that chain shows the group note instead of a figure of its own. C-Chain AVAX and P-Chain AVAX are separate asset keys and are never added into one line.

No route this card reads returns a valued endpoint twenty-four hours back over the same addresses and assets, so the 24 h change is unavailable in every row. The price route’s own daily move is the AVAX market, which is a different measurement.

Balance history

History range
Display unit
Requested dates follow the read's own successful timestamp.Daily balance, rebuilt from returned transactions and anchored to the live balance

Reading balance history

Requested: C-Chain AVAX only, daily. Returned coverage unavailable. Chains requested: C. 42 eligible addresses; none read yet.

Source: Routescan, Wurrly Intel registry. No successful read yet.

Transaction count unavailable. Anchor time unavailable.

Current positions. Read time unavailable. Staking positions unavailable for this read.

Reading current staking positions

Read method

The series is rebuilt from the transactions the feeds return and then shifted so its last figure equals the live balance the node reported. The shift is the anchor adjustment, and the reach of the feeds behind it is stated above. Nothing is drawn before that shift is proved.

A day's figure is that UTC day's close: the balance after every movement dated that day.

Historical USD is each slot day's own final recorded close for AVAX, from Coinbase Exchange, joined on the UTC day. A day that has not finished has no close, and no other day's price stands in for it. The C-Chain and P-Chain AVAX are the same asset in that market, so both join the one AVAX close. Price join revision 2026-09-14.

Quantity coverage start unavailable.

Flows

Transfers summed by counterparty over the selected window
Flow window

Reading transfer history

Requested: External AVAX transfers of at least 1 AVAX, summed by counterparty. Returned coverage unavailable. Minimum transfer: 1 AVAX. Chains requested: C, P. 42 eligible addresses; none read yet.

Source: Routescan, Wurrly Intel registry. No successful read yet.

Read method

A trailing window is the interval from the read’s own time minus 30 periods of 24 hours up to that time. The start instant is excluded and the end instant is included, so two adjacent windows never both count the moment they share. Every figure in a trailing window is summed from the dated transfer rows the read returned, one row at a time, in exact decimal.

The returned history is the source’s own aggregate, summed over every row it read rather than over the rows it sent. It is never filtered by its first and last date to make a trailing total: a window that the returned rows cannot reach is reported as unavailable instead.

Inflow is AVAX this subject received and outflow is AVAX it sent. A movement with this subject on both sides is internal and is counted but never summed into an external total; a row with this subject on neither side is unmatched and is counted the same way. A row the feeds dated unreadably belongs to no trailing window, and the count of those is stated above.

Every amount on this card arrived from the source as a JavaScript number, so the sums are exact over the figures received and the received figures are not exact to the last digit of the chain. Each row’s Details says so beside the figure it applies to.

Transfers

Returned transfers, newest firstMinimum transfer: 1 AVAX

Reading transfer history

Requested: Returned AVAX transfers of at least 1 AVAX, newest first, including movements between the subject's own addresses. Returned coverage unavailable. Minimum transfer: 1 AVAX. Chains requested: C, P. 42 eligible addresses; none read yet.

Source: Routescan, Wurrly Intel registry. No successful read yet.

Read method

These are the transfers the flow read returned, newest first. The same request answers the card above: one read of the source, two measurements of it. Every row is at least 1 AVAX, because the source drops everything below that before it answers, and there are no token rows in it, so no token quantity is ever compared against the numeric 1 of another asset’s unit. A different threshold would need a source that reads to a different depth, which is not a setting on this page.

TRANSFERS shows every returned row, including movements between this subject’s own addresses, each marked Internal. A subject’s own P-Chain key counts as its own in both spellings, so a wallet moving value between its C-Chain and P-Chain sides is Internal rather than a pair of external flows to itself. INFLOW and OUTFLOW are external directions relative to this subject and exclude those rows, and they exclude rows with this subject on neither side and rows whose other endpoint is a chain rather than an address, which have no direction to sort into. CROSS-CHAIN holds the movements between two Avalanche chains: two endpoint chains that differ, or the atomic feed, which returns nothing else.

No pair identifier reaches this page, so a cross-chain export and its matching import are two rows with two amounts and two links. Nothing on this card adds them into one movement, and no figure here counts a pair once.

A historical USD value is that row’s own UTC day’s final closing price multiplied by its exact quantity. A day that has not finished has no close and says so; a day the price read did not return says so separately. Today’s price is never substituted for either.

Pages are windows on the frozen read named in the footer. A newer read landing while you are reading does not replace these rows; it offers itself at the top of the card, and adopting it returns to page 1.

Visualizer

Registry addresses as boxes, and the transfers the read observed between themRegistry addresses are grouped by role. Arrows show transfers returned by the selected read.A counterparty is the address or organisation on the other side of a transfer.

AVAX One (AVX). Reading transfers

Visualizer view

AVAX One (AVX): registry addresses by role, and the transfers this read observed between them25 boxes and no arrows. Transfer coverage is being read.Custody7 addressestreasury, vaults, signersWorking8 addresses shown of 20 addressesstaging, pass-throughs, forwardersStaking8 addresses shown of 13 addressesvalidator owners, P-Chain keys, protoco…Exits2 addressesdeposit addresses, exchanges, sinksAVX BitGo-template mult…vault · C-Chain · Proven0xf261…5ed4AVX BitGo-template mult…vault · C-Chain · Proven0x113f…fdddAVX BitGo-template mult…vault · C-Chain · Proven0xfbbb…906eAVX BitGo-template mult…vault · C-Chain · Proven0xfd2e…4db4AVX BitGo-template mult…vault · C-Chain · Proven0xbed8…84d9AVX BitGo-template mult…vault · C-Chain · Proven0xed9b…db77AVX vault signer / oper…vault · C-Chain · Proven0x786a…c174AVX tAVAX walletlst · C-Chain · Proven0x2470…f853AVX pass-throughpass-through · C-Chain · Pr…0x9758…17c7AVX pass-throughpass-through · C-Chain · Pr…0x9402…d3eeAVX pass-throughpass-through · C-Chain · Pr…0xa436…cdb4AVX pass-throughpass-through · C-Chain · Pr…0x5f0f…528cAVX pass-throughpass-through · C-Chain · Pr…0x4098…43f4AVX pass-throughpass-through · C-Chain · Pr…0x27d3…cb5cAVX pass-throughpass-through · C-Chain · Pr…0xa908…45e3AVX validator ownervalidator-owner · P-Chain ·…P-avax1jx93…ua3jfzAVX validator ownervalidator-owner · P-Chain ·…P-avax15wf0…4vjcszAVX validator ownervalidator-owner · P-Chain ·…P-avax1p25v…8f298xAVX validator owner (on…validator-owner · P-Chain ·…P-avax1y9lc…gd5dsxAVX validator owner (on…validator-owner · P-Chain ·…P-avax10ms8…cyv04nAVX validator owner (on…validator-owner · P-Chain ·…P-avax1qu2e…79m54zAVX validator owner (on…validator-owner · P-Chain ·…P-avax1n48v…jf3errAVX validator ownervalidator-owner · P-Chain ·…P-avax1manf…uu7xxxAVX BitGo-template mult…exchange · C-Chain · Proven0xd50b…02b0AVX pass-throughexchange · C-Chain · Proven0x5f18…b594

Select an address to read its identity and observed transfers.

Registry addresses in scope, with each one's role. 42 of 42 addresses read.

Wurrly Intel registry: compiled with this page.

Reading transfers. Transfer coverage is being read.

No transfer read has answered for this scope.

Read method

The boxes are the registry’s own rows, placed by the role the research gave each one: custody first, the working wallets next, the staking and protocol keys, then the exits. Whoever was on the other side of a returned transfer joins an outer column, on the right when this subject paid them and on the left when they only paid in. Grouping is not attribution: a box is named only where the registry names it.

Arrows are the transfers this read returned, summed by pair, asset, chain and kind. Two assets between one pair of boxes are two arrows, never one; a token quantity is never added to an AVAX total and never takes the AVAX reporting threshold. Reverse directions stay apart. A sum is labelled At least only where the source states the depth it reports to and says its coverage was partial; otherwise it is labelled Observed, which is still scoped to this request.

An endpoint the feed left as a chain rather than an address is not a counterparty, so no arrow is drawn to it and the count of transfers that were excluded for that reason is stated in the scope line above.

A column of more than 8 addresses folds its tail behind one control. Folding changes the drawing and nothing else: Connections still lists every canonical relationship, and any movement whose two ends fold into one box is kept as that group’s own internal subtotal, so the arrows plus the subtotals still add up to the same per-asset totals.

Proven: a filed quantity matched to the unit, or a transaction identified by its hash. Inferred: behaviour or timing, with the base rate stated in the source. Candidate: a lead, one tier below inferred, with a written test for promoting it and a written test for killing it. Explorer tag: an explorer's attribution label. Standing describes the cited claim. A transfer alone does not establish ownership.

Minimum transfer: 1 AVAX.

Evidence

Registry claims, address by address, with each claim's standing42 registry addresses.

Proven: a filed quantity matched to the unit, or a transaction identified by its hash. Inferred: behaviour or timing, with the base rate stated in the source. Candidate: a lead, one tier below inferred, with a written test for promoting it and a written test for killing it. Explorer tag: an explorer's attribution label. Unattributed: no ownership attribution is established in the registry. Standing describes the cited claim. A transfer alone does not establish ownership.

Evidence class: A flow tie, B co-signature or shared infrastructure, C filed-quantity match, D node or provider continuity, E adjacency.

Registry method states a review on 4 September 2026. No record states a review date of its own.

  3. AVX BitGo-template multisig (method Send…

    ProvenC-Chainvault

    0xf2614b91f6988c6f9914050da270814806ea5ed4

    Attribution
    Filed under AVAX One (AVX) as vault. Open entity
    Claim supported
    Multi Sig) parent vault - funded by a 7.22M atomic import from P-avax1r836g3a (12 Nov 2025); 7.24M out; operated by signer 0x786a7c97
    Evidence
    code hash = BitGo template; same signer; created 10 Nov-11 Dec 2025
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  4. AVX BitGo-template multisig (method Send…

    ProvenC-Chainexchange

    0xd50b1bf1ff33e3c296ffc5d0a22adcb02de402b0

    Attribution
    Filed under AVAX One (AVX) as exchange. Open entity
    Claim supported
    Multi Sig) vault - 2.52M out incl. the tAVAX funding; funded by the Prime hot wallet + Wintermute; operated by signer 0x786a7c97
    Evidence
    code hash = BitGo template; same signer; created 10 Nov-11 Dec 2025
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  5. AVX BitGo-template multisig (method Send…

    ProvenC-Chainvault

    0x113fa347a0d926ec5774e449c497a474bc89fddd

    Attribution
    Filed under AVAX One (AVX) as vault. Open entity
    Claim supported
    Multi Sig) vault - 1.52M out; operated by signer 0x786a7c97
    Evidence
    code hash = BitGo template; same signer; created 10 Nov-11 Dec 2025
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  6. AVX BitGo-template multisig (method Send…

    ProvenC-Chainvault

    0xfbbb39fec94db8ebd5e4383fbe72bd02ea73906e

    Attribution
    Filed under AVAX One (AVX) as vault. Open entity
    Claim supported
    Multi Sig) vault - 1.52M out; operated by signer 0x786a7c97
    Evidence
    code hash = BitGo template; same signer; created 10 Nov-11 Dec 2025
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  7. AVX BitGo-template multisig (method Send…

    ProvenC-Chainvault

    0xfd2e158c11955a8147d28862d07eae3c743d4db4

    Attribution
    Filed under AVAX One (AVX) as vault. Open entity
    Claim supported
    Multi Sig) vault - 1.51M out; operated by signer 0x786a7c97
    Evidence
    code hash = BitGo template; same signer; created 10 Nov-11 Dec 2025
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  8. AVX BitGo-template multisig (method Send…

    ProvenC-Chainvault

    0xbed8f8a09f60b005089fbd7ba7d155a1c1bf84d9

    Attribution
    Filed under AVAX One (AVX) as vault. Open entity
    Claim supported
    Multi Sig) vault - 332K out; operated by signer 0x786a7c97
    Evidence
    code hash = BitGo template; same signer; created 10 Nov-11 Dec 2025
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  9. AVX BitGo-template multisig (method Send…

    ProvenC-Chainvault

    0xed9b72b1598592d6082bc3727b956e35fe0adb77

    Attribution
    Filed under AVAX One (AVX) as vault. Open entity
    Claim supported
    Multi Sig) vault - 28K out; operated by signer 0x786a7c97
    Evidence
    code hash = BitGo template; same signer; created 10 Nov-11 Dec 2025
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  23. AVX pass-through

    ProvenC-Chainexchange

    0x5f185306bd6130d7a4a10617abea9aeb96cbb594

    Attribution
    Filed under AVAX One (AVX) as exchange. Open entity
    Claim supported
    sends to the Coinbase Prime hot wallet: 380,004 on 25 Nov 2025, then 657 / 21,277 / 1,477 / 3,974 / 76,762 (Apr-Aug 2026); ~484K total
    Evidence
    Snowscan txs; earlier sheet omitted the 380,004
    Source

    Open addressOpen in Snowscan (opens in a new tab)

  28. AVX validator owner

    ProvenP-Chainvalidator-owner

    P-avax1jx9365quuvrlgrreur6pgs7c3mpe0j8xua3jfz

    Attribution
    Filed under AVAX One (AVX) as validator-owner. Open entity
    Claim supported
    imported 3,571,126; NodeID-3PbwqCPFxE4SAty... 488,781 (2026-08-20 to 2026-09-14, fee 5.0000)
    Evidence
    Glacier history; rolling terms since 2026-05-01 | 16 Sep 2026: 528,083 AVAX, inside the 250,000-plus validator population the merge enumerated
    Source

    Open addressOpen in Avascan (opens in a new tab)

  29. AVX validator owner

    ProvenP-Chainvalidator-owner

    P-avax15wf0rwjujj8npppyxknn4vtrll9tu56p4vjcsz

    Attribution
    Filed under AVAX One (AVX) as validator-owner. Open entity
    Claim supported
    imported 2,033,978; NodeID-N4bXacP2FXEKEwH... 517,593 (2026-08-24 to 2026-09-14, fee 100.0000)
    Evidence
    Glacier history; rolling terms since 2025-11-24 | 16 Sep 2026: 519,110 AVAX, inside the 250,000-plus validator population the merge enumerated
    Source

    Open addressOpen in Avascan (opens in a new tab)

  30. AVX validator owner

    ProvenP-Chainvalidator-owner

    P-avax1p25v8qwsauzmsmg7yqvqm24eh4w6c5lq8f298x

    Attribution
    Filed under AVAX One (AVX) as validator-owner. Open entity
    Claim supported
    imported 2,000,001; NodeID-LiC9NDMWBoPmnwj... 500,000 (2026-03-20 to 2026-11-30, fee 100.0000)
    Evidence
    Glacier history; rolling terms since 2025-11-24
    Source

    Open addressOpen in Avascan (opens in a new tab)

  31. AVX validator owner (one key of a 2-of-3…

    ProvenP-Chainvalidator-owner

    P-avax1y9lc2dd0hqvp5cxsjmpdvk3w5608usn5gd5dsx

    Attribution
    Filed under AVAX One (AVX) as validator-owner. Open entity
    Claim supported
    BitGo multisig owner set) - imported 1,500,000; NodeID-6HTKn9FJ52yTaWG... 1,499,999 (2026-04-01 to 2026-11-30, fee 100.0000)
    Evidence
    Glacier history; rolling terms since 2025-11-25 | Avascan: reward owner is a 2-of-3 set incl. this address
    Source

    Open addressOpen in Avascan (opens in a new tab)

  32. AVX validator owner (one key of a 2-of-3…

    ProvenP-Chainvalidator-owner

    P-avax10ms8mu37qqw52a22d74r0gqq5zwt5k76cyv04n

    Attribution
    Filed under AVAX One (AVX) as validator-owner. Open entity
    Claim supported
    BitGo multisig owner set) - imported 1,500,000; NodeID-EFHu9didDPWweR3... 1,500,000 (2026-04-01 to 2026-12-31, fee 100.0000)
    Evidence
    Glacier history; rolling terms since 2025-11-25 | Avascan: reward owner is a 2-of-3 set incl. this address
    Source

    Open addressOpen in Avascan (opens in a new tab)

  33. AVX validator owner (one key of a 2-of-3…

    ProvenP-Chainvalidator-owner

    P-avax1qu2eq03hnztvxplvwdcj546pmz2v854x79m54z

    Attribution
    Filed under AVAX One (AVX) as validator-owner. Open entity
    Claim supported
    BitGo multisig owner set) - imported 1,500,000; NodeID-BSDn9cwxnNdJLjN... 1,549,921 (2026-08-14 to 2026-09-14, fee 100.0000)
    Evidence
    Glacier history; rolling terms since 2025-11-25 | Avascan: reward owner is a 2-of-3 set incl. this address
    Source

    Open addressOpen in Avascan (opens in a new tab)

  34. AVX validator owner (one key of a 2-of-3…

    ProvenP-Chainvalidator-owner

    P-avax1n48v60nyp44l9tc0xfxywwjc37822ep7jf3err

    Attribution
    Filed under AVAX One (AVX) as validator-owner. Open entity
    Claim supported
    BitGo multisig owner set) - imported 1,220,217; NodeID-9cFYF35nTK7Jv58... 1,249,557 (2026-09-01 to 2026-09-15, fee 100.0000)
    Evidence
    Glacier history; rolling terms since 2025-11-25 | Avascan: reward owner is a 2-of-3 set incl. this address
    Source

    Open addressOpen in Avascan (opens in a new tab)

  35. AVX validator owner

    ProvenP-Chainvalidator-owner

    P-avax1manfsr5fv49mn97m4dnyehywedm68agquu7xxx

    Attribution
    Filed under AVAX One (AVX) as validator-owner. Open entity
    Claim supported
    imported 1,000,001; NodeID-Mn5SoSEvAjc2Dpi... 500,000 (2026-04-30 to 2027-01-28, fee 100.0000)
    Evidence
    Glacier history; rolling terms since 2025-11-24
    Source

    Open addressOpen in Avascan (opens in a new tab)

  36. AVX validator owner

    ProvenP-Chainvalidator-owner

    P-avax13l9l8jku3uvh6dkutgk0206a72qky0jvr7xf69

    Attribution
    Filed under AVAX One (AVX) as validator-owner. Open entity
    Claim supported
    imported 633,949; NodeID-Hu7kfdP1PUD2hLV... 633,949 (2026-06-03 to 2026-12-29, fee 5.0000)
    Evidence
    Glacier history; rolling terms since 2026-06-03
    Source

    Open addressOpen in Avascan (opens in a new tab)

  37. AVX validator owner (one key of a 2-of-3…

    ProvenP-Chainvalidator-owner

    P-avax1r28ymq2y52k8ayruc9mhg2rajxh950mpum3ms2

    Attribution
    Filed under AVAX One (AVX) as validator-owner. Open entity
    Claim supported
    BitGo multisig owner set) - imported 628,449; no current validator
    Evidence
    Glacier history; rolling terms since 2025-11-25 | Avascan: reward owner is a 2-of-3 set incl. this address
    Source

    Open addressOpen in Avascan (opens in a new tab)

  38. AVX pass-through, 1 Dec 2025

    InferredC-Chainpass-through

    0xede4d02e707e6cccd57043a98aeced1f091f75a4

    Attribution
    Filed under AVAX One (AVX) as pass-through. Open entity
    Claim supported
    one item in its life, an atomic export of 400,000.001 AVAX at 15:34:52 UTC
    Evidence
    scratch/hunt/blue/CANDIDATES.md: exactly three validators network-wide started at 2026-09-16 12:52:39 UTC, all three ending 2026-10-20 13:50, and two of the three owner sets are registry-proven AVX; threshold 2 confirmed at UTXO level. Class D and co-timing, not a flow. Re-run: POST https://avalanche-p-chain-rpc.publicnode.com platform.getCurrentValidators, then GET https://data-api.avax.network/v1/networks/mainnet/blockchains/c-chain/transactions?addresses={P-key}&pageSize=100 for the C-Chain funder
    Source

    How this row was graded

    Evidence class
    D, node or provider continuity
    Confidence
    0.80 on a scale of 0 to 1
    What would promote it
    its export resolved through the destination key's ImportTx to an owner set already proven AVX
    What would kill it
    that owner set belonging to another named entity

    Promotion is a person's decision, and every promotion writes the re-runnable query into the evidence above.

    Open addressOpen in Snowscan (opens in a new tab)

  39. AVX rehearsal pass-through, 21 Nov 2025

    InferredC-Chainpass-through

    0x4843599a5310afd021b8c67e8ac1e6a75ffd9b9d

    Attribution
    Filed under AVAX One (AVX) as pass-through. Open entity
    Claim supported
    one item in its life, an atomic export of 0.011 AVAX at 19:55:36 UTC
    Evidence
    scratch/hunt/blue/CANDIDATES.md: exactly three validators network-wide started at 2026-09-16 12:52:39 UTC, all three ending 2026-10-20 13:50, and two of the three owner sets are registry-proven AVX; threshold 2 confirmed at UTXO level. Class D and co-timing, not a flow. Re-run: POST https://avalanche-p-chain-rpc.publicnode.com platform.getCurrentValidators, then GET https://data-api.avax.network/v1/networks/mainnet/blockchains/c-chain/transactions?addresses={P-key}&pageSize=100 for the C-Chain funder
    Source

    How this row was graded

    Evidence class
    D, node or provider continuity
    Confidence
    0.80 on a scale of 0 to 1
    What would promote it
    its export resolved through the destination key's ImportTx to an owner set already proven AVX
    What would kill it
    that owner set belonging to another named entity

    Promotion is a person's decision, and every promotion writes the re-runnable query into the evidence above.

    Open addressOpen in Snowscan (opens in a new tab)

  40. AVX validator owner key, Sep 2026 set 1 of 3

    InferredP-Chainvalidator-owner

    P-avax19lcmlhl664cky7lfsku05g8kdxvvyt7wt0sepr

    Attribution
    Filed under AVAX One (AVX) as validator-owner. Open entity
    Claim supported
    one key of a 2-of-3 owner set behind 414,520 AVAX started at 12:52:39 UTC on 16 Sep 2026 and ending 20 Oct 2026 13:50
    Evidence
    scratch/hunt/blue/CANDIDATES.md: exactly three validators network-wide started at 2026-09-16 12:52:39 UTC, all three ending 2026-10-20 13:50, and two of the three owner sets are registry-proven AVX; threshold 2 confirmed at UTXO level. Class D and co-timing, not a flow. Re-run: POST https://avalanche-p-chain-rpc.publicnode.com platform.getCurrentValidators, then GET https://data-api.avax.network/v1/networks/mainnet/blockchains/c-chain/transactions?addresses={P-key}&pageSize=100 for the C-Chain funder
    Source

    How this row was graded

    Evidence class
    D, node or provider continuity
    Confidence
    0.80 on a scale of 0 to 1
    What would promote it
    the C-Chain funder of this owner set resolved through the atomic bridge to an AVX vault
    What would kill it
    that funder belonging to another named entity

    Promotion is a person's decision, and every promotion writes the re-runnable query into the evidence above.

    Open addressOpen in Avascan (opens in a new tab)

  41. AVX validator owner key, Sep 2026 set 2 of 3

    InferredP-Chainvalidator-owner

    P-avax1ekk3umc25ynver6vsnfagyknldlrrxnfcnln86

    Attribution
    Filed under AVAX One (AVX) as validator-owner. Open entity
    Claim supported
    one key of a 2-of-3 owner set behind 414,520 AVAX started at 12:52:39 UTC on 16 Sep 2026 and ending 20 Oct 2026 13:50
    Evidence
    scratch/hunt/blue/CANDIDATES.md: exactly three validators network-wide started at 2026-09-16 12:52:39 UTC, all three ending 2026-10-20 13:50, and two of the three owner sets are registry-proven AVX; threshold 2 confirmed at UTXO level. Class D and co-timing, not a flow. Re-run: POST https://avalanche-p-chain-rpc.publicnode.com platform.getCurrentValidators, then GET https://data-api.avax.network/v1/networks/mainnet/blockchains/c-chain/transactions?addresses={P-key}&pageSize=100 for the C-Chain funder
    Source

    How this row was graded

    Evidence class
    D, node or provider continuity
    Confidence
    0.80 on a scale of 0 to 1
    What would promote it
    the C-Chain funder of this owner set resolved through the atomic bridge to an AVX vault
    What would kill it
    that funder belonging to another named entity

    Promotion is a person's decision, and every promotion writes the re-runnable query into the evidence above.

    Open addressOpen in Avascan (opens in a new tab)

  42. AVX validator owner key, Sep 2026 set 3 of 3

    InferredP-Chainvalidator-owner

    P-avax1mu49lsn86q0ul4zuug37w0r086pv64qnakxstx

    Attribution
    Filed under AVAX One (AVX) as validator-owner. Open entity
    Claim supported
    one key of a 2-of-3 owner set behind 414,520 AVAX started at 12:52:39 UTC on 16 Sep 2026 and ending 20 Oct 2026 13:50
    Evidence
    scratch/hunt/blue/CANDIDATES.md: exactly three validators network-wide started at 2026-09-16 12:52:39 UTC, all three ending 2026-10-20 13:50, and two of the three owner sets are registry-proven AVX; threshold 2 confirmed at UTXO level. Class D and co-timing, not a flow. Re-run: POST https://avalanche-p-chain-rpc.publicnode.com platform.getCurrentValidators, then GET https://data-api.avax.network/v1/networks/mainnet/blockchains/c-chain/transactions?addresses={P-key}&pageSize=100 for the C-Chain funder
    Source

    How this row was graded

    Evidence class
    D, node or provider continuity
    Confidence
    0.80 on a scale of 0 to 1
    What would promote it
    the C-Chain funder of this owner set resolved through the atomic bridge to an AVX vault
    What would kill it
    that funder belonging to another named entity

    Promotion is a person's decision, and every promotion writes the re-runnable query into the evidence above.

    Open addressOpen in Avascan (opens in a new tab)

Registry claims, address by address, with each claim's standing. 42 of 42 addresses read.

Wurrly Intel registry: compiled with this page.

Source: research address registry. 42 registry addresses for this subject, every one of them shown.

Read method

Nothing here is a new claim. The registry is the research’s label sheet: an address enters it when a figure on one of the research pages established it, and it takes that figure’s standing. This card restates those rows; it does not add to them, and it never upgrades a standing.

Registry method states a review on 4 September 2026. That is the method’s assertion about the whole sheet rather than a date filed against any one row, so it is not copied into a record. A record the registry files no review date against says so.

A source link renders only where this application resolved the destination itself. The one destination the registry files per entity is the research article that entity is written up on, and it is labelled Related research rather than presented as the citation for an individual address’s figure. No anchor, filing URL or transaction hash is derived from evidence prose.

A candidate is a lead one tier below inferred, and it attributes nothing. Where the registry grades a row, the grade, the evidence class and the two tests are printed as the research wrote them, and a confidence appears only on a row that carries a number. A proven row prints no confidence and neither test: nobody measured a number for it, and a row already at the top standing has nothing written that would move it up or out. Promotion is a person's decision, and every promotion writes the re-runnable query into the evidence above.

An explorer link, where one is shown, is an inspection destination and not evidence of ownership. Snowscan reads the C-Chain and Avascan reads the P-Chain.