Skip to content

Commit d91176a

Browse files
update readme
1 parent e22846b commit d91176a

File tree

1 file changed

+5
-5
lines changed
  • create-leo-app/template-offline-public-transaction-ts

1 file changed

+5
-5
lines changed

create-leo-app/template-offline-public-transaction-ts/README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
# Offline Transaction Builder
22

33
## 1. Overview
4-
### 1.1 Proving Keys for Zero Knowledge Function Execution
5-
To achieve zero knowledge execution, all Aleo functions require a `ProvingKey` and `VerifyingKey` in order to build a
6-
zero knowledge ZkSnark proof of execution. If a user does not possess these keys for a function, they are normally
4+
### 1.1 Proving Keys for Zero-Knowledge Function Execution
5+
To achieve zero-knowledge execution, all Aleo functions require a `ProvingKey` and `VerifyingKey` in order to build a
6+
zero-knowledge zk-SNARK proof of execution. If a user does not possess these keys for a function, they are normally
77
downloaded from the internet when the function is called.
88

99
### 1.2 Key Providers
@@ -31,7 +31,7 @@ construction of the offline transaction.
3131
### 2.1 Pre-Download the Keys
3232
First run this command online to download the key material to disk:
3333

34-
`npm start`
34+
`npm run build`
3535

3636
Once this command is run, all proving keys for the `transfer_public`, `bond_public`, `unbond_public`, and
3737
`claim_unbond_public` functions will be downloaded to the `./keys` folder. The machine can then be disconnected from
@@ -43,7 +43,7 @@ adding the key material yourself.
4343

4444
Once the key material is downloaded, turn off your internet connection and run the following command:
4545

46-
`npm start`
46+
`npm run dev`
4747

4848
You should see the transactions being built and the resulting transaction IDs printed to the console.
4949

0 commit comments

Comments
 (0)