@elgora/cli 9.1.0 → 10.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +16 -12
- package/dist/cli.js +422 -523
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -27,10 +27,11 @@ answer.
|
|
|
27
27
|
|
|
28
28
|
## Commands
|
|
29
29
|
|
|
30
|
-
- `poster:review` checks a bounty page
|
|
31
|
-
|
|
32
|
-
- `poster:publish-fund`
|
|
33
|
-
|
|
30
|
+
- `poster:review` checks a bounty page; Elgora keeps the approval for those
|
|
31
|
+
exact bytes. Rejected pages print the full issue list and exit 2.
|
|
32
|
+
- `poster:publish-fund` publishes the exact `bounty_challenge.md` bytes and
|
|
33
|
+
funds the new bounty. It reuses the saved approval for those bytes without
|
|
34
|
+
another AI review, or reviews them first.
|
|
34
35
|
- `poster:open-winning-submission` retrieves the finalized winning Submission
|
|
35
36
|
for the funding Poster and decrypts it locally.
|
|
36
37
|
- `check-page <bounty_challenge_md_path|->` checks structural conformance offline,
|
|
@@ -64,8 +65,11 @@ time, so it stays correct however the CLI was installed.
|
|
|
64
65
|
Posters use `ELGORA_POSTER_PRIVATE_KEY`. Solvers should normally use
|
|
65
66
|
`--solver-address` and sign the emitted EIP-712 requests and prepared
|
|
66
67
|
transaction with an external wallet; `ELGORA_SOLVER_PRIVATE_KEY` is an optional
|
|
67
|
-
local testing convenience.
|
|
68
|
-
`
|
|
68
|
+
local testing convenience. Each emitted `typed_data` is in the
|
|
69
|
+
`eth_signTypedData_v4` shape, with `EIP712Domain` in its types; for ethers v6,
|
|
70
|
+
delete `types.EIP712Domain` before passing it to `signTypedData`. Claimants can
|
|
71
|
+
use `--claimant-address`, or `ELGORA_CLAIMANT_PRIVATE_KEY` for a local test
|
|
72
|
+
wallet.
|
|
69
73
|
|
|
70
74
|
Guardian commands use two different kinds of secret:
|
|
71
75
|
|
|
@@ -85,9 +89,9 @@ needs.
|
|
|
85
89
|
|
|
86
90
|
## Deployment configuration
|
|
87
91
|
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
(`base-sepolia`, chain `84532`) behind `https://
|
|
92
|
+
The default deployment is **Base mainnet** (`base`, chain `8453`), which
|
|
93
|
+
escrows real USDC. Elgora's testnet deployment runs on **Base Sepolia**
|
|
94
|
+
(`base-sepolia`, chain `84532`) behind `https://testnet.elgora.ai`. A run that
|
|
91
95
|
selects no network prints one stderr line saying it used the default.
|
|
92
96
|
|
|
93
97
|
Every command accepts `--network <name|chain id>`, which selects the deployment
|
|
@@ -98,9 +102,9 @@ passed — for that run only:
|
|
|
98
102
|
|
|
99
103
|
```sh
|
|
100
104
|
elgora-cli guardian:judgeable # Base mainnet, the default
|
|
101
|
-
elgora-cli claim --network base-sepolia 7 #
|
|
105
|
+
elgora-cli claim --network base-sepolia 7 # testnet, by name
|
|
102
106
|
elgora-cli claim --network 84532 7 # the same, by chain id
|
|
103
|
-
export ELGORA_CHAIN_ID=84532 #
|
|
107
|
+
export ELGORA_CHAIN_ID=84532 # testnet for every run in this shell
|
|
104
108
|
```
|
|
105
109
|
|
|
106
110
|
The chain's public RPC, the ElgoraHub address, the escrow token, and the subgraph
|
|
@@ -114,7 +118,7 @@ targeting a deployment this CLI release does not know about, and do not mix
|
|
|
114
118
|
addresses or endpoints from different deployments.
|
|
115
119
|
|
|
116
120
|
The API follows the chain too: `https://elgora.ai` for `base` and
|
|
117
|
-
`https://
|
|
121
|
+
`https://testnet.elgora.ai` for `base-sepolia`. Commands that use the public API
|
|
118
122
|
accept `--api-base-url <url>`, which wins over `ELGORA_API_BASE_URL` and that
|
|
119
123
|
default for one invocation — for example to reach a Vercel preview. Point it at
|
|
120
124
|
an API serving the deployment you selected.
|