BuidlGuidl / BuidlGuidl/learning-lab
Labs: Deploy a Contract
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 4d 53m
- Merged PRs (30d)
- 6
Description
The third lab in the lineup after 101 and wallets, where the user will deploy a contract.
Some open question as this is built out.
- How much code do we want them writing? I've tried out a couple contracts so far, a vending machine and a crowdfunding contract. Both had them code just about as much as in v1. Do we want that much coding at this stage, it might be early. On the other hand, it's pretty easy coding with obvious examples given at every stage.
- As far as the contract goes, are those appropriate for this lab or do we want something simpler? The deploy is super easy in browser, so i think we stick with one of these contracts so there will be more meat to this lab. Very open.
- And lastly, we made them leave the browser to create a wallet in the lab just before this. I would think we should have them interact with the contract outside our lab here as well. Doesn't make sense to have them create the wallet and not use it in this step as well, but maybe we leave the deploy process easy and in browser for now. Open to thoughts on this.
Added some new branches for a quick vibe check, obv not linked anywhere. These are all in browser with no outside interaction, which probably should change. Note these were created with Fable, so I don't like 80% of the topic/card names, and I'll do a full copy re-do when we lock down what's the right move, but the process/flow the user goes through is what I could use some thoughts on.
[Vending Machine](https://github.com/BuidlGuidl/learning-lab/tree/labs-deploy-vending)
[Crowdfunding](https://github.com/BuidlGuidl/learning-lab/tree/labs-deploy-crowdfinding)
Contributor guide
Research direction
Start by reviewing the labs-deploy-vending and labs-deploy-crowdfinding branches linked in the issue, comparing their browser-based lab flows. Read through the existing branches and the preceding wallet lab to understand the intended progression. Done means the contract example, amount of coding, and wallet interaction are decided and the lab flow is finalized for integration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- blockchain, content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100