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
{{ message }}
This repository was archived by the owner on Mar 8, 2024. It is now read-only.

3
+

4
4
5
-
Command-line interface to create, fetch, sign, and verify PayIDs.
6
-
Based on the Typescript PayID[Utils](https://github.com/payid-org/utils) library.
5
+
Command-line interface to create, fetch, sign, and verify PayStrings.
6
+
Based on the Typescript PayString[Utils](https://github.com/paystring/utils) library.
7
7
8
8
## Prerequisites
9
9
10
-
Before you install PayID CLI locally, ensure that both [node](https://nodejs.org/en/download/) and
10
+
Before you install PayString CLI locally, ensure that both [node](https://nodejs.org/en/download/) and
11
11
[npm](https://docs.npmjs.com/downloading-and-installing-packages-locally) are installed locally.
12
12
13
-
You can also run PayID CLI as a Docker container. If you run commands that cause information to be stored locally, that information only persists for the duration of the container.
13
+
You can also run PayString CLI as a Docker container. If you run commands that cause information to be stored locally, that information only persists for the duration of the container.
14
14
15
15
## Installation
16
16
17
-
To install PayID CLI, run the command:
17
+
To install PayString CLI, run the command:
18
18
19
19
```
20
-
npm install -g @payid-org/payid-cli
20
+
npm install -g @paystring/paystring-cli
21
21
```
22
22
23
-
This command installs PayID CLI as a global npm module and links it as a `payid` executable
24
-
(typically under /usr/local/bin/payid).
23
+
This command installs PayString CLI as a global npm module and links it as a `paystring` executable
24
+
(typically under /usr/local/bin/paystring).
25
25
26
26
Alternatively, install and run via Docker:
27
27
28
28
```
29
-
docker run xpring/payid-cli
29
+
docker run xpring/paystring-cli
30
30
```
31
31
32
32
## Interactive vs. single command mode
33
33
34
-
You can run PayID CLI in either interactive mode or non-interactive (single command) mode.
34
+
You can run PayString CLI in either interactive mode or non-interactive (single command) mode.
35
35
In interactive mode, a prompt is displayed, and you can run multiple commands from this prompt. Run the `exit` command to leave interactive mode.
36
36
37
37
Interactive mode retains a history of executed commands that you can access by with the up arrow key. Use the <Tab> key for command completion.
@@ -40,25 +40,25 @@ In non-interactive mode, you run a single command, based on supplied command lin
40
40
No prompt is displayed in this mode. Non-interactive mode is useful for running commands from a script, or to chain the results
41
41
of multiple commands together.
42
42
43
-
To run the CLI in interactive mode, run `payid`. You can now enter `<command> arguments` for each command you want to run.
43
+
To run the CLI in interactive mode, run `paystring`. You can now enter `<command> arguments` for each command you want to run.
44
44
45
-
To run the CLI in non-interactive mode, run `payid <command> <arguments>`.
45
+
To run the CLI in non-interactive mode, run `paystring <command> <arguments>`.
46
46
47
47
Examples of non-interactive mode:
48
48
49
-
The following command lists information about the specified PayID.
49
+
The following command lists information about the specified PayString.
50
50
51
51
```
52
-
payid load 'nhartner$xpring.money'
52
+
paystring load 'nhartner$xpring.money'
53
53
```
54
54
55
-
You can run multiple commands chained together. This set of commands initializes a new or existing PayID, associates a specified crypto-address for the specified currency and network, and then saves the PayID with this information.
55
+
You can run multiple commands chained together. This set of commands initializes a new or existing PayString, associates a specified crypto-address for the specified currency and network, and then saves the PayString with this information.
The PayID JSON representation specified here is saved to the local filesystem as example.json.
116
+
The PayString JSON representation specified here is saved to the local filesystem as example.json.
117
117
118
118
### Identity Keys
119
119
120
-
The PayID protocol supports signing address mappings using one or more cryptographic keys.
121
-
PayID CLI provides several commands to generate and load keys. Once a key is generated
122
-
or loaded by PayID CLI, it is retained in PayID CLI's local storage for use when you sign your PayID.
120
+
The PayString protocol supports signing address mappings using one or more cryptographic keys.
121
+
PayString CLI provides several commands to generate and load keys. Once a key is generated
122
+
or loaded by PayString CLI, it is retained in PayString CLI's local storage for use when you sign your PayString.
123
123
124
124
You can generate multiple identity keys by using the `keys generate` and `keys load` commands.
125
125
126
126
To remove all loaded keys from the CLI's local storage, use the `keys clear` command.
127
-
To see all keys currently loaded into PayID CLI, use the `keys list` command.
127
+
To see all keys currently loaded into PayString CLI, use the `keys list` command.
128
128
129
129
To generate a new key run:
130
130
@@ -135,34 +135,34 @@ keys generate
135
135
This generates a new key and saves it to a file named `identity-key.pem`. To load a previously
136
136
created identity key, run `keys load </path/to/pem/file>`.
137
137
138
-
### Sign a PayID
138
+
### Sign a PayString
139
139
140
-
Before you sign an PayID, you must either load the PayID using the `load` command, or create a PayID using the
141
-
`init` command, and you must execute commands so that the PayID one or more crypto-addresses.
140
+
Before you sign an PayString, you must either load the PayString using the `load` command, or create a PayString using the
141
+
`init` command, and you must execute commands so that the PayString one or more crypto-addresses.
142
142
143
-
Once a PayID has been initialized or loaded, you can sign it using an [identity key](#identity-keys). You must either generate a new key, or load an existing one. Once your PayID has been loaded or initialized, and your identity key has been generated or loaded,
144
-
you can sign the PayID using `sign` command. The `sign` command signs each of your PayID address
145
-
mappings using the loaded identity keys, and outputs the resulting PayID with a `verifiedAddress` field.
143
+
Once a PayString has been initialized or loaded, you can sign it using an [identity key](#identity-keys). You must either generate a new key, or load an existing one. Once your PayString has been loaded or initialized, and your identity key has been generated or loaded,
144
+
you can sign the PayString using `sign` command. The `sign` command signs each of your PayString address
145
+
mappings using the loaded identity keys, and outputs the resulting PayString with a `verifiedAddress` field.
146
146
147
147
By default, the sign command clears the unsigned `addresses` from the results. If you wish to
148
148
retain unsigned addresses after signing, use `sign --keep-addresses` or `sign -k` instead.
149
149
150
-
Finally, run the `save` command to save your PayID, with signed addresses, to file.
150
+
Finally, run the `save` command to save your PayString, with signed addresses, to file.
151
151
152
-
### Inspect a Verified PayID
152
+
### Inspect a Verified PayString
153
153
154
-
Two commands are available to verify a PayID's verified addresses.
154
+
Two commands are available to verify a PayString's verified addresses.
155
155
156
156
-`verify` - checks if all the verified addresses have valid signatures.
157
157
-`inspect` - displays details information about each verified address and signatures.
158
158
159
-
## Create, sign, and inspect a PayID
159
+
## Create, sign, and inspect a PayString
160
160
161
-
With a combination of commands, you can create a PayID, add an address mapping, generate an identity key,
162
-
sign your PayID address mapping, and then inspect the final result.
161
+
With a combination of commands, you can create a PayString, add an address mapping, generate an identity key,
162
+
sign your PayString address mapping, and then inspect the final result.
By using, reproducing, or distributing this code, you agree to the terms and conditions for use (including the Limitation of Liability) in the [Apache License 2.0](https://github.com/payid-org/payid-cli/blob/master/LICENSE). If you do not agree, you may not use, reproduce, or distribute the code. **This code is not authorised for download in Australia. Any persons located in Australia are expressly prohibited from downloading, using, reproducing or distributing the code.** This code is not owned by, or associated with, NPP Australia Limited, and has no sponsorship, affiliation or other connection with the "Pay ID" service operated by NPP Australia Limited in Australia.
174
+
By using, reproducing, or distributing this code, you agree to the terms and conditions for use (including the Limitation of Liability) in the [Apache License 2.0](https://github.com/paystring/payid-cli/blob/master/LICENSE). If you do not agree, you may not use, reproduce, or distribute the code. **This code is not authorised for download in Australia. Any persons located in Australia are expressly prohibited from downloading, using, reproducing or distributing the code.**
0 commit comments