bnb-chain · Anos995 · Nov 25, 2024 · Nov 25, 2024 · Nov 28, 2024 · Dec 13, 2024
diff --git a/BAPs/BAP-578.md b/BAPs/BAP-578.md
diff --git a/BAPs/README.md b/BAPs/README.md
@@ -0,0 +1,29 @@
+# BNB Chain Application Proposals (BAPs)
+
+- [BNB Chain Application Proposals (BAPs)](#bnb-chain-application-proposals-baps)
+  - [What is a BAP?](#what-is-a-bap)
+  - [BAP Workflow](#bap-workflow)
+  - [BAP Format](#bap-format)
+    - [Numbering and File Naming](#numbering-and-file-naming)
+
+## What is a BAP?
+
+BNB Chain Application Proposals (BAPs) are community-driven design documents that specify application-level standards, conventions, and best practices for the BNB Chain ecosystem. BAPs aim to improve interoperability and user experience across dApps, wallets, services, and tooling.
+
+- Scope includes: token and NFT standards, wallet interaction flows, RPC/ABI conventions, indexer/query schemas, cross-dApp messaging, off-chain service interfaces, and other app-layer norms.
+- BAPs are distinct from BEPs (BNB Chain Evolution Proposals), which target protocol/consensus or node-level changes.
+
+## BAP Workflow
+
+BAP workflow follows the process described in [BEP-1](https://github.com/bnb-chain/BEPs/blob/master/BEPs/BEP1.md#4--bep-workflow).
+![overall workflow](../BEPs/assets/bep-1/workflow.png)
+
+The **Review** stage is central to BAPs and requires feedback from the community, especially from relevant ecosystem partners. Feedback can be provided in this repository or on the [BNB Chain Forum](https://forum.bnbchain.org/). PR status is maintained by the BAP editors, primarily the maintainers of this GitHub repository.
+
+## BAP Format
+The BAP format follows the [BEP format](https://github.com/bnb-chain/BEPs/blob/master/BEPs/BEP1.md#5--bep-format). Providing reference implementations is strongly recommended to clarify interface definitions.
+
+### Numbering and File Naming
+
+- Provisional PRs may use `BAP-xxxx.md`; a concrete number is assigned upon Acceptance.
+- Place the file at `BAPs/BAP-<number>.md` with a clear, descriptive title.
diff --git a/BEPs/BEP-299.md b/BEPs/BEP-299.md
@@ -1,7 +1,7 @@
 <pre>
   BEP: 299
   Title: Token Migration after BC Fusion
-  Status: Candidate
+  Status: Enabled
   Type: Standards
   Created: 2023-10-16
 </pre>

diff --git a/BEPs/BEP-336.md b/BEPs/BEP-336.md
@@ -1,7 +1,7 @@
 <pre>
   BEP: 336
   Title: Implement EIP-4844: Shard Blob Transactions
-  Status: Candidate
+  Status: Enabled
   Type: Standards
   Created: 2023-12-04
 </pre>

diff --git a/BEPs/BEP-342.md b/BEPs/BEP-342.md
@@ -1,15 +1,15 @@
 <pre>
   BEP: 342
   Title: Implement EIP-5656: MCOPY
-  Status: Candidate
+  Status: Enabled
   Type: Standards
   Created: 2024-01-15
 </pre>
 
 
 # BEP-342: Implement EIP-5656: MCOPY
 
-- [BEP-342: Implement Implement EIP-5656: MCOPY](#bep-342-implement-eip-5656-mcopy)
+- [BEP-342: Implement EIP-5656: MCOPY](#bep-342-implement-eip-5656-mcopy)
   - [1. Summary](#1-summary)
   - [2. Abstract](#2-abstract)
   - [3. Motivation](#3-motivation)

diff --git a/BEPs/BEP-343.md b/BEPs/BEP-343.md
@@ -1,7 +1,7 @@
 <pre>
   BEP: 343
   Title: Implement EIP-1153: Transient storage opcodes
-  Status: Candidate
+  Status: Enabled
   Type: Standards
   Created: 2024-01-15
 </pre>

diff --git a/BEPs/BEP-344.md b/BEPs/BEP-344.md
@@ -1,7 +1,7 @@
 <pre>
   BEP: 344
   Title: Implement EIP-6780: SELFDESTRUCT only in same transaction
-  Status: Candidate
+  Status: Enabled
   Type: Standards
   Created: 2024-01-15
 </pre>

diff --git a/BEPs/BEP-345.md b/BEPs/BEP-345.md
@@ -1,7 +1,7 @@
 <pre>
   BEP: 345
   Title: Implement EIP-7516: BLOBBASEFEE opcode
-  Status: Candidate
+  Status: Enabled
   Type: Standards
   Created: 2024-01-15
 </pre>

diff --git a/BEPs/BEP-363.md b/BEPs/BEP-363.md
@@ -21,10 +21,11 @@
       - [4.1.5 Relayer Fee](#415-relayer-fee)
       - [4.1.6 Execution Order](#416-execution-order)
     - [4.2 GreenfieldExecutor](#42-greenfieldexecutor)
-      - [4.2.1 API](#421-api)
-      - [4.2.2 Error Handling](#422-error-handling)
-      - [4.2.3 Execution Order](#423-execution-order)
-      - [4.2.4 Pros and Cons](#424-pros-and-cons)
+      - [4.2.1 Support Msgs](#421-support-msgs)
+      - [4.2.2 API](#422-api)
+      - [4.2.3 Error Handling](#423-error-handling)
+      - [4.2.4 Execution Order](#424-execution-order)
+      - [4.2.5 Pros and Cons](#425-pros-and-cons)
   - [5. License](#5-license)
 
 ## 1. Summary

diff --git a/BEPs/BEP-364.md b/BEPs/BEP-364.md
@@ -14,6 +14,14 @@
   - [2. Motivation](#2-motivation)
   - [3. Status](#3-status)
   - [4. Specification](#4-specification)
+    - [4.1 APIs](#41-apis)
+      - [4.1.1 SP APIs](#411-sp-apis)
+        - [SDK](#sdk)
+      - [4.1.2 Greenfield Chain New Messages](#412-greenfield-chain-new-messages)
+    - [4.2 New workflow for object creation/update on Greenfield](#42-new-workflow-for-object-creationupdate-on-greenfield)
+      - [4.2.1 Users](#421-users)
+      - [4.2.2 SP](#422-sp)
+    - [4.3 Security](#43-security)
   - [5. License](#5-license)
 
 

diff --git a/BEPs/BEP-366.md b/BEPs/BEP-366.md
@@ -12,17 +12,18 @@
 
 <!-- code_chunk_output -->
 
-- [BEP-366: Greenfield Atomic Object Update](#bep-greenfield-atomic-object-update)
+- [BEP-366: Greenfield Atomic Object Update](#bep-366-greenfield-atomic-object-update)
   - [1. Summary](#1-summary)
   - [2. Motivation](#2-motivation)
   - [3. Status](#3-status)
   - [4. Specification](#4-specification)
     - [4.1 Requirements](#41-requirements)
     - [4.2 Implementation](#42-implementation)
-    - [4.2.1 Change To Current Model](#421-change-to-current-model)
-    - [4.2.2 New Model And Message](#422-new-model-and-message)
-    - [4.3 Workflow](#43-workflow)
-    - [4.4 Fees & User Charges](#44-fees-&-user-charges)
+      - [4.2.1. Change To Current Model](#421-change-to-current-model)
+      - [4.2.1. New Model And Message](#421-new-model-and-message)
+  - [4.3 Workflow](#43-workflow)
+  - [4.4 Fees \& User Charges](#44-fees--user-charges)
+  - [5. License](#5-license)
 <!-- /code_chunk_output -->
 
 ## 1. Summary

diff --git a/BEPs/BEP-381.md b/BEPs/BEP-381.md
@@ -12,7 +12,7 @@
 
 <!-- code_chunk_output -->
 
-- [BEP-381: Precompile for secp256r1 Curve Support](#bep-precompile-for-secp256r1-curve-support)
+- [BEP-381: Precompile for secp256r1 Curve Support](#bep-381-precompile-for-secp256r1-curve-support)
   - [1. Summary](#1-summary)
   - [2. Motivation](#2-motivation)
   - [3. Status](#3-status)
@@ -23,10 +23,10 @@
     - [4.3 Precompiled Contract Specification](#43-precompiled-contract-specification)
     - [4.4 Precompiled Contract Gas Usage](#44-precompiled-contract-gas-usage)
   - [5. Rationale](#5-rationale)
-  - [6. Backwards Compatibility](#6-backwards-compatibily)
+  - [6. Backwards Compatibility](#6-backwards-compatibility)
   - [7. Test Cases](#7-test-cases)
   - [8. Reference Implementation](#8-reference-implementation)
-  - [9. Security Considerations](#8-security-consideration)
+  - [9. Security Considerations](#9-security-considerations)
   - [10. Copyright](#10-copyright)
 <!-- /code_chunk_output -->
 

diff --git a/BEPs/BEP-402.md b/BEPs/BEP-402.md
@@ -1,7 +1,7 @@
 <pre>
   BEP: 402
   Title: Complete Missing Fields in Block Header to Generate Signature
-  Status: Candidate
+  Status: Enabled
   Type: Standards
   Created: 2024-06-28
 </pre>

diff --git a/BEPs/BEP-404.md b/BEPs/BEP-404.md
@@ -1,7 +1,7 @@
 <pre>
   BEP: 404
   Title: Clear Miner History when Switching Validators Set
-  Status: Candidate
+  Status: Enabled
   Type: Standards
   Created: 2024-07-01
 </pre>

diff --git a/BEPs/BEP-414.md b/BEPs/BEP-414.md
@@ -8,6 +8,21 @@
 
 # BEP-414: Paymaster API Spec for EOA Wallets
 
+- [BEP-414: Paymaster API Spec for EOA Wallets](#bep-414-paymaster-api-spec-for-eoa-wallets)
+  - [1. Summary](#1-summary)
+  - [2. Abstract](#2-abstract)
+  - [3. Status](#3-status)
+  - [4. Motivation](#4-motivation)
+  - [5. Specification](#5-specification)
+    - [5.1 Definitions](#51-definitions)
+    - [5.2 Workflow](#52-workflow)
+    - [5.3 Wallet Interaction](#53-wallet-interaction)
+    - [5.4 Paymaster API Spec](#54-paymaster-api-spec)
+      - [`pm_isSponsorable`](#pm_issponsorable)
+      - [`eth_sendrawtransaction`](#eth_sendrawtransaction)
+    - [5.5 Sponsor Policy \&\& Fee Charge](#55-sponsor-policy--fee-charge)
+  - [6 License](#6-license)
+
 ## 1. Summary
 
 Unlike the paymaster defined in EIP-4337, this proposal introduces a paymaster solution specifically tailored for EOA (Externally Owned Account) wallets, along with standardized paymaster APIs. With minimal modifications, wallets can integrate paymasters that implement these API standards, enabling users to send transactions with zero gas fees.
@@ -172,4 +187,5 @@ Paymasters have complete autonomy in defining sponsor policies, which can be imp
 Paymasters also enjoy flexibility in their fee collection methods. Charges can be directly deducted from the sponsor's credit card, or sponsors can pre-deposit cryptocurrency to the paymaster platform, from which the balance is then charged.
 
 ## 6 License
-The content is licensed under CC0.
+
+The content is licensed under [CC0](https://creativecommons.org/publicdomain/zero/1.0/).