-
Notifications
You must be signed in to change notification settings - Fork 721
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updates Service Provider Guide #826
Conversation
@@ -208,8 +245,4 @@ invariant broken: | |||
``` | |||
|
|||
When submitting a invariant-broken transaction, transaction fee tokens are not | |||
deducted as the blockchain will halt (aka. this is a free transaction). | |||
|
|||
## Upgrade to Validator Node |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Full Node setup should be providing the setup how to create a Full Node.
Opening REST API, GRPC and remote access are all suggestions that are not for a validator node, which should have different security setups. Therefore upgrading an open Full Node to a Validator Node should not be emphasized in this setup.
Looks good to me! |
Some gaps I see here.
|
Happy to merge this and improve it later with the above |
Thanks for the suggestions @zmanian Good hint for the websocket, I will add an example. I agree, that merging now and adding more info later would be best right now, since I know a few parties waiting for these changes already. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tiny contributions for grammar, thank you for doing this work, I am always learning.
Co-authored-by: Barrie Byron <barrie.byron@tendermint.com>
Thanks so much @barriebyron for the review 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is wonderful @toschdev. Thanks @barriebyron and @zmanian for comments too.
docs/gaia-tutorials/installation.md
Outdated
@@ -21,7 +21,7 @@ source ~/.bash_profile | |||
``` | |||
|
|||
::: tip | |||
**Go 1.15+** is required for the Cosmos SDK. | |||
**Go 1.16+** or later is required for the Cosmos SDK. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gaia is still on 1.15 until 1.16 is properly integrated into actions and tests
docs/gaia-tutorials/installation.md
Outdated
build_tags: netgo,ledger | ||
go: go version go1.12.5 darwin/amd64 | ||
go: go version go1.16 darwin/amd64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as before, we are on go1.15
|
||
minimum-gas-prices = "" | ||
minimum-gas-prices = "0.025uatom" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest matching what's written as the example's text, e.g., is "10uatom" written as "10utom"? Is 0.025uatom the official recommendation? If there's an official standard, perhaps a link could be helpful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it's actually in the same document a few lines below
End of chapter a note on gas and fees
. So I thought let's make it even more clear. Having no input is actually dangerous (because of transaction flood) - so let's add it to the code snipped directly.
https://github.com/cosmos/gaia/blob/main/docs/gaia-tutorials/join-mainnet.md#a-note-on-gas-and-fees
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Speaking about this, we could consider making this default into the bootstrapped app.toml
file.
|
||
By default every node is in `PruneSyncable` mode. If you would like to change your nodes pruning strategy then you must do so when the node is initialized. For example, if you would like to change your node to the `PruneEverything` mode then you can pass the `---pruning everything` flag when you call `gaiad start`. | ||
By default every node is in `default` mode. This is the recommended setting for most environments. | ||
If you would like to change your nodes pruning strategy then you must do so when the node is initialized. Passing a flag when starting `gaia` will always override settings in the `app.toml` file, if you would like to change your node to the `everything` mode then you can pass the `---pruning everything` flag when you call `gaiad start`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re: only when the node is initialized
. Do you mean when the node is started? Or after initialization i.e., gaiad init, sets the mode in stone? Does the command line argument then modify the behaviour after it's started the first time?
|
||
By default every node is in `PruneSyncable` mode. If you would like to change your nodes pruning strategy then you must do so when the node is initialized. For example, if you would like to change your node to the `PruneEverything` mode then you can pass the `---pruning everything` flag when you call `gaiad start`. | ||
By default every node is in `default` mode. This is the recommended setting for most environments. | ||
If you would like to change your nodes pruning strategy then you must do so when the node is initialized. Passing a flag when starting `gaia` will always override settings in the `app.toml` file, if you would like to change your node to the `everything` mode then you can pass the `---pruning everything` flag when you call `gaiad start`. | ||
|
||
> Note: When you are pruning state you will not be able to query the heights that are not in your store. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe that it is possible but only by specifying a node target that has a different pruning strategy.
@@ -4,79 +4,194 @@ order: 5 | |||
|
|||
# Service Providers | |||
|
|||
We define 'service providers' as entities providing services for end-users that involve some form of interaction with a Cosmos-SDK based blockchain (this includes the Cosmos Hub). More specifically, this document will be focused around interactions with tokens. | |||
'Service Providers' are defined as entities that provide services for end-users that involve some form of interaction with the Cosmos Hub. More specifically, this document is focused on interactions with tokens. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest adding, "for example, exchanges".
docs/resources/service-providers.md
Outdated
|
||
We will describe the steps to run and interact with a full-node for the Cosmos Hub. For other SDK-based blockchain, the process should be similar. | ||
- Full Nodes: Interact with the blockchain. | ||
- REST Server: Serve as a relayer for HTTP calls. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest changing the term relayer
as it overlaps with IBC's relayer terminology.
|
||
When choosing to remote access a Full Node and gaiad, you need a Full Node running and gaia installed on your local machine. | ||
|
||
`gaiad` is the tool that enables you to interact with the node that runs on the Cosmos Hub network, whether you run it yourself or not. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line could be moved earlier.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how far earlier do you have in mind? Beginning of this chapter or even at the start of the whole article?
Closes: #824
Description
/docs/gaia-tutorials/installation.md
/docs/gaia-tutorials/join-mainnet.md
/docs/resources/service-providers.md
For contributor use:
docs/
) or specification (x/<module>/spec/
)godoc
comments.Unreleased
section inCHANGELOG.md
Files changed
in the Github PR explorerFor admin use:
WIP
,R4R
,docs
, etc)