Private mempool

docs/announce/altai-gnfd.md

@@ -0,0 +1,30 @@
+# Altai Upgrade of Greenfield
+
+<div class="doc-announce-info">
+    <span class="version-tag">Hardfork</span>
+</div>
+
+
+## Upgrade Timeline
+
+- Testnet: Sep 21th 2024 06:00:00 AM UTC Blockheight: 12,513,708
+
+- Mainnet: Sep 23th 2024 06:00:00 AM UTC Blockheight: 11,917,971
+
+
+For Validators: greenfield [v1.9.1](https://github.com/bnb-chain/greenfield/releases/tag/v1.9.1?ref=bnbchain.ghost.io)
+
+For SP: no action needed.
+
+
+## Hot Fix Release
+Greenfield and the Metamask extension are facing compatibility issues, affecting some functionalities such as bucket creation on Dcellar.
+This issue is occurring because the MetaMask Extension recently upgraded its middleware library to the latest version, 
+implementing stricter EIP712 signature verification rules.
+
+This release contains the hotfix to resolve this issue, all dapps that using the go-sdk and js-sdk is suggested to upgrade to the 
+latest version.
+
+- [Go-SDK v1.7.3](https://github.com/bnb-chain/greenfield-go-sdk/releases/tag/v1.7.3)
+- [Js-SDK v2.2.0-alpha](https://github.com/bnb-chain/greenfield-js-sdk/releases/tag/%40bnb-chain%2Fgreenfield-js-sdk%402.2.0-alpha.0)
+

docs/announce/bohr-bsc.md

@@ -7,11 +7,11 @@
 ## Upgrade Timeline
 The Bohr upgrade will happen at:
 
-- Testnet:  2024-08-20 01:23:16 AM UTC
-- Mainnet:  It is not determined yet, target Later Sep 2024
+- Testnet:  2024-08-20 01:23:16 AM UTC(passed)
+- Mainnet:  2024-09-26 02:20:00 AM UTC
 
-## Upgrade BSC Testnet Nodes to v1.4.13 Before Hardfork
-Release [v1.4.13](https://github.com/bnb-chain/bsc/releases/tag/v1.4.13) is a hard fork release for BSC Testnet, the HF name is: [Bohr](https://forum.bnbchain.org/t/bnb-chain-roadmap-mainnet/936#p-1418-h-6bohr-wip-27)
+## Upgrade BSC Mainnet Nodes to v1.4.14 Before Hardfork
+Release [v1.4.14](https://github.com/bnb-chain/bsc/releases/tag/v1.4.14) is a hard fork release for BSC Mainnet, the HF name is: [Bohr](https://forum.bnbchain.org/t/bnb-chain-roadmap-mainnet/936)
 
 There are 4 BEPs in Bohr:
 

docs/announce/final-sunset-bc-mainnet.md

@@ -0,0 +1,44 @@
+# Final Sunset Hardfork of BC Mainnet
+
+<div class="doc-announce-info">
+    <span class="version-tag">Hardfork</span>
+</div>
+
+## Upgrade Timeline
+
+The Final Sunset Hardfork will happen at:
+
+- Mainnet: November 19 2024 6:00:00 AM UTC
+
+## Upgrade to BC Node v0.10.24 Before Hardfork
+
+BC node need to be upgraded before the hardfork time.
+
+- https://github.com/bnb-chain/node/releases/tag/v0.10.24
+
+### Upgrade Instructions
+
+As a fullnode runner, you need to take the following steps before the hardfork block height.
+
+1) Download the new v0.10.24 binary and replace the previous version.
+
+2) Download the new config
+   file [app.toml](https://github.com/bnb-chain/node/releases/download/v0.10.24/mainnet_config.zip) to replace the
+   previous version or add the following under the [upgrade] module of `app.toml`.
+
+```toml
+FinalSunsetHeight = 384544850
+```
+
+3) Stop the bnbchaind process and restart it with v0.10.24.
+
+```shell
+service bnbchaind restart
+```
+
+## Key Highlight
+
+After Final Sunset, the cross-chain communication between the Beacon Chain and BSC will be completely stopped.
+The validators in the Beacon Chain community will gradually shut down, and the entire chain will no longer accept 
+new transactions or propose new blocks.
+For more information about BNB Chain Fusion, please refer to [this](https://www.bnbchain.org/en/bnb-chain-fusion).

docs/announce/fjord-opbnb.md

@@ -0,0 +1,54 @@
+# Fjord Upgrade of opBNB
+
+<div class="doc-announce-info">
+    <span class="version-tag">Hardfork</span>
+</div>
+
+
+## Upgrade Timeline
+
+The Fjord upgrade will happen at:
+
+- Testnet: Sep-10-2024 06:00 AM +UTC
+- Mainnet: Sep-24-2024 06:00 AM +UTC
+
+## Upgrade opBNB op-node and op-geth to v0.5.0 Before Hardfork
+
+Releases:
+
+- https://github.com/bnb-chain/opbnb/releases/tag/v0.5.0
+- https://github.com/bnb-chain/op-geth/releases/tag/v0.5.0
+
+Docker Images
+
+- ghcr.io/bnb-chain/op-node:v0.5.0
+- ghcr.io/bnb-chain/op-geth:v0.5.0
+- ghcr.io/bnb-chain/op-batcher:v0.5.0
+- ghcr.io/bnb-chain/op-proposer:v0.5.0
+
+## Key Highlight: L1 fee calculation changed
+
+Fjord updates the L1 cost calculation function to use a FastLZ-based compression estimator. The L1 cost is computed as:
+
+```
+l1FeeScaled = l1BaseFeeScalar*l1BaseFee*16 + l1BlobFeeScalar*l1BlobBaseFee
+estimatedSizeScaled = max(minTransactionSize * 1e6, intercept + fastlzCoef*fastlzSize)
+l1Fee = estimatedSizeScaled * l1FeeScaled / 1e12
+```
+
+You can find the detailed explanation in the [spec](https://specs.optimism.io/protocol/fjord/exec-engine.html).
+
+## User Facing Changes
+
+* New flag `--wait-node-sync` added to op-batcher (default false), indicates if during startup, the batcher should wait for a recent batcher tx on L1 to finalize (via more block confirmations). This should help avoid duplicate batcher txs
+* New flag `--wait-node-sync` added to op-proposer (default false), indicates if during startup, the proposer should wait for the rollup node to sync to the current L1 tip before proceeding with its driver loop
+* New flag `--compression-algo` added to op-batcher (default zlib), user can choose brotli algo after Fjord fork
+* New flag `--l1.rpc-max-cache-size` added to op-node (default 1000), so user can config the the maximum cache size of the L1 client
+
+## Pull Requests
+
+* Merge upstream v1.7.7 by @bnoieh in https://github.com/bnb-chain/opbnb/pull/216
+* feat(op-node): Keep consistent status when meet an unexpected el sync by @krish-nr in https://github.com/bnb-chain/opbnb/pull/222
+* feat(op-node): add l1 cache size config by @welkin22 in https://github.com/bnb-chain/opbnb/pull/225
+* feat(op-chain-ops): add Wright fork config into genesis file generation code by @welkin22 in https://github.com/bnb-chain/opbnb/pull/226
+

docs/announce/index.md

@@ -2,25 +2,18 @@
 # Announcement
 
 <div class="doc-announce">
-    <a href="./bohr-bsc/">
+    <a href="./savanna-greenfield/">
         <div>
-            <div class="announce-title">Bohr Upgrade of BSC (Testnet) </div>
-            <div class="announce-desc">Introduce 4 BEPs on BSC Testnet</div>
+            <div class="announce-title">Greenfield Savanna Hardfork (Testnet) </div>
+            <div class="announce-desc">Bugfixing on Greenfield Testnet</div>
         </div>
-        <span class="announce-date">2024 Aug 20</span>
+        <span class="announce-date">2024 December 02</span>
     </a>
-    <a href="./wright-opbnb/">
+    <a href="./savanna-greenfield/">
         <div>
-            <div class="announce-title">Wright Upgrade of opBNB (Mainnet) </div>
-            <div class="announce-desc">Introduce Gasless Feature on opBNB Mainnet</div>
+            <div class="announce-title">Greenfield Savanna Hardfork (Mainnet) </div>
+            <div class="announce-desc">Bugfixing on Greenfield Mainnet</div>
         </div>
-        <span class="announce-date">2024 Aug 27</span>
-    </a>
-    <a href="./bohr-bsc/">
-        <div>
-            <div class="announce-title">Bohr Upgrade of BSC (Mainnet) </div>
-            <div class="announce-desc">Introduce 4 BEPs on BSC Mainnet</div>
-        </div>
-        <span class="announce-date">To be determined, target Later Sep 2024</span>
+        <span class="announce-date">2024 December 12</span>
     </a>
 </div>

docs/announce/savanna-greenfield.md

@@ -0,0 +1,28 @@
+# Savanna Upgrade of Greenfield
+
+<div class="doc-announce-info">
+    <span class="version-tag">Hardfork</span>
+</div>
+
+
+## Upgrade Timeline
+
+- Testnet: December 2nd 2024 07:00:00 AM UTC Blockheight: 14691233
+
+- Mainnet: December 12th 2024 07:00:00 AM UTC Blockheight: 14667574
+
+## Validators and SPs should complete upgrading to the latest version before hardfork: 
+
+For Validators: greenfield [v1.10.0](https://github.com/bnb-chain/greenfield/releases/tag/v1.10.0?ref=bnbchain.ghost.io)
+
+For SPs: greenfield-storage-provider [v1.10.0](https://github.com/bnb-chain/greenfield-storage-provider/releases/tag/v1.10.0?ref=bnbchain.ghost.io)
+
+
+
+## Bug fixing
+
+* [#647] https://github.com/bnb-chain/greenfield/pull/647 fix: fail to resume frozen payment account when netflow is zero
+* [#1435] https://github.com/bnb-chain/greenfield-storage-provider/pull/1435 feat: fix gc objects
+
+
+[//]: # (Reference: https://www.bnbchain.org/en/blog/bnb-greenfield-savanna-hardfork)

docs/bc-fusion/overview.md

@@ -5,6 +5,8 @@ title: Overview - BC Fusion
 
 # Overview
 
+**BNB Beacon Chain has been shut down at block height 385,251,927 since December 3, 2024.**
+
 BNB Beacon Chain is a blockchain developed by the BNB Chain community that implements a vision of a decentralized
 exchange (DEX) for digital assets. Besides this, Beacon Chain and BSC is a dual-chain structure: Beacon Chain helps to
 enhance the security of BSC as a staking and governance layer. With the rise of various other forms of Dex, order-book
@@ -28,8 +30,7 @@ There will be several pahses to retrie Beacon Chain:
 - **Second Sunset Fork** - More Beacon chain transactions will be disabled, for example,MsgSideChainSubmitProposal. All
   TimeLock and AtomicSwap will automatically be refunded to the user's
   wallet. All the BSC delegation will be undelegated automatically.
-- **Final Sunset Fork** - Cross-chain communication between the Beacon Chain and BSC will be completely stopped. (
-  Estimated time on mainnet: 2024 Sep)
+- **Final Sunset Fork** - Cross-chain communication between the Beacon Chain and BSC will be completely stopped.
 - **Post BC Fusion** - Beacon Chain will be dumped and and a merkle tree will be generated for recover the assets, which
   are binded to BSC however not transffered to BSC yet.
 

docs/bc-fusion/post-fusion/faq.md

@@ -44,8 +44,7 @@ are the owner of the assets. Please take care of your key/mnemonic.
     - Mainnet API Endpoint: https://dex.bnbchain.org/api/v1/account/{bnb_address}
 * The snapshot file can be downloaded from Greenfield, R2, and so on. The users can download the snapshot file and set up
   a local BC node for retrieving any data on the blockchain.
-    - Testnet snpashot file: https://github.com/bnb-chain/node-dump/blob/master/Readme.md    
-    - Mainnet snpashot file: To be updated.
+    - Testnet/Mainnet snpashot file: https://github.com/bnb-chain/node-dump/blob/master/Readme.md
 
 ## 4. Can I still acccess the BC releated services or products after the fusion?
 

docs/bc-fusion/post-fusion/token-recovery.md

@@ -7,14 +7,11 @@ of token recovery.
 
 Be noted:
 
-* Token recovery dApp will only be available post fusion (the Beacon Chain has been shutdown).
 * Only [the crosschain bound/mirrored assets](../users/assets.md) can be recovered.
 
 URL:
 
-- **Testnet**: [https://testnet-bnb-beacon-chain-token-recovery.bnbchain.org/en](https://testnet-bnb-beacon-chain-token-recovery.bnbchain.org/en)
-
-- **Mainnet**: To be updated.
+- **Mainnet**: [https://www.bnbchain.org/en/token-recovery](https://www.bnbchain.org/en/token-recovery)
 
 ## Steps
 
@@ -27,7 +24,8 @@ When opening the token recovery dApp, you will be prompted to connect to your wa
 ![](../../assets/bcfusion/token-recovery-2.png){:style="width:800px"}
 
 [BNB Chain Wallet](https://chromewebstore.google.com/detail/bnb-chain-wallet/fhbohimaelbohpjbbldcngcnapndodjp)
-and [Trust Wallet](https://trustwallet.com/) will be supported (Trust wallet support will come soon).
+and [Trust Wallet Extension](https://trustwallet.com/) are supported. For Trust users, you can refer to 
+[this](https://trustwallet.com/blog/trust-wallet-to-deprecate-bnb-beacon-chain-bep2-bep8-support) for more information.
 
 ### Step 2: Select the BEP2/BEP8 assets to be recovered.
 
@@ -53,6 +51,8 @@ Be noted:
 * The account will be used in the later steps for sending a transaction to BSC. So it should have some BNB on BSC for
   the gas fee.
 
+* If this BSC address has already been used as the receiver for a token recovery from a BC address, and it is used again for the recovery of the same token from a different BC address, the unlock time will be recalculated, starting from the most recent recovery and extending 7 days forward.
+
 ### Step 4: Confirm the receiver address and signing.
 
 ![](../../assets/bcfusion/token-recovery-6.png){:style="width:800px"}
@@ -89,3 +89,4 @@ the token recovery request is sent successfully.
 
 Finally, you need to wait for 7 days for the BEP2/BEP8 assets to be recovered on BSC and received in your wallet.
 
+

docs/bc-fusion/validators/creation.md

@@ -67,7 +67,7 @@ The following addresses are required:
 
 ##### Generate Consensus Address
 
-Download the BSC geth binary from [the official release page](https://github.com/bnb-chain/bsc/releases/tag/v1.3.10).
+Download the BSC geth binary from [the official release page](https://github.com/bnb-chain/bsc/releases/).
 
 Note: Make sure you are downloading the correct binary based on your machine's platform, e.g., if you are using MacOS,
 you should download the `geth_mac` file. In the following, we will refer the binary as `geth` for simplicity.
@@ -239,3 +239,4 @@ The `Signature` is your `identity` for associating to the old validator created
 
 Once you have filled out all the required information, click the `Submit` button to submit the transaction.
 
+Note: Upon completing these steps, your node is not guaranteed to become an active validator. Selection is based on a ranking that reflects the total BNB staked, with only the top N nodes being chosen as active validators. The number N is determined by the "maxElectedValidators" parameter within the StakeHubContract (0x0000000000000000000000000000000000002002). As of November 4th, 2024, this number stands at 8 for the testnet and 45 for the mainnet.

docs/bnb-greenfield/core-concept/billing-payment.md

@@ -74,6 +74,49 @@ It will also provide a possibility for projects to sponsor the storage and bandw
 
 For more details, you can refer to the [BEP of the paymaster](https://github.com/bnb-chain/BEPs/pull/362).
 
+### Force Settlement, Freeze and Resume
+
+If a user doesn't deposit for a long time, his previous deposit may be
+all used up for the stored objects. Greenfield has a forced settlement
+mechanism to ensure enough funds are secured for further service fees.
+
+There are two configurations, `ReserveTime` and `ForcedSettleTime`.
+
+Let's take an example where the `ReserveTime` is 7 days and the `ForcedSettleTime` is 1 day.
+If a user wants to store an object at the price of
+approximately $0.1 per month($0.00000004/second), he must reserve fees
+for 7 days in the buffer balance, which is `$0.00000004 * 7 * 86400 =
+$0.024192`. If the user deposits is $1 initially, the stream payment
+record will be as below:
+
+- **CRUD Timestamp**: 100;
+
+- **Static Balance**: $0.975808;
+
+- **Netflow Rate**: -$0.00000004/sec;
+
+- **Buffer Balance**: $0.024192.
+
+After 10000 seconds, the dynamic balance of the user will be `0.975808 - 10000 * 0.00000004 = 0.975408`.
+
+After 24395200 seconds(approximately 282 days), the dynamic balance of
+the user will become negative. Users should have some alarms for such
+events that remind them to supply more funds in time.
+
+If no more funds are supplied and the dynamic balance plus buffer
+balance is under the forced settlement threshold, the account will be
+forcibly settled. All payment streams of the account will be closed and
+the account will be marked as frozen. The download speed for all
+objects associated with the account or payment account will be
+downgraded. 
+
+If someone deposits BNB tokens into a frozen payment account and the static balance is
+enough for reserved fees, the account will be resumed automatically 
+(be noted, the deposit is payment deposit, not the general transfer).
+Usually, the payment account will be "active" quickly. However, if there
+are many outflows associated to the payment account, the payment account will be
+queued for resume and handled in the following blocks. 
+
 ### Downgraded service
 
 Once the payment accounts run out of BNB, the objects associated with these payment accounts will

docs/bnb-greenfield/for-developers/data-archive/block-hub.md

@@ -48,7 +48,7 @@ data. By leveraging BlockHub, they can collect reliable data for analysis, resea
 # Accessing Block Data with BlockHub
 
 BlockHub supports BSC now and its API is fully compatible with Ethereum API specifications, ensuring ease of integration for
-developers. Detailed information about supported networks and endpoints can be found in [network and endpoints](../network-endpoint/endpoints.md#BlockHub). For more details
+developers. Detailed information about supported networks and endpoints can be found in [network and endpoints](../network-endpoint/endpoints.md). For more details
 about the API spec, please refer to [BlockHub API](https://github.com/bnb-chain/greenfield-bsc-archiver/?tab=readme-ov-file#BlockHub-api)
 
 # Try It Out

docs/bnb-greenfield/for-developers/network-endpoint/endpoints.md

@@ -53,9 +53,10 @@ order: 3
 - `https://gnfd-blobhub-bsc.bnbchain.org`
 
 ### Block Hub
-- **BSC:** coming soon
+- **BSC:**
+- `https://gnfd-bsc-archiver-mainnet.bnbchain.org/`
 
-  Refer to the [Block-Hub documentation](../data-archive/block-hub.md) for more details.
+Refer to the [Block-Hub documentation](../data-archive/block-hub.md) for more details.
 
 
 ## Testnet

docs/bnb-greenfield/for-developers/tutorials/app/data-marketplace.md

@@ -142,7 +142,7 @@ _Buyer_
 
 <h3>5. Environment Support</h3>
 
-* BNB Smart Chain Testnet: [https://testnet-marketplace.mindpress.io](https://testnet-marketplace.mindpress.io)   (VPN required in some areas)
+* BNB Smart Chain Testnet: [https://mindpress.io](https://mindpress.io)   (VPN required in some areas)
 
 <h3>6. Technical Design </h3>
 

docs/bnb-opbnb/faq/cross-chain-faqs.md

@@ -41,4 +41,4 @@ With that said, there is a way for developers to allow arbitrary message sending
 
 ### Can I directly transfer assets between opBNB and Greenfield?
 
-Currently, direct cross-chain transfers between opBNB and Greenfield are not supported. However, users can achieve cross-chain transfers between these two networks by conducting a two-step process through the Binance Smart Chain (BSC). This involves transferring assets from opBNB to BSC and then from BSC to Greenfield.
+Currently, direct cross-chain transfers between opBNB and Greenfield are not supported. However, users can achieve cross-chain transfers between these two networks by conducting a two-step process through the BNB Smart Chain (BSC). This involves transferring assets from opBNB to BSC and then from BSC to Greenfield.

docs/bnb-smart-chain/developers/faucet.md

@@ -16,9 +16,10 @@ To get some tBNB of BSC testnet for testing purposes, you can use the [online fa
 
 
 ## Claim tBNB from Discord
-1. Visit the BNB Chain Discord [faucet channel](https://discord.com/channels/789402563035660308/1099937267021250560)
-2. Type `/faucet {your receiver account}` and sent.
-3. You will receive **0.3 tBNB** in few seconds.
+1. Join the [BNB Chain Discord](https://discord.com/invite/bnbchain)
+2. Visit the BNB Chain Discord [faucet channel](https://discord.com/channels/789402563035660308/1099937267021250560)
+3. Type `/faucet {your receiver account}` and sent.
+4. You will receive **0.3 tBNB** in few seconds.
 
 *You can only claim once in 24 hours.*