Skip to content

Commit

Permalink
Update xgov-171.md
Browse files Browse the repository at this point in the history
  • Loading branch information
@heartberg
heartberg authored Apr 25, 2024
1 parent 2c8d1d5 commit e4ac83c
Showing 1 changed file with 88 additions and 24 deletions.
112 changes: 88 additions & 24 deletions Proposals/xgov-171.md
View file
Original file line number Diff line number Diff line change
@@ -1,47 +1,106 @@
---
id: <proposal number (same as PR)>
period: <Period number (Integer) (When do you want to submit your proposal)>
title: <The proposal title is a few words, not a complete sentence>
author: <a comma separated list of the author's or authors' name + GitHub username (in parenthesis), or name and email (in angle brackets). Example, FirstName LastName (@GitHubUsername), FirstName LastName <[email protected]>, FirstName (@GitHubUsername) and GitHubUsername (@GitHubUsername)>
email: <Email address to start the contract process >
id: 171
period: 4
title: Everyone Launchpad Security Audit
author: Jesco Brandt (@heartberg), Mark Crae (@dolphinkitty)
email: [email protected]
discussions-to: <Indicating the URL where the proposal is being discussed>
company_name: <Name of the company>
company_name: Everyone
category: <dApps, Tools, Community, Other>

Check failure on line 9 in Proposals/xgov-171.md

View workflow job for this annotation

GitHub Actions / xGov Walidator

preamble header `category` has an unrecognized value 

error[preamble-enum-category]: preamble header `category` has an unrecognized value
 --> Proposals/xgov-171.md:9:10
  |
9 | category: <dApps, Tools, Community, Other>
  |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ must be one of: `dApps`, `Tools`, `Community`, `Other`
  |

Check failure on line 9 in Proposals/xgov-171.md

View workflow job for this annotation

GitHub Actions / xGov Walidator

preamble header `category` has an unrecognized value 

error[preamble-enum-category]: preamble header `category` has an unrecognized value
 --> Proposals/xgov-171.md:9:10
  |
9 | category: <dApps, Tools, Community, Other>
  |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ must be one of: `dApps`, `Tools`, `Community`, `Other`
  |
focus_area: <Banking,DEX,Defi,Deployment,Education,Gaming,IDE,Identity,Libraries,Metaverse,Monitoring,Node,NFT,Oracle,Social,Storage,Teal,User Onboarding,Wallet, Other>

Check failure on line 10 in Proposals/xgov-171.md

View workflow job for this annotation

GitHub Actions / xGov Walidator

preamble header `focus_area` has an unrecognized value 

error[preamble-enum-focus_area]: preamble header `focus_area` has an unrecognized value
  --> Proposals/xgov-171.md:10:12
   |
10 | focus_area: <Banking,DEX,Defi,Deployment,Education,Gaming,IDE,Identity,Libraries,Metaverse,Monitoring,Node,NFT,Oracle,Social,Storage,Teal,User Onboarding,Wallet, Other>
   |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ must be one of: `Banking`, `Defi`, `Dex`, `Gaming`, `Identity`, `Marketplace`, `Metaverse`, `NFT`, `Oracle`, `Storage`, `User Onboarding`, `IDE`, `Teal`, `Deployment`, `Libraries`, `Monitoring`, `Node`, `Education`, `Social`, `Wallet`, `Other`
   |

Check failure on line 10 in Proposals/xgov-171.md

View workflow job for this annotation

GitHub Actions / xGov Walidator

preamble header `focus_area` has an unrecognized value 

error[preamble-enum-focus_area]: preamble header `focus_area` has an unrecognized value
  --> Proposals/xgov-171.md:10:12
   |
10 | focus_area: <Banking,DEX,Defi,Deployment,Education,Gaming,IDE,Identity,Libraries,Metaverse,Monitoring,Node,NFT,Oracle,Social,Storage,Teal,User Onboarding,Wallet, Other>
   |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ must be one of: `Banking`, `Defi`, `Dex`, `Gaming`, `Identity`, `Marketplace`, `Metaverse`, `NFT`, `Oracle`, `Storage`, `User Onboarding`, `IDE`, `Teal`, `Deployment`, `Libraries`, `Monitoring`, `Node`, `Education`, `Social`, `Wallet`, `Other`
   |
open_source: <Yes, No>

Check failure on line 11 in Proposals/xgov-171.md

View workflow job for this annotation

GitHub Actions / xGov Walidator

preamble header `open_source` has an unrecognized value 

error[preamble-enum-open_source]: preamble header `open_source` has an unrecognized value
  --> Proposals/xgov-171.md:11:13
   |
11 | open_source: <Yes, No>
   |             ^^^^^^^^^^ must be one of: `Yes`, `No`
   |

Check failure on line 11 in Proposals/xgov-171.md

View workflow job for this annotation

GitHub Actions / xGov Walidator

preamble header `open_source` has an unrecognized value 

error[preamble-enum-open_source]: preamble header `open_source` has an unrecognized value
  --> Proposals/xgov-171.md:11:13
   |
11 | open_source: <Yes, No>
   |             ^^^^^^^^^^ must be one of: `Yes`, `No`
   |
funding_type: <Proactive, Retroactive>
funding_type: Proactive
amount_requested: <Amount (integer) requested in ALGO, it should be at least 10000>

Check failure on line 13 in Proposals/xgov-171.md

View workflow job for this annotation

GitHub Actions / xGov Walidator

preamble header `amount_requested` must be an unsigned integer 

error[preamble-amount_requested]: preamble header `amount_requested` must be an unsigned integer
  --> Proposals/xgov-171.md:13:18
   |
13 | amount_requested: <Amount (integer) requested in ALGO, it should be at least 10000>
   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not a non-negative integer
   |

Check failure on line 13 in Proposals/xgov-171.md

View workflow job for this annotation

GitHub Actions / xGov Walidator

preamble header `amount_requested` must be an unsigned integer 

error[preamble-amount_requested]: preamble header `amount_requested` must be an unsigned integer
  --> Proposals/xgov-171.md:13:18
   |
13 | amount_requested: <Amount (integer) requested in ALGO, it should be at least 10000>
   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not a non-negative integer
   |
delivery_date: <project delivery date, in ISO 8601 (yyyy-mm-dd) format>
delivery_date: 2024-08-30
status: <Draft, Final, Approved>

Check failure on line 15 in Proposals/xgov-171.md

View workflow job for this annotation

GitHub Actions / xGov Walidator

preamble header `status` has an unrecognized value 

error[preamble-enum-status]: preamble header `status` has an unrecognized value
  --> Proposals/xgov-171.md:15:8
   |
15 | status: <Draft, Final, Approved>
   |        ^^^^^^^^^^^^^^^^^^^^^^^^^ must be one of: `Draft`, `Final`, `Approved`
   |

Check failure on line 15 in Proposals/xgov-171.md

View workflow job for this annotation

GitHub Actions / xGov Walidator

preamble header `status` has an unrecognized value 

error[preamble-enum-status]: preamble header `status` has an unrecognized value
  --> Proposals/xgov-171.md:15:8
   |
15 | status: <Draft, Final, Approved>
   |        ^^^^^^^^^^^^^^^^^^^^^^^^^ must be one of: `Draft`, `Final`, `Approved`
   |
---

>Proposals that do not include information on all template sections will be rejected.
>Please, before submitting the grant proposal, review the contract template and ensure you're comfortable with its terms. <a href="https://drive.google.com/file/d/1dsKwQGhnS3h_PrSkoidhnvqlX7soLpZ-/view">Contract Template</a>
## Abstract
A summary of the project, including how the Algorand ecosystem would benefit (proactive)/ has benefitted (retroactive) from its implementation.
This proposal seeks funding for a security audit of the Everyone launchpad, a comprehensive crowdfunding platform enabling developers, teams, and projects to seamlessly mint, sell, and distribute tokens within the Algorand ecosystem.

Engineering work for the v1 launchpad’s smart contracts, front-end interface, and back-end functionality are already complete, and have undergone extensive QA on Testnet. We are not requesting funds for any core development work – this funding request is purely to pay for a security audit.

We have communicated with all reputable audit service providers on Algorand and received multiple price quotes and timelines.

XGov funding will enable us to immediately proceed with an audit, then go live with the launchpad within weeks.

Once released, the Everyone launchpad will provide critically needed utilities within the Algorand ecosystem to kickstart funding for new Algorand projects.

By providing a reliable and user-friendly funding platform, the Everyone launchpad has the potential to significantly accelerate Algorand's adoption, mirroring the success driven by similar launchpads on other blockchains.

## Team
Information about the team members and their qualifications, including relevant experience and skills.
Jesco Brandt (@heartberg)
** Full Stack Engineer with 3 years of professional experience
** GitHub: heartberg (Everyone) · GitHub 3

Mark Crae (@dolphinkitty)
** Product Manager / Designer with 10+ years of experience

## Experience with Algorand
Details about the team's experience with the Algorand protocol and any previous projects built on it.
> eg
> Using SDKs
> Building applications
> Understanding of DApps
> Knowledge about the ecosystem
> Running nodes
Jesco has been actively developing Algorand based projects for >3 years. In this time he has created ~20 PyTeal and Python smart contracts, and multiple Front / Back ends to support this. These smart contracts cover a wide range of application types, including staking, vesting, trading, and more.

Mark authored the proposed ARC-40 standard for Asset set (NFT collection) meta data configuration and verification workflows.

Together, Mark and Jesco have been building the Everyone platform (including the launchpad) and other Algorand projects for over 2 years.

## Present Proposal
A detailed plan for the development and implementation of the proposal.
The Everyone launchpad will enable any developer, project, or team to mint assets and deploy dedicated token sale contracts on the Algorand blockchain.

The launchpad includes all the necessary launchpad features, but also integrates many additional features that you will not see on other launchpad platforms, for example: token locking, staking, project promotion, and community engagement, etc.
Key features include:

### Accessibility and permissions
The launchpad support for both permissioned and permissionless tokens sales
- Initially, we plan to offer permissioned launches to ensure user safety. This approach integrates a (human + AI) review step within the permissionless configuration flow
- Support for private and public token sales – Flexible whitelisting options enable projects to control who can access and participate in their sale.
- Public sales – enable any user to request whitelisting. Non-whitelisted users can also participate on a FCFS basis
- Whitelist spots can be purchased or distributed via lottery / FCFS
- Private sales – enable teams to create their own private whitelist to facilitate invite only participation in token sales

To enhance clarity and accountability, we're asking proposers to detail the maintenance period, availability, and sustainability plans for their projects. This includes information on potential costs and the duration for which services will be offered at no or reduced cost
### Target raise / Allocations
Teams can configure every aspect of their token sale including:
- Hard cap / Soft cap amounts, initial supply
- Number of whitelisted / non-whitelisted participants
- Wallet caps for each tier of token sale participant

### Token sale timeline
Teams can define the start time and durations of each phase of the token sale:
- Whitelisting phase
- Token sale phase – whitelisted participants
- Token sale phase – non-whitelisted participants
- 2x Allocation phase for all sale participants

### Token vesting and claim
All purchased tokens can be claimed after the sale.
Projects can configure optional token vesting for both team tokens and purchased tokens. Vesting schedules are fully customizable, including: initial unlock, cliff, periodic unlocks.

### Dashboard + portfolio
The Vesting dashboard enables users to track their token vesting across multiple project launches. This integrates with portfolio management tools.

### UX
On the admin side, the launchpad’s easy to use no-code UX provides a streamlined configuration process. On the user facing side, an intuitive UX enables easy onboard, whitelisting, sale participation, and token claim.

### Everyone platform
The launchpad is integrated within the Everyone platform, joining a suite of other user-friendly no-code utilities for the Algorand network.

The Everyone platform enables projects to create a sophisticated multi-page mini site to promote their launch and engage their community. Launchpad project pages include: project information and links; team info; community list with follow/unfollow functionality; NFT galleries, and much more.

The platform's integrated approach, combining a launchpad with other key apps and services enable projects to establish a cohesive and branded presence, promoting trust and engagement within their token sale and across the lifecycle of their project.

### Sustainability and maintenance
Our goal is to build the launchpad into a sustainable business, however, we acknowledge the current low-level of launch activity on the Algorand network. We believe that by providing a high quality launchpad that the community can get behind, we will be able to generate more launch and funding activity in the months and years ahead. We also assume that other ecosystem expansion drivers will help make a dedicated Algorand launchpad a viable business / utility.

We are in this for the long haul. We expect the Everyone platform to be around for many years, even in a worst case scenario we will keep the platform running fully maintained for multiple years.

### Deliverable
Proposals must include clear, non-technical descriptions of deliverables. We encourage the use of multimedia (blog/video) to help explain your proposal's benefits to the community.
The necessary features of the launchpad are already complete and have been extensively tested, hence we are ready to undertake the security audit. We have shared detailed information regarding our smart contract code with auditors, and have received pricing quotes and timelines.

Usage of the launchpad on Mainnet will commence once xGov funds are received and the necessary audit has been completed. We believe that reward distribution will occur on 7 July, after which auditors have indicated that they will require approx 3 weeks to complete the audit. Therefor we anticipate that the audit will be complete by 7 Aug, unless any issues need to be addressed. Allowing for all the unknowns, we will aim to have the launchpad operational on Mainnet by 30 Aug.

Delivery can be checked by performing the necessary steps within the launchpad app to configure and run a demo token sale, or the Everyone team would be happy to demonstrate the deliverables via zoom.

Proposals that do not specify deliverables and a process to check deliverables will be rejected.
Prior to this, we will begin beta signup for the launchpad app before the session 4 review phase ends (5 May). And to give governors more insight into the scope and quality of the built product, we will open up access to explore and use the launchpad via Testnet, around the time that voting commences on 13 May.

## Future Blueprint
> This part can be optional for one-time grants.
Expand All @@ -50,7 +109,12 @@ A high-level plan, defining an overarching strategic objective and capturing the
> For Milestone-based grants, please refer to <a href="https://github.com/algorandfoundation/ARCs/blob/main/ARCs/arc-0034.md#submit-a-proposal"> How to submit a proposal</a>.
## Benefits for the community
A description of the potential benefits that the proposal could bring to the Algorand community and its users.
Key benefits
- Provide a new and critically needed funding mechanism for developers, teams and projects within the Algorand ecosystem.
- Kickstart adoption of Algorand by new developers, teams and projects.
- Promote an accessible, secure, more transparent, and inclusive launchpad participation process. We are not planning to release a utility token for the launchpad, therefor there - will be no whales that receive preferential access. We want to ensure a broad distribution of tokens from each launch to aid the long term sustainability of each launched projects
- The launchpad fills a key missing component within the Algorand ecosystem that inhibits adoption by new developers and projects.
- As the launchpad is where new projects present themselves, it acts as a key entry point for new users to Agorand. Consequently. we are building the product with a high user-experience to ensure that users receive a good impression of what the Algorand ecosystem has to offer.

## Additional information
Any other relevant details or documentation that the team would like to include in the proposal.
Expand Down

0 comments on commit e4ac83c

Please sign in to comment.