bitlayer-org · Nanyan · Jun 25, 2025 · Jun 25, 2025 · Jun 25, 2025
diff --git a/blog/2024-03-01-first-blog-post.md b/blog/2024-03-01-first-blog-post.md
diff --git a/blog/_category_.json b/blog/_category_.json
diff --git a/blog/authors.yml b/blog/authors.yml
diff --git a/docs/Build/DeveloperResources/Indexers/TheGraph.md b/docs/Build/DeveloperResources/Indexers/TheGraph.md
@@ -40,5 +40,5 @@ graph-node:
  > Note: The node connected to graph-node needs to be in `archive` mode (add flag --syncmode full --gcmode archive when starting the node), we recommend each user to build their own RPC node.
 
 ### Migration
-You can migrate your subgraph from bitlayer graph node or project local graph node to offical environment when the graph enables bitlayer.
+You can migrate your subgraph from bitlayer graph node or project local graph node to official environment when the graph enables bitlayer.
 To migrate smoothly, please set dataSources.source.startBlock in subgraph.yaml, we suggest using the block in which the contract was created. 
diff --git a/docs/Build/TrackPack/DappSecurityMannual.md → docs/Build/TrackPack/DappSecurityManual.md b/docs/Build/TrackPack/DappSecurityMannual.md → docs/Build/TrackPack/DappSecurityManual.md
@@ -2,7 +2,7 @@
 sidebar_position: 2
 ---
 
-# Dapp Security Mannual
+# Dapp Security Manual
 
 # 1 Overview
 Bitlayer aims to become a Layer 2 public blockchain for BTC, achieving 100% EVM compatibility as well as compatibility with Ethereum ecosystem tools, using BTC as the native token. 

diff --git a/docs/Learn/Bitlayer PoS/AboutGas.md b/docs/Learn/Bitlayer PoS/AboutGas.md
@@ -9,7 +9,7 @@ sidebar_position: 20
 
 - On the Bitlayer, there is a minimum priority fee requirement. Developers can use `eth_gasPrice` or `eth_maxPriorityFeePerGas` to estimate the gas price required for a transaction in real time.
 
-- For the Mainnet/Testnet, a minimum tip of `0.05 gwei` is required. Usually, `0.055 gwei` `gasPrice` for legacy transactions, `0.05 gwei` `maxPriorityFeePerGas` (and set enough amount to `maxFeePerGas`) for EIP1559 transactions SHOULD BE enough.
+- For the Mainnet/Testnet, a minimum tip of `0.05 gwei` is required. Usually, `0.0500001 gwei` `gasPrice` for legacy transactions, `0.05 gwei` `maxPriorityFeePerGas` (and set enough amount to `maxFeePerGas`) for EIP1559 transactions SHOULD BE enough.
 
 - For Dapp developers, it's recommended that setting the `maxPriorityFeePerGas` by code before calling apis to send the transaction, rather then leave it empty (filled by the default strategy of wallet (e.g. Metamask) or SDK).
 
@@ -19,4 +19,4 @@ There are multiple way to get BTC gas on Bitlayer:
 
 1. Visit https://www.bitlayer.org/bridge
 
-2. Visit https://www.bitlayer.org/gas-swap 
+2. Visit https://www.bitlayer.org/flash-bridge 
diff --git a/docs/Learn/Bitlayer PoS/BitlayerVsEth.md b/docs/Learn/Bitlayer PoS/BitlayerVsEth.md
@@ -27,7 +27,7 @@ Bitlayer's native gas token is BTC, utilized with an 18-digit precision, divergi
 :::
 To accommodate transaction processing priorities, Bitlayer has established a minimum priority fee requirement. Developers can dynamically estimate the required gas price for transactions using `eth_gasPrice` or `eth_maxPriorityFeePerGas`.
 
-For transactions on the Mainnet/Testnet, a minimum tip of 0.05 gwei is necessary. Typically, setting a `gasPrice` of 0.055 gwei for legacy transactions or a `maxPriorityFeePerGas` of 0.05 gwei (with an adequately set `maxFeePerGas`) for EIP-1559 transactions should suffice for most operations.
+For transactions on the Mainnet/Testnet, a minimum tip of 0.05 gwei is necessary. Typically, setting a `gasPrice` of `0.0500001 gwei` for legacy transactions or a `maxPriorityFeePerGas` of `0.05 gwei` (with an adequately set `maxFeePerGas`) for EIP-1559 transactions should suffice for most operations.
 
 Dapp developers are advised to programmatically set the `maxPriorityFeePerGas` before initiating transactions via APIs, rather than relying on default strategies employed by wallets (like MetaMask) or SDKs, to ensure optimal transaction processing.
 

diff --git a/docs/Learn/Bitlayer PoS/Bridges.md b/docs/Learn/Bitlayer PoS/Bridges.md
@@ -23,11 +23,11 @@ You can find the Proof of Reserve information here: [POR page](./POR).
 
 Mainnet-V1(Bitlayer PoS): The Bitlayer team is working with multiple MPC custody platforms, including Coinbase and Sinohope (HK.1611), to secure the assets.
 
-Mainnet-V2&V3(Bitcoin Finality): The bitlyer team will deliver trustless bridge using BitVM and DLC technology.[WIP]
+Mainnet-V2&V3(Bitcoin Finality): The bitlyer team will deliver trustless bridge using BitVM technology.[WIP]
 
 #### EVM to Bitlayer 
 
-The Bitlayer team builds the trustless bridge together with the [Polyhedra](https://x.com/PolyhedraZK) team.
+The Bitlayer team builds the trustless bridge based on Chainlink CCIP. Users can check the lane status via [CCIP explorer](https://ccip.chain.link/status?search=Bitlayer).
 
 ### 3rd Party Bridges
 

diff --git a/docs/Learn/Bitlayer PoS/Overview.md b/docs/Learn/Bitlayer PoS/Overview.md
@@ -14,7 +14,7 @@ sidebar_position: 10
 | Will block reorg? | Yes |  |
 | Finality | very high probability safe with `15 blocks confirmations`; <br/>**absolutely safe** with `21 blocks confirmations` | refer to [About Finality](./AboutFinality.md) |
 | EIP-1559 supported | Yes | But the base fee will not be burned |
-| Priority fee per gas requied | 0.05 gwei |  |
+| Priority fee per gas required | 0.05 gwei |  |
 | Minimum gasPrice for legacy transaction | 0.050000007 gwei |  |
 | EVM compatibility | Supported up to `Cancun` | But without opcode `PREVRANDAO`, `BLOBHASH`, and `BLOBBASEFEE`, <br/>do NOT support `Blob transaction` |
 | Solidity version supported | ≤ 0.8.28 |  |

diff --git a/docs/Learn/Bitlayer PoS/POR.md b/docs/Learn/Bitlayer PoS/POR.md
@@ -42,9 +42,7 @@ bc1q0v9kx63urmfesags7azaa0uq0lgz7hpmx0y0rl
 0xc2e3A3C18ccb634622B57fF119a1C8C7f12e8C0c
 0xA586a732394A1AFfCF15b972cd47C936033C9FA7
 0x011Ef1fe26D20077A59F38e9Ad155b166AD87D40
-0xce19f75bce7fb74c9e2328766ebe50465df24ca3
 0xa3532633401AbFfbd15e6be825a45FB7F141469B
-0xA4252F2A68b2A078c86E0569eB7Fb872A37864AF
 0x3111653DB0e7094b111b8e435Df9193b62C2C576
 0x92221E8Bc4E1D9a3E5D1cC39A524E90Cd4bdF8b1
 0x0CA2a8900b8140E1e70dc96F32857732f5F67B31