Throwing errors in assembly is a simple way to further improve your gas costs. The following snippet shows two contracts performing the same data validation, one using solidity and another one using inline assembly, where the latter is more optimal than the former 👇
Storage buckets allow you to point to explicit storage slots of your choosing, not relying on the compiler to perform such task.
A great pattern if you want to avoid painful situations where a contract's storage might get corrupted during an upgrade👇
Packing structs can make gas costs reduce dramatically, but did you know you can access packed structs efficiently using inline assembly?
Here's an easy example, where data is accessed and cleaned using yul, efficiently obtaining the stored values:
DM us if you want to get your protocol's gas costs reduced by our top-tier researchers🫡
Exciting news! 🎉 We are very happy to have contributed to the launch of Reental's new utility token. Turing Consulting has been fortunate to have been able to assist our partners in the design, conception and stress testing of their $RNT token.
In this new economy, tokenization is moving towards sophistication, and it is increasingly important to build solid tokenomics that strengthen and generate value for companies, but above all for users, who are the center and the key of the web ecosystem3.
Congratulations to the entire Reental team for the launch ! 🚀