A launchpad to faciliate the creation of HyperQube-powered extension chains on the Zenon Network (Network of Momentum).
Demo deployed at qubepad.vercel.app
This project is a work in progress and still not fully configurable.
- Framework: Next.js 15 with App Router
- Database: Vercel Postgres powered by Neondb
- ORM: Drizzle
- Package Manager: npm
- UI Components: Shadcn UI
- Styling: Tailwind CSS
- Form Handling: React Hook Form with Zod validation
- Data Fetching: SWR
- Automation: Vercel Cron Jobs
-
Clone the repository
-
Install dependencies:
bun install
-
Copy the environment variables:
cp .env.example .env
-
Update the following required environment variables:
DATABASE_URL: Your Postgres connection stringNEXT_PUBLIC_SIGNATURE_MESSAGE_SUFFIX: The suffix message used for signature verification (default: "HYPERQUBE LAUNCH")CRON_SECRET: A strong random string to secure cron job endpoints
-
Push the database schema:
bun run push
-
Start the development server:
bun run dev
The signature message suffix is implemented with a three-tier fallback system:
- Environment Variable: Can be set via
NEXT_PUBLIC_SIGNATURE_MESSAGE_SUFFIX - Code of Conduct Hash: Automatically generated at build time as a truncated SHA-256 hash of the project's Code of Conduct
- Default Value: Falls back to "HYPERQUBE LAUNCH" if neither of the above are available
This implementation ensures message consistency across the application while allowing for easy customization. The Code of Conduct hash option creates a verifiable link between the registration process and the project's community guidelines.
Pillar data is automatically updated from ZenonHub every 12 hours using Vercel Cron Jobs. The system tracks the last update time and displays it in the UI. To enable this feature in production:
- Set the
CRON_SECRETenvironment variable to a strong random string - Ensure the
vercel.jsonfile contains the cron job configuration:{ "crons": [ { "path": "/api/cron/update-pillars", "schedule": "0 */12 * * *" } ] } - Deploy to Vercel, which will automatically schedule and run the cron job
Please note that this project adheres to the HyperQube Code of Conduct. By participating in this project, you agree to abide by its terms.
Built by Aliens