ConfigOption/node uri - Revision history

Fireduck at 21:58, 27 November 2019

2019-11-27T21:58:15Z

Fireduck at 07:19, 5 July 2019

2019-07-05T07:19:06Z

Fireduck at 07:18, 5 July 2019

2019-07-05T07:18:39Z

Fireduck at 07:09, 4 July 2019

2019-07-04T07:09:16Z

Fireduck at 07:03, 4 July 2019

2019-07-04T07:03:22Z

Fireduck at 07:01, 4 July 2019

2019-07-04T07:01:49Z

Fireduck at 06:59, 4 July 2019

2019-07-04T06:59:25Z

Fireduck: Created page with "==node_uri== Controls which SnowBlossomNode this program connects to. General form is: schema://host[:port][/?key=node:...] If using grpc+tls, the key parameter specifi..."

2019-07-04T06:59:09Z

Created page with "==node_uri== Controls which SnowBlossomNode this program connects to. General form is: schema://host[:port][/?key=node:...] If using grpc+tls, the key parameter specifi..."

New page

==node_uri==

Controls which [[SnowBlossomNode]] this program connects to.

General form is: schema://host[:port][/?key=node:...]

If using grpc+tls, the key parameter specifies which TLS key the node is expected to use.

===Default===
None
===Examples===
<code>
node_uri=grpc://snow-tx1.snowblossom.org
node_uri=grpc://snow-tx1.snowblossom.org:2338
node_uri=grpc+tls://snow-tx1.snowblossom.org
node_uri=grpc+tls://snow-tx1.snowblossom.org?key=node:fgmfupck7seaq8t2gl6plzs5vh7nyl6656wscgq3

</code>

[[Category:ConfigOptions]]
[[Category:ConfigOptionsNode]]
[[Category:ConfigOptionsMiner]]
[[Category:ConfigOptionsMrPlow]]
[[Category:ConfigOptionsShackletonExplorer]]
[[Category:ConfigOptionsClient]]

← Older revision		Revision as of 21:58, 27 November 2019
Line 43:		Line 43:
	[[Category:ConfigOptionsShackletonExplorer]]		[[Category:ConfigOptionsShackletonExplorer]]
	[[Category:ConfigOptionsClient]]		[[Category:ConfigOptionsClient]]
		+	[[Category:ConfigOptionsChannelNode]]

← Older revision		Revision as of 07:19, 5 July 2019
Line 15:		Line 15:

	Normal URI parsing applies.		Normal URI parsing applies.
		+
		+	It can also be a comma separated list of multiple URIs, in which case the first to reply will be used.

← Older revision		Revision as of 07:18, 5 July 2019
Line 30:		Line 30:

	node_uri=grpc+tls://snow-tx1.snowblossom.org?key=node:fgmfupck7seaq8t2gl6plzs5vh7nyl6656wscgq3		node_uri=grpc+tls://snow-tx1.snowblossom.org?key=node:fgmfupck7seaq8t2gl6plzs5vh7nyl6656wscgq3
		+
		+	node_uri=grpc+tls://snow-tx1.snowblossom.org,grpc+tls://snow-de1.snowblossom.org

	</code>		</code>

← Older revision		Revision as of 07:09, 4 July 2019
Line 8:		Line 8:

	For best security and privacy it is best to use grpc+tls and specify the key.		For best security and privacy it is best to use grpc+tls and specify the key.
		+	If you don't know the key for a particular server, connect without the key and look for a log entry like this:
		+
		+	<code>
		+	INFO: Connected to TLS server with key: node:fse8tvly48zwz9fej6x5znsrm573pyyf83uj9kxw
		+	</code>

	Normal URI parsing applies.		Normal URI parsing applies.

← Older revision		Revision as of 07:03, 4 July 2019
Line 8:		Line 8:

	For best security and privacy it is best to use grpc+tls and specify the key.		For best security and privacy it is best to use grpc+tls and specify the key.
		+
		+	Normal URI parsing applies.

← Older revision		Revision as of 07:01, 4 July 2019
Line 6:		Line 6:

	If using grpc+tls, the key parameter specifies which TLS key the node is expected to use.		If using grpc+tls, the key parameter specifies which TLS key the node is expected to use.
		+
		+	For best security and privacy it is best to use grpc+tls and specify the key.
		+

@@ Line 12: / Line 12: @@
 ===Examples===
 <code>
 node_uri=grpc://snow-tx1.snowblossom.org
 node_uri=grpc://snow-tx1.snowblossom.org:2338
 node_uri=grpc+tls://snow-tx1.snowblossom.org
 node_uri=grpc+tls://snow-tx1.snowblossom.org?key=node:fgmfupck7seaq8t2gl6plzs5vh7nyl6656wscgq3