Public apology to the world: it was me. I used Fable to generate codama renderers for Lua, PHP, Ruby, and Python. The government has now sunset Fable. I understand their decision. @solana powers were never meant to be PHP.
Repo links below
Solana Kit 6.9 is out.
This version adds fixed-point number support and a first-class Sol type.
Exact decimal and binary math in JS for token balances, prices, anywhere rounding errors are unacceptable.
Plus more shipped in this release 👇
In the age of AI slop, some of us are still making things by hand, I promise ❤️ Octocat for the new GitHub Copilot App was modeled, rigged, and animated in Blender...
@b_migliaccio@grod220 That’s why you should create your own. It’s pretty easy to setup agent loops with custom tools and memory strategies and it feels like coding with magic. ☺️
@redacted_noah@SolPlay_jonas@toly I would love to join that meeting. I’ve asked Jonas to invite me but I’m not sure when it is exactly so I can’t say for sure yet. 🤞
I would go further and add that there is a matrix of versions to worry about. There is the version of the IDL standard you use and there is the version of the program itself. The IDL itself has all of that information which is now fully onchain meaning you can technically index that program and access that historical metadata. But even if that was not desired and you wanted to have multiple IDL versions accessible onchain directly, PMP is a primitive that allows you to create such “historical IDL” standards. You can even store that standard in a brand new program and have it linked on PMP for discoverability.
I fail to see why it’s “too late” or how PMP introduced an opportunity cost. If you have a strong feeling that an IDL versioning standard would lift the Solana DX then we should totally work towards one together.
Are you using Kit plugins?
If not, you really should be. Plugins (and plugin clients) enable interoperability among JS clients, allowing them to seamlessly work with different Solana programs and tools.
Just load a program and send a transaction in two lines — auto PDA derivation, no manual serialization.
This is a nice improvement to the Solana Kit developer experience (more on the way).
Kit Plugins: https://t.co/SY7fXztVZb
Also added to our Solana Development Skill 👇
@callum_codes@yongfook I inject frontmatter to my prompts so it has more context about the human behind the prompt (amongst other things like the exact time, the communication channel being used and the attachment URLs so it can save attachments instead of just viewing them).
Just watched it! Token 2022 is a beast haha.
Looks like an issue on the written Codama IDL which should use a size-prefixed empty struct just so we have two bytes of 0 after the extension discriminator. I might play with using a hidden constant instead so you still don’t need to pass an empty object on the API.
Looks like “confidentialMintBurn” is also constructed that way so I’ll take a look at both.
I’ll keep you posted.