tysehr37

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!

Thank you! That's our goal. We want to make building in Web3 significantly faster and easy with Cookbook.

Software engineers tend to follow demand, with some lagtime. Since crypto goes through these manic bull/bear cycles, demand dramatically spikes and falls. Hard to make a career change when the next bear cycle can wipe out your prospects. As crypto stabilizes, there should be a wave of immigration into web3 engineering. You can already kind of see who these engineers will be, they're often the web2 developers who just happen to be working on web3 projects (and don't know solidity)

Someone was actually building a decentralized commodities exchange, and used a couple of Cookbook contracts to build out their infrastructure

We work with SMBs and Startups for advanced contracts, analytics and tooling. That's really how we're able to sustainably keep Cookbook free for individual developers

It really depends on what you're after, we do have a widget to embed web3 functions into any site, it's in early beta.

Definitely plans to support different smart contract languages over time. For the short term we're focusing on Solidity as most web3 devs use it.

This is exactly it. The way to think about it is that smart contracts are effectively server-side code that is specialized to run on blockchains. They use many of the same building blocks and can often be reused. When I want to build Auth in Nodejs, I might use Passport.js, and I often use Express.js. Often I'll use mongoose.js as well. That's effectively what we're providing with cookbook, a way to find and utilize solidity packages created by the community.

thank you!!

Many of the contracts have their audits listed, you can read through the audits to see whether its safe to use or not. But as always, you should make sure to do your own testing before deploying to production.

The majority of web3 developers only just recently entered the space, and are looking for simpler tools. We discovered this from a long series of interviews. The goal is to build cookbook in a web2 dev accessible way, and present all of the stats and audits and information so that they are more able to make dapps.

Feel free to request one or contribute one, we're adding new contracts every day