SDK
IDL & Programs
Bundled IDLs and raw Anchor program access for cases where the higher-level SDK surface is not enough.
SDK
Raw programs and bundled IDLs
Most integrations should start from DumpsterClient. Drop to IDLs and raw program instances only when you need lower-level control.
Import bundled IDLs
The bundled JSON IDLs are useful for:
- custom tooling
- raw account coder access
- external code generation
import {
dumpsterIdl,
dumpsterFeesIdl,
dumpsterSwapIdl,
} from '@dumpster-cash/dumpster-sdk';Get raw Anchor program instances
The raw program factories are useful for event parsing, coder access, or custom flows not wrapped by the higher-level SDK yet.
import {
getDumpsterProgram,
getDumpsterFeeProgram,
getDumpsterSwapProgram,
} from '@dumpster-cash/dumpster-sdk';
const dumpsterProgram = getDumpsterProgram(connection);
const dumpsterFeesProgram = getDumpsterFeeProgram(connection);
const dumpsterSwapProgram = getDumpsterSwapProgram(connection);Good reasons to use raw programs
- parse logs with
EventParser - inspect account layouts with the Anchor coder
- prototype a new instruction before adding a typed SDK wrapper
- verify low-level account metadata during debugging
Good reasons to stay on DumpsterClient
- trade previews
- instruction building
- PDA derivation
- account fetching
- transaction assembly
Add a wrapper once the flow stabilizes
If you find yourself repeating the same raw-program sequence across multiple apps or scripts, that is the right moment to promote it into the SDK surface.