You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our docker setup include two nodes `keosd` and `nodeosd`. The `keosd` is responsible for running the wallet and as well the `cleos` commmand, since this way `cleos` won't spin up its own version of `keosd` daemon everytime you invoke it. The other `nodeos` node is responsible for running the blockchain and compiling files.
12
12
13
-
14
13
## Attention
15
14
16
-
This repo only works using [eosio.cdt](https://github.com/EOSIO/eosio.cdt/releases/tag/v1.5.0) version `v1.5.0`
17
-
18
-
### If you have problems compiling
19
-
20
-
We map one virtual disk volume to the folder `/contracts` in order for us to be able to compile all of EOS Smart contract dependencies. If this isn't working for you you'll need to link your eos instalation to our Docker images. You can change the `volume:` keys on `docker-compose.yml` to match your EOS installation path:
21
-
22
-
```
23
-
# Install EOS as described in https://developers.eos.io
24
-
cd YOUR_EOS_REPO_PATH
25
-
./eosio_install.sh
26
-
cd build/contracts
27
-
pwd
28
-
```
29
-
30
-
With the result of `pwd` you can map it on the `docker-compose.yml`:
31
-
32
-
```
33
-
nodeosd:
34
-
container_name: nodeosd
35
-
...
36
-
volumes:
37
-
- nodeos-data-volume:/opt/eosio/bin/data-dir
38
-
- ../contracts:/contracts # here, change ..contracts to the result of your pwd here, before `:`
39
-
```
40
-
41
-
### Setup aliases
42
-
43
-
It can be a little tricky to interact with EOS using docker, those alias will help you around:
"ricardian_contract": "---\nspec-version: 0.0.1\ntitle: Create new community\nsummary: Creates a new community on BeSpiral. It requires you to send: `cmm_asset`, `creator`, `logo`, `name`, `description`, `inviter_reward` and `invited_reward`. A BeSpiral community is closelly tied to a BeSpiral Token. A community allows a group of people with common goals and objectives to connect and allow the creation of incentives to reach those objectives. It also help to buy and sell products\nicon:"
731
+
"ricardian_contract": ""
732
732
},
733
733
{
734
734
"name": "createsale",
735
735
"type": "createsale",
736
-
"ricardian_contract": "---\nspec-version: 0.0.1\ntitle: Create a sale on a given community\nsummary: Enable a single user to create a new sale (either buy or sell) on a given community. It requires you to send: `from`, `title`, `description`, `quantity`, `image`, `is_buy` and `units`. All information sent is going to be saved. Note that `quantity` is related to price and `units` to number of items available.\nicon:"
"ricardian_contract": "---\nspec-version: 0.0.1\ntitle: Delete a sale\nsummary: Enable the sale creator to remove a single sale. It requires you to send: `sale_id`. No information is going to be saved.\nicon:"
"ricardian_contract": "---\nspec-version: 0.0.1\ntitle: Invites a new account to a given community\nsummary: Add a user to the BeSpiral community network. It requires you to send: `cmm_asset`, `inviter` and `new_user`. We'll save who invited the new account and on which community\nicon:"
"ricardian_contract": "---\nspec-version: 0.0.1\ntitle: React to a sale\nsummary: Enable any user in the same community (except by creator) to react to a sale. It requires you to send: `sale_id`, `from` and `type`. No information is going to be saved.\nicon:"
"ricardian_contract": "---\nspec-version: 0.0.1\ntitle: Process a sale transfer\nsummary: Enable different users to exchange value for a given sale. It requires you to send: `sale_id`, `from`, `to`, `quantity` and `units`. No information is going to be saved, only used to update previous sale information. Note that `from` is the one interested in the sale, `to` the sale creator, `quantity` is related to price and `units` to number of items available.\nicon:"
786
+
"ricardian_contract": ""
787
787
},
788
788
{
789
789
"name": "update",
790
790
"type": "update",
791
-
"ricardian_contract": "---\nspec-version: 0.0.1\ntitle: Update some information about a community\nsummary: Update information on a existing community on BeSpiral. It requires you to send: `cmm_asset`, `logo`, `name`, `description`, `inviter_reward` and `invited_reward`. All information will be saved, with the exception of the asset that cannot be changed\nicon:"
791
+
"ricardian_contract": ""
792
792
},
793
793
{
794
794
"name": "updatesale",
795
795
"type": "updatesale",
796
-
"ricardian_contract": "---\nspec-version: 0.0.1\ntitle: Update a sale\nsummary: Enable the sale creator to update some details of a single sale. It requires you to send: `sale_id`, `title`, `description`, `quantity`, `image` and `units`. Except by `sale_id`, all information sent is going to be updated. Note that `quantity` is related to price and `units` to number of items available.\nicon:"
"body": "---\nspec-version: 0.0.1\ntitle: General Data Storage\nsummary: This smart contract will store data added by the user. The user consents to the storage of this data by signing the transaction.\nicon:"
888
-
},
889
-
{
890
-
"id": "Data Usage",
891
-
"body": "---\nspec-version: 0.0.1\ntitle: General Data Use\nsummary: This smart contract will store user data. The smart contract will not use the stored data for any purpose outside store and delete.\nicon:"
892
-
},
893
-
{
894
-
"id": "Data Ownership",
895
-
"body": "---\nspec-version: 0.0.1\ntitle: Data Ownership\nsummary: The user of this smart contract verifies that the data is owned by the smart contract, and that the smart contract can use the data in accordance to the terms defined in the Ricardian Contract.\nicon:"
896
-
},
897
-
{
898
-
"id": "Data Distribution",
899
-
"body": "---\nspec-version: 0.0.1\ntitle: Data Ownership\nsummary: The smart contract promises to not actively share or distribute the address data. The user of the smart contract understands that data stored in a multi index table is not private data and can be accessed by any user of the blockchain.\nicon:"
900
-
},
901
-
{
902
-
"id": "Data Future",
903
-
"body": "---\nspec-version: 0.0.1\ntitle: Data Ownership\nsummary: The smart contract promises to only use the data in accordance of the terms defined in the Ricardian Contract, now and at all future dates.\nicon:"
0 commit comments