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
> Before creating a pull request, make sure there is an issue corresponding to your changes. If there isn't one,
29
+
> [create one first](#issues).
30
+
31
+
If you want to implement a feature or fix a bug, fork this repository from the `master` and after all the changes
32
+
[create a pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)
33
+
to the `master` branch. Don't forget to run automated tests locally before creating a PR.
34
+
35
+
### Pull request must include the following information:
36
+
37
+
-**Title**. The pull request should be named after the issue number as follows: "Issue <ISSUE_NUMBER>"
38
+
39
+
-**Description**. Briefly describe the feature or fix that was made.
40
+
41
+
-**Changes**. Describe the main changes made in the codebase. It is advisable to insert links to the code for
42
+
greater clarity.
43
+
44
+
-**Interface changes**. Describe how the external interface has changed. It is advisable to insert links to
Copy file name to clipboardExpand all lines: README.md
+20-15Lines changed: 20 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,8 @@ can be set via environment variables or command line parameters see [table
71
71
below](#table_conf). Use `--config` parameter with any command to set configuration file name. By default daemon
72
72
use configuration file in JSON format `snetd.config.json` but other formats are
73
73
also supported via [Viper](https://github.com/spf13/viper). Use `init-full` or `init`
74
-
command to save configuration file with default values. The following configuration properties can be set using a configuration file.
74
+
command to save configuration file with default values. The following configuration properties can be set using a
75
+
configuration file.
75
76
76
77
### Main properties <aname="main_properties"></a>
77
78
@@ -125,21 +126,25 @@ These parameters are needed if you specified free_calls in the service metadata.
125
126
126
127
***private_key_for_free_calls** (required) —
127
128
The private key is used to sign authorization tokens for free calls. This address is NOT required to have any tokens.
128
-
129
-
⚠️ This private key must correspond to the public address specified in your service_metadata.json under the free_calls.public_key field.
130
129
131
-
132
-
***trusted_free_call_signers** (optional, default SingularityNET addresses) — A list of trusted public addresses that are allowed to issue free call tokens on your behalf (e.g. trusted centralized backends or marketplaces).
130
+
⚠️ This private key must correspond to the public address specified in your service_metadata.json under the
131
+
free_calls.public_key field.
133
132
134
-
⚠️ If this field is left empty, free calls will not work via the SingularityNET Marketplace, but will still be available for clients using the Web3 approach (e.g., via SDKs).
133
+
134
+
***trusted_free_call_signers** (optional, default SingularityNET addresses) — A list of trusted public addresses that
135
+
are allowed to issue free call tokens on your behalf (e.g. trusted centralized backends or marketplaces).
136
+
137
+
⚠️ If this field is left empty, free calls will not work via the SingularityNET Marketplace, but will still be
138
+
available for clients using the Web3 approach (e.g., via SDKs).
135
139
136
140
```json
137
141
"trusted_free_call_signers": [
138
142
"0x7DF35C98f41F3Af0df1dc4c7F7D4C19a71Dd059F",
139
143
"0x3Bb9b2499c283cec176e7C707Ecb495B7a961ebf" ]
140
144
```
141
145
142
-
***min_balance_for_free_call** (optional, default 10) — The minimum token (FET) balance (in whole tokens) required on the user's wallet to be eligible for free calls (Web3-based flow).
146
+
***min_balance_for_free_call** (optional, default 10) — The minimum token (FET) balance (in whole tokens) required on
147
+
the user's wallet to be eligible for free calls (Web3-based flow).
143
148
```json
144
149
"min_balance_for_free_call": "1"
145
150
```
@@ -223,6 +228,14 @@ This options are less frequently needed.
223
228
***metering_endpoint** (optional; only applies if `metering_enabled` is set to true) —
224
229
Needs to be a vaild url where the request and response stats are published as part of Metering
225
230
231
+
***private_key_for_metering** (optional; only applies if `metering_enabled` is set to true)
232
+
This is used for authentication between daemon and the metering service in the context publishing stats, Even the
233
+
latest Channel Status is published, this way the offline channel state balance can also be tracked.
234
+
Daemon will send a signature signed by this private key, metering service will already have the public key
235
+
corresponding
236
+
to this Daemon, metering service will ensure that the signer it receives matches the public key configured at its end.
237
+
This is mandatory only when metering is enabled.
238
+
226
239
***ssl_cert** (optional; default: `""`) —
227
240
path to certificate to use for SSL.
228
241
@@ -238,14 +251,6 @@ This options are less frequently needed.
238
251
***payment_channel_storage_server** (optional) —
239
252
see [etcd server configuration](./etcddb#etcd-server-configuration)
240
253
241
-
***pvt_key_for_metering** (optional;only applies if `metering_enabled` is set to true)
242
-
This is used for authentication between daemon and the metering service in the context publishing stats, Even the
243
-
latest Channel Status is published, this way the offline channel state balance can also be tracked.
244
-
Daemon will send a signature signed by this private key, metering service will already have the public key
245
-
corresponding
246
-
to this Daemon, metering service will ensure that the signer it receives matches the public key configured at its end.
The SingularityNET team and community appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
4
+
5
+
Only latest release version is supported. Ensure that you tested latest version before reporting vulnerability.
6
+
7
+
If you find a bug or have a question, you are free to open an issue. If you have a security related question or want to report a security vulnerability, please send it to [security@singualritynet.io](mailto:security@singualritynet.io).
0 commit comments