search

gitcoinco / ethdenver

https://medium.com/gitcoin/ethdenver-request-for-project-proposals-9ed979dafbbe
10 stars 2 forks source link

ETHDenver - Web Service Which Generates Custom Token Contracts #4

Closed vs77bb closed 5 years ago

vs77bb commented 6 years ago

This is an ETHDenver Bounties Track Issue.

Idea

Submission by Shaun Martin:

Web service which generates and manages custom token (ERC20+721) contracts. It would provide users with an API and other off-chain resources to help make the most of their tokens. Aimed at game devs, the idea is help them integrate token minting, sales, and trading in-app with a minimal amount of fuss.

Requirements

inhumantsar commented 6 years ago

Thanks for accepting my submission! I'd like to propose a minor change to the requirements though: We would focus on ERC721 first rather than ERC20 tokens. The ERC20 field is relatively well-serviced and we believe ERC721 deeds will be more immediately relevant to game developers. We are currently planning to implement the updated ERC721 spec by @fulldecent and others. (update 2/13 the spec situation is fluid, we may switch to EIP-821)

Our core goal for the Hackathon is the parameterized deployment of deed contracts via an API. To accomplish this, we will first need to implement the updated spec, including the metadata and accountability extensions. We will also need to develop at least one -- preferably multiple -- minting strategies and implement them as well. Destruction and contract upgrade strategies may also be considered but are non-essential.

Some stretch goals we may elect to attempt include: storing additional deed metadata off-chain using the API; broker or auction contract generation to support deed sales; and a sample web client for generated contract users.

The team currently consists of @kevgary, @koshroy, @adumit and myself. The code will live at https://github.com/deedfactory

fulldecent commented 6 years ago

Thanks for the help! We can definitely use implementations to help with interop and getting the standard accepted.

You might think 721 is dead simple. But actually, the details uncovered with interop work and a little more planning can help us avoid disasters like ERC-20

gitcoinbot commented 6 years ago

This issue now has a funding of 0.5 ETH (455.25 USD) attached to it.

gitcoinbot commented 6 years ago

Work has been started on the 0.5 ETH (470.25 USD) funding by:

  1. @inhumantsar

    Please work together and coordinate delivery of the issue scope. Gitcoin doesn't know enough about everyones skillsets / free time to say who should work on what, but we trust that the community is smart and well-intentioned enough to work together. As a general rule; if you start work first, youll be at the top of the above list ^^, and should have 'dibs' as long as you follow through.

    On the above list? Please leave a comment to let the funder (@owocki) and the other parties involved what you're working, with respect to this issue and your plans to resolve it. If you don't leave a comment, the funder may expire your submission at their discretion.

owocki commented 6 years ago

hi from gitcoin.co here ==> was just debugging an issue with gitcoinbot leaving too many comments about work starting.. i put in a fix and we should be okay now.

fulldecent commented 5 years ago

Anything left here? Can this issue and repo be closed?

owocki commented 5 years ago

closing it now