Treasury

Coming back is easy to announce and hard to prove, so this is the proof. Every lamport, in order, each row linked to the transaction behind it. Unresolved items appear here too — a log that is always clean is not a log worth trusting.

On-chain data, as of just now

Balances

Claimable fees: -- SOL
Solana treasury: -- SOL
Ethereum vault: 0 ETH
Unresolved in the log: 0Operations recorded but not yet confirmed. This counts what the log shows, not what a bridge watcher has checked — that does not exist yet, and this figure would not know about an arrival that matched nothing.

Accounting

Gross fees claimed: 0 SOL
Paid to lockers35% of every claim, paid in SOL to holders who locked the token. The other 65% funds acquisition.: 0 SOL
SOL bridged out: 0 SOL
ETH received after bridge fees: -- ETH
ETH spent on Rebels: 0 ETH
Gas and bridge costsPaid by the Night Labs operations wallet, not from fees. Shown separately so the 65%-to-acquisition figure stays honest.: -- ETH

Operation log

Chain verified

1 entry, each carrying the hash of the one before it, unbroken from the first. Any edit, deletion or reorder would break this and it would say so.

All treasury operations, most recent first
Type	When	In	Out	Status	Source	Destination
NoteOperation log initialised. Supabase table created with append-only triggers (UPDATE/DELETE/TRUNCATE rejected for all roles including service_role) and RLS granting anon read only. This is the genesis entry.	1 day ago	--	--	confirmed	--	--

The log is append-only. Corrections are added as compensating entries; nothing is edited or removed.