FUNDING AND SEQUENCING AUDIT — 18 OCTOBER 2026

Scope: attachment Geplakte tekst(20261018-001054).txt, specifically its three alleged first funders, the unknown 52bf40 funder, the conclusion that all operators are one operation, and its explanation for the frozen SequencerInbox. This review uses the attachment, the earlier raw audit, fresh public PulseChain RPC block/receipt reads, an independent Ethereum transaction index, and official primary documentation. No transaction was sent and no Sophia access is claimed.

VERDICT FOR THE PAGE

Three directed funding transfers in the attachment are real. They are not three proofs of one owner or coordinated pDAI restoration. One is an inherited 2022 Ethereum withdrawal from Binance infrastructure. Draw funding arrows separately from administrator authority, contract calls, token transfers and unverified ownership hypotheses. Do not enclose all these wallets in a single confirmed common-owner cluster.

1. VERIFIED DIRECT FUNDING EDGES

A. Binance address 9696 -> CRV recipient 4254
From: 0x9696f59e4d72e237be84ffd425dcad154bf96976
To: 0x42543853a72edb6f1ff9bddab0cf4676187ec28a
Transaction: 0x920569fbaa1a8c05c6372bcc3ad807e507e6c57e46f08ed54dbc7fb73cf15be4
Block: 14,702,307
UTC: 2022-05-03 03:37:27
Value: 0.27706 ETH
Successful receipt, 21,000 gas used, empty calldata, signed chain ID 1.
PulseChain inherited this historical Ethereum transaction. It predates the Pulse fork block 17,233,000 by more than a year. An independent Ethereum Routescan lookup matches the hash, from, to, amount, block hash, timestamp and chain ID.
Binance's own 10 November 2022 reserve publication lists this exact 9696 address as part of its wallet infrastructure. It is therefore a shared service source, not an established private operator-cluster address. Sharing withdrawals from it does not prove that 4254, e121 or 5996 are controlled by the same person. Nothing in this transfer establishes a coordinated PulseChain operation in 2026.
Explorer: https://etherscan.io/tx/0x920569fbaa1a8c05c6372bcc3ad807e507e6c57e46f08ed54dbc7fb73cf15be4
Independent index raw: funding_raw/ethereum_4254_index.json
Primary attribution: https://www.binance.com/en-NZ/blog/community/2895840147147652626
The provider's two irrelevant failed probes are not negative evidence: publicnode returned HTTP403 and Flashbots returned result:null. The successful Routescan result is separately preserved.

B. b40F -> a0b3
From: 0xb40f1ac813d2d04ada0d7409ce84d5ac2b33be4c
To: 0xa0b347117a878da9942fa5c31b87c773a2969913
Transaction: 0xa257fa66eb29ed2e7f1497883fc645b9e2e4b08d4f8b1313b41e84f3355c1037
Block: 27,388,701
UTC: 2026-08-27 01:37:55
Value: 487,962.10769127 PLS
Successful receipt, 21,000 gas used, empty calldata, signed chain ID 369.
This is confirmed post-fork PulseChain funding. The sender's identity, payment purpose, and common ownership with a0b3 are not established by this transfer. The existing research census explicitly classified b40F as a high-volume hub without sufficient same-owner evidence. Do not elevate the user-supplied 'pDAI hub' label into a proven shared operator identity.
Explorer: https://otter.pulsechain.com/tx/0xa257fa66eb29ed2e7f1497883fc645b9e2e4b08d4f8b1313b41e84f3355c1037

C. 48Fc -> 532223
From: 0x48fc8b22ae5319786a8e25ef49b1b49942000000
To: 0x532223e71da2abdb44ea4b9eae93fca98167bacb
Transaction: 0x213958aaaf999066fd8a4c0c41df2627acf8094dd2a034e0ab269d048e8c8677
Block: 22,277,457
UTC: 2024-12-25 15:38:05
Value: 2,000 PLS
Successful receipt, 21,000 gas used, empty calldata, signed chain ID 369.
This is a concrete direct funding link to 48Fc. Its direction is 48Fc -> 532223. The attachment reverses that arrow in one of its prose conclusions. The transfer does not by itself prove that 48Fc signed 532223's later contract calls. The alleged later upgrade-message action needs its own transaction/trace and authorization analysis; this funding audit does not certify that action merely from a wallet label.
Explorer: https://otter.pulsechain.com/tx/0x213958aaaf999066fd8a4c0c41df2627acf8094dd2a034e0ab269d048e8c8677

For these three transfers, full blocks and independently requested receipts are preserved in funding_raw/block_*.json and funding_raw/receipt_*.json. funding_raw/summary.json contains exact amounts and chain classification. Their 'first-ever funder' status has not been certified by a complete native-value history.

D. Why the script misses 52bf40: a contract-mediated native payment
Recipient: 0x52bf40e314638621ae8cd06889a0ea245c784016
Earliest indexed incoming native transfer found in this review:
Transaction: 0xd4a2c86714cb790acb56dea3ec4151d4e12f3d42f08b4f3268871a042eaa5ad4
Block: 26,945,941
UTC: 2026-07-04 06:41:55
Amount: 1,328,743.431358277879773986 PLS
Immediate sender: 0xf868da5a5d5f799cee2205d8fd1f5ad2c4a28499
The explorer identifies this contract as WPLSOmnibridgeRouter. The successful full transaction trace independently confirms: WPLS 0xa1077a294dde1b09bb078844df40758a5d0f9a27 -> native withdrawal to f868 -> identical native PLS amount to 52bf40. There are no trace errors and receipt status is 1.
Outer sender: 0xfb18da3bca8057eb05aab6e77a32925949093533
Outer destination: 0x6ef79fd6f9f840264332884240539ed7a2da8b2b
Outer value: 0. The outer sender is therefore a message/transaction executor, not a proved economic funder of the final PLS payment. The bridge message calls mediator 0x0e18d0d556b652794ef12bf68b2dc857ef5f3996, which transfers WPLS to the unwrapping router.
The normal-transaction index returns 40 rows with outgoing nonces 0 through 39 and zero direct incoming native transfers through pin 27,824,343. Its first outer transaction already spends PLS. The internal index has the earlier router payment. This is a concrete demonstration of why the attached normal-only filter returns no funder. The original source-chain depositor/common ownership has not been traced or established here; do not substitute the bridge router or message executor for that identity.
Explorer: https://otter.pulsechain.com/tx/0xd4a2c86714cb790acb56dea3ec4151d4e12f3d42f08b4f3268871a042eaa5ad4
Raw: funding_raw/fund52_tx.json; fund52_receipt.json; fund52_trace_transaction.json; fund52_block.json; first_52bf40_internal_index.json; first_52bf40_index.json.
The public RPC does not expose debug_traceTransaction but does support trace_transaction. The failed debug-method response is preserved and was not treated as absence of internal transfers.

2. THE ATTACHED FIRST-FUNDER SCRIPT CANNOT PROVE ITS LABEL

- It asks the public OTS index for only 8 transactions (6 in the follow-up), with no pagination. That is a candidate-finding step, not a comprehensive funding audit.
- It selects only outer transaction.to == address and outer value > 0. Contract-mediated native payments are excluded, even if OTS includes the containing transaction. ERC20 funding is also excluded.
- It sorts only by block number; transaction index is needed to order transfers within one block.
- It does not inspect successful receipts or reverted call ancestry. A failed transfer attempt is not funding.
- It calls rpc(...).get('result') and then turns missing values into 0 or '0x'. An RPC JSON error can therefore become a false zero balance, zero nonce, or 'EOA'. Errors must remain unknown/error, not measured zero.
- Its requests.post has no timeout, and its JSON prefix check is not a meaningful success check. A valid JSON error is accepted as an empty result.
- 'No funder returned' means the limited query found no matching outer transfer. It does not mean the wallet had no prior funding.
- A first withdrawal from a shared exchange/service does not establish common beneficial ownership among recipients.

3. THE FROZEN SEQUENCER EXPLANATION IS TECHNICALLY WRONG

The attachment says the SequencerInbox count can remain still because researchers lack the private L2 RPC. Lack of RPC visibility cannot hide transactions, logs or counters in the identified public PulseChain L1 contract. A private node can execute transactions locally, but fresh finalized rollup input through this standard SequencerInbox would leave parent-chain evidence.

The earlier raw audit confirmed the SequencerInbox at 0x1c479675ad559dc151f6ec7ed3fbf8cee79582b6 is bound to the examined Bridge and Rollup through their getters. Between block 17,233,000 and pin 27,824,343:
- Batch count: 193,542 -> 193,542.
- Bridge sequencer message count: 193,542 -> 193,542.
- Delayed messages consumed by the sequencer inbox: 841,504 -> 841,504.
- Delayed messages submitted to the Bridge: 841,519 -> 841,594.
- Post-fork SequencerBatchDelivered logs: zero.
- All post-fork events at that address: one AdminChanged event.
- Positive control: 124 batch events in the last 1,000 pre-fork blocks.
- Latest confirmed rollup node advances from 5,069 to 5,355, which is a separate state/assertion counter, not evidence of new posted transaction batches.

Thus 75 new delayed messages were submitted, without an observed increase in their sequencing consumption. An input queue, a validator stake, a confirmed assertion and an executed Outbox message are separate things. Standard force inclusion of delayed messages is not an invisible loophole: it changes the canonical inbox state as well.

The careful conclusion is 'The examined inherited deployment has no observed post-fork sequencer batches; actual child-chain execution has not been independently replayed.' It is too strong to say there is no private node or no separate L2 anywhere. It is also wrong to present a secret but functioning peUSD L2 as demonstrated merely because no public RPC is known.

Official technical sources:
https://docs.arbitrum.io/how-arbitrum-works/deep-dives/batchposter
https://docs.arbitrum.io/how-arbitrum-works/deep-dives/sequencer
Local raw/evaluation sources:
../arb_pdai_audit/sequencer/summary.json
../arb_pdai_audit/sequencer/activity_checks.json
../arb_pdai_audit/rollup/findings.txt
../arb_pdai_audit/rollup/roles_and_stakers.json

4. WHAT THE MAP MAY SAY ABOUT CONTROL

The independently read EIP-1967 admin slots do support a specific control path: 5996 is proxy administrator of the UpgradeExecutor, and that UpgradeExecutor is the Rollup's owner/proxy administrator. a0b3 is current proxy administrator of the Outbox, Bridge and SequencerInbox. These are precise administrative capabilities, not proof that every wallet using the infrastructure has one owner. Current roles must not automatically be projected backwards onto the 2023 pDAI withdrawal.

The 3.205M CRV gateway withdrawal to 4254 is a real token transfer. Its quantity alone is not proof of its dollar value, redemption liquidity, or sale proceeds. Likewise, control of an escrow or upgrade path does not produce external backing for a stablecoin.

Recommended diagram semantics:
Solid green: successful measured token/native transfer, with token + amount + date/tx.
Solid cyan: verified current administrator/owner edge, with slot/getter + pin.
Dashed amber: proposed integration or unverified same-owner hypothesis.
Grey: inherited/shared-service history, including Binance funding.
Red blocked marker: missing evidence or a failed current precondition; do not label an unverified path as running.
