Auto-generated documentation.
Compute the balance tree and the nullifier tree given the deposits and claims.
polycli ulxly compute-balance-nullifier-tree [flags]This command will attempt to compute the root of the balnace tree based on the bridge events that are provided.
Example usage:
polycli ulxly compute-balance-nullifier-tree \
--l2-claims-file l2-claim-0-to-11454081.ndjson \
--l2-deposits-file l2-deposits-0-to-11454081.ndjson \
--l2-network-id 3 \
--bridge-address 0x528e26b25a34a4A5d0dbDa1d57D318153d2ED582 \
--rpc-url http://localhost:8213 | jq '.'In this case we are assuming we have two files
l2-claim-0-to-11454081.ndjson and l2-deposits-0-to-11454081.ndjson that would have been generated
with a call to polycli ulxly get-deposits and polycli ulxly get-claims pointing to each network.
The output will be the roots of the trees for the provided deposits and claims.
This is the response from polycli:
{
"balanceTreeRoot": "0x089ed8cce8639374a1bbd2480df7ed5224ea715b7521e1e2de549a6def791757",
"nullifierTreeRoot": "0x7f075c4345694cc79a573890d7ec6222534cf470355611801104be0c8bf972c4",
"initPessimisticRoot": "0x4358f03557f5d34ab419bee9919b4858c9d9bdedbe8e7ce7fb78ff9c4bc65676"
}Note: more info https://github.com/BrianSeong99/Agglayer_PessimisticProof_Benchmark?tab=readme-ov-file#architecture-of-pessimistic-proof
--bridge-address string bridge address
-h, --help help for compute-balance-nullifier-tree
--insecure skip TLS certificate verification
--l2-claims-file string ndjson file with l2 claim events data
--l2-deposits-file string ndjson file with l2 deposit events data
--l2-network-id uint32 L2 network ID
-r, --rpc-url string RPC URLThe command also inherits flags from parent commands.
--config string config file (default is $HOME/.polygon-cli.yaml)
--pretty-logs output logs in pretty format instead of JSON (default true)
-v, --verbosity string log level (string or int):
0 - silent
100 - panic
200 - fatal
300 - error
400 - warn
500 - info (default)
600 - debug
700 - trace (default "info")- polycli ulxly - Utilities for interacting with the uLxLy bridge.