We were looking at potential ways to use GPT in Cookbook and found an interesting user pain-point in the process.
Some context: Cookbook is a web3 developer tool that aggregates smart contracts and provides metadata, documentation, security reports, and integration tools to use these smart contracts in your project.
As we've been building Cookbook, we realized that most smart contracts running in production have incomplete documentation, or lack detail.
We put together a quick MVP for docs generated GPT3.5 and the results are pretty promising. While they definitely can have issues, on the whole, they seem to do a good job filling in empty documentation, and provide an accurate description of the code.
We'd love to try:
- generated testing suites
- generated security scans
- no-code smart contract creation
Would love to get your thoughts and feedback on how we can make this a more useful feature. Looking forward to getting it running with GPT4!
Some context: Cookbook is a web3 developer tool that aggregates smart contracts and provides metadata, documentation, security reports, and integration tools to use these smart contracts in your project.
As we've been building Cookbook, we realized that most smart contracts running in production have incomplete documentation, or lack detail.
We put together a quick MVP for docs generated GPT3.5 and the results are pretty promising. While they definitely can have issues, on the whole, they seem to do a good job filling in empty documentation, and provide an accurate description of the code.
We'd love to try:
- generated testing suites
- generated security scans
- no-code smart contract creation
Would love to get your thoughts and feedback on how we can make this a more useful feature. Looking forward to getting it running with GPT4!