byont-ventures / hackathon

This workshop will be about getting your hands dirty in the web3 space by creating your first NFT project! This project will be initially divided into three tracks - frontend, backend, and stretch challenges.

Web3 Workshop

This workshop will be about getting your hands dirty in the web3 space by creating your first NFT project! This project will be initially divided into three tracks - frontend, backend, and stretch challenges.

How the workshop will work

The workshop is a collection of coding challenges to familiarize you with web3 development in general. It is not a complete tutorial, as that is too much to learn in one day, but it is an excellent primer to grasp the overall concept.

We've designed each coding challenge to be more complicated than the previous one. Remember that sometimes there are multiple ways to get to a solution. We encourage you to look things up online or ask questions if you are lost. We will be sharing helpful resources with you throughout this course.

We'll also host a #workshop channel on our Discord server, where you can ask questions and get help from the workshop facilitators and other participants. We will also be sharing resources and links there.

You can refer to the accompanying presentation for more information about the workshop in general on Canva.

We have also included a glossary that includes terms that are often used in the crypto-space, along with their explanations.

The different tracks

In the backend (or smart contract) track, you will learn how to create an NFT smart contract using a new programming language and development framework. The frontend track builds on your existing knowledge and shows you how to view, interact, and mint NFTs using Next.js (13).

You can refer to the stretch challenges if you're already familiar with web3 development or need a more significant challenge. You may also start with the stretch challenges immediately if you are working in teams. In that case, try the challenges of your respective track before the workshop.

Getting started

Below you'll find the different tracks, but we recommend that all participants first go through the Workshop Preparation guide, which will help you set up your development environment and explain the core concepts of web3.

• Workshop Preparation
• Frontend Challenges
• Backend Challenges
• Stretch Challenges
• Glossary

About Byont Labs

Byont Labs is a blockchain development studio that specializes in building decentralized applications. We are a team of developers, designers, and blockchain enthusiasts passionate about creating the future of the web.

Feedback

We've prepared and tested this workshop thoroughly, but there will inevitably be some unclear documentation, misbehaving configuration, and typos. If you find anything, have any feedback, or want to share your findings, feel free to create an issue on Github or let us know on Discord.

hackathon's Issues

Add glossary for crypto dummies

We've received feedback that terms such as mint are unfamiliar and could use some explanation

Smart contract deployment command not able to verify

running from backend folder:

FOUNDRY_PROFILE=challenge-12 forge create \
  --rpc-url <rpc_url> \
  --private-key <private_key> \
  --etherscan-api-key <etherscan_api_key> \
  --verify \
  contracts/challenge-12/src/Challenge_12.sol:Challenge12 \
  --constructor-args "NFT Example" "NFTEX" 100

Error logs:

Submitting verification for [contracts/challenge-12/src/Challenge_12.sol:Challenge12]
"0xeD297cd9016Ae8832Abc8E815978F4552Db762bd".
Submitted contract for verification:
Response: OK
GUID: bcy8bqwajizywag74w1phceejzidlam3svhmd7xq5qwznb823c
URL:
https://goerli.etherscan.io/address/0xed297cd9016ae8832abc8e815978f4552db762bd
Contract verification status:
Response: NOTOK
Details: Pending in queue
Contract verification status:
Response: NOTOK
Details: Fail - Unable to verify
Contract failed to verify.

The contract deploys but verification fails

Refer to IPFS browser more often

In (i believe) challenge 11 we introduce IPFS, in the prerequisites we mention ipfsbrowser.com as a no installation alternative. Perhaps we should repeat this in challenge 11 as people seem to forget this

Some components in frontend do not exist

See attached screenshot:

File: testpage.tsx

npm run build will fail.