---
# System prepended metadata

title: Untitled

---

## Portfolio Structure

### Project Name

The name of the project - optionally include customer

### Site Link

The link of the deployed dapp (if relevant)

### Github Link

The link of the public github repo (if relevant)

### Description

The description that will display in any kind of project cards, open graph links, or search engine results. Be brief and descriptive, limit to around 200 chars. 

### Image

A square (1:1) image representing the client

### Applicable Services

List out all raider roles attached to the service, eg front end, back end, tokenomics, auditing, design, etc

### Contributors

List out all raiders and their roles for the project

### The Challenge

Markdown field. Describe what the client was trying to do and why this was difficult - does not have to be grandiose. 
Being general is better - "Client needed to allow users to interact with their novel tokenomic design" is better than "Client needed a react website with ethers js"

### Our Approach

Describe how Raidguild decided to complete the task. This is where we get specific, so for example "We decided to use React + Ethers to create a reactive UI that enabled users to interact with their novel smart contracts."

### Results

Describe what happened with the project after hand off. General is better if the results are not stellar; "Client made $4,137 since launching" is a bad look compared to "Client's dapp generated revenue after launching." If there's splash or pizazz or zazzle or whatever, include it. 
