Contribution tokens (ERC721) #52

New Issue

2018-06-15T13:34:49Z

raucao commented

2018-06-15 13:34:49 +00:00

(Migrated from github.com)

From IRC:

<raucao> we'll use ERC721 tokens which can store metadata (the ipfs hash) and have an id
<raucao> and add a property to those for how many kredits were issued
<raucao> then we can use those both in contracts as well as for history views etc
<raucao> and the normal tokens can be sent around and whatnot
<raucao> then, when we distribute money, we can do that to the normal kredits tokens
<raucao> so a contributor can decide to either get dividends with those, or sell them to someone else
<raucao> and also, we can sell pure kredits tokens that don't represent contributions to people who want to support opensource projects, without them being able to vote with those or anything
<raucao> the way we see that now, it would solve our remaining problems with the current tokens and be super clean as well

From IRC: ``` <raucao> we'll use ERC721 tokens which can store metadata (the ipfs hash) and have an id <raucao> and add a property to those for how many kredits were issued <raucao> then we can use those both in contracts as well as for history views etc <raucao> and the normal tokens can be sent around and whatnot <raucao> then, when we distribute money, we can do that to the normal kredits tokens <raucao> so a contributor can decide to either get dividends with those, or sell them to someone else <raucao> and also, we can sell pure kredits tokens that don't represent contributions to people who want to support opensource projects, without them being able to vote with those or anything <raucao> the way we see that now, it would solve our remaining problems with the current tokens and be super clean as well ```

raucao commented

2018-06-15 13:35:35 +00:00

(Migrated from github.com)

ERC 721 tokens:

Zeppelin contracts (we also inherit from a Zeppelin contract for the normal ERC 20 kredits tokens):

ERC 721 tokens: * https://github.com/ethereum/EIPs/blob/master/EIPS/eip-721.md * https://medium.com/crypto-currently/the-anatomy-of-erc721-e9db77abfc24 Zeppelin contracts (we also inherit from a Zeppelin contract for the normal ERC 20 kredits tokens): * https://github.com/OpenZeppelin/openzeppelin-solidity/tree/master/contracts/token/ERC721 * https://medium.com/blockchannel/walking-through-the-erc721-full-implementation-72ad72735f3c

raucao commented

2018-06-16 12:25:16 +00:00

(Migrated from github.com)

Notes from afk convo:

Maybe don't create proposals by default at all. Create the contribution, and only if one core team member vetos it, then create a proposal to vote on.
Without voting, there's no transaction to confirm the contribution anymore, so we need another way of issuing the kredits then. Could make sense to allow the user to do it for themselves from time to time (i.e. "transfer me all the kredits I earned"). Question is how to make it both cheap and convenient.

Notes from afk convo: * Maybe don't create proposals by default at all. Create the contribution, and only if one core team member vetos it, then create a proposal to vote on. * Without voting, there's no transaction to confirm the contribution anymore, so we need another way of issuing the kredits then. Could make sense to allow the user to do it for themselves from time to time (i.e. "transfer me all the kredits I earned"). Question is how to make it both cheap and convenient.

bumi commented

2019-03-31 14:01:08 +00:00

(Migrated from github.com)

First version in #62

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: kredits/contracts#52