fluencelabs/eip712-validation-node
1
0
Fork 0
mirror of https://github.com/fluencelabs/eip712-validation-node synced 2025-05-03 04:12:13 +00:00
Code Issues Projects Releases Wiki Activity

update readme.md

Browse Source
This commit is contained in:
boneyard93501 2021-10-04 10:52:54 -05:00
parent edff3861fd
commit dbaab5b9b4
1 changed files with 11 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -73,21 +73,23 @@ TODO:
## Running A Peer ## Running A Peer
Install the Node dependencies and start the peer: Install the Node dependencies and start the peer in the `` directory:
```bash ```bash
npm i npm i
npm start npm start
``` ```
With the node up and running, we can access the validation and query capabilities with Aqua initiated from any other (client) peer including a browser. The currently exposes two validation methods: Or run with:
* ... and ```bash
* ... nohup node start &
```
with the difference being that ... takes a .... for a long-running daemon.
the corresponding Aqua are: With the node up and running, we can access the validation and query capabilities with Aqua initiated from any other (client) peer including a browser. We can currently call the validation process from [Aqua](./aqua/snapshot.aqua) with two methods: `validate` and `validate_from_url` with the former accepting a json string and the later the url to a json body.
* ... ad Using the command line utility [`fldist`]("https://doc.fluence.dev/docs/knowledge_tools"), for example, we can run:
* ... respectively.
TBD