Inside NetX — infrastructure, BSC products and separate trading

Open the interactive map. Coverage and remaining gaps.

Final community wording review: the four officially declared wallets now say network not stated. The declaration card explains: Network not stated in official announcement. This is a source limitation, not a claim that the address cannot exist or be used on an EVM network. No network, funding or ownership attribution has been added.

This edition adds BSC migration/redemption, deposit-family control, NFT proceeds and recurring allocations, plus a separately bounded trading system. Earlier AgentCity, bridge and parallel payment panels are retained. These are historical evidence syntheses, not new transactions or a new all-network monitoring cutoff.

Historical infrastructure snapshot: 9 October 2026; official functional-wallet declarations and their focused chain baseline checked 10 October 2026. This is a selected historical infrastructure map, not a fresh exhaustive audit. Earlier editions are preserved separately. This edition includes the previously omitted Gate-funded Polygon deployer, separate BSC same-address funding, NetX provisioning cohort and Morph bootstrap. Older infrastructure checks replay saved historical evidence; the four newly published wallets have separate10October pins below. These are not continuously live balances. No personal names, local computer paths, location details or private repository links appear in the shareable HTML or this guide. Times below are UTC.

Sharing and reading limits

Share the interactive HTML together with this guide: full addresses, transaction proofs and branch-specific evidence pins are in the guide, not every diagram node. Use the five guided views and zoom for individual branches; the full-height map is not intended as one readable chat screenshot. Fine-detail tags can be hidden in READ mode, so key ownership, network and settlement limits also appear in the header, boundary labels and interpretation cards.

“Launch-state funder” describes observed funding; the reserve role is a strong inference. Coordinated AgentCity and Morph batch patterns support a testing interpretation, not direct proof of purpose. Redeemer addresses and payment events are not counts of independent people or customers. Gate custody deposits do not establish later exchange sales or beneficial account ownership.

The final artifact is the canonical source for a future 1:1 NetX Scope update. The currently published website has not been synchronized by this revision; do not describe it as this edition.

Panel reference key — identity, not a transfer

Matching R labels are printed inside the relevant nodes and in the dotted reference-key cards. These are non-directional correspondences, not additional transactions.

R2/R7 also match the added testnet AbD2/3534 nodes; R7 matches the BSC3534 funding recipient. R3/R6 additionally match the Morph v2 operator/recipient and legacy relayer. These are address references, not staking-to-payment or cross-chain settlement arrows.

Official wallet declarations: no observed funding link to the existing cluster in reviewed scope. This is a source-role panel, not observed wallet distribution.

This revision changes presentation only; it adds no new chain observations and advances no monitoring baseline.

Project connection is not common team ownership

NetX-linked operational infrastructure — deployments, funding and administrative roles support a project connection for the bridge, TH and related operational core. Individual identities and common team ownership are not independently proven. Confirmed transaction/technical roles and this strong operational inference are separate evidence levels.

• Operational core: the bridge, TH/migration administrators and directly linked infrastructure have documented funding, deployment or administrative connections. This supports a project connection, not blanket legal/team ownership of every key.
• Recipients and users: a funding transfer or contract interaction establishes that relationship only. Neither receipt of funds nor presence on the NetX network makes an address a team wallet.
• Separate trading: the6011→72ef→50867 execution system remains outside that attribution. NetX-team control and official market-making/multi-client mandate are unproven.

The header and a dedicated interpretation card make this distinction explicit. No ownership arrow was added, no recipient was reclassified as team-controlled, and no chain baseline changed.

What is confirmed

• Polygon and Morph are parallel payment paths, shown as separate chain-specific lanes using the same payer, relayer and recipient addresses. Repeated addresses are not new wallets.
• On 24 September 2026, Polygon router 0x2cca979b14a6ce59aa72f82c93e6e9577f4c98c1 processed sponsorPay at 05:49:50 UTC, order 7d9ccaaa2a0f. Morph router 0xf97fc1738e79e47cceb22868660cc12207721cc6 processed sponsorPay at 06:01:23 UTC, order eb5e252dee1b.
• Each call moved exactly 0.0066 USDC directly from payer to recipient. The calls are 11 minutes 33 seconds apart, with distinct order IDs. Total across the two calls is 0.0132 USDC, counted once.
• Shared payer: 0x3534E4bc5C5D8E3A293cb9cB6CEB3Ebc398F9186; transaction relayer: 0xd203660dcafcdae516d3fd74c0609df037d6afd7; recipient: 0x292A83a4363062916815EBbe2eF137d7B791d32d.
• Authority is chain-specific: Polygon 2cca owner is 0xfa370e9d6bd46cc6eb8614964cf067518ff5049b, with AbD2/d203 authorized relayers at the inspected pin. Morph f97f owner is AbD2. The upper grouped authority node covers Polygon 4539 and Morph f97f, not ownership of Polygon 2cca. Historical state is not a promise of current permissions.
• BSC–NetX production bridge is separate infrastructure, with its own 9B3Ec finalization relayer, pool funding and 2-of-3 administrator Safe. The grouped bridge-pair node represents matched bridge operations, not a payment settlement leg.
• Preserved the historical validator return and funding paths. Funding does not establish wallet ownership.

Inference and what remains unproven

Strong operational inference: repeated participants, method, amount and close timing support coordinated Polygon/Morph operation. They do not prove one corporate controller or why the calls were made.

Not established: a Polygon-to-Morph asset transfer; a matching payment-to-NetX settlement transaction; named merchant identity or commercial purchases; Lawson/NETSTARS attribution; independent customer adoption; NETX demand or token purchases arising from these calls. No arrow asserting those links is drawn. The absence of a matching leg in reviewed evidence is not proof that no such activity exists anywhere.

How to read the map

Each payment lane has its own payer, router, relayer and recipient on that chain. The participants have matching addresses across chains; this is not a cross-chain transfer arrow. Dashed arrows represent the signed permit, transaction submission and router execution. Highlighted token arrows represent payer → recipient directly, not router custody. Execution and token arrows describe the same payment and must not be added as separate economic volume.

The bridge boundary separates actual BSC–NetX bridge operations from Polygon/Morph payment execution. Boundaries identify networks/infrastructure, not company ownership. Five guided views isolate infrastructure/bridge/declarations, Polygon/Morph payments, AgentCity TESTNET, BSC products/allocations, and separate trading. Official declaration nodes remain isolated, not omitted. Repeated nodes carry matching R1–R17 reference labels. The dotted reference-key cards connect the explanatory panels without directional arrows or synthetic transfer edges. The former BSC-to-Polygon fa370 correspondence arrow is now the non-directional R9 reference. These keys are outside directed route/reachability traversal; they do not merge chain balances or imply shared legal ownership.

Verified missing branches added in this edition

Polygon deployment: Gate funding is not router custody

1. Explorer-labelled Gate 1 sent 99.318 POL to deployer 0xfa370e9d6bd46cc6eb8614964cf067518ff5049b on 31 July 2026 at 10:22:11 UTC. Funding transaction.
2. The deployer created Polygon PaymentRouter2cca at 10:31:33 UTC, 9m22s later. Creation transferred zero native principal to the router, consumed 0.851286347997360502 POL in gas and established fa370 as initial owner. Deployment transaction.
3. At the 8 October 12:30:57 UTC evidence pin, fa370 retained 98.466713652002639498 POL, nonce1. The exact native funding/gas/balance reconciliation closes.
4. Separately, BSC TH/migration administrator b67a sent 0.01 BNB to the same fa370 address on BSC on 29 January 2026 at 11:28:40 UTC. BSC transaction. BSC nonce0 and full0.01BNB retained at 8 October17:55:14UTC.

Confirmed: transfers, same-address correspondence, contract deployment and observed technical ownership. Not established: b67a as a legally proven team wallet, Gate-account owner, bridged BNB/POL lot, Gate-funded payment principal or a Gate→router→120-address asset path. The BSC 0.01BNB is not Polygon deployment gas. Historical and pinned ownership agree; a complete intervening ownership-event scan was not performed.

NetX mainnet provisioning: a separate 120-address cohort

• Shared funder6EC153 sent 150 NETX to bcA918 on 6 July07:48:42UTC, then 100 NETX on 7 July03:41:57UTC. The second funding arrived after the initial recipient batch. 150NETX; later100NETX.
• bcA918 created batch contract1ef64 on 7 July03:28:21UTC, then successfully called three disjoint40-recipient native batches:
  • **03:29:03UTC:**40×2NETX=80. Batch1.
  • **03:30:42UTC:**40×0.3NETX=12. Batch2.
  • **03:30:48UTC:**40×0.3NETX=12. Batch3.
• 104 NETX is initial principal only. Later84 external top-ups add 138.571387970742209622 NETX; combined unique external principal is 242.571387970742209622 NETX. Do not count the one-NETX self-transfer as another external top-up or add repeated hops as new principal.
• AbD2 supplied bcA918 with four locally deployed BCH/FTT/USDT/USDC-labelled token inventories. These labels do not make them official stablecoins or externally valued assets. This application-wallet relationship is separate from native6EC153 funding.
• Through the pinned8October mainnet state, all120 signed histories reconcile: 16,834 successful outgoing transactions involving native peer transfers, local-token transfers and recorder calls. No known production-bridge/DEX/approval/deployment activity or external recipient outflow appears in those signed histories. Prepared-cohort testing is a strong operational inference, not a confirmed mandate or120independent customers.
• The individual batch effects are supported by successful calldata, aggregate events and per-wallet reconciliation. Historical internal traces were unavailable; do not describe the empty explorer internal index as a complete trace.

Morph bootstrap: real funding, separately from NetX funding

• On 27 July2026, EC7908 funded AbD2 on Morph with 0.02 ETH at03:39:36UTC, 5USDT0 at03:40:00UTC and 5USDC at03:41:07UTC. ETH; USDT0; USDC.
• AbD2 then provisioned refund source2ec4 and initial payerB5d782 with 0.001ETH+1USDC+1USDT0 each, and relayerd203 with 0.001ETH. These are bootstrap balances, not a count of payments or users.
• AbD2 deployed f97f at04:06:09UTC, 26m33s after ETH funding, then authorized d203 at04:06:11UTC.
• Refund inventory resides at2ec4, which approved router spending; f97f executes transferFrom, not token custody. This initial payer is not the same address as3534 in the later parallel-payment examples.
• This Morph EC7908→AbD2 edge has the opposite direction to the separately observed AbD2→EC7908 NetX-mainnet edge. Chain-specific roles are not a cross-chain asset transfer or contradiction. Morph upstream source1AB497 remains unattributed; no Gate origin for these Morph funds is established.

Validator return retained and clarified

The 1NETX funder→Validv10 transfer on 17August02:21:29UTC is a confirmed transfer; gas-support purpose is inference. Funding. Validv10 returned0.8NETX on 8October06:19:51UTC. This is separate from the 10,000,098NETX reserve return. No new staking/bridge or trading claim follows from that small transfer.

Public transaction anchors

• Reserve → distributor: 10,000 NETX.
• Validv10 return, 22 September: 98 NETX at11:44:00, then 10,000,000 NETX at11:44:42. Count their sum once; these are historical transfers, not today's balances.
• NetX Safe route configuration and BSC counterpart.
• Observed Polygon sponsorPay, 24 September 05:49:50.
• Observed Morph sponsorPay, 24 September06:01:23.
• Morph v2 deployment.

Full address entry points

Address pages are starting points, not substitutes for transaction receipts or historical authority reads.

Additional full address entry points

• TH/migration administrator b67a onBSC.
• fa370 same address onBSC.
• Explorer-labelled Gate1 onPolygon.
• Cohort provisioner bcA918 and batch contract1ef64.
• Morph refund source2ec4 and initial payerB5d782.

Official functional-wallet declarations — separate evidence class

The official NetX homepage links NetX World’s original unlock update,20 September2026. Its embedded table image, missed by the generated secondary summary, publishes four full addresses. Confirmed: official declared purposes. Not established: allocation transfers, private-key/legal control, or a transaction link to this map’s existing cluster. The source does not specify the intended chain.

The separate “Official wallet declarations” panel uses dashed “declares only” arrows from a publication node. These declaration-only relationships are not transfer/authority arrows. No connection to treasury, bridge, PaymentRouters or trading wallets is drawn. The market/liquidity role is not evidence of an active market maker.

All four have native balance0, nonce0 and code0x at these10October mainnet pins:

Canonical BSC NETXbalance0 for each. Reviewed NetX/BSC/Morph normal/internal/token indices are empty; Morph token-holding index is also empty. Polygon history and token holdings were blocked by403, not verified empty. Zero native state and empty provider indices do not prove no activity across all chains or complete historical internal/log coverage.

The article expects staged allocations and distinguishes unlocking from circulation. Its repurchase/burn statement is a plan, not observed buybacks. Four wallet roles are not an exact mapping of the five release-schedule categories. Archived original table and verification record (archived research reference; not hosted here).

Community caption

Inside NetX: an evidence-backed overview of infrastructure funding, bridge authority, Polygon/Morph payments and AgentCity testnet. It distinguishes who funds wallets, who can administer contracts and how assets move — including batch-payment return loops consistent with coordinated testing and shared testnet participants. Testnet activity is not production settlement; connected wallets are not automatically controlled by one party. Official wallet declarations remain separate from observed funding. This is a selected historical overview, with detailed branches and unresolved gaps linked in the coverage audit, not a complete ownership chart.

This edition also shows BSC product migrations, recurring allocations and a separately investigated trading system. Its team affiliation and official market-making or multi-client mandate are unproven; shared exchange routes do not establish shared ownership.

Share the self-contained HTML with this guide, or use its image/SVG export and keep the caveats visible. No public hosting or community posting was performed. Verification receipt.

Added AgentCity TESTNET branch — exact evidence and limits

All activity in this section is NetX testnet, chain587. Native tNETX has no real-world monetary value. This is a synthesis of existing records through8October, not a new live-chain scan.

• AbD2 deployed sponsored faucet3ddd on 30June2026 04:08:31UTC, then granted CLAIM_ROLE to bcA918 at 07:37:19UTC. R2/R10 match the same addresses in other panels, not cross-chain money flows.
• Known payer3534 received a mock-token claim on 2July02:40:16UTC. The received mock token was 0xbe82ef0eca9e5762691a801898b5340b03e33966, raw amount10000000000000000. This token is not the later native stake; no lot-provenance arrow joins them. -3534 successfully called AgentCity DualStakingRegistry6F8E with 1 tNETX on7September15:16:39UTC (first stake) and 2 tNETX at15:35:45UTC (second stake). Selector0x7b0472f0, agentID2860, total 3 tNETX across two calls. First call was67d12h36m23s after the claim, not immediate use or proof of the same assets.
• Another faucet participant2aba made two separate1-tNETX stakes on 1September07:59:12UTC (first) and 08:03:33UTC (second). Four calls /5 tNETX combined is not four calls /5 tNETX by3534.
• A successful3534 testnet-bridge source call on 12August09:46:24UTC is shown as a call, not a completed source/destination operation. Destination97 and native10tNETX do not turn this into a production bridge transfer.
• Workflow21C452 registered agentID2893 for owner6B9D on 12September15:41:45UTC. The workflow group summarizes three documented callers; it does not mean each performed every labelled action.
• The factory created C68E with 11.958333675tNETX on25September08:06:42UTC, configured settlement at08:12:36UTC and emitted NodeSettled naming that same mission at08:15:48UTC. The dashed settlement→mission arrow is an event reference, not a transfer of mission escrow or proof of full completion. No unverified factory caller is assigned in the map.
• Collaboration-stage calls are documented separately; orchestrate example. A separate earlier missionac878 reached successful finalization on 14August23:13:12UTC. Do not splice those events into the C68E lifecycle.

Confirmed: same addresses, faucet administration/calls, native staking and testnet mission execution. Strong inference: coordinated test infrastructure. Not established: a3534 staking→C68E mission funding route, mainnet AgentCity settlement, commercial revenue, team ownership of every recipient, or Lawson/NETSTARS attribution. The earlier absence statement refers to the reconstructed mission's production connection; it must not be generalized into “no shared testnet participants.”

AgentCity and crossover address entry points

Other omitted confirmed joins now visible

• TH administratorb67a sent0.005BNB to bridge deployer/signer0D1504 on 21August02:42:32UTC. The recipient deployed production BSC bridgee139c at03:40:13UTC, 57m41s later. Technical Safe control still requires2-of-3, not that funder alone.
• Recorded NETX-owner43fB funding of distributor6e393 is a separate BSC branch. The distributor sent100NETX to3534 on 30January05:16:13UTC. This is not Polygon/Morph payment principal or a bridge match. Example43fB→6e393 funding.
• Morph v2 gas came from legacy relayerd203: 0.01ETH toE2A60 at 17:28:46UTC during the documented13September rollout. OperatorEC7908 fundedE2A60 with10,000 project TUSD69seconds later. The project token, relayer, router and operator/recipient are distinct roles. Recorded14September baseline:12 successful batch calls,1,100 payment events,860 project TUSD returned. Repeatedly circulating tokens are not1,100unique customers,860USDrevenue or official TrueUSD. The map's funding and return arrows describe different stages, not extra economic volume.

Sharing and completeness

The diagram and this guide are privacy-preserving public artifacts. For the coverage assessment, send COVERAGE.md with them: it explicitly separates represented paths from linked research and unproven joins. The detailed repository evidence may have a different publication/privacy scope from this standalone HTML.

Added BSC lifecycle and allocations

These panels summarize historical receipts and pinned authority checks already documented in the research. They are not new October transactions, a fresh all-network audit or a new monitoring baseline. Source-to-claim ledger.

Migration and signed claims

• Administrator b67a directly deployed TT, TH, payout4A and collection8ee5. Its recorded payout ownership is distinct from the off-chain claim authorizer1494. The diagram summarizes the legacy August TH cohort: 240,972 unique TH and 207,638 resulting NETX deposited at Gate1 via four intermediaries. Subsequent exchange sales and beneficial account ownership are unproven; not every participant is individually followed.
• Linked TT example, not an additional drawn path: 29March2026, b67a funded d1d250 with70,000TT at09:36:16UTC. d1d250 deposited it into8ee5 at09:39:34UTC, then claimed70,000NETX from4A at10:05:23UTC, 25m49s later with the exact same order ID. TT input and NETX output are different assets; do not sum them as one token volume.
• NXL token FCFd292 is a BSC product token, not native NETX. Users sent NXL to intake5f3243; shared payout4A separately paid canonical BSC NETX. The dashed intake→payout relationship means matching user, exact amount and order ID, not token forwarding, a cross-chain bridge or a contract-to-contract call.
• Recorded final cohort: 42 exact matched paths /39 redeemer addresses /8,024.427248450624882664 NETX. All 46 inspected accepted claim signatures recover1494; owner and signer must not be merged. Eleven known intake orders were unmatched/unused at the pin, not proven failed or lost. Count unique principal once. Example intake,15June12:02:40UTC and matching payout,12:04:08UTC.

Distinct deposit owners, not a single master key

V1/V2 owner/deployerd1d250 performed configuration and sent 465,146 NETX across16 grants to c2ebb. Funding does not prove custody of the recipient key or a trading mandate. V3 owner47e8 deployed the NXL/GenesisBundle/V3 sequence; V4 has separate ownerbddd. Each version has its own authorization signer. Product names and ABI reward labels do not prove native validator operation or validator-funded yield. Historical getters are not continuous lifetime ownership histories.

NFT proceeds and recurring distributions

• GenesisBundle purchases paid 8,560 USDT to47e8. The owner forwarded 8,560.00016 USDT, including separately received0.00016dust, through34d527 to labelled Gate1 on 29September08:43:49UTC and 10:07:36UTC. Owner→relay; relay→Gate. Count8,560.00016USDT once, not at both hops.
• June4Ea3, JulyeDa2 and AugustA115 each received 443,834 NETX from Gate1 and paid recurring tiers. The grouped node represents three distinct EOAs, not one key or one443,834-total combined batch. b67a supplied July 0.003BNB and August 0.005BNB, not the June gas grant. Julygas; Augustgas.
• August returned 150,000 NETX to Gate through34d527, sent 293,833 NETX to non-Gate recipients and retained 1NETX at review. The return was50,000 plus100,000, not an additional allocation on top of gross443,834. 50,000return; 100,000return.
• Strong operational inference: coordinated recurring allocation ledger. Unproven: vesting/compensation category, beneficiary identity, legal controller, exchange-account ownership and post-deposit sale. Later monthly discovery remains incomplete.

R12 matchesb67a across the prior gas-funding and new migration/allocation panels; R14 matches4A; R15 matches47e8; R16 matches34d527. Repeated exchange nodes denote the same labelled custody endpoint, not a link between the controlling keys of its users. The broader34d527 evidence favors deposit/sweep-like infrastructure; it must not be presented as a proven project-owned trading relay.

Separate trading / execution system

The visually separate lower boundary has no directional relationship to NetX validator, bridge, payment or product administrators. This is lack of an established link in reviewed evidence, not proof of independence. No node calls6011 a team wallet or an official market maker.

• **Confirmed authority:**6011 owns proxy administrator72ef, which has upgrade authority over50867. Observed runtime restricts its upgrade window to 09:00 inclusive–23:00 exclusive UTC.6011 deployed the proxy and also submitted actual execution calls.
• At the 9October08:09:32UTC pin, at least eight identified keys had execution/withdraw permission. These are not eight upgrade owners or a complete membership enumeration. Historical permission-grant dates for the later additions remain open.
• Confirmed sale: Gate1→50867 541.11NETX, 8October14:28:10UTC; two seconds later multi-pool execution returns 90.283552063460336633USDT net to50867, with zero net BTCB. Refill; sale. The return arrow is proceeds from that same trade, not extra trading volume.
• Confirmed reverse route: two 8October19:29:13/19:30:29UTC purchases credit98f870 a total 829.641586893792455325NETX, then the full lot reaches Gate 36m58s after the second purchase. Firstbuy; secondbuy. The separate5f1c branch has exact purchase→MEXC13 follow-ups on5/7October, not additional hops of the829.641586…lot. Examplepurchase; deposit5m26slater.
• Multi-asset execution is supported by a separate GOATED withdrawal/conversion/USDT-return route; it is not evidence of a mandate to work for multiple clients. R17 matches50867 across its authority, sale and purchase roles. Do not merge other watched055a/218c/B769 execution systems into this ownership tree.

UNPROVEN: NetX-team control/ownership, a direct operational link to production administration, official market-making or multi-client mandate, profitability, intentional price suppression, beneficial exchange-account ownership and post-deposit sales. Inventory rebalancing/arbitrage are hypotheses only. The same restriction applies to a production Polygon/Morph→NetX/AgentCity settlement link: it remains unproven, and no such arrow was added.

Added public address entry points

Delivery and visual-review scope. This edition is a broader evidence-backed overview, not a complete wallet catalogue or proof of every controller.