| Page Properties |
|---|
| Target release | |
|---|
| Epic | |
|---|
| Document status | |
|---|
| Document owner | |
|---|
| Designer | |
|---|
| Developers | |
|---|
| QA | |
|---|
|
Goals
- Create the container that holds Rholang contracts on the blockchain. Has a public / private key pair which is the 'address' for the account on the blockchain.
Background and strategic fit
Basic requirement for running contracts on the blockchain.
Assumptions
- There exists a 1 to 1 relationship between a smart contract (that can be called) and an 'account' (public/private key pair).
- It is possible to have nested contracts within an account (One contract calls another).
- The cost to execute the nested contract is borne by the calling contract.
- Funding execution of a contract is a transaction, and it will cost Phlogiston.
Requirements
| # | Title | User Story | Importance | Notes |
|---|
| 1 |
As an entity that controls Rev's I want to be able to sign my transactions in a variety of different ways, such as Ubi-key pairs or handset keys. | - ETH is implementing account abstraction
| 2 | | | | Generate Account address | Generate a unique account address | Must Have | |
| 2 | address as wallet | Address functions as a wallet, in that it holds Phlogiston. | Must Have |
|
| 3 | Account holds code | This account also houses Rholang smart contract code. | Must Have |
|
User interaction and design
...
Below is a list of questions to be addressed as a result of this requirements document:
Not Doing