wurrly

CustodianInferred

The shared P-Chain custody wallet

41 registry addresses

Observed portfolio value

Reading balances

No successful balance read yet.

One single-key, many-address P-Chain wallet. It delivered AVX's 15.98M treasury on 28 October 2025, it exports into the Coinbase deposit addresses that AVAT's staging wallet also used, and it funds validators. Its keys co-sign the same transactions. At 30 June 2026 the hub held 968,474 AVAX unstaked and 468,858 AVAX staked, which the filed custodian figures leave no room for, so this desk is not Coinbase Custody staking AVAT's tokens. Coinbase Prime is the reading, stated as inference. 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: P. 41 eligible addresses; none read yet.

Source: Avalanche P-Chain API, 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. 41 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: P. 41 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: P. 41 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.

The shared P-Chain custody wallet. Reading transfers

Visualizer view

The shared P-Chain custody wallet: registry addresses by role, and the transfers this read observed between them10 boxes and no arrows. Transfer coverage is being read.Custody1 addresstreasury, vaults, signersWorking1 addressstaging, pass-throughs, forwardersStaking8 addresses shown of 39 addressesvalidator owners, P-Chain keys, protoco…AVX treasury source keyvault · P-Chain · ProvenP-avax1r836…uaefk4Shared single-key P-Cha…staging · P-Chain · InferredP-avax1jygr…w5pa0cShared custody wallet k…custody · P-Chain · InferredP-avax124xd…xu0qfsShared custody wallet k…custody · P-Chain · InferredP-avax13rke…ccgnspShared custody wallet k…custody · P-Chain · InferredP-avax13tt3…72peyxShared custody wallet k…custody · P-Chain · InferredP-avax14jfk…dc82szShared custody wallet k…custody · P-Chain · InferredP-avax16can…jh4ltuShared custody wallet k…custody · P-Chain · InferredP-avax198s3…8vne09Shared custody wallet k…custody · P-Chain · InferredP-avax19ean…ggy4klShared custody wallet k…custody · P-Chain · InferredP-avax1c3ak…j5wntp

Select an address to read its identity and observed transfers.

Registry addresses in scope, with each one's role. 41 of 41 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 standing41 of 41 registry addresses on P-Chain; all registry evidence shown.

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.

  1. AVX treasury source key

    ProvenP-Chainvault

    P-avax1r836g3aee9p07w3cd3v8wdfg88x0r8d0uaefk4

    Attribution
    Filed under The shared P-Chain custody wallet as vault. Open entity
    Claim supported
    received 15,980,899.65 on 28 Oct 2025 (tx 2r8g3xiQ..., 148 UTXOs from 594 input addresses); exported 7,220,215.76 to the parent vault on 12 Nov 2025 (three ExportTx); co-signs with the AVAT desk keys
    Evidence
    Glacier; co-signature 11 Jun 2026
    Source

    Open addressOpen in Avascan (opens in a new tab)

  2. Shared single-key P-Chain custody wallet (the…

    InferredP-Chainstaging

    P-avax1jygrh3yhtv4kjhhksqh024vupav2ugjpw5pa0c

    Attribution
    Filed under The shared P-Chain custody wallet as staging. Open entity
    Claim supported
    staking desk) - funds validators NodeID-HuPCfRaL (500K, 20 percent) and 9AeN8dgN (300K, 2 percent) as an input key rather than as their reward owner; exports 2.75M AVAX into the Coinbase deposit addresses that AVAT's staging wallet also used; the same wallet delivered the AVX treasury. At 30 June 2026 23:59:59 UTC it held 968,474.011 AVAX unstaked and 468,857.738 AVAX staked, which the filed custodian figures leave no room for. Coinbase Prime is the reading, stated as inference
    Evidence
    co-signing set of 35 keys | Glacier balances at blockTimestamp 1782863999 (scratch/hunt/blue/METHOD.md). This desk is not Coinbase Custody staking AVAT's tokens: that job is nine single-key vaults on monthly cycles that never co-sign. Re-run: GET https://data-api.avax.network/v1/networks/mainnet/blockchains/p-chain/balances?addresses=P-avax1jygrh3yhtv4kjhhksqh024vupav2ugjpw5pa0c&blockTimestamp=1782863999
    Source

    How this row was graded

    Evidence class
    B, co-signature or shared infrastructure

    Open addressOpen in Avascan (opens in a new tab)

  3. Shared custody wallet key

    InferredP-Chaincustody

    P-avax124xdc2azae3q45k6yngm77jjhade42qkxu0qfs

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  4. Shared custody wallet key

    InferredP-Chaincustody

    P-avax13rkec4lllkwwgqx0xpfu5h567rkpy08lccgnsp

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  5. Shared custody wallet key

    InferredP-Chaincustody

    P-avax13tt3hepz0ua82arc85suplv2hr932hv372peyx

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  6. Shared custody wallet key

    InferredP-Chaincustody

    P-avax14jfkafpxtp6rpv7a7phrflthjnj5hly0dc82sz

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  7. Shared custody wallet key

    InferredP-Chaincustody

    P-avax16canfak86c44ta90f8hpx8ha4l64zrkajh4ltu

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  8. Shared custody wallet key

    InferredP-Chaincustody

    P-avax198s3zcg7jm3pvxs4kemld95ugqnr4aln8vne09

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  9. Shared custody wallet key

    InferredP-Chaincustody

    P-avax19eantxs6r87dkpd7f5n7k9hefzadkdgqggy4kl

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  10. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1c3akrdcakhp8079g3de6jq087hthpa4lj5wntp

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  11. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1d3ww8mh6tdnzyuzgp6shkqjhqus493zuetpxmm

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  12. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1d40dt0uu6qsaj98s0l6hpcq2zsznmwncfc0ess

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  13. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1d930zex55j6wsw034swjdy8nx94qu9gcfvp2ly

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  14. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1dcamjf07y7gzgv87ardn4upahysupa4n8qc6xa

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  15. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1de68p9dxglx6fjldrran67pas7zpjvgfefr8uw

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  16. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1dy2n0ul9kfamj82j6xemdww30mavldvwqtt2ts

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  17. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1dykauxudm7syhtc86xl35wlnaust4njhasezrm

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  18. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1exa4nk58nj2qsevvysy4hfxafdrgwpvkw2lalv

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  19. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1gttk6d4glndun52h6c99lmyv54p5zcqre9cw08

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  20. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1jryzl5jggdwtmlev8fj4qfude9f76wpfhujjeg

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  21. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1kuw65mgqc0jg3a24kj4t37w9fkk4umrkc63c7h

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  22. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1m0334hafuhsw8sgqg2wcd27cjsusjhtu5wwnge

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  23. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1mf0da2ewvf9ksutuky0gn7zgdv839gp7n3l8yk

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  24. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1mn7ujl0azqmf3mevxq5xm8agn0vxnvx9p3j4n7

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  25. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1p9rvwcd6juzrjwgteat60ems8m28ah79vswjdj

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  26. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1qzqn5scmuu6qw89thh2ewxa8znwupe9f0v2vj2

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  27. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1tey2g8gdme4x9620tcc6pus0y3j6pjkw0aszhw

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  28. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1u6mqhxdg8qds7s4day7jvzexwnayld2ekg2wnm

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  29. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1ucg0cp7agyewmdtnk5xc2ajd4fpfcn4u5jdjkg

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  30. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1vtwh43xdgefypf3ttd9cndndr22gqhmm4vwt3g

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  31. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1wcjv0e7d5qs60asklxl2gpfgpzj9mk6rpn59qn

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  32. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1xk9edv4kdncr82hajaatq9he43s0eyh94m632m

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  33. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1y8g78h50gk3gpd57y4j9zyvyz2lyjds3wgkvfc

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  34. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1ynpm00y75kgae03wz3qv9akdf95eqm3dcd7pq2

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  35. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1yz9zsf87t3c9plm8h68lx9qnvzyajawjwza4s9

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signs with the hub (P-avax1jygrh3y...) and the AVX source key
    Evidence
    Glacier: consumed inputs in the same transactions as the hub / r836g3a (11 Jun 2026 validator add, 21 Aug 2026 export)
    Source

    Open addressOpen in Avascan (opens in a new tab)

  36. Shared custody wallet key

    InferredP-Chaincustody

    P-avax16xp9e2c85cc540kdwrxwdr5665tq9zszz6wgs9

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    exports into the Coinbase deposit addresses that AVAT's staging wallet also used (the atomic imports the Wallets page traced)
    Evidence
    Figure 07 dust sweep + staking desk trace: one of the nine keys behind 2,750,000 AVAX of atomic imports
    Source

    Open addressOpen in Avascan (opens in a new tab)

  37. Shared custody wallet key

    InferredP-Chaincustody

    P-avax1sqzgjetteazy4kdc78fu2httjnrfpkusm8dqwf

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    exports into the Coinbase deposit addresses that AVAT's staging wallet also used (the atomic imports the Wallets page traced)
    Evidence
    Figure 07 dust sweep + staking desk trace: one of the nine keys behind 2,750,000 AVAX of atomic imports
    Source

    Open addressOpen in Avascan (opens in a new tab)

  38. Shared custody wallet key

    InferredP-Chaincustody

    P-avax15wwdv5wqk2wva90pplsnkvgq6mzucanywtcm0a

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    exports into the Coinbase deposit addresses that AVAT's staging wallet also used (the atomic imports the Wallets page traced)
    Evidence
    Figure 07 dust sweep + staking desk trace: one of the nine keys behind 2,750,000 AVAX of atomic imports
    Source

    Open addressOpen in Avascan (opens in a new tab)

  39. Shared custody wallet key, the 39th

    InferredP-Chaincustody

    P-avax1jvv0ufjwqszfj8g8qfaucymf2zft92k9ezqvsh

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    two transactions in its life: a 132,604.942 AVAX delegation on 20 May 2026 and the export it was co-spent in on 20 Aug 2026. It says no more about AVAT than the other 37
    Evidence
    scratch/hunt/blue/CANDIDATES.md item 7: consumed inputs in ExportTx 2n59eqkvVKcZQbTT3VQtNtpnkyPxL9LLac9kgE42kcgnrTYnjL at 15:59 UTC on 20 Aug 2026 alongside two registry keys of the same family. Re-run: GET https://data-api.avax.network/v1/networks/mainnet/blockchains/p-chain/transactions?addresses=P-avax1jvv0ufjwqszfj8g8qfaucymf2zft92k9ezqvsh&pageSize=100
    Source

    How this row was graded

    Evidence class
    B, co-signature or shared infrastructure
    What would promote it
    a common-input co-spend with a key the registry has already proven
    What would kill it
    the August export re-read without it among the inputs

    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)

  40. Shared custody wallet key

    InferredP-Chaincustody

    P-avax16jc0reklan5jd8uxja65pumgsk8t7qgmxsjfuf

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signed ExportTx hTuyhDf8N6uW at 19:59:55 UTC on 23 Jun 2026 with the registry family keys P-avax19eantxs and P-avax1sqzgjet, one of the fifteen transfers that carried 2,750,001.50 AVAX into the Coinbase deposit addresses
    Evidence
    scratch/hunt/blue2/deposit-provenance.md section 2, re-measured in deposit-provenance-verify.md: the fifteen ExportTx consumed 34 distinct input addresses between them and 31 are already in this entity, so the family signs as one wallet. This key is one of the three that were not, on the same common-input rule the registry already uses for the rest of the family. Re-run: GET https://data-api.avax.network/v1/networks/mainnet/blockchains/p-chain/transactions/hTuyhDf8N6uW3J9gm6aqWfAJtNU3Bea6N3Q3HDd4WLYbBNGX9 and read the input owners
    Source

    How this row was graded

    Evidence class
    B, co-signature or shared infrastructure
    Confidence
    0.85 on a scale of 0 to 1
    What would promote it
    a second co-signature with a key already in this entity
    What would kill it
    a co-signature with a key in another 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. Shared custody wallet key

    InferredP-Chaincustody

    P-avax13qnmzeund3ej59s8eydx3wwy3v26trczc8773y

    Attribution
    Filed under The shared P-Chain custody wallet as custody. Open entity
    Claim supported
    co-signed ExportTx 2UQksnsTHKin at 18:52:08 UTC on 13 Jul 2026 with the registry family keys P-avax1jryzl5j, one of the fifteen transfers that carried 2,750,001.50 AVAX into the Coinbase deposit addresses
    Evidence
    scratch/hunt/blue2/deposit-provenance.md section 2, re-measured in deposit-provenance-verify.md: the fifteen ExportTx consumed 34 distinct input addresses between them and 31 are already in this entity, so the family signs as one wallet. This key is one of the three that were not, on the same common-input rule the registry already uses for the rest of the family. Re-run: GET https://data-api.avax.network/v1/networks/mainnet/blockchains/p-chain/transactions/2UQksnsTHKin6f4KSwBQPWj96t1KBSTgseTf3bG15K2wuBijcg and read the input owners
    Source

    How this row was graded

    Evidence class
    B, co-signature or shared infrastructure
    Confidence
    0.85 on a scale of 0 to 1
    What would promote it
    a second co-signature with a key already in this entity
    What would kill it
    a co-signature with a key in another 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. 41 of 41 addresses read.

Wurrly Intel registry: compiled with this page.

Source: research address registry. 41 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.