I opened Solana Explorer today and searched for the Jupiter v6 program.
What I saw surprised me.
It is marked Executable: Yes, has a balance of 6.19 SOL, and its actual bytecode lives in a completely separate account called Executable Data. The program itself holds no state at all.
That is Solana's account model in one screenshot. The logic lives in one account. The data lives somewhere else. They are never mixed.
Coming from Web2, this felt strange at first. Now it feels clean.
This is Jupiter's live transaction history on Solana Explorer.
Failed. Failed. Failed. Success. Success.
At first I thought something was broken. Then I read the instruction names. The failed ones are all trying to create token accounts that already exist. The successful ones are simple SOL transfers.
This is normal. Programs attempt things optimistically and fail fast. Failed transactions still cost a small fee. The network does not hide any of this. Everything is public and permanent.
This caught me off guard.
Jupiter's upgrade authority is not a single wallet. It is a Squads V3 multisig with 7 members and a 4 of 7 approval threshold.
That means 4 out of 7 keyholders have to sign before anyone can push an update to the program that handles billions in DEX volume.
You can verify this yourself on Solana Explorer. No trust required. Just a public address and the data it holds.
That is the whole point.
address: JUP6LkbZbjS1jKKwapdHNy74zcZ3tLUZoi5QNyVTaV4
Top comments (0)