> For the complete documentation index, see [llms.txt](https://docs.evently.market/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.evently.market/developers/setup.md).

# Setup & Installation

## Prerequisites

* Node.js 18+
* npm or yarn
* A Web3 wallet (MetaMask, Rabby)
* Git

***

## Clone & Install

```bash
git clone https://github.com/eventlymarket/evently.git
cd evently/frontend
npm install
```

***

## Environment Variables

```bash
cp .env.local.example .env.local
```

Edit `.env.local`:

```env
NEXT_PUBLIC_PROFILES_ADDRESS=0x9F0708145BCCD1F5B16F610cB8a75A63fA4A9a24
NEXT_PUBLIC_MARKETS_ADDRESS=TBD
NEXT_PUBLIC_USDM_ADDRESS=0xFAfDdbb3FC7688494971a79cc65DCa3EF82079E7
NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID=your_project_id
NEXT_PUBLIC_SUPABASE_URL=your_supabase_url
NEXT_PUBLIC_SUPABASE_ANON_KEY=your_supabase_anon_key
NEXT_PUBLIC_URL=https://evently.market
```

WalletConnect Project ID: [cloud.walletconnect.com](https://cloud.walletconnect.com)

***

## Add MegaETH to MetaMask

| Setting      | Value                                                    |
| ------------ | -------------------------------------------------------- |
| Network Name | MegaETH Mainnet                                          |
| RPC URL      | `https://mainnet.megaeth.com/rpc`                        |
| Chain ID     | `4326`                                                   |
| Symbol       | `ETH`                                                    |
| Explorer     | [megaeth.blockscout.com](https://megaeth.blockscout.com) |

***

## Run Development Server

```bash
npm run dev
```

Open <http://localhost:3000>.

***

## Build for Production

```bash
npm run build
npm run start
```

***

## Deploy to Vercel

1. Push repo to GitHub
2. Import at [vercel.com](https://vercel.com)
3. Add environment variables in Vercel dashboard
4. Set primary domain to `evently.market`
5. Deploy

***

## Design Tokens

```css
/* Brand colors */
--pink:  #F786C6;   /* Create market accent — use sparingly */
--blue:  #70BAD2;   /* Primary accent, logo "ly", UI highlights */
--green: #6DD0A9;   /* Action color — Buy / Yes buttons */

/* Neutrals */
--page:  #F9F8F5;   /* Page background (light mode) */
--card:  #FFFFFF;   /* Card surfaces */
--t1:    #111113;   /* Primary text */
--t2:    #52525b;   /* Secondary text */
--t3:    #a1a1aa;   /* Tertiary / muted text */

/* Dark mode */
--page:  #0a0a0b;
--card:  #111113;
--t1:    #f0edee;
```

## Typography

| Use            | Font           | Class           |
| -------------- | -------------- | --------------- |
| UI / Headings  | Geist Sans     | default body    |
| Numbers / Data | JetBrains Mono | `.font-numeric` |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.evently.market/developers/setup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.