🧵 → So you’ve started using Foundry and you’re deploying a contract that requires you to load structured data - arrays, structs, etc. - into a contract (to render NFTs on-chain, for example). How do you do it?
If you're borrowing or lending on Blend, you can now subscribe to get notifications. Stay updated on key events such as when your loan gets refinanced, when lenders initiate an auction to exit your loan, or when you get repaid.
🔔https://t.co/bCTUb2iDkB
🔔https://t.co/Mp5nBI1cNC
🧵-> Uploading data to the Ethereum blockchain is expensive. While it's uncommon to see, you can actually compress your data before uploading it, significantly reducing your storage costs. So how do you do this?
It's worth noting compression algorithms are good at getting rid of redundancy (e.g. long repeated patterns), so not all data will benefit from this approach. So it's probably worth compressing your data first and seeing if the size difference is significant.
@0xAlcibiades@fmnxl One case where you could use this is if you are writing an NFT contract where the images are generated on chain. You could store each of the constituent parts on the contract. But more broadly, this applies to any contract that you need to upload data to
🧵 → So you’ve started using Foundry and you’re deploying a contract that requires you to load structured data - arrays, structs, etc. - into a contract (to render NFTs on-chain, for example). How do you do it?