Guides
Supported files IDLs and compiled programs
Byteatlas accepts two kinds of input: a Solana IDL in JSON, or a compiled program binary
Updated
Formats
| File | What it is | Good for |
|---|---|---|
.json | An Anchor IDL describing the program's interface | The clearest picture of instructions, arguments and accounts, as the program's authors defined them |
.so | A compiled Solana program binary | Exploring a program when you only have what is deployed. Accepted today; full binary analysis is coming soon |
Anchor IDL versions
Both IDL generations open. Newer IDLs (Anchor 0.30 and later) use writable, signer and pda with seeds, and carry the program address. Older IDLs use isMut and isSigner. Byteatlas reads either and shows them the same way
- Seeds are shown when the IDL declares them, as constants, account paths or argument paths
- Nested account groups are flattened, so a grouped account appears as group.account
- Argument types are written out plainly, for example Vec<u8>, Option<pubkey> or [u8; 32]
Exploring without source code
You never need the program's source. Byteatlas works from the information available in a supported IDL or compiled binary, so you can explore programs you didn't write
Your file stays on your machine
Files are read in your browser. Nothing is uploaded to a server, so you can open IDLs and binaries for programs that aren't public yet
Opening a file
- Launch the app and use Upload program to choose a file
- One file at a time. Opening another file replaces the current program
- There is no fixed size limit. Files are read in memory, so very large binaries take longer
- Unsupported files are turned away with a reason before anything is read