mirror of
https://github.com/fluencelabs/eip712-validation-node
synced 2025-05-02 11:52:14 +00:00
update readme.md
This commit is contained in:
parent
edff3861fd
commit
dbaab5b9b4
20
README.md
20
README.md
@ -73,21 +73,23 @@ TODO:
|
||||
|
||||
## Running A Peer
|
||||
|
||||
Install the Node dependencies and start the peer:
|
||||
Install the Node dependencies and start the peer in the `` directory:
|
||||
|
||||
```bash
|
||||
npm i
|
||||
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
|
||||
* ...
|
||||
|
||||
with the difference being that ... takes a ....
|
||||
```bash
|
||||
nohup node start &
|
||||
```
|
||||
|
||||
the corresponding Aqua are:
|
||||
for a long-running daemon.
|
||||
|
||||
* ... ad
|
||||
* ... respectively.
|
||||
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.
|
||||
|
||||
Using the command line utility [`fldist`]("https://doc.fluence.dev/docs/knowledge_tools"), for example, we can run:
|
||||
|
||||
TBD
|
||||
|
Loading…
x
Reference in New Issue
Block a user