Magic Next.js Passwordless Deployment
Budget: €250 – €750 EUR
I have an unfinished password-less Web3 authentication project built strictly from Magic’s official EVM + Next.js guide. The codebase is already scaffolded in Next.js 14 with TypeScript and Tailwind; what I need now is an experienced full-stack engineer to take it across the finish line and make it production-ready on a Google Cloud VM.
What matters most
• Authentication setup is the priority. The Magic SDK must seamlessly issue auth tokens and wallet keys without traditional passwords.
• We will keep using Magic.link as the wallet provider exactly as the guide recommends—no MetaMask or Coinbase diversion.
• Two roles only: admin and user. Admins will access an internal dashboard; users reach the standard dApp interface.
Scope of work
– Finish wiring the Magic SDK to NextAuth (or the guide’s native hooks) so users can log in with email links and instantly receive an EVM wallet address.
– Ensure Web3.js interactions (e.g., balance checks, contract calls) run correctly under that wallet context.
– Harden the app and deploy it on a Google Cloud VM running Ubuntu, Node.js 18+, Nginx (as reverse proxy with Let’s Encrypt SSL), and PM2 for process management.
– Provide environment-variable templates, CI/CD or simple deployment scripts, and a short runbook so I can repeat the setup on a fresh VM.
Acceptance criteria
1. Email link login creates a session and injected wallet usable in Web3.js calls.
2. Admin route is gated; non-admins are redirected.
3. App is reachable over HTTPS at my domain, proxied through Nginx, served by PM2.
4. A single command (or documented steps) redeploys latest build with zero downtime.
5. All steps remain faithful to the official Magic EVM + Next.js guide—no vendor lock-ins beyond the stated stack.
If this is crystal clear to you and you’ve shipped similar Web3 builds before, let’s get started right away.
What matters most
• Authentication setup is the priority. The Magic SDK must seamlessly issue auth tokens and wallet keys without traditional passwords.
• We will keep using Magic.link as the wallet provider exactly as the guide recommends—no MetaMask or Coinbase diversion.
• Two roles only: admin and user. Admins will access an internal dashboard; users reach the standard dApp interface.
Scope of work
– Finish wiring the Magic SDK to NextAuth (or the guide’s native hooks) so users can log in with email links and instantly receive an EVM wallet address.
– Ensure Web3.js interactions (e.g., balance checks, contract calls) run correctly under that wallet context.
– Harden the app and deploy it on a Google Cloud VM running Ubuntu, Node.js 18+, Nginx (as reverse proxy with Let’s Encrypt SSL), and PM2 for process management.
– Provide environment-variable templates, CI/CD or simple deployment scripts, and a short runbook so I can repeat the setup on a fresh VM.
Acceptance criteria
1. Email link login creates a session and injected wallet usable in Web3.js calls.
2. Admin route is gated; non-admins are redirected.
3. App is reachable over HTTPS at my domain, proxied through Nginx, served by PM2.
4. A single command (or documented steps) redeploys latest build with zero downtime.
5. All steps remain faithful to the official Magic EVM + Next.js guide—no vendor lock-ins beyond the stated stack.
If this is crystal clear to you and you’ve shipped similar Web3 builds before, let’s get started right away.