Skip to content

Latest commit

 

History

History
79 lines (43 loc) · 3.93 KB

FAQ.md

File metadata and controls

79 lines (43 loc) · 3.93 KB

FAQ

How do I deploy this?

Definitely go with what you have previous experience and are comfortable with. Otherwise here are two great choices

  1. Vercel is a great choice because of how easy it is to deploy to. It will allow you to focus on building your app
  2. Fleek is a great web3 native choice that we used sometimes at OP labs. It allows you to deploy both to a CDN and to IPFS with minimal setup with a similar experience to vercel

Note: Getting forge to build on vercel can be a blocker. To make it easier for hackers there is a npm run build:production command that does not build forge before building

You can also just be happy using local host :).

If you have any trouble deploying email [email protected] with a link to your github repo and a description of your issue.

How do I get Optimism Goerli ETH?

See here.

What is the Attestation Station

See here.

I'm not hacking on the Attestation Station. Can I still use this?

Absolutely! It's a great start for any full stack hack project

I'm not even hacking on Optimism. Can I still use this?

You dissapoint us. But yes. With minor tweeks this boilerplate will work on any EVM chain

I need a backend?

You got lots of choices here

  • the graph is the most web3 native way but requires knowledge of graphql
  • TRPC is what we use at OP labs to move fast and would work very well at a hackathon
  • Ponder is a graphql alternative with an aim of better dev experience but is early in it's own development
  • express is the most well documented backend choice

The easiest place to deploy your backend fast and for free are the following

How do I bridge from L1 to L2?

If doing it programatically try using the official optimism sdk. Remember that Goerli must be ran in bedrock:true mode while mainnet must be ran as bedrock:false

Why wagmi

Wagmi is a typesafe library based around React Query that simplifies and speeds up the process of building web3 frontends

Why Forge

Forge is a superfast and robust toolchain that reduces context switching, speeds up development, and tends to be easier to use than alternatives even for JavaScript Devs

Why Vite

Compared to NEXT.js vite is a better choice for a hackathon. It has a faster and better dev server, is simpler, and very easy to deploy since it's build output is just static assets. That said, NEXT.js is also a great choice and we recomend using Wagmi CLI if you believe NEXT.js would be more productive for your project

Why no javascript tests

Bless your heart for writing tests at a hackathon! You are awesome! I recomend using vitest which will work with 0 config and has a nearly identical API to jest

If you want to write E2E tests our recomendation is to try synpress to test with metamask and cypress

Why npm?

NPM is the most minimal tool and we don't want you fighting your tooling at this hackathon. That said, you can definitely consider using pnpm which will speed up your installs. To use pnpm just run npm i pnpm --global and then run pnpm import to transfer the package-lock.json

Why wagmi cli?

Try it out! You will be amazed at how much it will streamline your workflow of going from contract to UI.

Why don't typerrors break the build

This repo uses esbuild to build and treats typechecking as a linting step. This is in general a best practice anyways and it helps you stay productive while hacking without being slowed down by typescript