Sirwin
Sirwin
Week 22 Recap, BUIDL

Week 23 Recap, BUIDL

By Mike Bivens | Journey to Web3 | 17 Jul 2022


This has been a very eventful week! I've got a few announcements sprinkled throughout this week's recap. It was the first week of the BUIDL chapter for my Journey to Web3 and it was full of efforts directed at different projects, community engagements, research, and I even started drafting a couple of great articles to be shared on medium at a later date. As always, please feel free to leave any feedback about any of these components or share your thoughts!

I'm back in the swing of practicing for live coding/algorithm interviews. I've received a lot of conflicting advice about these. I've heard both extreme sides of the spectrum about how prevalent they are in web3 dev interviews. I've been told that every single interview process I will have would include this and then I've been told this practice has been left behind by web3 companies and that I shouldn't expect to have this at all. After hearing both extremes and a handful of answers that fall in between, I've decided it's just best to spend the time practicing algorithms again. I try to fit this in nearly every day but I just don't enjoy it as much as actually just BUIDLing projects.

<usual_enterance> If you're new here I'm creating this blog series as I go from coding newbie to working in web3. I'm creating this to reflect on the technical and non-technical growth and to leave it behind for others who might be interested in how they can follow a similar path. </usual_enterance>

In this week's recap:

  • Supportive Content
  • Alchemy's Road to Web3
  • WAGMI Squad
  • Portfolio Rebuild
  • Road to Web3 Analytics
  • full-blockchain-solidity-course-js Contributions
  • What's Next?

Supportive Content

Reading articles and watching videos to learn, review, and research.

An Introduction to Smart Contracts and Their Potential and Inherent Limitations

  • A Harvard Law Forum article covering an introduction to smart contracts and legal enforceability

What the media is missing about decentralized autonomous organizations

  • A quick look at what mainstream media gets wrong about DAOs

What Are Wrapped Tokens?

  • Helpful for a baseline understanding of what wrapped tokens are and their purpose

Asynchronous Programming: A Beginner’s Guide

  • Very quick refresher on asynchronous principles

How $800k Evaporated from the PoWH Coin Ponzi Scheme Overnight

  • Interesting case study 

Next.js in 100 seconds

Next.js Crash Course

EVM: From Solidity to byte code, memory and storage

  • Great technical discussion on Solidty 

Ethereum Under the Hood: Algorithms And Data Structures - 0xPoland S01E02

  • Technical discussion on Ethereum algos and data structures that I did have trouble following along with at some parts

Alchemy's Road to Web3

The final week's challenge was released earlier this week, and I was able to complete it. This marks the completion of the Road to Web3 and it's challenges for me. 

Week 10 had us building with Lens Protocol to create a decentralized Twitter.

My repo

The tutorial

After completing this, I had a back and forth with Albert (thatguyintech) on Twitter and we're working towards a partnership between Road to Web3 and WAGMI Squad! I reached out in another tweet to elicit feedback about what people would like to see. Feel free to contribute to that conversation as well

I proposed tutorials around building with different protocols and creating a simple analytics dashboard to pull information about NFTs. The responses seemed to lean more towards the former.


WAGMI Squad

So a lot has happened with WAGMI Squad this week. First off, check out the drafted website. I built this first version with Next.js and Tailwind CSS, you'll see the start of our branding profile with the light gold-ish coloring on the logo below which was also agreed upon and finalized this week.

e7009d91c023a5a4d8e85b1987f4b7b459de8d9e51e18ec4482c9df4a2bbc1f7.png

The repo for the website can be found here.

Regarding the components of making WAGMI Squad into an actual DAO (like tokens, reputation, governance) we are deep in the research and drafting for system design. At first in my introduction of WAGMI Squad, I had proposed using an ERC20 as the reputation token and an ERC721 as the access token. The further we got into the research of it, the more we realized that maybe this didn't make total sense. Gas fees are a serious concern as this organization is not focused on building and maintaining a treasury. It would be just plain silly to burden the DAO with these fees when we want to encourage active voting and rewarding members for their contributions. It would just get too expensive.

We also looked into solutions to building the DAO with tools like Colony and Aragon. While those tools could be very helpful in just rapidly building the DAO, they just narrowly miss the mark of our ideal setup. Additionally, building the DAO and learning how to securely build these components is precisely the goal of the organization so it further just makes sense for us to build this from the ground up. 

Right now, we are looking into using a system design somewhat as you see below. With a central governance contract that outlines proposals and voting, while using ERC1155 for role-based access tokens. A general membership token that has upgradeable metadata (particularly for membership status and recording reputation score) with additional tokens to delegate leadership roles that so far include Reputation and Role Administrators.

Please note that this was a very quick draft up of what these contract functions might look like and what they would do that I made to help visualize the system design. Emphasis on draft, I would LOVE to get feedback from more people about adjustments that could/should be made or functions that might have been left out at this point. 

d1c025b011d2611d373bd2ed62ebabd489e7ed1f1c26f4e10a14a08ea584d6cb.jpg

While working through all this system design research and drafting, we're also having conversations about what the Road to Web3 partnership could look like (see the Road to Web3 section). 

We also had an all-members meeting to touch base on the status of the DAO, open projects, and what's coming next. This was definitely much needed for the organization and re-evaluate the status while assessing what changes should be considered.


Portfolio Rebuild

I rebuilt my portfolio website and am in the process of getting away from Host Gator. At this point, I still have my domain registered with them but it's now hosted on vercel. 

The rebuilt website is now a Next.js site that I'm pretty happy with. The home page includes an introduction, a little about me and my journey to becoming a blockend developer, my main tech stack, top projects, linked blogs, organizations I'm a member of, and a contact form. 

ee30a65990f8c6eb8dafec5176952aa60786aa202f21471f6c91346ef78f48ef.jpg

743ad2947c9e714474fecc1b98f1ee838194e3874203d75ceef2a8d61b0f8549.jpg

A secondary page contains my project cards with information about every completed project that I have thus far. 

5f2a7e63f790969be06b3d55ef709f42bc3bef4ebcbc42f413b1fdd63df958f2.jpg

I've still got some work to do on it, but I pushed it to live. I'd like to adjust some styling choices and I've got some ideas for additional pages I'd like to try and build but right now I need to focus my efforts on the other projects I've got open.

The repo for the website is here.


Road to Web3 Analytics

There isn't any code written here but I'm starting the conversation now for this project. The Raod to Web3 Twitter account suggested to me that building a simple analytics dashboard to see some information around on-chain activity of their PoK holders would be interesting. And I agree.

On-chain analytics is something I have a lot of interest in and I had already been thinking about doing a project like this so I figured this opportunity could prove to be a valuable proof-of-concept for the much-larger in-scale project I want to build for TheDrop. I'm partnered up with another developer on this project and we're looking for what our options are in using available APIs to pull the relevant data we are interested in. Hopefully, we can settle on one of the options and start building this soon.


full-blockchain-solidity-course-js Contributions

This would be my first contribution to an open-source project. I'm trying to give back to Patrick Collins' 32 hours course that was very transformative in my web3 dev training by going back through my notes and adding to the documentation for the project with the requested timestamps he's left behind in the issues section of the Github repository. It might not be much but I think it's still valuable to the project and the community trying to learn with the materials he built. 

Here's the repo with the documentation I'm adding the timestamps to.

It's not taking up too much time because thankfully, I had thought about this before while working through the video and made notes. So I just have to confirm those notes and then add the details to the README. I'll probably be done with adding in what timestamps are left by the end of next week as there's a couple others that have contributed to this already.


What's Next?

This next week is going to be just as busy, continuing my usual research activities by reading articles, watching YouTube videos, and listening to podcasts. If you're wondering how I manage to do everything, it's because this is literally all I do with my life. I code and read about others' code. I have never grinded or wanted something in my life as much as I do this. I'm putting in more focused time and dedication to becoming a web3 developer than any other effort in my life. I'll continue to do so even after I've got myself a job as a blockend dev because I want to continue moving to the next level of understanding and capacity for building valuable tools and products with this technology. 

That being said, what else am I doing next week to work towards that? Well, that would include continued algorithm practice, writing articles, contributions to Patrick's course documentation, and building on the open projects like the PoK analytics and WAGMI Squad components. There's a lot of open work with the DAO, more than just the system design and coding, for instance, there's documentation and rules that need to be more formally drafted and building out what the partnership with Road to Web3 would look like.

There's a lot to do, but nothing is going to slow me down this next week. The week after might be a little different though...I have to move halfway across the country and, believe it or not, that actually takes a lot of time and energy.


You can find me here:

LinkedIn | GitHub | Twitter |  Portfolio

How do you rate this article?

1


Mike Bivens
Mike Bivens

Blockend Dev | He/Him Founder of WAGMI Squad & TheDrop https://www.msbivens.com/


Journey to Web3
Journey to Web3

I am using this blog to talk about my experiences from pre-software development boot camp towards entering the Web3 ecosystem. I'll share thoughts and what I'm learning, reflect on the journey, and share informational interviews for others to follow along.

Send a $0.01 microtip in crypto to the author, and earn yourself as you read!

20% to author / 80% to me.
We pay the tips from our rewards pool.