Safe Wallet Pro – Vercel Context
Documents deployment configuration and environment setup for a Safe{Wallet} dApp on Vercel.
What this file does
Documents deployment configuration and environment setup for a Safe{Wallet} dApp on Vercel.
When to use it
- Deploying a Safe{Wallet} integration to Vercel
- Setting up environment variables for a Safe dApp
- Configuring the Safe App manifest file
- Syncing CI/CD workflows with Vercel settings
Assumes this stack
Safe Wallet Pro – Vercel Context
This document provides deployment context and configuration guidance for the Safe Wallet Pro project.
It is intended for Vercel AI Agents, developers, and contributors to ensure proper setup and deployment.
📌 Project Overview
-
Name: Safe Wallet Pro
-
Type: Safe{Wallet} integration + dApp (frontend + backend)
-
Main Signer Address:
0xFDf84a0e7D07bC56f7De56696fc409704cC83a24 -
Core SDKs:
@safe-global/protocol-kit@safe-global/safe-core-sdkethers.jsorviem
-
Key Features:
- Safe transaction management
- WalletConnect + Reown integration
- Contract verification + Safe App manifest
- Automated deployment from GitHub to Vercel
🚀 Deployment Guidelines
Build & Output
- Framework: Next.js (or Vite if specified in
package.json) - Build Command:
npm run build - Output Directory:
.next(for Next.js)dist(for Vite)
Environment Variables
Set these in Vercel Dashboard → Project → Settings → Environment Variables:
NEXT_PUBLIC_ALCHEMY_API_KEY→ RPC provider key (Alchemy, Infura, or custom)NEXT_PUBLIC_SAFE_APP_URL→ deployed app URLNEXT_PUBLIC_SIGNER_ADDRESS→0xFDf84a0e7D07bC56f7De56696fc409704cC83a24
Safe App Manifest
- The app manifest must be deployed at:
/public/safe-app.json
Example minimal safe-app.json:
{
"name": "Safe Wallet Pro",
"description": "Safe{Wallet} integration dApp with contract verification",
"iconPath": "logo.png",
"safeAppsSdkVersion": "1.6.0",
"accessControl": {
"type": "domain",
"value": "safe-wallet-pro.vercel.app"
}
}
✅ Notes
- Always bump the version tag (
vX.Y.Z) before publishing a release. - Ensure CI/CD workflows (GitHub Actions + Vercel) are kept in sync with these settings.
- For local testing, also include
http://127.0.0.1/#in your configuration.
What's inside
4 sections: project overview, deployment guidelines, environment variables, and Safe App manifest example.
Change this for your project
- Replace
0xFDf84a0e7D07bC56f7De56696fc409704cC83a24with your signer address - Replace
safe-wallet-pro.vercel.appwith your deployed domain - Replace
NEXT_PUBLIC_ALCHEMY_API_KEYwith your own RPC provider key
Where it goes
Keep it in your repository where the agent or team that needs it will read it.
Related Documents
Zig 0.16.0 Context Document for LLMs
Documents breaking changes from Zig 0.13/0.14 to 0.16.0, covering syntax, I/O, build system, and standard library updates.
绘制对比图片 KITTI
Documents the topic remapping and data flow needed to connect Fast-LIO2 frontend with SC-PGO backend for KITTI evaluation.
Beads Workflow Context
Guides when to use bd graph-based issue tracker versus TodoWrite for session vs multi-session work, with commands and workflows.
EPIC: usda-data-crush-stats
Maps a multi-year USDA grape crush data pipeline from raw downloads through bronze, silver, and gold layers to final CSV fact and dimension tables.