Developer-DAO / Developer-DAO/pixel-avatars
Public Mint option of Pixel Avatars
- Dominant language
- JavaScript
- Stars
- 136
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
We had brainstormed on our meeting last week that we wanted to have an option for public without dao tokens to mint Pixel Avatars. We will charge a small fee ( to be decided ) for the public mint and allow a certain amount(TBD) of public mints.
Pixel Avatars will be generated form metadata of Developer Dao token. For public mints, we can randomize the metadata and create a `headless` avatar that doesn't depend on the Dao token.
To decide:
- How many public mints to allow?
- Should we limit public mints per address? For example only let one address publicly mint one avatar. This will stop someone buying all public mints since we plan to keep the cost low.
- What price to charge for public mint
- How to market the public mint option
Todo:
- test out the contract to ensure the collected funds can only be withdraw by the allow listed wallet or the contract deployer address. We will use the dao address to deploy contract.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the minting contract and its existing contract tests. Resolve the listed decisions about public-mint limits, per-address limits, and price before implementing the headless-avatar flow. Done means public mints work without DAO tokens and tests verify collected funds can only be withdrawn by the allowlisted wallet or contract deployer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100