update stale documents for bnb smart chain #421
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
buddh0
commented
Jul 25, 2024
| @@ -13,10 +13,11 @@ Simply speaking, an archive node is a full node running with an additional speci | |||
|
|
|||
| Developers are limited to querying the limited recent blocks to check the balance of an address and the state of a smart contract with a full node. It is hard to get all what they want as the blockchain is moving forward at the same time, while they can query any block at a specific point in time with an archive node. | |||
| Archive nodes are used by various applications on the blockchain for challenging use cases, including but not limited to the followings: | |||
| * Automatic trading system needs historical data to optimize trading model | |||
buddh0
commented
Jul 25, 2024
| @@ -64,8 +64,7 @@ We support running a full node on **Mac OS X**, **Linux**, and **Windows**. | |||
|
|
|||
| !!! note | |||
| Make sure you use the version of geth you downloaded with wget above, and not your local installation of geth, which might be the wrong version. | |||
| 1. Since `v1.3.1`, the flags `--txlookuplimit` has been replaced by `--history.transactions`. Make sure you no longer use `--txlookuplimit`, otherwise, node may not start. | |||
There was a problem hiding this comment.
txlookuplimit is also ok
buddh0
commented
Jul 25, 2024
| @@ -13,6 +13,7 @@ Since BSC is EVM-compatible, your existing Ethereum smart contract skills will s | |||
| ## Connecting | |||
|
|
|||
| Here are some resources to help you get connected to the BSC network: | |||
|
|
|||
| - [Network Information and RPC Providers](./rpc.md) | |||
buddh0
commented
Jul 25, 2024
| @@ -64,13 +64,6 @@ BC and BSC share the same token universe for BNB and BEP2 tokens. This defines: | |||
| 2. The total circulation of the same token should be managed across the two networks, i.e. the total effective supply of a token should be the sum of the token’s total effective supply on both BSC and BC. | |||
| 3. The tokens can be initially created on BSC in a similar format as ERC20 token standard, or on BC as a BEP2, then created on the other. There are native ways on both networks to link the two and secure the total supply of the token. | |||
|
|
|||
| ## Cross-Chain Transfer and Communication | |||
There was a problem hiding this comment.
even the final sunset is not enabled
we can still not to emphasize the Corss-Chain
zzzckck
approved these changes
Jul 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.