Blue lahar patch 1 #17

ZaatarHerb · 2022-02-19T03:59:13Z

No description provided.

1/ "is comprised of" is incorrect; should be "comprises" or "is composed of" 2/ "three" not "3" - the rule is write out numerals up to nine 3/ Nodes service these Relays by submitting them ... and sending the "responses" - "responses" reads better than "response" as the subject, "relays," is plural 4/ The mechanism the Network uses to regulate the interactions between Applications and Nodes *is* [not "are" as the subject, "mechanism." is singular] 5/ Sessions - a data structure - are generated... [using the dashes avoids having to write "Sessions are a data structure that *is* generated..." which sounds awkward ["are" generated is incorrect as the subject is “structure"] 6/ changed "which" to "that" to avoid using which twice in the same sentence, and deleted "will" as it's implied 7/ deleted a few unnecessary commas

height · 2022-02-19T03:59:14Z

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

Olshansk · 2022-02-24T18:57:43Z

main-concepts/protocol/README.md


-An Application submits Relays, or API requests meant to be routed to any public database node. Nodes service these Relays, by submitting them to the public databases they are meant for, and sending the response (if any) back to the Application. The Network Layer is comprised of all the rules, protocols and finality storage that serve as the backbone of the interactions between Applications and Nodes, including (but not limited to), configuration, record tracking, governance and economic policy.&#x20;
+An Application submits Relays, or API requests meant to be routed to any public database node. Nodes service these Relays by submitting them to the public databases they are meant for, and sending the responses (if any) back to the Application. The Network Layer comprises all the rules, protocols and finality storage that serve as the backbone of the interactions between Applications and Nodes, including (but not limited to) configuration, record tracking, governance and economic policy.&#x20;


The Pocket Network (composed of the utility, network, persistence and consensus layers) comprises...

Olshansk · 2022-02-24T19:01:10Z

paths/node-runner/README.md

@@ -42,11 +42,40 @@ If you're determined to learn by doing, we recommend using [Node Pilot](https://

 ### Hardware

-**Hardware Requirements:** 4 CPU’s (or vCPU’s) | 8 GB RAM | 200GB Disk
+**Hardware Requirements:** 4 CPUs (or vCPUs) | 8 GB RAM | 200GB Disk


Just to be safe: 8 vCPUs | 16 GB RAM | 300 GB Disk

This will require an update to some sentences below.

Olshansk · 2022-02-24T19:01:29Z

paths/node-runner/README.md

+
+Plan hardware for 4 vCPUs per Pocket node, but when creating the node allocate 16. This will allow nodes extra resources to close app large sessions.
+
+Since the Pocket node is a continuously running blockchain, new data is always being stored on it. As 200GB might suffice only for about six months, consider having much more storage than minimally required.  


Since the Pocket node is a continuously running blockchain, new data is always being stored on it. -> Since the Pocket node is a continuously synching the blockchain, new data is always being written to disk.

Olshansk · 2022-02-24T19:03:32Z

paths/node-runner/README.md

+
+**NOTE**: You'll also need to run the full nodes of other blockchains, which may have their own hardware requirements that exceed Pocket's. 
+
+The blockchains, i.e., relay chains, you wish to support will determine the vCPU, RAM and disk space you’ll need for the server hosting them. A guide is available [here]: (https://docs.decentralizedauthority.com/hardware-recommendations)


A guide is available here.

Olshansk · 2022-02-24T19:04:08Z

paths/node-runner/README.md

+
+If you plan to run the relay chains on the same machine as your Pocket node, make sure you have enough resources to support them.
+
+TIP: Take the minimum required disk space you calculated for your blockchain node and triple it. This will accommodate potential rapid blockchain growth. As chains and validators tend to get hungrier, e.g., due to unforeseen bugs or natural growth, additional vCPU and RAM may be required later. {: .alert .alert-info}


NIT: Make the TIPS bolded or italicize the whole sentence so it stands out a bit.

Ditto for the TIPs below.

I don't think {: .alert .alert-info} works on github markdown.

Olshansk · 2022-02-24T19:21:40Z

paths/node-runner/README.md

+
+For VPS or Dedicated Servers, you may not have your choice of hardware. So select the closest to the required specifications. You will want as dedicated a server as possible without "noisy neighbours" or shared resources to achieve maximum performance.
+
+**HOST**: Pick a reliable host or data centre. Remember: if they go down - you go down.


Remember: if they go down - you go down. It makes sense, but I'm just not a fan of the wording.

Maybe, "Please note that if validator may get jailed if your host provider is down for a prolonged period of time".

Olshansk · 2022-02-24T19:22:33Z

paths/node-runner/README.md

+
+**HOST**: Pick a reliable host or data centre. Remember: if they go down - you go down.
+
+**REGION**: Host as close as possible to one of the Pocket network portals. For a list of portal locations see: [insert info or link here]


TODO: link is still missing.

Olshansk · 2022-02-24T19:25:03Z

paths/node-runner/README.md

+
+**REGION**: Host as close as possible to one of the Pocket network portals. For a list of portal locations see: [insert info or link here]
+
+**Pocket Nodes per Relay Chain**: A single relay-chain can be connected to multiple Pocket nodes. The maximum number depends on the hardware and bandwidth limitations of the chain node and the number of RPC requests it will receive at a time. How to check if you’ve reached your limit: trial and error.


How to check if you’ve reached your limit: trial and error.

Optimizing your rewards will come with empirical experience over time; i.e. trial and error.

Olshansk · 2022-02-24T19:26:01Z

paths/node-runner/README.md

+
+NOTE: Addresses below in params are random from the explorer, but you should get a hash in the result that represents some value other than 0x0.
+
+Etherum full node:


Consider making a bulleted list

Olshansk · 2022-02-24T19:26:14Z

paths/node-runner/README.md

+NOTE: Addresses below in params are random from the explorer, but you should get a hash in the result that represents some value other than 0x0.
+
+Etherum full node:
+curl -X POST --data '{"relay_network_id":"0021","payload":{"data":"{\"jsonrpc\":\"2.0\",\"method\":\"eth_getBalance\",\"params\":[\"0xD45C4950741A023a6Bd426EB11178AeF943728a0\", \"latest\"],\"id\":1}","method":"POST","path":"","headers":{}}}' localhost:8082/v1/client/sim


Commands should be wrapped in triple quotes(```): ...

Olshansk · 2023-01-21T00:46:35Z

@BlueLahar Do you still plan to respond to the comments?

ZaatarHerb added 2 commits December 14, 2021 22:51

update node runner readme.md

f372071

replcae en dash with em dashj

b1e9a6e

Olshansk requested review from jacklaing and Olshansk February 24, 2022 19:27

Olshansk requested changes Feb 24, 2022

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Blue lahar patch 1 #17

Blue lahar patch 1 #17

ZaatarHerb commented Feb 19, 2022

height bot commented Feb 19, 2022

Olshansk Feb 24, 2022

Olshansk Feb 24, 2022

Olshansk Feb 24, 2022

Olshansk Feb 24, 2022

Olshansk Feb 24, 2022

Olshansk Feb 24, 2022

Olshansk Feb 24, 2022

Olshansk Feb 24, 2022

Olshansk Feb 24, 2022

Olshansk Feb 24, 2022

Olshansk Feb 24, 2022

Olshansk commented Jan 21, 2023


		An Application submits Relays, or API requests meant to be routed to any public database node. Nodes service these Relays, by submitting them to the public databases they are meant for, and sending the response (if any) back to the Application. The Network Layer is comprised of all the rules, protocols and finality storage that serve as the backbone of the interactions between Applications and Nodes, including (but not limited to), configuration, record tracking, governance and economic policy.
		An Application submits Relays, or API requests meant to be routed to any public database node. Nodes service these Relays by submitting them to the public databases they are meant for, and sending the responses (if any) back to the Application. The Network Layer comprises all the rules, protocols and finality storage that serve as the backbone of the interactions between Applications and Nodes, including (but not limited to) configuration, record tracking, governance and economic policy.


		Plan hardware for 4 vCPUs per Pocket node, but when creating the node allocate 16. This will allow nodes extra resources to close app large sessions.

		Since the Pocket node is a continuously running blockchain, new data is always being stored on it. As 200GB might suffice only for about six months, consider having much more storage than minimally required.


		NOTE: You'll also need to run the full nodes of other blockchains, which may have their own hardware requirements that exceed Pocket's.

		The blockchains, i.e., relay chains, you wish to support will determine the vCPU, RAM and disk space you’ll need for the server hosting them. A guide is available [here]: (https://docs.decentralizedauthority.com/hardware-recommendations)


		If you plan to run the relay chains on the same machine as your Pocket node, make sure you have enough resources to support them.

		TIP: Take the minimum required disk space you calculated for your blockchain node and triple it. This will accommodate potential rapid blockchain growth. As chains and validators tend to get hungrier, e.g., due to unforeseen bugs or natural growth, additional vCPU and RAM may be required later. {: .alert .alert-info}


		For VPS or Dedicated Servers, you may not have your choice of hardware. So select the closest to the required specifications. You will want as dedicated a server as possible without "noisy neighbours" or shared resources to achieve maximum performance.

		HOST: Pick a reliable host or data centre. Remember: if they go down - you go down.


		HOST: Pick a reliable host or data centre. Remember: if they go down - you go down.

		REGION: Host as close as possible to one of the Pocket network portals. For a list of portal locations see: [insert info or link here]


		REGION: Host as close as possible to one of the Pocket network portals. For a list of portal locations see: [insert info or link here]

		Pocket Nodes per Relay Chain: A single relay-chain can be connected to multiple Pocket nodes. The maximum number depends on the hardware and bandwidth limitations of the chain node and the number of RPC requests it will receive at a time. How to check if you’ve reached your limit: trial and error.


		NOTE: Addresses below in params are random from the explorer, but you should get a hash in the result that represents some value other than 0x0.

		Etherum full node:

Blue lahar patch 1 #17

Are you sure you want to change the base?

Blue lahar patch 1 #17

Conversation

ZaatarHerb commented Feb 19, 2022

height bot commented Feb 19, 2022

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Olshansk commented Jan 21, 2023