This repository has been archived by the owner on Jun 17, 2020. It is now read-only.
Supporting Cryptofex Smartcontract IDE #970
Labels
Development
splitting into core-dev, developer-education, ...? (guides: @dckc, ...)
Help Wanted
needs-SMART-objective
Specific; Measurable; Assignable; Realistic; Time-related
Benefit to RChain
Cryptofex intends to make programming smart contracts easier creating an IDE for smart contract development in rholang and solidity. Better development tools should catalyze the whole ecosystem.
https://cryptofex.io/
https://youtu.be/ymq8EA9fi7o
Detailed Description
HELP_WANTED
This is not my area of expertise, but there are people within the RContributors system who are knowledgeable and interested in smart contract development. Two aspects are "support" and "leverage".
Support: How can we support the Cryptofex effort? Alpha testing? Discussion channel in Colab? Reviews and comments? Feature suggestions?
Benefit from: How can we benefit from Cryptofex? Might Cryptofex help team members in issues #956 and #919? Are there other ways we can leverage the work Cryptofex is doing?
This issue if properly formulated will be sponsored by the dApp development community @kvalentine, @nedrobinson.
In addition, if anyone would like to propose a better or alternate approach, that would likely be supported as well. For comparison please see these projects: Truffle, Ganache, OpenZeppelin.
Budget and Objective
Please make the issue SMART: Specific, Measurable, Achievable, Realistic, Timely.
Estimated Budget of Task: $[000]
Estimated Timeline Required to Complete the Task: [days/weeks]
How will we measure completion? [example: pull request merged]
See CONTRIBUTING.md for details on budget and reward process.
Legal
Task Submitter shall not submit Tasks that will involve RHOC being transacted in any manner that (i) jeopardizes RHOC’s status as a software access token or other relevant and applicable description of the RHOC as an “asset”—not a security— or (2) violates, in any manner, applicable U.S. Securities laws.
The text was updated successfully, but these errors were encountered: