Sources & methodology.

The official NetX homepage links NetX World’s original unlock update, 20 September 2026 ↗. 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 balance 0, nonce 0 and code 0x at these 10 October mainnet pins:

Canonical BSC NETXbalance 0 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 by 403, 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. Historical state observations above were checked against a saved research snapshot. Public explorer pages may now show newer state; archived verification files are not hosted here..

• Shared funder 6EC153 sent 150 NETX to bcA918 on 6 July 07:48:42 UTC, then 100 NETX on 7 July 03:41:57 UTC. The second funding arrived after the initial recipient batch. 150NETX ↗; later100NETX ↗.
• bcA918 created batch contract 1ef64 ↗ on 7 July 03:28:21 UTC, then successfully called three disjoint 40-recipient native batches:
• 03:29:03UTC:40×2NETX=80. Batch1 ↗.
• 03:30:42 UTC:40×0.3NETX=12. Batch2 ↗.
• 03:30:48UTC:40×0.3NETX=12. Batch3 ↗.
• 104 NETX is initial principal only. Later 84 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 native 6EC153 funding.
• Through the pinned 8 October mainnet state, all 120 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 or 120 independent 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.

Historical validator return

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

The BSC–NetX bridge has matched cross-chain operations, its own finalization relayer and a 2-of-3 administrator Safe. On 22 September 2026, one BSC source call moved 11,595.9251 NETX gross. Ten seconds later, the matching NetX destination delivered 11,594.9251 NETX, after an explicit 1-NETX fee.

Polygon deployment

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 PaymentRouter 2cca 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, nonce 1. 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 nonce 0 and full 0.01 BNB retained at 8 October 17:55:14 UTC.

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.

Morph bootstrap

• On 27 July 2026, EC7908 funded AbD2 on Morph with 0.02 ETH at 03:39:36 UTC, 5 USDT0 at 03:40:00 UTC and 5 USDC at 03:41:07 UTC. ETH ↗; USDT0 ↗; USDC ↗.
• AbD2 then provisioned refund source 2ec4 and initial payer B5d782 with 0.001 ETH + 1 USDC + 1 USDT0 each, and relayer d203 with 0.001 ETH. These are bootstrap balances, not a count of payments or users.
• AbD2 deployed f97f at 04:06:09 UTC ↗, 26m33s after ETH funding, then authorized d203 at 04:06:11 UTC ↗.
• Refund inventory resides at 2ec4, which approved router spending; f97f executes transferFrom, not token custody. This initial payer is not the same address as 3534 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 source 1AB497 remains unattributed; no Gate origin for these Morph funds is established.

On 24 September 2026, a Polygon PaymentRouter call at 05:49:50 UTC and a Morph call at 06:01:23 UTC each transferred 0.0066 USDC directly from payer to recipient. The transactions were 11 minutes 33 seconds apart, with different order IDs and matching payer, relayer and recipient addresses.

Observed: two chain-specific executions, totaling 0.0132 USDC. The router executes the transfer; the payment does not pass into router custody.

Inference: repeated participants, amount, method and close timing support coordinated operation.

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 funding/provisioning, the separate bridge, deployment/bootstrap funding, parallel payment examples, and the new official wallet declarations. Repeated nodes explicitly represent the same address in another explanatory panel; no synthetic money-transfer edge connects the panels.

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.

Public transaction anchors

• Reserve → distributor: 10,000 NETX ↗.
• Validv10 return, 22 September: 98 NETX at 11:44:00 ↗, then 10,000,000 NETX at 11: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 September 06: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 on BSC ↗.
• fa370 same address on BSC ↗.
• Explorer-labelled Gate 1 on Polygon ↗.
• Cohort provisioner bcA918 ↗ and batch contract 1ef64 ↗.
• Morph refund source 2ec4 ↗ and initial payer B5d782 ↗.