Proof Application Requirements
Target release | Mercury |
|---|---|
Epic | Proof Requirements |
Document status | DRAFT |
Document owner | @Luigi D'Onorio DeMeo |
Designer | |
Developers | @Paolo Donorio demeo |
QA |
Goals
Simplify user experience
Background and strategic fit
We are building an on/off chain voting scheme. The voting scheme attempts to keep privacy while still being auditable.
Assumptions
Requirements
# | Title | User Story | Importance | Notes |
|---|---|---|---|---|
1 | Option for a JSON-RPC server listening | get updates from blockchain to present to user | Must have | Believe Rchain provide some basic support of protobufer so we think it should be good to go, but confirming. |
2 | Equivalent of WEB3 | enable user to have equivalent to metamask experience | Must have | Javascript library for interacting our contracts with rchain |
3 | ecrecover(), and sha3() functions | for our on-chain vote parsing | Important | We understand there will not be actual functions such as these in rholang but the capability needs to be the same. |
4 | Comparison of solidity and rholang | Tutorial to assist developers understand how to do certain things in rholang that are common nature in solidity | Moderate |
|
5 | Truffle-like tooling | easy to use development/testing environments | Important |
|
6 | Mathematical library | allow developers to easily implement mathematical functions such as exponent, root, logarithms, ect. | Important |
|
7 | Storage | need to understand cost of storange SSTORE opcode in ethereum | Important |
|
8 | Key pairs from external systems | Ability to use key pairs from systems such as Ethereum, Bitcoin, ect. for Proof of Authority chain | Moderate |
|