---
# System prepended metadata

title: RaidGuild Adventures (WIP)

---

# RaidGuild Adventures (WIP)
An exploration into a new org structure that fits with the legal wrapper initiatives 

![image](https://hackmd.io/_uploads/SyyVzeQ6Jl.png)

This Focuses on the three pillers of RaidGuild 

- Dev Firm/Service DAO
- Cohort (education and onboarding)
- Adventuring (incubation)

Mainly it is introduing and intgrating the cohort and adventuring system into an already function Service DAO. Its goal is to create a structure the helps incubate new Service DAOs to add an angle of scale, where we have hit some limits with the current system. This takes advantage of the new legal structure that can allow charging for services, making and distributing revenue to members.

## Introduction

### ✨ Vision & Purpose

Raid Guild is evolving into a decentralized incubator network—a member-owned system for launching, supporting, and spinning out autonomous edge-tech ventures. Instead of acting like a traditional venture fund or dev shop, we now function as an internal economy: a network where contributors fund and build new projects through shared ownership, internal signals, and seasonal coordination.

Our goal is to create a thriving ecosystem where:
- Builders can go from learning (Cohort) to launching (Incubation) to leading (Independent Ventures)
- Value stays aligned with contribution, not speculation
- Tokenized projects grow from inside the network, supported by committed members

This model supports rapid experimentation, shared accountability, and long-term alignment—while staying nimble enough to evolve with the space.

---

### 🌀 Network Philosophy

We believe:
- The best ventures come from the inside
- Everyone in the network should have a voice in where resources go
- Budgeting is a signaling process, not a fixed allocation
- Tokens should be earned and used, not bought and flipped
- Contribution, not capital, is the foundation of ownership

---

### 🧱 Key Principles

**1. Closed Internal Economy**  
We coordinate capital internally using Allocation eXecution Entitlements—**AXEs**—instead of raising external funds. No presales to outsiders. No speculative token launches.

> 🪓 **Why AXEs?**  
> In the lore of Raid Guild, an AXE is more than a weapon—it's a pledge of loyalty, a commitment to action, and a symbol of readiness to shape the future. 
> 
> AXEs (Allocation eXecution Entitlements) represent your power to influence the direction of the Guild. Inspired by the iconic "You have my axe" moment in Lord of the Rings, AXEs signal that you’re putting your weight behind a project or initiative. 
> 
> They're non-transferable, earned through dues and contribution, and used to support what matters most inside the Guild. 
> 
> Use them wisely. Wield them proudly.

**2. Incubation as the Core Engine**  
Members can propose and participate in projects. Projects receive internal support through AXE-based presales, and successful ones may spin out into independent ventures.

**3. Seasonal Rhythm**  
We move in defined seasons. Each season includes member dues, AXE allocation, internal project presales, governance checkpoints, and deliverable reviews.

**4. Decentralized, Not Detached**  
We prioritize contributor autonomy while maintaining collective coordination. Participation is flexible, but membership carries responsibility.

**5. Exit-Ready by Default**  
Projects that gain traction and show internal demand can "graduate" into fully independent entities, with 10% of their token supply or value retained by the Guild.

---

This is not a roadmap—it’s an open system. A set of tools and rituals. A new way of organizing that values experimentation, shared incentives, and decentralized ownership.



## Internal Economy

### 🪓 AXEs (Allocation eXecution Entitlements)

AXEs are the lifeblood of the Raid Guild internal economy. They are non-transferable, non-financial governance credits that empower members to allocate budget support to incubated projects.

AXEs are:
- 🛠️ **Earned** through dues, contributions, and optional compensation
- 🎯 **Used** to support internal project presales
- 🧱 **Non-transferable** and carry no promise of financial return
- 🔁 **Reallocatable** (before budget lock-in) if a member changes their mind

AXEs are not tokens. They are internal coordination tools that reflect conviction, not capital.

---

### 🔁 How AXEs Are Earned

Members can receive AXEs in multiple ways:

1. **Quarterly Dues**
   - Members contribute 0.01–1 ETH per quarter (flexible range)
   - The more you contribute, the more AXEs you earn

2. **Guild Contributions**
   - Completing work for the network (e.g. governance, cohort mentorship, RIPs)
   - Members may opt to receive part or all of their compensation as AXEs

3. **Seasonal Rewards or Bonuses**
   - Top contributors, reviewers, or mentors may receive bonus AXEs at the end of a season

---

### 🧪 Using AXEs in Internal Presales

Each project in incubation may offer a limited-time presale in exchange for AXEs. This:
- Signals member belief and prioritization
- Helps determine budget allocation for the season
- Assigns **Project Points** to members who contribute

These Project Points may later:
- Be used for project-specific governance
- Unlock access to project services or tools
- Convert to tokens if the project exits into independence

---

### ♻️ Reallocation & Refunds

If a member changes their mind after allocating AXEs to a project:
- They may request a reallocation (if the project hasn't locked funding)
- Project Points can be returned for AXEs
- Returned AXEs can be used to support other incubations

Cooldowns or slippage may be applied to discourage constant flipping.

---

### 🧭 Seasonal AXE Cycle

1. **Dues & Contributions** → earn AXEs
2. **AXE Presales** → allocate to internal projects
3. **Project Budgets Finalized** → top signaled projects receive funding
4. **Build Phase** → contributors earn Project Points for their work
5. **Exit or Sunset** → successful projects may convert Points into tokens; Guild retains 10% of supply or value

---

This economy is not speculative. It is expressive.
It’s how we wield our AXEs to build what matters.

![raidguild_internal_economy_flowchart](https://hackmd.io/_uploads/rJi4a1mayx.png)


## Member Roles & Progression

### 🧙 Path to Membership

Raid Guild is a meritocratic, lore-driven organization where membership is earned through participation, not bought. All members begin their journey through **Cohort**, our onboarding experience and rite of passage.

**Membership Tiers:**

- **Community Member** – Graduates of Cohort. Can contribute, earn AXEs, and participate in project teams.
- **Core Member** – Trusted contributors who maintain voting rights, mentor others, and shape the direction of the Guild.

To become a Core Member:

- Complete the Cohort
- Perform one Community Service (mentorship, project review, RIP, etc.)
- Be nominated or validated by existing Core Members

---

### 🛠️ Responsibilities of Core Members

Being a Core Member is both a right and a responsibility. To retain voting rights and active status, members must:

- Pay dues (0.01–1 ETH per season)
- Complete at least one service per season:
  - Mentor a Cohort participant
  - Write or review a RIP
  - Support project due diligence
  - Participate in governance or incubation

Failure to complete a service for one season moves a Core Member to "Non-Voting." Inactivity for a full year reverts them to Community Member status.

---

### 📜 Rights of Core Members

Core Members may:

- Vote on Guild-level proposals and RIPs
- Allocate AXEs to incubated projects
- Propose and participate in incubations
- Access internal tools and funding support
- quarterly dividends based on revenue created by projects and legal governance chares 



Core Members receive **Shares** (voting) and **Loot** (non-voting) in the onchain DAO when dues are paid. These are tracked transparently via a Moloch DAO contract and used alongside AXEs to govern Guild resources. Detailed mechanics of the onchain ledger and treasury governance will be covered in the Governance & Budgeting section.---

### ⚔️ Culture of Participation

This model only works when members show up. We are a guild, not a gig platform. Voting is earned. Incubation is built on trust. Holding AXEs means you are ready to shape the future of the network—not just benefit from it.

Everyone works. Everyone fights.

---

### 🌀 Rejoining the Core

If a member has become inactive or stepped back from Core status, they may reapply by:

- Paying dues again
- Performing a service
- Receiving confirmation from at least one Core Member or coordinator

Guild life is seasonal. You can step away and return. What matters is that when you return, you return with your axe.

![raidguild_member_roles_flowchart](https://hackmd.io/_uploads/B1ITA1mTkx.png)


## Governance & Budgeting

### 🗳️ Dual-Layered Governance

Raid Guild governance is coordinated through a hybrid model:

- **Onchain DAO contracts** (Moloch DAO) for legal share management and treasury control
- **AXEs** (Allocation eXecution Entitlements) for flexible, off-chain budgeting and internal coordination

This structure blends **legal accountability** with **creative flexibility**, giving members both formal voting rights and expressive allocation power.

---

### 🧾 Shares, Loot & Transparency

When a Core Member pays dues, they receive:

- **Shares** (voting power on proposals, with responsibilities, used for dividends)
- **Loot** (non-voting economic share, used for dividends)
- **AXEs** (internal allocation power for project support)

These are recorded transparently via a Moloch DAO smart contract, creating a verifiable ledger of:

- Active membership
- Voting rights
- Treasury distribution eligibility

If a Core Member fails to meet seasonal responsibilities (dues + one service), their **Shares convert to Loot**, retaining dividend rights but removing governance power.

Members may also **voluntarily convert Shares to Loot** if they wish to remain passive.

Any member may **burn their Shares and/or Loot to exit** and receive a **fair share of the current Dividend Treasury**. Partial exits are allowed.

---

### 💰 Dual Treasury Design

Raid Guild operates two separate onchain treasuries:

1. **Budget Treasury** – Used to fund incubated projects based on AXE-weighted support. Allocation is executed by Shareholders as a seasonal duty (ideally automated).
2. **Dividend Treasury** – Accumulates revenue from incubated projects (e.g., % of income or token value). Distributed quarterly to all Share and Loot holders based on proportion.

This structure separates contribution-driven budgeting from reward-based revenue sharing.

---

### 🪓 Budget Allocation via AXEs

At the beginning of each season:

- Members receive AXEs based on dues and contributions
- Projects open **AXE presales** to request budget support
- Members allocate AXEs as signals for which projects to fund

The Guild then reviews the **AXE-weighted signals** and distributes ETH from the Budget Treasury to top-supported incubations.

AXEs do not reset each season. They carry forward, allowing long-term conviction and enabling signal reallocation when needed.

---

### 💸 Dividends & Revenue Sharing

Each quarter, a portion of revenue generated by incubated projects (suggested: 5–10%) is directed into the **Dividend Treasury.**

- **Share and Loot holders** receive a proportional distribution from this pool
- Distributions may occur as ETH, stables, or streaming rewards
- Loot allows financial participation without governance responsibility

Exiting members burn their Shares/Loot and receive a corresponding share of the Dividend Treasury.

---

### 🧠 Project Budgeting Lifecycle

1. **Season Starts** – Members pay dues, earn AXEs
2. **Incubations Pitch** – Projects announce presales and goals
3. **AXE Allocation** – Members signal support with AXEs
4. **Treasury Release** – ETH allocated proportionally to top-supported projects
5. **Build Phase** – Project teams report milestones and results
6. **Review & Exit** – Projects may continue, exit, or sunset

---

### 🔐 Snapshot & Voting Mechanics

Formal DAO votes are taken via Snapshot or onchain proposals. These include:

- Electing new Core Members
- Updating legal or treasury policies
- Approving RIPs (RaidGuild Improvement Proposals)
- Project exit events

Each vote is weighted by **onchain Shares**. Loot holders do not vote but receive financial participation.

---

This governance system enables a **living network**: expressive, transparent, and accountable—without becoming bureaucratic. Members show up with their axes, and their shares ensure the weight of their voice is felt.

![raidguild_gov_budget_flowchart](https://hackmd.io/_uploads/S1E3n1Qpkx.png)



## Incubation Flow

### 🧪 Incubation Philosophy

At Raid Guild, incubation isn’t a service—it’s a path to autonomy. We believe the best projects emerge from within, when aligned builders explore bold ideas with support from a trusted network.

Incubation is not about gatekeeping. It’s about:
- Reducing risk with early support
- Creating alignment through internal ownership
- Testing viability through internal budget signals
- Preparing successful projects to graduate with independence

---

### 🛠️ Launching an Incubation

To propose a new project for incubation, a team must:
- Include at least one active Core Member
- Submit a short proposal (can be informal at first)
- Outline purpose, value proposition, potential utility of internal token or reputation system
- Optionally request feedback from members before launching a presale

Proposals may be shared in Discord, on Snapshot, or via RIPs depending on maturity and readiness.

---

### 🪙 Internal Presale with AXEs

Once the project is approved to incubate, the team may open an internal presale:
- **Only members may participate** using AXEs
- No ETH or external fundraising allowed at this stage
- Presales help estimate demand and determine seasonal budget

In return, participants receive **Project Points**, which:
- Represent governance within the project
- May unlock access to services or coordination tools
- May later convert to actual tokens if the project exits the Guild

---

### ⚙️ Project Development Phase

After presale:
- Projects receive ETH from the Budget Treasury, based on AXE-weighted support
- Teams set milestones and deliverables
- Core Members may assist with mentorship, technical reviews, or community testing

Milestones are reported back to the Guild to maintain visibility and accountability.

---

### 🧾 Internal Use of Project Points

Project Points earned during the presale and build phase can be used for:
- Voting on internal roadmap decisions
- Gating tools, bounties, or knowledge bases
- Claiming perks or airdrops if/when a token is launched

They do not represent a financial claim and are not transferable outside the Guild until a formal token launch.

---

### 🛫 Graduation & Exit

If a project reaches maturity, it may exit the Guild with a token launch or legal formation.

To graduate, a project must:
- Deliver on key milestones
- Propose an exit structure (token allocation, team setup, IP rights)
- Allocate **10% of its token supply or equivalent value** to the Guild
- Offer Project Point holders a mapping or conversion path to new tokens or roles

A DAO vote (via Snapshot or onchain) is held to confirm the exit.

After exit:
- The project becomes an independent entity
- It may continue to collaborate with the Guild or operate autonomously
- The Guild may hold tokens, receive revenue share, or maintain partnership agreements

---

This flow creates a safe, aligned space for experimentation—where contributors signal with their AXEs, build with peers, and if successful, carry their project into the world with shared support and sovereignty.

![raidguild_incubation_flowchart](https://hackmd.io/_uploads/Syyi6Jmpkl.png)

## Index

## 🧰 Forms, Processes & Templates — Suggested Outline

### **1. Member & Governance Tools**

#### 📝 Member Dues + Role Form
- ETH dues payment form (link or QR)
- Select governance tier: Core or Loot-only
- Auto-issue Shares, Loot, and AXEs upon payment

#### 🧾 Community Service Tracker
- Submit proof of seasonal service (RIP, mentorship, review)
- Logged on-chain or in Notion/DAO dashboard
- Triggers share retention for Core Members

#### 🛡️ Exit Request Form
- Voluntary exit from Guild
- Select full or partial exit
- System calculates proportional dividend claim
- Initiates burn of shares/loot and disbursement

---

### **2. Project Lifecycle Templates**

#### 📄 Incubation Proposal Template
- Project name, purpose, team
- Problem/solution summary
- Milestones
- Requested budget
- Optional: internal token concept
- Expected impact

#### 🛠️ Project Presale Setup Sheet
- Total AXE goal
- AXE-to-Point rate
- Start and end time
- Link to Notion or GitHub repo
- Snapshot of supporters at end

#### 📈 Milestone Report Template
- What was planned
- What was built
- Current blockers
- Treasury usage log
- Next steps

#### 🧳 Exit Proposal Template
- Reason for graduating
- Token supply and allocation
- Distribution to Point holders
- 10% Guild share mechanics
- Timeline + DAO vote request

---

### **3. Budgeting & Treasury Tools**

#### 📊 AXE Allocation Tracker
- Members allocate AXEs via a spreadsheet or app
- Visualize which projects are getting support
- Snapshot total allocation at budget deadline

#### 💰 Treasury Distribution Calculator
- Calculates:
  - ETH to projects from Budget Treasury
  - Quarterly dividend to Shares + Loot
  - Exit redemption amounts for burn requests

---

### **4. Communication & Culture**

#### 📜 RIP Template (RaidGuild Improvement Proposal)
- Title
- Author
- Summary
- Motivation
- Specification
- Impact
- Vote type (onchain/Snapshot)

#### 🧭 New Member Guide
- How to get started
- What is an AXE?
- How to join a project
- Dues, roles, and responsibilities

#### ⚖️ Legal + Governance Summary PDF
- Org structure
- DAO + legal stack
- Treasury flows
- Exit mechanics

---


## 🔑 Member Roles Summary

| Role        | Asset Type       | Power             | How to Get It                      |
|-------------|------------------|-------------------|------------------------------------|
| **Member**  | AXEs             | Budget allocation | Pay dues (0.01–1 ETH)               |
| **Apprentice**  | AXEs             | Budget allocation | Pay dues and participate in cohort demoday           |
| **Core**    | Shares + Loot + AXEs | Governance + Dividends | Must also complete service (RIP, review, ops, etc.) |
| **Loot-only** | Loot + AXEs    | Dividends only    | Choose passive mode or demoted from Core |


MVP IDEAS
- option 1: Focus on Dues (new cohorts)
- option 2: Focus on adventure signaling (run internal pilot)

---

## ✅ MVP Idea 1 (focus on Dues with comminty onboarding and cohort): **Forge – Member Portal **
A simple web app where members can pay dues, receive AXEs, view their membership status, and track their support across the network.

a **Member Dues MVP** app could be the perfect lightweight entry point to activate the Raid Guild network. It sets the tone, collects signals, and creates the foundation for the full coordination layer.

---

### 🔥 **Forge MVP Spec: The RaidGuild Community Portal**

> **Tagline:** “The Forge is where you enter the Guild.  
> Claim your AXEs. Find your party. Join the adventure.”

---

### 🧱 Core Goals (MVP)

- Help new members join and contribute, **without pressure to go Core**
- Make dues → AXEs → participation super clear
- Provide a lightweight hub for **community updates**, events, cohorts
- Track your contributions and support projects with AXEs
- Offer an **optional upgrade path** to become Core

---

### 🧭 Flows & Features

#### 🔐 1. **Connect Wallet**

- Detect if member paid dues this season
- Show current role:
  - 👤 Member
  - 🧪 Apprentice (post-cohort)
  - 🧙 Core Member
  - 💤 Loot-only (inactive Core)
- Display balances:
  - AXEs (allocation power)
  - Project Points (if any)

---

#### 💸 2. **Pay Dues**

- Choose 0.01 to 1 ETH
- On payment → Issue AXEs
- Message:  
  > “Welcome to the Guild. You now wield AXEs—use them to support what we build together.”

---

#### ⚔️ 3. **Do DAO Tasks (Earn More AXEs)**

- Display task board:
  - “Write a RIP”
  - “Review a cohort project”
  - “Submit feedback on an incubation”
- Tasks pay additional AXEs (auto or approved by steward)

---

#### 🎓 4. **Cohort Participation**

- Next Cohort start date
- Link to apply or join waitlist
- After demo day → unlocks **Apprentice status**
  - Can apply to become Core by paying dues + DAO task
- Message:  
  > “You’ve completed the trials. You are now an Apprentice.”

---

#### 🧙 5. **Core Member Upgrade (Optional)**

- Requirements:
  - ✅ Apprentice
  - ✅ Paid dues
  - ✅ DAO task completed
- Unlocks: Shares, voting, governance proposals
- Message:  
  > “You now sit at the council table. The Guild listens when you speak.”

---

#### 📣 6. **Community Feed & Events**

- Next Town Hall
- Next Cohort
- Active Projects seeking AXE support
- Open bounties or seasonal quests

---

#### 🔁 7. **AXE Allocation Panel**

- Display your AXEs
- Browse open internal presales
- Allocate AXEs to projects
- Reallocate (if project hasn’t locked budget yet)

---

### 🧾 Backoffice Tools (Optional Admin Panel)

- View dues logs
- Validate service tasks
- Promote members from Apprentice → Core
- Trigger share issuance via Moloch DAO
- Generate seasonal dividend report

---

### 🧑‍💻 Tech Stack (Suggested)

| Layer | Stack |
|-------|-------|
| Frontend | Next.js, Tailwind, RainbowKit, Wagmi |
| Wallet | MetaMask, WalletConnect |
| Backend | Supabase or Firebase (AXE/task DB) |
| Contracts | Moloch DAO (Shares/Loot), AXE off-chain balance |
| Deployment | Vercel or Netlify |

---

### 🧠 MVP Summary

| Phase | User |
|-------|------|
| 1 | Join by paying dues → get AXEs (kyc) |
| 2 | Earn more AXEs by doing DAO tasks |
| 3 | Participate in a cohort → become Apprentice |
| 4 | Pay dues + complete DAO task → become Core (optional) |
| 5 | Use AXEs to support projects, show up at events, shape the network |

---

### 🔥 Bonus Ideas (Post-MVP)

- Streaming dues via Superfluid
- Internal quest board w/ bounties
- Cohort leaderboard
- Seasonal AXE awards
- Guild map or visual ledger of contributors

---


## MVP Option 2 - focus on signal

Absolutely—here’s a tight spec for a **signaling test project** inside Raid Guild, using the **AXE + Project Points + Conviction model** we just defined.

---

# 🧪 Project Spec: *Signal the Guild* — MVP Test of AXE-Based Project Signaling

## 🎯 Purpose

To test a lightweight internal mechanism where **Raid Guild members stake AXEs to signal conviction** for potential incubated projects. The system rewards conviction with **Project Points**, which are used for **governance, participation, and recognition** within each project.

---

## 🧱 Core Concepts

| Concept          | Description |
|------------------|-------------|
| **AXEs**         | Non-transferable points earned by Guild members (via dues, cohort, contributions). Used to signal support. |
| **Project Points** | Non-transferable points earned by staking AXEs into projects. Reflect support and influence. |
| **Staking Modes** | Members choose between Burned, Locked, or Soft-lock when staking. Rewards differ by conviction level. |

---

## 🧪 Goals of the Test

- Gather member sentiment toward 3–5 real or fictional projects
- Test behavior across Burned, Locked, and Soft-lock staking
- Observe Project Point accrual and dashboard clarity
- Use Project Points to unlock access to something (e.g., voting, Discord role, exclusive update)

---

## 🔧 Technical Scope (MVP)

### 1. **Project Gallery**
- List of 3–5 projects
- Each with: name, logo, description, AXE target, total support so far

### 2. **Stake AXEs Modal**
- User selects:
  - Number of AXEs to stake
  - Conviction method:
    - 🔥 Burned – earns 1.5× Points
    - 🔒 Locked (30 days) – earns 1.0× Points
    - 🌀 Soft-lock – earns 0.5× Points
- On confirm:
  - AXEs are reduced from off-chain balance
  - Project Points are added to user record

### 3. **User Dashboard**
- Remaining AXEs
- Projects supported
- Points per project
- Option to view other top supporters (optional)

---


### 🎨 UX Language

> “Choose your conviction:  
> - 🧱 Burn: Ride or die. You believe.  
> - 🕰 Lock: You’re in for the long haul.  
> - 🌀 Soft: You’re interested, but cautious.”  
>  
> “Project Points track your commitment and influence.  
> The deeper your support, the greater your mark.”

---


### 🧠 Stretch Ideas

- Discord bot that updates project support levels live
- Roles granted based on Project Points (e.g., `supporter-wen3`)
- Bounties unlocked if project gets enough support
- Visual leaderboard per project

---

### 🧾 Deliverables

- 🖥 Web app (or Notion prototype) with wallet login
- 🧠 Internal doc explaining mechanics
- 📊 End-of-test report on behavior and feedback
- 💬 Optional: cohort presentation or town hall session

---

### ✅ Success =

- Members understand the mechanics
- AXEs are staked across conviction levels
- Project Points help identify and reward supporters
- Clear signal on which projects are resonating

---
