NetX Coverage audit — 10 October 2026
This is a selected, evidence-backed overview of documented NetX funding, bridge administration, payment infrastructure, AgentCity testnet, BSC products/allocations and a separate trading system. It is not an exhaustive wallet-ownership map or a fresh all-network audit. Earlier bounded studies have different evidence pins; adding a panel does not refresh them.
| Investigation branch | Map coverage | Detailed evidence / limit |
|---|---|---|
| Launch-state funder, Validv10 and returned funds | Included, summarized | Network and governance (archived research reference; not hosted here); full staking/governance contract hierarchy is not drawn. |
| NetX mainnet distributor59947 | Included, summarized | Distribution (archived research reference; not hosted here); every recipient and two-hop route is not drawn. |
| Mainnet provisioning / 120-address cohort | Included, grouped | Cohort (archived research reference; not hosted here); all120 signed histories were checked at the recorded pin, not120 independent users or every asset/internal trace. |
| Production BSC–NetX bridge, Safe and relayer | Included, grouped | Bridge (archived research reference; not hosted here); every operation, fee/pool snapshot and all three individual Safe owners remain in detailed evidence. |
| BSC TH-admin funding of bridge signer and Polygon deployer address | Included | Migration/admin proof (archived research reference; not hosted here); direct gas grants and same-address joins, not legal ownership. |
| Gate-labelled Polygon funding / Morph bootstrap | Included, separate | Payments (archived research reference; not hosted here); Morph upstream1AB497 remains unattributed. Gate custody does not identify an exchange-account owner. |
| Parallel Polygon/Morph legacy payments | Included, representative example | Payments (archived research reference; not hosted here); not a complete payment history or a matched NetX settlement leg. |
| Morph v2 operator/relayer/payer return loop | Included, grouped | Recorded baseline12 calls /1,100 payments /860 project TUSD returned; not1,100 customers or official TrueUSD. Not every authorized relayer or payer is drawn. |
| AgentCity testnet registration, collaboration and mission/node settlement | Included, representative contracts | AgentCity (archived research reference; not hosted here); reputation, governance, sanction, evidence, investment and ERC-8004 subregistries remain in the source index. The displayed C68E node settlement is not proof of full mission completion. |
| Sponsored testnet faucet / known-payer crossover | Included | Second pass (archived research reference; not hosted here); AbD2 role grant, bcA918 calls,3534 claim and staking. Faucet mock tokens are not the later staked native tNETX lot. |
| Testnet bridge / other test environments | Partial | 3534 source-call example only. No matched completion inferred. The120-address earlier-testnet cohort, BSC-testnet/Amoy lineage and other test deployments are in cohort evidence (archived research reference; not hosted here), not all drawn. |
| BSC NETX owner43fB → distributor6e393 → known payer3534 | Included, representative join | Distribution proof (archived research reference; not hosted here);99 direct recipients, not all traced two hops. |
| TH/TT migration, NXL redemptions, NFT proceeds and deposit-family control | Included, representative paths and separate owner roles | Migration/staking (archived research reference; not hosted here), second pass (archived research reference; not hosted here), third pass (archived research reference; not hosted here). Different owners and signing keys must not be collapsed. |
| Monthly443,834-NETX executors and exchange execution/collection | Included, grouped monthly branch and isolated trading branch | Distribution/exchanges (archived research reference; not hosted here), older research map (archived research reference; not hosted here). Pooled custody prevents exact downstream proceeds attribution; no official market-making mandate or production-admin link established. |
| Four officially declared allocation wallets | Included, isolated | Source declarations and focused10October pins are separate from observed funding. Network not stated in official announcement; Polygon history/holdings remain unverified. |
Completeness conclusion
The selected infrastructure story is substantially more complete: funding, authority, payment execution, batch execution with testing inferred, testnet crossovers and AgentCity execution are distinguishable. The entire investigation is not fully drawn, and known gaps are not erased by the diagram. All relevant branches above have either a visible representative path or linked research with an explicit detail reference.
The main unresolved questions remain: legal/human controllers, the origin/purpose of some pooled funding, complete two-hop follow-up for all99 BSC recipients, later monthly executors, and any transaction-level production payment → NetX/AgentCity settlement. Absence in reviewed evidence is not proof of absence on every chain.
Do not extend exchange hot wallets into generic multichain recipient graphs: those routes lose NETX-specific attribution and do not establish team control.
Attribution label clarified
“NetX-linked operational infrastructure” describes a strong operational inference for the bridge, TH and related operational core, supported by documented deployments, funding and administrative roles. It is not an assertion of common team ownership or individual identity. Funded recipients/users and wallets merely present on NetX are not included in that ownership inference; the separate trading system has no proven team affiliation. Topology and underlying evidence are unchanged from the prior edition.
Scope of the two added branches
BSC migration/redemption, V1/V2/V3/V4 owner roles, GenesisBundle USDT forwarding and June–August rotating allocations are now visibly represented. Detailed contract implementations, every verifier key, every TH/TT input, all recipients and all downstream exits are not fully drawn; they remain in linked research. The allocation executor c2ebb still has the documented17missingnonces/24,000NETXnet-reconciliation gap; displayed465,146NETX is confirmed incoming funding, not a complete downstream ledger.
The50867 trading system has a distinct boundary and a prominent in-panel warning: NetX-team control, an official market-maker/multi-client mandate, profitability, price suppression and beneficial exchange ownership are unproven. Confirmed authority6011→72ef→50867, execution keys, one sale and separate reverse-purchase→Gate/MEXC examples are shown. No directional trading→project-administrator edge exists. Other watched execution systems are not assigned to6011.
Matching R14/4A and the dashed NXL order relationship do not imply token movement from intake to payout. R15/47e8 andR16/34d527 distinguish technical identity from purpose. Repeated Gate custody and shared sweep infrastructure do not identify the beneficial controllers of depositors. The production payment→NetX/AgentCity settlement link remains unproven.