Type Safety & ABI Caching with thirdweb Generate
Let's dive into what it is, why we built it, and how you can get started.
Background - Our SDK and ABI Management
This abstracts away the complexity of copy-pasting smart contract ABIs, and saves you the headache of ensuring your ABIs are up-to-date with the latest version.
Learn more about how this works from our engineering team's blog post:
The trade-off to this approach is that the SDK doesn't know your contract ABIs at build-time; meaning your IDE doesn't know what functions, arguments, and return values your smart contracts have while you're developing.
As a developer, there's a lack of type-safety and little IDE support when working with your smart contracts that don't conform to common standards like ERC721, ERC1155, ERC20, etc.
In addition to this, apps using these functions were waiting for the SDK to fetch the ABI each time they called
getContract with our SDK; making the performance slightly slower on each new request than if they just provided the ABI upfront.
Introducing thirdweb Generate
- Detects all smart contract addresses in your project
- Fetches the ABIs for each address
- Caches them in memory (inside
- Provides type safety for smart contract interactions on:
contract.callin the Typescript SDK
useContractWritein the React SDK
This provides better performance in your application and a safer developer experience when working with your smart contracts.
Get Started with Generate
To get these benefits, all you need to do is use our CLI to run the
generate command from within your project directory:
This will create a
thirdweb.json file at the root of your project which you can update with any new contract addresses you want to cache in the future.
View the full reference and available options in our documentation:
Here's a demo of the benefits you'll get out of the box: