Treasury Witness · Pons treasury path · week 2026-W43

Where the fees went this week

Every transfer along the path owner EOA → fee escrow → fee Safe → treasury hop → buyback EOAs → burners, read from the chain for the last 7 days and summed by hop. Blue rows end at a witnessed treasury address; red rows end at a generated asset's burner or buyer. Re-derive any row with the addresses below and any RPC you trust.

blocks91,718,975 – 97,537,337generated2026-10-25T11:02:22Zreport sha256a6674465a79d1d5dc6a5d0b393e2b0fa8f782aef6cbb6f1a9a0d37135e818a73attestationkind-15 3752448 (auto-sign lane, no seal)logs{"escrow_claims": 0, "safe_in": 0, "safe_out": 0, "treas_in": 0, "treas_out": 0, "burner_in": 0, "burns": 4051}

Flows by hop

fromtotokenamounttransfers
treasury proxyburn addressPONS2,030,136.18454,039
0xd21958b3…burn addressPONS0.33761
0x073dd0ad…burn addressPONS0.33481
0x20c419ae…burn addressPONS0.21341
0x693debf3…burn addressPONS0.19371
0x5b313163…burn addressPONS0.19091
0xfcb995b2…burn addressPONS0.18821
0xf16976ff…burn addressPONS0.17851
0xa6de3930…burn addressPONS0.12601
0x322ec64e…burn addressPONS0.11431
0x35ffaf2b…burn addressPONS0.09951
0x531ebeb5…burn addressPONS0.05661
0x8366a39c…burn addressPONS0.00381

Registry (witness lines)

roleaddress
fee Safe0x263ed295dafae1d9aadd6e56c4b6f9f38ee019dd
V2 fee escrow0xd3afeb2a57f70ef218aa82451c51b2fb0416ac9e
treasury hop0xcd9107d2bdfad6b56a7ac235bebe46e555c1801c
treasury proxy0x5795d227dcc305afe212bef18e81b111def7c324
deployer / owner EOA0xfdde5a1e3cdf791da71e49f817d70c7ced72cc36
Relay router0xb92fe925dc43a0ecde6c8b1a2709c170ec4fff4f
PONS/WETH V3 pool0x10cc6bd38112cac182db90b6a71d8bb5939526ba
burn address0x000000000000000000000000000000000000dead
burner EOA 10xda4bcee76b29efec9697fcf663601c2042043968
burner EOA 20xf89f3858bc7bac05a83ec284e3e9acdb58bf892a
burner EOA 30x8afc1142f5d3ca6c55bbc8c81d0c9cdf2cce380c
burner EOA 40xb9f5f4ea1af1f5d3678470eb98e8fbdcadeb24b0

This is a prototype from the public RPC; GH-W1-001 §3.15 backfills the same table from the archive node and publishes any discrepancy. The attestation carries no seal: it is an auto-signed chain attestation whose daily Merkle root is hardware-signed (see the verifier's daily roots).