-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: IdlBuffer Program #7393
Comments
I think this is a great idea, especially if it was standard via the Solana/agave tooling. Having all programs upload their idl will boost comparability for programs |
It might be interesting to consider some version pairing constraints. Imagine you store your program's version in the ELF header instead, and then when you register the IDL with You could also - in the future - maybe outfit the In either case, the tricky part is for |
@buffalojoec updated the spec to incorporate the versioning feedback: https://solanafoundation.notion.site/Program-Metadata-128d36dad52d801e974fcc3a30736506 |
I think it's better to leave the IdlBuffer unopinionated for now (storing only authority & bytes) & allow developers to figure out versioning systems - like just getting Relevant: https://discord.com/channels/428295358100013066/1295768706806321264/1298759290525319189 |
There has been some issue with supporting IDLs in the program binary via a new ELF header section, versus officially supporting IDLs in PDAs.
Given that Anza is prioritizing changes to make program binaries smaller & more efficient to load, it seems like officially supporting the IDL in PDAs is better for cluster performance.
Good place to start would probably be to copy the
IdlInstruction
s from anchor's injected macros.I think it would be awesome if uploading IDLs to this program was natively supported in
solana program deploy
as wellThe text was updated successfully, but these errors were encountered: