You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: nexus-sdk/cli.md
+25-5Lines changed: 25 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -45,16 +45,16 @@ This command should also check that the URL is accessible by the Leader node. It
45
45
**`nexus tool validate --on-chain <ident>`**
46
46
47
47
{% hint style="warning" %}
48
-
The specific design for onchain tools is still in progress and as a result the implementation is not yet implemented. When running the command, it will panic.
48
+
The specific design for onchain tools is still in progress and as a result the implementation is not yet present. When running the command, it will panic.
Command that makes a request to `GET <url>/meta` to fetch the Tool definition and then submits a TX to our Tool Registry. It also locks the collateral.
55
+
Command that makes a request to `GET <url>/meta` to fetch the Tool definition and then submits a TX to our Tool Registry. It also locks the collateral and sets the single invocation cost of the Tool which defaults to 0 MIST.
56
56
57
-
This returns an OwnerCap object ID that can be used to manage the Tool.
57
+
This returns 2 OwnerCap object IDs that can be used to manage the Tool and its Gas settlement methods.
58
58
59
59
{% hint style="info" %}
60
60
This command requires that a wallet is connected to the CLI...
@@ -65,7 +65,7 @@ This command requires that a wallet is connected to the CLI...
65
65
**`nexus tool register --on-chain <ident>`**
66
66
67
67
{% hint style="warning" %}
68
-
The specific design for onchain tools is still in progress and as a result the implementation is not yet implemented. When running the command, it will panic.
68
+
The specific design for onchain tools is still in progress and as a result the implementation is not yet present. When running the command, it will panic.
69
69
{% endhint %}
70
70
71
71
---
@@ -162,6 +162,22 @@ Inspects a DAG execution process based on the provided `DAGExecution` object ID
162
162
163
163
---
164
164
165
+
### `nexus gas`
166
+
167
+
Set of commands to manage Nexus gas budgets and tickets.
168
+
169
+
---
170
+
171
+
**`nexus gas add-budget --coin <object_id>`**
172
+
173
+
Upload the coin object to the Nexus gas service as budget in the "invoker address" scope. That means that if a DAG execution is started from the address that the coin was uploaded from, the coin can be used to pay for the gas.
174
+
175
+
{% hint style="info" %}
176
+
This command requires that a wallet is connected to the CLI...
177
+
{% endhint %}
178
+
179
+
---
180
+
165
181
### `nexus network`
166
182
167
183
Set of commands for managing Nexus networks.
@@ -174,6 +190,10 @@ Create a new Nexus network and assign `count-leader-caps` (default: 5) leader ca
174
190
175
191
The network object ID is returned.
176
192
193
+
{% hint style="info" %}
194
+
This command requires that a wallet is connected to the CLI...
Copy file name to clipboardExpand all lines: nexus-sdk/guides/setup.md
+12Lines changed: 12 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -87,6 +87,18 @@ source .envrc
87
87
To automatically load these variables every time you navigate to the project directory, consider using [direnv](https://direnv.net/). After installing it, run `direnv allow` within your project directory.
88
88
{% endhint %}
89
89
90
+
### Upload some gas budget to Nexus
91
+
92
+
In order to pay for the network transaction fees and the tool invocations, you need to upload some gas budget to Nexus. You can do this by running the following command:
93
+
94
+
```bash
95
+
nexus gas add-budget --coin <object_id>
96
+
```
97
+
98
+
{% hint style="info" %}
99
+
Note that this coin can only be used to pay for Nexus and tool invocation fees only if the DAG is executed from the **same address**.
100
+
{% endhint %}
101
+
90
102
### Configure the Sui client
91
103
92
104
After installing the Sui binaries, configure and activate your Talus `devnet` environment:
0 commit comments