kredits/contracts
9
1
Fork 0
Code Issues 21 Pull Requests Actions Projects 1 Releases 8 Activity

[WIP] Add Contribution contract #55

Merged
bumi merged 5 commits from contribution-contract into master 2019-04-02 19:36:38 +00:00
Conversation 0 Commits 5 Files Changed 10
+205 -4
bumi commented 2018-06-18 13:32:25 +00:00 (Migrated from github.com)
Copy Link
Copy Source

The contribution contract implements an ERC721 interface which represents any contribution.
The contributions are non-fungible (as opposed to the Kredits tokens) and can be not be transferred.
The contract stores the history of any contribution. Contributions can be claimed which will issue the Kredits tokens to the contributor.

This is an early implementation and misses some access control and probably more things.

To do:

  • Store token metadata URL in ContributionData
  • Store contribution IPFS hash in ContributionData
  • Rename operator to proposal
  • Remove obsolete data and functions from Proposal
  • Add proposal id to ContributionData
  • Veto function for Contribution: creates a proposal if requirement fulfilled (maybe just coreonly for now)
  • If contribution has a proposal, then only allow claiming if proposal result is positive
  • Add rejection to Proposal
  • Update JS wrapper to reflect changes

ref: #52

The contribution contract implements an ERC721 interface which represents any contribution. The contributions are non-fungible (as opposed to the Kredits tokens) and can be not be transferred. The contract stores the history of any contribution. Contributions can be claimed which will issue the Kredits tokens to the contributor. This is an early implementation and misses some access control and probably more things. To do: - [ ] Store token metadata URL in ContributionData - [ ] Store contribution IPFS hash in ContributionData - [ ] Rename operator to proposal - [ ] Remove obsolete data and functions from Proposal - [ ] Add proposal id to ContributionData - [ ] Veto function for Contribution: creates a proposal if requirement fulfilled (maybe just coreonly for now) - [ ] If contribution has a proposal, then only allow claiming if proposal result is positive - [ ] Add rejection to Proposal - [ ] Update JS wrapper to reflect changes ref: #52
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
good first issue
Good for newcomers
 ipfs
rsk
scaling
bug
Something is not working
 dev environment
Config, builds, CI, deployment, etc.
 docs
Documentation
 duplicate
This issue or pull request already exists
 enhancement
Improving existing functionality
 feature
New functionality
 idea
Something to consider
 invalid
Not a bug
 kredits-1
Small contribution
 kredits-2
Medium contribution
 kredits-3
Large contribution
 question
Looking for an answer
release
major
release
minor
release
patch
security
All your base are belong to us
 ui/ux
User interface, process design, etc.
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
bkero (bkero) bumi (bumi) fsmanuel (fsmanuel) galfert (galfert) greg (Greg) haythem (haythem) hueso (hueso) raucao (Râu Cao) slvrbckt (Nick Jennings)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kredits/contracts#55