Skip to content
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.

Sign up for GitHub

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

Corrected typos #1884

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Corrected typos #1884

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ad1b3d7
Fix typos in p2p/README.md
helicopter-1 Feb 20, 2025
7c2c8a4
Fix typos in wallet/README.md
helicopter-1 Feb 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion p2p/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ Each message starts with a 4-bytes header that contains the length of the messag
| 4 bytes | Message length | `u32` | The length of the message body that follows.
| Variable | Message body | `enum Message` | An encoded `Rust` enum.

The message body is a SCALE-encoded `Rust` enum. With this encoding, the first byte of the encoded data specifes the enum variant contained in the enum; the rest is that variant's encoded data.
The message body is a SCALE-encoded `Rust` enum. With this encoding, the first byte of the encoded data specifies the enum variant contained in the enum; the rest is that variant's encoded data.

The encoded `enum Message`:
| Length | Description | Type | Comments |
Expand Down
2 changes: 1 addition & 1 deletion wallet/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ All the data of the wallet is stored in what is called a "wallet file". The wall

The node, by default, simplifies RPC security by creating what is called a "cookie file". A cookie file is a file that is created in the data directory of the node. In order to prevent any users of the computer from accessing the node with no proper permissions, the cookie file is created with randomly generated passwords on every run of the node. The wallet can automatically detect the cookie file and attempt to use it to reach the node. This way, the experience for the users, especially novice users, is seamless and is also secure, where unauthorized access to another account in the machine does not entail a breach in the node.

In case a different mode of authentication is desired, the user can check the available security options by running the node with the `--help` command line argument. Using simple username and password is possible. It is also designed to be timing resistent, hence, brute-forcing the password will only work if the password is short. We recommend using very long and randomized passwords for good security.
In case a different mode of authentication is desired, the user can check the available security options by running the node with the `--help` command line argument. Using simple username and password is possible. It is also designed to be timing resistant, hence, brute-forcing the password will only work if the password is short. We recommend using very long and randomized passwords for good security.

### Port accessibility of RPC servers in the node (and wallet)

Expand Down