Crates.io | momoka |
lib.rs | momoka |
version | 1.0.1 |
source | src |
created_at | 2023-05-15 15:44:28.127368 |
updated_at | 2023-05-15 16:35:40.101231 |
description | The momoka rs client |
homepage | |
repository | https://github.com/lens-protocol/momoka |
max_upload_size | |
id | 865146 |
size | 331,655 |
This is the rust implementation of the momoka library. It is currently beta and still recommended you use the momoka-node for now. The rust library will be the main client in the future, the node and client verifier logic will always be supported and maintained so people can verify client side.
$ cargo install momoka
Usage: momoka [OPTIONS]
Options:
-n <NODE> The URL of the node
-e <ENVIRONMENT> The environment (e.g., "MUMBAI" or "POLYGON")
-d <DEPLOYMENT> The deployment (e.g., "PRODUCTION")
-t <TX_ID> The transaction ID to check proof for
-r Flag indicating whether to perform a resync
-h, --help Print help
-V, --version Print version
It is easy to run the momoka verifier locally using cargo. You can do so by running the following commands:
$ momoka
Note if you do not supply a -n="YOUR_NODE"
it will use a free node which has very low rate limits. If using it for anything in production you should supply your own node.
This will start verifying any incoming momoka transactions live. You can also can specify to resync from transaction 1 by adding the -r
flag (this needs a node which is paid and has a high rate limit).
$ momoka -t="TX_ID"
It is easy to run the momoka verifier locally using cargo. You can do so by running the following command:
$ cargo run -- -n="YOUR_NODE" [-r] [-t="TX_ID"]