diff --git a/docs/announce/altai-gnfd.md b/docs/announce/altai-gnfd.md new file mode 100644 index 0000000000..78189488c7 --- /dev/null +++ b/docs/announce/altai-gnfd.md @@ -0,0 +1,30 @@ +# Altai Upgrade of Greenfield + +
+ Hardfork +
+ + +## 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) + diff --git a/docs/announce/bohr-bsc.md b/docs/announce/bohr-bsc.md index c7217f36ff..4031e81589 100644 --- a/docs/announce/bohr-bsc.md +++ b/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: diff --git a/docs/announce/final-sunset-bc-mainnet.md b/docs/announce/final-sunset-bc-mainnet.md new file mode 100644 index 0000000000..9d5c4f77c4 --- /dev/null +++ b/docs/announce/final-sunset-bc-mainnet.md @@ -0,0 +1,44 @@ +# Final Sunset Hardfork of BC Mainnet + +
+ Hardfork +
+ +## 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). \ No newline at end of file diff --git a/docs/announce/fjord-opbnb.md b/docs/announce/fjord-opbnb.md new file mode 100644 index 0000000000..28276e63ce --- /dev/null +++ b/docs/announce/fjord-opbnb.md @@ -0,0 +1,54 @@ +# Fjord Upgrade of opBNB + +
+ Hardfork +
+ + +## 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 + diff --git a/docs/announce/index.md b/docs/announce/index.md index cf67dfe2ac..a8973fb980 100644 --- a/docs/announce/index.md +++ b/docs/announce/index.md @@ -2,25 +2,18 @@ # Announcement
- +
-
Bohr Upgrade of BSC (Testnet)
-
Introduce 4 BEPs on BSC Testnet
+
Greenfield Savanna Hardfork (Testnet)
+
Bugfixing on Greenfield Testnet
- 2024 Aug 20 + 2024 December 02
- +
-
Wright Upgrade of opBNB (Mainnet)
-
Introduce Gasless Feature on opBNB Mainnet
+
Greenfield Savanna Hardfork (Mainnet)
+
Bugfixing on Greenfield Mainnet
- 2024 Aug 27 -
- -
-
Bohr Upgrade of BSC (Mainnet)
-
Introduce 4 BEPs on BSC Mainnet
-
- To be determined, target Later Sep 2024 + 2024 December 12
diff --git a/docs/announce/savanna-greenfield.md b/docs/announce/savanna-greenfield.md new file mode 100644 index 0000000000..a5820c57dc --- /dev/null +++ b/docs/announce/savanna-greenfield.md @@ -0,0 +1,28 @@ +# Savanna Upgrade of Greenfield + +
+ Hardfork +
+ + +## 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) \ No newline at end of file diff --git a/docs/assets/bcfusion/token-recovery-1.png b/docs/assets/bcfusion/token-recovery-1.png index 3fbfb63f6d..b21ab974f3 100644 Binary files a/docs/assets/bcfusion/token-recovery-1.png and b/docs/assets/bcfusion/token-recovery-1.png differ diff --git a/docs/assets/bcfusion/token-recovery-10.png b/docs/assets/bcfusion/token-recovery-10.png index 3550399441..01668d492b 100644 Binary files a/docs/assets/bcfusion/token-recovery-10.png and b/docs/assets/bcfusion/token-recovery-10.png differ diff --git a/docs/assets/bcfusion/token-recovery-11.png b/docs/assets/bcfusion/token-recovery-11.png index 914a78ca74..aceaaeafee 100644 Binary files a/docs/assets/bcfusion/token-recovery-11.png and b/docs/assets/bcfusion/token-recovery-11.png differ diff --git a/docs/assets/bcfusion/token-recovery-2.png b/docs/assets/bcfusion/token-recovery-2.png index 4ce2baa323..734ce4d6c5 100644 Binary files a/docs/assets/bcfusion/token-recovery-2.png and b/docs/assets/bcfusion/token-recovery-2.png differ diff --git a/docs/assets/bcfusion/token-recovery-3.png b/docs/assets/bcfusion/token-recovery-3.png index f54bf9c347..a341cc44fa 100644 Binary files a/docs/assets/bcfusion/token-recovery-3.png and b/docs/assets/bcfusion/token-recovery-3.png differ diff --git a/docs/assets/bcfusion/token-recovery-4.png b/docs/assets/bcfusion/token-recovery-4.png index 60694d36ef..c7708e63b0 100644 Binary files a/docs/assets/bcfusion/token-recovery-4.png and b/docs/assets/bcfusion/token-recovery-4.png differ diff --git a/docs/assets/bcfusion/token-recovery-5.png b/docs/assets/bcfusion/token-recovery-5.png index 6a269fed14..e850d0d2f1 100644 Binary files a/docs/assets/bcfusion/token-recovery-5.png and b/docs/assets/bcfusion/token-recovery-5.png differ diff --git a/docs/assets/bcfusion/token-recovery-6.png b/docs/assets/bcfusion/token-recovery-6.png index 31ef5c40f9..789eb2817a 100644 Binary files a/docs/assets/bcfusion/token-recovery-6.png and b/docs/assets/bcfusion/token-recovery-6.png differ diff --git a/docs/assets/bcfusion/token-recovery-7.png b/docs/assets/bcfusion/token-recovery-7.png index 338af58fa7..550001ec36 100644 Binary files a/docs/assets/bcfusion/token-recovery-7.png and b/docs/assets/bcfusion/token-recovery-7.png differ diff --git a/docs/assets/bcfusion/token-recovery-8.png b/docs/assets/bcfusion/token-recovery-8.png index e1c39e12af..56f4cd4fa1 100644 Binary files a/docs/assets/bcfusion/token-recovery-8.png and b/docs/assets/bcfusion/token-recovery-8.png differ diff --git a/docs/assets/bcfusion/token-recovery-9.png b/docs/assets/bcfusion/token-recovery-9.png index 20985b9f7f..b3788ce731 100644 Binary files a/docs/assets/bcfusion/token-recovery-9.png and b/docs/assets/bcfusion/token-recovery-9.png differ diff --git a/docs/bc-fusion/overview.md b/docs/bc-fusion/overview.md index 32e1993d5b..b2a49dc9ec 100644 --- a/docs/bc-fusion/overview.md +++ b/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. diff --git a/docs/bc-fusion/post-fusion/faq.md b/docs/bc-fusion/post-fusion/faq.md index 986c821a5d..2da95e5b64 100644 --- a/docs/bc-fusion/post-fusion/faq.md +++ b/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? diff --git a/docs/bc-fusion/post-fusion/token-recovery.md b/docs/bc-fusion/post-fusion/token-recovery.md index 6901943adc..5caa932428 100644 --- a/docs/bc-fusion/post-fusion/token-recovery.md +++ b/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. + diff --git a/docs/bc-fusion/validators/creation.md b/docs/bc-fusion/validators/creation.md index 0531fd5fdf..d108a80aea 100644 --- a/docs/bc-fusion/validators/creation.md +++ b/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. \ No newline at end of file diff --git a/docs/bnb-greenfield/core-concept/billing-payment.md b/docs/bnb-greenfield/core-concept/billing-payment.md index 7bed59bf49..92f5af0fcf 100644 --- a/docs/bnb-greenfield/core-concept/billing-payment.md +++ b/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 diff --git a/docs/bnb-greenfield/for-developers/data-archive/block-hub.md b/docs/bnb-greenfield/for-developers/data-archive/block-hub.md index 66cde59866..b941f378c4 100644 --- a/docs/bnb-greenfield/for-developers/data-archive/block-hub.md +++ b/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 diff --git a/docs/bnb-greenfield/for-developers/network-endpoint/endpoints.md b/docs/bnb-greenfield/for-developers/network-endpoint/endpoints.md index 8d39467094..3624725a56 100644 --- a/docs/bnb-greenfield/for-developers/network-endpoint/endpoints.md +++ b/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 diff --git a/docs/bnb-greenfield/for-developers/tutorials/app/data-marketplace.md b/docs/bnb-greenfield/for-developers/tutorials/app/data-marketplace.md index fd59ee2889..506b59b8a0 100644 --- a/docs/bnb-greenfield/for-developers/tutorials/app/data-marketplace.md +++ b/docs/bnb-greenfield/for-developers/tutorials/app/data-marketplace.md @@ -142,7 +142,7 @@ _Buyer_

5. Environment Support

-* 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)

6. Technical Design

diff --git a/docs/bnb-opbnb/faq/cross-chain-faqs.md b/docs/bnb-opbnb/faq/cross-chain-faqs.md index cfc99797d6..a7fa68c412 100644 --- a/docs/bnb-opbnb/faq/cross-chain-faqs.md +++ b/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. diff --git a/docs/bnb-smart-chain/developers/faucet.md b/docs/bnb-smart-chain/developers/faucet.md index 300a1a8a80..16ef244cd1 100644 --- a/docs/bnb-smart-chain/developers/faucet.md +++ b/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.* diff --git a/docs/bnb-smart-chain/developers/json_rpc/bsc-api-list.md b/docs/bnb-smart-chain/developers/json_rpc/bsc-api-list.md new file mode 100644 index 0000000000..d123c61a89 --- /dev/null +++ b/docs/bnb-smart-chain/developers/json_rpc/bsc-api-list.md @@ -0,0 +1,171 @@ +--- +title: Bsc API List- BSC Develop +--- + +## Finality API +Finality is a crucial aspect of blockchain security, ensuring that once a block is confirmed, it cannot be reversed or altered. This provides users with the confidence to act on the information in the block without delay. + +### Probabilistic Finality and Economic Finality + +In probabilistic finality, the deeper a block is buried in the chain, the lower the likelihood of it being reverted. The more blocks follow a particular block, the more likely the chain containing that block will be the longest. **Typically, BSC users should wait for at least 11 or 15 different validators to seal a block. If validators are allowed to produce multiple consecutive blocks, the number of blocks required to achieve probabilistic finality is approximately 11\*n or 15\*n, where "n" is the number of consecutive blocks produced.** + +Economic Finality refers to the high cost associated with reverting a block. In proof-of-stake systems that use a slashing mechanism (such as Casper FFG, Tendermint, or BSC Fast Finality), if validators violate the voting rules, part or all of their stake can be forfeited. This economic penalty makes it extremely expensive to undermine finality. Generally, block n achieves economic finality by block n+2, meaning that BSC Fast Finality reduces the confirmation time to two blocks in most cases. This improves the user experience by making transaction confirmation faster and more reliable. + +### Economic Finality API + +### [eth_getHeaderByNumber]() as in the Ethereum client. +**Parameters** + +**BlockNumber** QUANTITY|TAG + +* HEX String - an integer block number +* String "earliest" for the earliest/genesis block +* String "latest" - for the latest mined block +* String "safe" - for the latest justified head block +* String "**finalized**" - for the latest finalized block + +### [eth_getBlockByNumber]() as in the Ethereum client. +**Parameters** + +**BlockNumber** QUANTITY|TAG + +* HEX String - an integer block number +* String "earliest" for the earliest/genesis block +* String "latest" - for the latest mined block +* String "safe" - for the latest justified head block +* String "**finalized**" - for the latest finalized block + +**Full_transaction_flag** Boolean + +- If true it returns the full transaction objects, if false only the hashes of the transactions. + +### eth_newFinalizedHeaderFilter +Here are two APIs that can help you trace the latest finalized blocks: +1. Create a finalized header filter: +``` +curl -X POST "http://localhost:8545" -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_newFinalizedHeaderFilter","params":[],"id":1}' +``` +This will return an rpc.ID which will expire in 5 minutes, then you can get another: +``` +{"jsonrpc":"2.0","id":1,"result":"0xcbdc7c21459e2cfbf72e2028f15a98c"} +``` +2. Get latest finalized blocks using above rpc.ID. You can call it many times until rpc.ID expires: +``` +curl -X POST "http://localhost:8545" -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getFilterChanges","params":["0xcbdc7c21459e2cfbf72e2028f15a98c"],"id":1}' +``` +This will return block hashes: +``` +{"jsonrpc":"2.0","id":1,"result":["0x4b52061726b9f15905217699fd5dab8ff9bb704b3b16d27c34541cb15752a91f","0x2b984b80b25f0dddc92ba11290a3d250fc8a3ec6a09bd485c21dbbb8155d2f90"]} +``` + +### Combined Probabilistic Finality and Economic Finality API + +These methods allow you to handle block finality using a straightforward API. + +### eth_getFinalizedHeader +* `verifiedValidatorNum` must be within the range [1, len(currentValidators)]. +* This function calculates `probabilisticFinalizedHeight` as the highest height of the block verified by `verifiedValidatorNum` validators and then returns the block header with a height equal to `max(fastFinalizedHeight, probabilisticFinalizedHeight)`. +* The height of the returned block header is guaranteed to increase monotonically. +For example: +``` +curl -X POST "http://localhost:8545/" -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getFinalizedHeader","params":[15],"id":1}' +``` + +### eth_getFinalizedBlock +* `verifiedValidatorNum` must be within the range [1, len(currentValidators)]. +* This function calculates `probabilisticFinalizedHeight` as the highest height of the block verified by `verifiedValidatorNum` validators and then returns the block header with a height equal to `max(fastFinalizedHeight, probabilisticFinalizedHeight)`. +* If `fullTx` is true, the block includes all transactions; otherwise, only transaction hashes are included. +* The height of the returned block is guaranteed to be monotonically increasing. +For example: +``` +curl -X POST "http://localhost:8545/" -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getFinalizedBlock","params":[11, false],"id":1}' + +curl -X POST "http://localhost:8545/" -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getFinalizedBlock","params":[15, true],"id":1}' +``` + +## Blob API + +### eth_getBlobSidecarByTxHash +**Parameters** + +**Hash** String (REQUIRED) + +* HEX String - the hash of the transaction + +**full_blob_flag** Boolean (OPTIONAL) + +* Default is true. If ture it returns the full blob info, if false only return first 32 bytes of blobs. + +``` +curl -X POST "http://localhost:8545/" -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getBlobSidecarByTxHash","params":["0x377d3615d2e76f4dcc0c9a1674d2f5487cba7644192e7a4a5af9fe5f08b60a63"],"id":1}' + +curl -X POST "http://localhost:8545/" -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getBlobSidecarByTxHash","params":["0x377d3615d2e76f4dcc0c9a1674d2f5487cba7644192e7a4a5af9fe5f08b60a63", false],"id":1}' +``` + +### eth_getBlobSidecars +**Parameters** + +**BlockNumber** QUANTITY|TAG + +* HEX String - an integer block number +* HEX String - the hash of the block +* String "earliest" for the earliest/genesis block +* String "latest" - for the latest mined block +* String "safe" - for the latest justified head block +* String "finalized" - for the latest finalized block + +**full_blob_flag** Boolean (OPTIONAL) + +* Default is true. If ture it returns the full blob info, if false only return first 32 bytes of blobs. + +``` +curl -X POST "http://localhost:8545/" -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getBlobSidecars","params":["latest"],"id":1}' + +curl -X POST "http://localhost:8545/" -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getBlobSidecarByTxHash","params":["0xc5043f", false],"id":1}' +``` + + + +## Others + +### eth_health + +* a health check endpoint to detect whether the RPC func of a node is ok. Return true is ok, false is no health. + + +``` +curl -X POST "http://localhost:8545/" -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_health","params":[],"id":1}' +``` + +### eth_getTransactionsByBlockNumber + +* get all the transactions for the given block number. + +**Parameters** + +**BlockNumber** QUANTITY|TAG + +* HEX String - an integer block number +* String "earliest" for the earliest/genesis block +* String "latest" - for the latest mined block +* String "safe" - for the latest justified head block +* String "finalized" - for the latest finalized block + +``` +curl -X POST "http://localhost:8545/" -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getTransactionsByBlockNumber","params":["0x539492"],"id":1}' +``` + + +### eth_getTransactionDataAndReceipt + +* get the original transaction data and transaction receipt for the given transaction hash. + +**Parameters** + +**Hash** String (REQUIRED) + +* HEX String - the hash of the transaction + +``` +curl -X POST "http://localhost:8545/" -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getTransactionDataAndReceipt","params":["0x516a2ab1506b020e7f49d0d0ddbc471065624d1a603087262cebf4ca114ff588"],"id":1}' +``` \ No newline at end of file diff --git a/docs/bnb-smart-chain/developers/rpc.md b/docs/bnb-smart-chain/developers/json_rpc/json-rpc-endpoint.md similarity index 57% rename from docs/bnb-smart-chain/developers/rpc.md rename to docs/bnb-smart-chain/developers/json_rpc/json-rpc-endpoint.md index 91e77b3981..89e6f1ab49 100644 --- a/docs/bnb-smart-chain/developers/rpc.md +++ b/docs/bnb-smart-chain/developers/json_rpc/json-rpc-endpoint.md @@ -1,9 +1,9 @@ --- -title: RPC - BSC Develop +title: JSON-RPC-Endpoint - BSC Develop --- -# JSON-RPC Endpoint +# JSON-RPC-Endpoint JSON-RPC endpoints refers to the network location where a program could transfer its RPC requests to access server data. Once you connect a decentralized application to an RPC endpoint, you can access the functionalities of different operations, which could enable real-time usage of blockchain data. BNB Chain provides several RPC endpoints for connectinto both its Minent and Testnet. In this section, we list the JSON-RPC endpoints that can be used for connecting to BNB Smart Chain. @@ -62,6 +62,8 @@ You could find more endpoints from **[here](https://chainlist.org/chain/56)**. * **All That Node:** +* **Alchemy:** + ### Starting HTTP JSON-RPC You can start the HTTP JSON-RPC with the --http flag @@ -73,7 +75,26 @@ geth attach https://bsc-dataseed.bnbchain.org geth attach https://bsc-testnet-dataseed.bnbchain.org ``` -### JSON-RPC methods +## JSON-RPC API List + +BSC (BNB Smart Chain) is EVM-compatible and strives to be as compatible as possible with the Go-Ethereum API. However, BSC also has unique features, such as faster finality and the storage of blob data on the execution layer, which require their own specialized APIs. + +### Geth(Go-Ethereum) API + +BSC is nearly fully compatible with the Geth APIs. Any exceptions or incompatibilities are explicitly listed. If you're looking for detailed usage of a specific API, you will most likely find the answer in the following link: + +[Geth JSON-RPC API documentation](https://geth.ethereum.org/docs/interacting-with-geth/rpc). + +### Finality + +Ethereum's PoS consensus protocol, known as "Gasper," is built on LMD-GHOST (a fork choice rule) and Casper FFG (a finality gadget). Similarly, BSC's consensus protocol, called "Parlia," is constructed on top of a difficulty-based fork choice mechanism with FFG, as described in [BEP-126](https://github.com/bnb-chain/BEPs/blob/master/BEPs/BEP126.md). To further enhance BSC's throughput, validators are allowed to produce multiple consecutive blocks, as explained in [BEP-341](https://github.com/bnb-chain/BEPs/blob/master/BEPs/BEP-341.md). These differences result in BSC having a unique finality process compared to Ethereum. For more details, please refer to the the following doc: + +[BSC Finality API](bsc-api-list.md#finality-api). + +### Blob + +Bsc implement EIP-4844, which support Shard Blob Transactions, as described in [BEP-336](https://github.com/bnb-chain/BEPs/blob/master/BEPs/BEP-336.md). For more details, please refer to the the following doc: [BSC Blob API](bsc-api-list.md#blob-api). -Please refer to this [wiki page](https://github.com/ethereum/wiki/wiki/JSON-RPC) or use Postman: +### Other BSC API +Bsc implement some others apis, as described in: [BSC API](bsc-api-list.md#others). \ No newline at end of file diff --git a/docs/bnb-smart-chain/developers/node_operators/archive_node.md b/docs/bnb-smart-chain/developers/node_operators/archive_node.md index 5be2d2f514..ee8e6aab72 100644 --- a/docs/bnb-smart-chain/developers/node_operators/archive_node.md +++ b/docs/bnb-smart-chain/developers/node_operators/archive_node.md @@ -27,25 +27,65 @@ Running an archive node will take a high cost as it includes all the block and s ### Run with an Erigon client -[Erigon](https://github.com/node-real/bsc-erigon) has supported BSC mainnet. You can also refer to [Free public BNB Smart Chain Archive Snapshot](https://github.com/allada/bsc-archive-snapshot) for the guide to run a BSC archive node with an Erigon client. The owner has switched to using an Erigon client for a BSC archive node recently. You can download the archive snapshot which is a tarball from aws s3. The s3 path is "s3://public-blockchain-snapshots/bsc/erigon-latest.tar.zstd". This path is public, but is configured as requester-pays. Also this means you'll need an AWS account in order to download it. +[Erigon](https://github.com/node-real/bsc-erigon) now supports the BSC mainnet. The latest version allows you to sync an archive node from scratch in just 3 days, using 4.3 TB of disk space. You can use Erigon to operate an archive node as shown below. -* Command to download to local dir: -``` -aws s3 cp --request-payer=requester "s3://public-blockchain-snapshots/bsc/erigon-latest.tar.zstd" local_data_dir +### Run with a Reth client -tar --use-compress-program=unzstd -xvf erigon-latest.tar.zstd -``` +[Reth](https://github.com/bnb-chain/reth) now supports the BSC network and demonstrates superior performance compared to Geth and Erigon in recent benchmark tests. You can utilize reth to operate an archive node (as well as full node); for more information, refer to [Full Node](./full_node.md). + + + +--- +title: BSC Erigon Node Deployment Guide +--- + +### BSC Erigon Node Deployment -* Command to run: +BSC Erigon, maintained by the Node Real team, is a fork of Erigon aimed at becoming the premier archive node implementation for the BSC network. +## Hardware Requirements + +To ensure optimal performance of your BSC Erigon node, we recommend the following hardware specifications: + +* RAM: 64GB or more (higher RAM correlates with better performance) +* Storage: SSD or NVMe + - Archive Node: Minimum 5TB + - Fast Node: Minimum 700GB + +## BSC Erigon Node Deployment Steps + +### 1. Obtain the Erigon Binary + +Option 1: Build from source +```shell +git clone https://github.com/node-real/bsc-erigon.git +cd bsc-erigon +make erigon ``` -./erigon --chain=bsc --datadir local_data_dir +Option 2: Use Docker image +```shell +docker pull ghcr.io/node-real/bsc-erigon:${latest_version} ``` +### 2. Launch the Erigon Node +By default, the node will run in archive mode. Syncing from scratch typically takes about 3 days. +```shell +./build/bin/erigon \ +--datadir="" \ +--chain=bsc \ +--port=30303 \ +--http.port=8545 \ +--authrpc.port=8551 \ +--torrent.port=42069 \ +--private.api.addr=127.0.0.1:9090 \ +--http --ws \ +--http.api=eth,debug,net,trace,web3,erigon,bsc +``` +**Note**: To avoid port conflicts, specify different ports for each chain if running multiple instances. -The known Issue with an Erigon client is that it does not really keep up with the latest blocks as mentioned in the Github. If you want to keep up with the latest blocks it is suggested to run a BSC archive node with high performance disk such as NVME, or run a BSC full node with a Geth client at the same time which means you need one proxy that will ask Erigon if it has the block height and if not forward it to the Geth client. - -### Run with a Reth client +### 3. Running a Fast Node (Non-Archive Mode) + Add the --prune.mode=minimal flag to start a fast node. This mode retains only the last 3 days of state and block data, supporting debug_trace* operations for the past 3 days. -[Reth](https://github.com/bnb-chain/reth) now supports the BSC network and demonstrates superior performance compared to Geth and Erigon in recent benchmark tests. You can utilize reth to operate an archive node; for more information, refer to [Reth Node](./reth_node.md). +If you prefer not to spend days syncing, you can obtain fast node snapshots from [community-maintained repositories](https://github.com/48Club/bsc-snapshots). +By following these steps, you can flexibly deploy either a full BSC Erigon node or a fast node based on your requirements. Whichever option you choose, BSC Erigon will provide you with an efficient and reliable node service. diff --git a/docs/bnb-smart-chain/developers/node_operators/full_node.md b/docs/bnb-smart-chain/developers/node_operators/full_node.md index 007a028e77..181c6ed17e 100644 --- a/docs/bnb-smart-chain/developers/node_operators/full_node.md +++ b/docs/bnb-smart-chain/developers/node_operators/full_node.md @@ -2,21 +2,46 @@ title: Full Node - BSC Develop --- -# How to Run A Fullnode on BNB Smart Chain -## Fullnodes Functions +## 1.About -* Stores the full blockchain history on disk and can answer the data request from the network. -* Receives and validates the new blocks and transactions. -* Verifies the states of every account. +Full node stores the full world state on disk and is capable of: -## Supported Platforms +* handle new transactions and produce new blocks, can be used as a validator node. +* execute and validate newly received blocks. +* verify the states of every account, as it has the full world state. + +Currently, there are 3 different clients to run a BSC full: + +* Geth: https://github.com/bnb-chain/bsc +* Reth: https://github.com/bnb-chain/reth +* Erigon: https://github.com/node-real/bsc-erigon + +Only Geth and Reth will be covered in this page, as Erigon is mainly to support archive mode, pls refer [archive_node.md](./archive_node.md) for its usage. + +!!! tip + If you want high performance and care little about state consistency, you can run a fast node, which is a full node with the flag `--tries-verify-mode none` set. + Check [here](fast_node.md) for full details on running a fast node. + ``` + ./geth --config ./config.toml --datadir --cache 8000 --tries-verify-mode none + ``` +## 2.Run BSC Full Node: Geth + +### 2.1.Supported Platforms We support running a full node on **Mac OS X**, **Linux**, and **Windows**. -## Steps to Run a Fullnode +### 2.2.Steps +There are 2 approaches to setup a BSC full node from scratch: + +- By Snapshot(Recommend): download the latest snapshot and sync based on it. + +- From Genesis(Not Recommend): sync the whole BSC chain from genesis block. -### Sync From Snapshot (Recommended) +!!! tip + As of Nov-2024, the latest block height of BSC mainnet is over 40M, it would need a more powerful hardware and take a great of time to sync from genesis, so it is suggested to setup a BSC full node based the snapshot. + +#### a.By Snapshot 1. Download the pre-build binaries from the [release page](https://github.com/bnb-chain/bsc/releases/latest) or follow the instructions below @@ -49,41 +74,15 @@ We support running a full node on **Mac OS X**, **Linux**, and **Windows**. 3. Download snapshot Download latest chaindata snapshot from [here](https://github.com/bnb-chain/bsc-snapshots). Follow the guide to structure your files. - !!! tip - Your --datadir flag should point to the folder where the extracted snapshot data is. - In our case, we created a new folder named `node`, and we moved the extracted snapshot data to this folder. - ``` - mv server/data-seed/geth/chaindata node/geth/chaindata - mv server/data-seed/geth/chaindata node/geth/triecache - ``` - 4. Start a full node ``` - ./geth --config ./config.toml --datadir ./node --cache 8000 --rpc.allow-unprotected-txs --history.transactions 0 + ## pls replace with your local path to datadir. + ./geth --config ./config.toml --datadir --cache 8000 ``` - !!! 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. - For all geth nodes, DO NOT use `-pipecommit` flag - - !!! tip - It is recommended to run a fast node, which is a full node with the flag `--tries-verify-mode none` set if you want high performance and care little about state consistency. - Check [here](fast_node.md) for full details on running a fast node. - It will run with Hash-Base Storage Scheme by default - ``` - ./geth --config ./config.toml --datadir ./node --cache 8000 --rpc.allow-unprotected-txs --history.transactions 0 --tries-verify-mode none - ``` - - It will run with Path-Base Storage Scheme. - It will enable inline state prune, keeping the latest 90000 blocks' history state by default. - ``` - ./geth --config ./config.toml --datadir ./node --cache 8000 --rpc.allow-unprotected-txs --history.transactions 0 --tries-verify-mode none --state.scheme path - ``` - - 5. Monitor node status - You can monitor the log from **./node/bsc.log** by default. When your node has started syncing, you should be able to see the following output: + You can monitor the log from **.//bsc.log** by default. When your node has started syncing, you should be able to see the following output: ``` t=2022-09-08T13:00:27+0000 lvl=info msg="Imported new chain segment" blocks=1 txs=177 mgas=17.317 elapsed=31.131ms mgasps=556.259 number=21,153,429 hash=0x42e6b54ba7106387f0650defc62c9ace3160b427702dab7bd1c5abb83a32d8db dirty="0.00 B" @@ -91,22 +90,14 @@ We support running a full node on **Mac OS X**, **Linux**, and **Windows**. t=2022-09-08T13:00:33+0000 lvl=info msg="Imported new chain segment" blocks=1 txs=197 mgas=19.364 elapsed=34.663ms mgasps=558.632 number=21,153,431 hash=0x0c7872b698f28cb5c36a8a3e1e315b1d31bda6109b15467a9735a12380e2ad14 dirty="0.00 B" ``` -### Sync From Genesis Block (Not Recommended) - -!!! caution - It is recommended to use HBSS with level DB for archive node, PBSS for archive node is not supported yet. - - -!!! note - To sync from genesis block, you would need a more powerful hardware. Server should at least have 40k IOPS and be at least an i3/i3en series server. - - +#### b.From Genesis ```bash -## start a full node -./geth --config ./config.toml --datadir ./node --cache 8000 --rpc.allow-unprotected-txs --history.transactions 0 +## start a full node from genesis with by one command +## pls replace with your local path to datadir. +./geth --config ./config.toml --datadir --cache 8000 ``` -## Sync Mode +### 2.3.Sync Mode There are two sync modes for running a full node: **snap** and **full** which can be specified by flag **--syncmode**. @@ -116,21 +107,92 @@ The **full** sync mode can also be used to do initial sync, which will execute a If the flag **--syncmode** is not provided, the default sync mode will depend on the state of the data folder. It will be **snap** mode if you sync from genesis or **full** mode if you start from a snapshot. -### Full Sync with Greenfield Peer (Optional) +### 2.4.Others +#### a.Greenfield Peers -Opting for **full** sync mode means your node will only need block headers and bodies from other network peers. To expedite this process, -consider utilizing the `Greenfield Peer`. +Opting for **full** sync mode means your node will only need block headers and bodies from other network peers. To expedite this process, consider utilizing the `Greenfield Peer`. This data seed, offered by Greenfield, allows for a more efficient synchronization. Configure your BSC node to connect with the Greenfield Light Peer by modifying your configuration file settings. For comprehensive instructions, see [Light Peer](../../../bnb-greenfield/for-developers/data-archive/light-peer.md). -## Local Private Network + +#### b.Local Private Network Please refer to [BSC-Deploy Tools](https://github.com/bnb-chain/node-deploy) to setup a local private network. -## Node Maintenance +#### c.Node Maintenance Please read [this guide](node_maintenance.md) -## Upgrade Geth +#### d.Upgrade Geth Please read [this guide](upgrade_geth.md) +## 3.Run BSC Full Node: Reth + +BSC Reth is a cutting-edge Rust client developed in collaboration with Paradigm, designed to provide seamless support for BNB Smart Chain (BSC). It aims to enhance client diversity on the BNB Chain by offering a secure and efficient execution client. + +### 3.1.Hardware Specifications + +To run BSC Reth effectively, ensure your system meets the following hardware requirements: + +* CPU with 16+ cores +* 128GB RAM +* High-performance NVMe SSD with at least 4TB of free space for a full node and 8TB for an archive node +* Broadband internet connection with upload/download speeds of 25 MB/s + +### 3.2.Running BSC Reth + +1. Download source code and build binary. +```shell +git clone https://github.com/bnb-chain/reth.git +cd reth +make build-bsc +``` + +2. Start the reth node, it will run in archive mode by default. You can add the `--full` flag to start a full node. +```shell +# for mainnet +export network=bsc + +# for testnet +# export network=bsc-testnet + +./target/release/bsc-reth node \ + --datadir=./datadir \ + --chain=${network} \ + --http \ + --http.api="eth, net, txpool, web3, rpc" \ + --log.file.directory ./datadir/logs +``` + +3. Optionally, you can run the reth node with docker. +```shell +# for mainnet +export network=bsc + +# for testnet +# export network=bsc-testnet + +# check this for version of the docker image, https://github.com/bnb-chain/reth/pkgs/container/bsc-reth +export version=latest + +# the directory where reth data will be stored +export data_dir=/xxx/xxx + +docker run -d -p 8545:8545 -p 30303:30303 -p 30303:30303/udp -v ${data_dir}:/data \ + --name bsc-reth ghcr.io/bnb-chain/bsc-reth:${version} node \ + --datadir=/data \ + --chain=${network} \ + --http \ + --http.api="eth, net, txpool, web3, rpc" \ + --log.file.directory /data/logs +``` + +### 3.3.Snapshot + +To synchronize a BSC reth node from scratch to the current block height can be a time-consuming process. +As We benchmark [Reth(v1.0.0)](https://github.com/bnb-chain/reth/releases/tag/v1.0.0) on AWS [lm4gn.8xlarge](https://instances.vantage.sh/aws/ec2/im4gn.8xlarge)(32 core 128G) with 2 x 7500 NVMe SSD for BSC mainnet. +It may take approximately 30 days to sync the latest block on BSC mainnet for an archive node and 24 days for a full node. + +Given the extended duration required for stage synchronization of the BSC network, the BNB Chain team is developing a segmented snapshot download solution, scheduled for release in the near future. +Currently, developers seeking to expedite the process can obtain archive node snapshots from [community-maintained repositories](https://github.com/fuzzland/snapshots). +These snapshots offer a faster alternative to syncing from genesis, allowing for quicker node setup and network participation. diff --git a/docs/bnb-smart-chain/developers/node_operators/reth_node.md b/docs/bnb-smart-chain/developers/node_operators/reth_node.md deleted file mode 100644 index 45a2c0c203..0000000000 --- a/docs/bnb-smart-chain/developers/node_operators/reth_node.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Reth Node - BSC Develop ---- - -# Reth Node for BSC - -BSC Reth is a cutting-edge Rust client developed in collaboration with Paradigm, designed to provide seamless support for BNB Smart Chain (BSC). It aims to enhance client diversity on the BNB Chain by offering a secure and efficient execution client. - -## Hardware Specifications - -To run BSC Reth effectively, ensure your system meets the following hardware requirements: - -* CPU with 16+ cores -* 128GB RAM -* High-performance NVMe SSD with at least 4TB of free space for a full node and 8TB for an archive node -* Broadband internet connection with upload/download speeds of 25 MB/s - -## Running BSC Reth - -1. Download source code and build binary. -```shell -git clone https://github.com/bnb-chain/reth.git -cd reth -make build-bsc -``` - -2. Start the reth node, it will run in archive mode by default. You can add the `--full` flag to start a full node. -```shell -# for mainnet -export network=bsc - -# for testnet -# export network=bsc-testnet - -./target/release/bsc-reth node \ - --datadir=./datadir \ - --chain=${network} \ - --http \ - --http.api="eth, net, txpool, web3, rpc" \ - --log.file.directory ./datadir/logs -``` - -3. Optionally, you can run the reth node with docker. -```shell -# for mainnet -export network=bsc - -# for testnet -# export network=bsc-testnet - -# check this for version of the docker image, https://github.com/bnb-chain/reth/pkgs/container/bsc-reth -export version=latest - -# the directory where reth data will be stored -export data_dir=/xxx/xxx - -docker run -d -p 8545:8545 -p 30303:30303 -p 30303:30303/udp -v ${data_dir}:/data \ - --name bsc-reth ghcr.io/bnb-chain/bsc-reth:${version} node \ - --datadir=/data \ - --chain=${network} \ - --http \ - --http.api="eth, net, txpool, web3, rpc" \ - --log.file.directory /data/logs -``` - -## Snapshot - -To synchronize a BSC reth node from scratch to the current block height can be a time-consuming process. -As We benchmark [Reth(v1.0.0)](https://github.com/bnb-chain/reth/releases/tag/v1.0.0) on AWS [lm4gn.8xlarge](https://instances.vantage.sh/aws/ec2/im4gn.8xlarge)(32 core 128G) with 2 x 7500 NVMe SSD for BSC mainnet. -It may take approximately 30 days to sync the latest block on BSC mainnet for an archive node and 24 days for a full node. - -Given the extended duration required for stage synchronization of the BSC network, the BNB Chain team is developing a segmented snapshot download solution, scheduled for release in the near future. -Currently, developers seeking to expedite the process can obtain archive node snapshots from [community-maintained repositories](https://github.com/fuzzland/snapshots). -These snapshots offer a faster alternative to syncing from genesis, allowing for quicker node setup and network participation. diff --git a/docs/bnb-smart-chain/developers/paymaster/overview.md b/docs/bnb-smart-chain/developers/paymaster/overview.md index d4968cf4af..d96ae568c8 100644 --- a/docs/bnb-smart-chain/developers/paymaster/overview.md +++ b/docs/bnb-smart-chain/developers/paymaster/overview.md @@ -89,4 +89,16 @@ The gas sponsorship process involves several key components and steps: This solution leverages the BEP322 Proposer-Builder Separation architecture to enable seamless gas sponsorship without requiring significant changes to existing wallet infrastructures. It provides a flexible system that can accommodate -various sponsorship models while maintaining the security and integrity of the blockchain network. \ No newline at end of file +various sponsorship models while maintaining the security and integrity of the blockchain network. + +## Paymaster Infra + +Ready to enable gasless experiences in your app or wallet? Here's some helpful information on paymaster infrastructure +that are available on BNB Chain: + +- [Nodereal](https://docs.nodereal.io/docs/megafuel-overview). The MegaFuel powered by Nodereal is a paymaster +implementation based on BNB Chain Paymaster for EOA Wallet. With minimal modifications, wallets can integrate MegaFuel +to support gas fee sponsorship, significantly enhancing user experience. At the same time, sponsors can customize +their sponsorship on MegaFuel, allowing sponsored users to send gasless transactions. +- [Bitget Wallet](https://web3.bitget.com/en/). Bitget Wallet has integrated the paymaster on BSC, providing gasless functionality +for sponsored user transactions. diff --git a/docs/bnb-smart-chain/developers/paymaster/wallet-demo.md b/docs/bnb-smart-chain/developers/paymaster/wallet-demo.md new file mode 100644 index 0000000000..3c9c7eecc6 --- /dev/null +++ b/docs/bnb-smart-chain/developers/paymaster/wallet-demo.md @@ -0,0 +1,22 @@ +--- +title: Experience Paymaster - BSC Paymaster +--- +# Experience Paymaster in mainstream Wallets + +Several mainstream cryptocurrency wallets have already implemented Paymaster integration. +This tutorial will guide you through the experience of sending gasless transactions in paymaster integrated wallets. + + +## Paymaster Integrated Wallets + +Wallets with integrated Paymaster functionality offer a seamless experience for users. +These wallets automatically detect whether a transaction is eligible for sponsorship. +When a transaction qualifies, the wallet sets the gas price to zero without any user intervention. + +To illustrate this, we'll walk through the process by transferring stable coin on BSC. + +![type:video](../../img/BNB_Send%20Gasless%20Transaction.mp4) + + + + diff --git a/docs/bnb-smart-chain/developers/paymaster/wallet-integration.md b/docs/bnb-smart-chain/developers/paymaster/wallet-integration.md index 1796dea226..d5cb86503d 100644 --- a/docs/bnb-smart-chain/developers/paymaster/wallet-integration.md +++ b/docs/bnb-smart-chain/developers/paymaster/wallet-integration.md @@ -9,7 +9,7 @@ This guide outlines the steps for wallet developers to integrate paymaster servi ![wallet-paymaster](../../img/paymaster-wallet.png) -Integration involves modifying the transaction creation and sending process to interact with paymaster services. For detailed information about the paymaster API interface, please refer to this document. +Integration involves modifying the transaction creation and sending process to interact with paymaster services. For detailed information about the paymaster API interface, please refer to this [document](./paymaster-api.md). The main steps are: diff --git a/docs/bnb-smart-chain/developers/quick-guide.md b/docs/bnb-smart-chain/developers/quick-guide.md index e9848b9fdb..e0f7a78362 100644 --- a/docs/bnb-smart-chain/developers/quick-guide.md +++ b/docs/bnb-smart-chain/developers/quick-guide.md @@ -14,7 +14,7 @@ Since BSC is EVM-compatible, your existing Ethereum smart contract skills will s Here are some resources to help you get connected to the BSC network: -- [Network Information and RPC Providers](./rpc.md) +- [Network Information and RPC Providers](json_rpc/json-rpc-endpoint.md) - [Wallet Configuration](./wallet-configuration.md) ## Get Tokens @@ -28,7 +28,7 @@ For the mainnet, you can withdraw tokens directly from a centralized exchange (C ## JSON-RPC API Interacting with BSC requires sending requests to specific JSON-RPC API methods. BSC's APIs are compatible with Geth. -- [JSON-RPC API](https://geth.ethereum.org/docs/interacting-with-geth/rpc) +- [JSON-RPC API](json_rpc/json-rpc-endpoint.md) ## Developer Tools - Explorer diff --git a/docs/bnb-smart-chain/governance/bnb-kol.md b/docs/bnb-smart-chain/governance/bnb-kol.md new file mode 100644 index 0000000000..523c239f53 --- /dev/null +++ b/docs/bnb-smart-chain/governance/bnb-kol.md @@ -0,0 +1,63 @@ +--- +title: A BNB Advocate`s Guide +--- + +# BNB On-Chain Governance Voting: A BNB Advocate`s Guide + +# Introduction + +Key Opinion Leaders (BNB Advocates) hold significant influence within the BNB Chain community. Your participation in on-chain governance is vital to ensure the network evolves in a truly decentralized manner. By maximizing your voting power, you can amplify your community's voice and drive positive change. + +# How to Increase Voting Power + +**As a tech leader, there are two primary ways to enhance your governance power:** + +1. Increase your BNB holdings: The more BNB you hold in your wallet, the more voting power you possess. Consider acquiring additional BNB to boost your influence in governance decisions. +2. Receive delegated BNB: Encourage your community members to delegate their voting power to you. This empowers you to vote on their behalf, increasing your overall influence in the governance process. + +**Steps to Gain More Voting Power from Your Community** + +1. Educate and Advocate: Explain the importance of on-chain governance and how it empowers the community to shape the future of BNB Chain. Clearly articulate the benefits of delegating voting power to you as a trusted tech leader. +2. Share Proposals and Insights: Regularly share your thoughts on upcoming proposals and explain how they might impact the community. Provide insightful analysis and encourage your followers to engage in the discussion. +3. Simplify Delegation: Make the delegation process as easy as possible for your community. Provide clear instructions and guidance on how to delegate their voting power to you. +4. Transparent Communication: Maintain open and transparent communication with your community. Keep them informed about how you plan to utilize their delegated voting power and the rationale behind your voting decisions. +5. Build Trust: Continuously build trust with your community by demonstrating your commitment to their interests and the overall well-being of the BNB Chain ecosystem. + +## Steps of governance power delegation(To be shared to your followers) + +1. Access the BNB Chain Governance page: + +1. Go to the Tally website (https://www.tally.xyz/gov/bnb-chain). + +1. Connect Your Wallet: + 1. Click on "Connect Wallet" and select your preferred wallet provider. + 2. Follow the prompts to connect and authorize access to your wallet. +2. Navigate to Delegation: + +1. Locate and click on the "Delegate" button or tab. + +![img](../img/tally-delegate.png) + +1. Choose Your Delegate: + +1. You have two main options: + 1. Delegate to Self: This means you will directly control your voting power and vote on proposals yourself. + 2. Delegate to Another Address: Enter the wallet address of the person or entity you want to delegate your voting power to. + +1. Confirm and Sign + 1. Once you've made your selection, review the details and click on the "Delegate" or "Delegate Votes" button. + 2. Your wallet will prompt you to confirm and sign the transaction. +2. Verify Delegation: + 1. After the transaction is confirmed on the blockchain, you can go to the "Votes" or "My Delegates" section on Tally to verify that your delegation was successful. + +# Important Considerations: + +- Factors Affecting Voting Power: + +- BNB Staking: The more BNB you staked on validators, the greater your voting power. +- Delegated BNB: The more people delegate their voting power to you, your voting power increases. + +# Disclaimer: + +- The specific process and rules for BNB on-chain governance voting might evolve. Always refer to official BNB Chain documentation and announcements for the latest information. +- Remember: On-chain governance is a powerful tool that enables the BNB Chain community to make collective decisions about the network's future. By participating, you contribute to the growth and development of the BNB Chain ecosystem. diff --git a/docs/bnb-smart-chain/governance/temp-check.md b/docs/bnb-smart-chain/governance/temp-check.md index 877b21b539..4b4bdd499b 100644 --- a/docs/bnb-smart-chain/governance/temp-check.md +++ b/docs/bnb-smart-chain/governance/temp-check.md @@ -70,4 +70,10 @@ Step 1: Go to https://snapshot.org/#/delegate/bnbchain-dao.eth Step 2: Find the current delegatees in Top delegates. -Step 3: Click the 'x' button along a delegatee to undelegate, the wallet will ask user to sign and send transaction to bsc \ No newline at end of file +Step 3: Click the 'x' button along a delegatee to undelegate, the wallet will ask user to sign and send transaction to bsc + +### Factors Affecting Temperature Governance Power: +- BNB Holding Balance: The more BNB you hold, the greater your voting power. +- Staked BNB: Delegating your BNB to a validator also contributes to your governance power. This ensures those actively participating in the network's security have a say. https://www.bnbchain.org/en/bnb-staking +- ListDAO Staked BNB: Your staked listDAO BNB(slisBNB) https://docs.bsc.lista.org/user-guide/liquid-staking-slisbnb + diff --git a/docs/bnb-smart-chain/img/BNB_Send Gasless Transaction.mp4 b/docs/bnb-smart-chain/img/BNB_Send Gasless Transaction.mp4 new file mode 100644 index 0000000000..6d41bd936a Binary files /dev/null and b/docs/bnb-smart-chain/img/BNB_Send Gasless Transaction.mp4 differ diff --git a/docs/bnb-smart-chain/img/mev/mev-blocks-by-builders.png b/docs/bnb-smart-chain/img/mev/mev-blocks-by-builders.png new file mode 100644 index 0000000000..cdad6b0dee Binary files /dev/null and b/docs/bnb-smart-chain/img/mev/mev-blocks-by-builders.png differ diff --git a/docs/bnb-smart-chain/img/mev/proxy.png b/docs/bnb-smart-chain/img/mev/proxy.png new file mode 100644 index 0000000000..080005ce77 Binary files /dev/null and b/docs/bnb-smart-chain/img/mev/proxy.png differ diff --git a/docs/bnb-smart-chain/img/tally-delegate.png b/docs/bnb-smart-chain/img/tally-delegate.png new file mode 100644 index 0000000000..afaf67d3f7 Binary files /dev/null and b/docs/bnb-smart-chain/img/tally-delegate.png differ diff --git a/docs/bnb-smart-chain/index.md b/docs/bnb-smart-chain/index.md index 29be1f27dc..176003020c 100644 --- a/docs/bnb-smart-chain/index.md +++ b/docs/bnb-smart-chain/index.md @@ -52,12 +52,12 @@ title: BNB Smart Chain
Run a Node

Run a BSC node

- +
MEV Builder

Become a builder and create blocks and offering them to the validator

- -
JSON-RPC API
+
+
JSON-RPC-Endpoint

Interacting with BSC requires sending requests to specific JSON-RPC API methods.

diff --git a/docs/bnb-smart-chain/staking/developer-guide.md b/docs/bnb-smart-chain/staking/developer-guide.md index bde8878243..4ad33c10cc 100644 --- a/docs/bnb-smart-chain/staking/developer-guide.md +++ b/docs/bnb-smart-chain/staking/developer-guide.md @@ -241,7 +241,8 @@ to `0` to get all the locked BNBs. The contracts do not save the initial delegation amount of a delegator. To get the accumulated reward, the following steps can be taken: 1) track the initial delegation amount in your system, 2) call -the `getPooledBNB` of the credit contract of a validator, 3) do the math. +the `getPooledBNB` of the credit contract of a validator, 3) do the math. You can refer +to [this code repository](https://github.com/bnb-chain/staking-reward-example) for example. ### How to get the total staking address of a validator? diff --git a/docs/bnb-smart-chain/staking/user-guide.md b/docs/bnb-smart-chain/staking/user-guide.md index 898a4ca071..e0262bcb05 100644 --- a/docs/bnb-smart-chain/staking/user-guide.md +++ b/docs/bnb-smart-chain/staking/user-guide.md @@ -61,3 +61,17 @@ To claim your stakes and rewards, you need to undelegate. After the unbonding period, you can claim your stakes by clicking the `Claim` button. ![](../img/staking/user-stake10.png){:style="width:400px"} + +## FAQs + +### Which wallet can be used to delegate to validators? + +Currently, `MetaMask` and `TrustWallet` are supported, along with any wallets compatible +with `WalletConnect`. + +### Can I delegate/undelegate/redelegate/claim stakes on explorers? + +If you want to do the aforementioned delegate/undelegate/redelegate/claim operations on BscScan or BscTrace, +you should call the staking hub contract in the following URLs: +* [BscScan Stake Hub](https://bscscan.com/address/0x0000000000000000000000000000000000002002#writeContract) +* [BscTrace Stake Hub](https://bsctrace.com/address/0x0000000000000000000000000000000000002002?tab=Contract&p=1&view=contract_write) diff --git a/docs/bnb-smart-chain/validator/create-val.md b/docs/bnb-smart-chain/validator/create-val.md index 561db210f9..aa1aab6cf3 100644 --- a/docs/bnb-smart-chain/validator/create-val.md +++ b/docs/bnb-smart-chain/validator/create-val.md @@ -64,7 +64,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. @@ -147,3 +147,4 @@ Identity is used to associate the new validator with the old validator created o 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. \ No newline at end of file diff --git a/docs/bnb-smart-chain/validator/mev/user-guide.md b/docs/bnb-smart-chain/validator/mev/user-guide.md new file mode 100644 index 0000000000..6d5e07ea2b --- /dev/null +++ b/docs/bnb-smart-chain/validator/mev/user-guide.md @@ -0,0 +1,67 @@ +--- +title: User Guide - BSC MEV +--- + + +# User Guide + +PBS(Proposer-Builder Separation) framework offers several advantages for BNB Chain users: + +- Users are less likely to have their transactions front-run or sandwiched. +- Increased competition among block builders can lead to more efficient markets and potentially lower gas prices. +- Enhanced transaction privacy: Users' transactions are exposed to fewer parties before being included in a block. +- Faster transaction processing: More efficient block construction can lead to quicker transaction confirmations. + +## For Retail Traders + +When you trade on a decentralized exchange (DEX), you risk being targeted by bots that can front-run your trades, meaning they see your transaction in the public mempool and execute a similar trade first, profiting from the price change you were going to cause. This can result in you getting a worse price or even losing money. Private RPCs offer a solution to this problem. They route your transactions through a private mempool(Provided by builders), hiding them from bots. This means your trades are less likely to be front-run, and you're more likely to get the price you expect. + +Some DEX protocols or builder providers are keen to provide free protection features, and the average transaction confirmation time is around 4-5 seconds, and it may fluctuate according to the network conditions. + +| Role | Status and Comments | +| ---------------------------- | ------------------------------------------------------------ | +| Free Privacy Protecting RPCs |
  • [Pancake Swap Private RPC](https://docs.pancakeswap.finance/products/pancakeswap-private-rpc)
  • [48 Club Private RPC](https://docs.48.club/privacy-rpc)
  • [Merkle Free BSC Private RPC](https://merkle.io/free-bsc-rpc)
| + +Several wallets now offer built-in protection against malicious MEV (Miner Extractable Value) attacks, enhancing the security and fairness of users' transactions. This protection is often available as a feature that users can manually enable during their swap or trading activities. + +**Wallets with Manual MEV Protection:** + +- **Private Transaction Relays:** These relays hide transaction details from malicious actors, preventing them from front-running or sandwich attacking the user's trade. +- **Specialized Builders:** Some wallets utilize builders that prioritize user protection and fair ordering of transactions, minimizing the potential for MEV exploitation. + +| Type | Name | Status | How to enable | +| ------ | -------------- | --------- | ------------------------------------------------------------ | +| Wallet | Trust Wallet | Supported | [TrustWallet Swap MEV Protection](https://trustwallet.com/blog/introducing-mev-protection-secure-your-swaps-with-trust-wallet) | +| Wallet | Binance Web3 Wallet | Supported | [Binance Alpha tokens MEV Protection](https://www.binance.com/en/support/announcement/introducing-binance-alpha-discover-emerging-crypto-projects-c6499e95c15e408ca44ca5f6db975d4d) | +| Wallet | OKX Wallet | Supported | [OKX Wallet Enable Swap MEV Protection](https://www.okx.com/help/okx-wallet-supports-flashbot-to-prevent-mev-attack) | +| Wallet | TokenPocket Wallet | Supported | [TokenPocket Swap MEV Protection](https://help.tokenpocket.pro/en/security-knowledge/security-measure/mev-protection-tutorial) | + + +## For Professional Traders and Service Providers + +While free private RPCs offer a good level of protection, you can opt for even stronger safeguards with premium private RPC services. These services often provide advanced features and dedicated infrastructure for enhanced security and performance. + +| Role | Status and Comments | +| ------------------------------------------------------------ | ------------------------------------------------------------ | +| 5 Builders (Private privacy protecting RPC service providers) |
  • [BloxRoute](https://bloxroute.com/products/protected-transactions/)
  • [Blocksmith](https://docs.blocksmith.org/bsc-builder/private-rpc)
  • [Nodereal](https://docs.nodereal.io/reference/bsc-bundle-service-api#overview)
  • [Blockrazor](https://blockrazor.gitbook.io/blockrazor/mev-service/bsc)
  • [Puissant](https://docs.48.club/)
| + +There are two aspects that may impact the transaction inclusion speed. + +1. Validator Network: Providers with a larger network of integrated validators can often offer faster inclusion speeds. More validators mean more opportunities for your transaction to be picked up and added to a block. +2. Builder Usage: Higher usage of a builder's service generally leads to faster inclusion. Increased usage makes the builder's block proposals more valuable to validators, incentivizing them to prioritize those blocks. + +You can view the latest MEV builder data (MEV_Blocks_by_Builders) from the [Dune dashboard](https://dune.com/bnbchain/bnb-smart-chain-mev-stats), and select the appropriate builders to broadcast transactions. The contacts of each builder are listed above in Table 1. + +You can check the number of validators integrated and the number of blocks of each builder, as mentioned above. + +1. The more validators are integrated, the faster the builder can be. +2. The more blocks that are produced, the faster the builder can be. + +![img](../../img/mev/mev-blocks-by-builders.png) + +For those who are very sensitive to transaction confirmation time, to maximize the transaction speed, it is recommended to build a proxy to broadcast the transaction to multiple builders to **increase the transaction inclusion speed**. You need to build your own RPC proxy with multiple builder service providers. + +![img](../../img/mev/proxy.png) + +A transaction proxy sample code is built by NodeReal, You can find it in the open-source git repo here https://github.com/node-real/private-tx-sender + diff --git a/docs/bnb-smart-chain/validator/mev/validator-integration.md b/docs/bnb-smart-chain/validator/mev/validator-integration.md index 49732f6c0d..78a127d7f0 100644 --- a/docs/bnb-smart-chain/validator/mev/validator-integration.md +++ b/docs/bnb-smart-chain/validator/mev/validator-integration.md @@ -5,7 +5,7 @@ title: Integration Guide for Validator - BSC MEV # Integration Guide for Validator -## Decison Make +## Decision Make When activating MEV functionality, validators encounter a mix of opportunities and challenges. Before enabling this feature, validators diff --git a/docs/bnb-smart-chain/validator/run-val.md b/docs/bnb-smart-chain/validator/run-val.md index c8103ed045..9f629ec2ba 100644 --- a/docs/bnb-smart-chain/validator/run-val.md +++ b/docs/bnb-smart-chain/validator/run-val.md @@ -8,19 +8,17 @@ title: Run BSC Validator - BNB Smart Chain ### Mainnet -- VPS running recent versions of Mac OS X or Linux. -- **IMPORTANT** 3T GB of free disk space, solid-state drive(SSD), gp3, 8k IOPS, 500 MB/S throughput, read latency <1ms (if start with snap sync, it will need NVMe SSD). -- 16 cores of CPU and 64 gigabytes of memory (RAM). -- Suggest m5zn.3xlarge or r7iz.4xlarge instance type on AWS, or c2-standard-16 on Google cloud. -- A broadband Internet connection with upload/download speeds of 5 megabyte per second +- Instance Spec: Suggest r7a.4xlarge instance type on AWS. +- Memory: 64 GB +- Disk: **IMPORTANT** 4T GB, solid-state drive(SSD), gp3, 8k IOPS, 500 MB/S throughput, read latency <1ms (if start with snap sync, it will need NVMe SSD). +- Network Bandwidth: > 10 Gbps ### Testnet -- CPU: 4core, Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz +- CPU: "AMD Gen 3 or newer" or "Intel Ice Lake or newer" - Memory: 16 GB -- Disk: ~1.5 TB -- Network Bandwidth: Upto 25 Gbps -- EBS Bandwidth: Upto 9.5 Gbps +- Disk: 1.5 TB, solid-state drive(SSD), gp3, 8k IOPS, 250 MB/S throughput. +- Network Bandwidth: > 2.5 Gbps ## Setup Validator Node @@ -163,4 +161,4 @@ For example, if v1.4.9 has known issues, we wanna disconnect nodes of this versi ``` [Node.P2P] PeerFilterPatterns = ["Geth/v1.4.9.*"] -``` \ No newline at end of file +``` diff --git a/docs/showcase/game/minigame.md b/docs/showcase/telegram/minigame.md similarity index 100% rename from docs/showcase/game/minigame.md rename to docs/showcase/telegram/minigame.md diff --git a/docs/showcase/telegram/wallets.md b/docs/showcase/telegram/wallets.md new file mode 100644 index 0000000000..044b01b92b --- /dev/null +++ b/docs/showcase/telegram/wallets.md @@ -0,0 +1,39 @@ +--- +title: Showcase - Telegram Wallets +--- + +## **BNB Chain on Telegram: Your Gateway to Web3 Convenience** + +Telegram isn't just for chatting anymore. It's evolving into a powerful hub for Web3 interactions, and BNB Chain is leading the way. If you've been curious about managing your BNB, interacting with dApps, or exploring the decentralized world all within your favorite messaging app, you're in the right place. Let's dive into the exciting possibilities! + +### **Telegram Wallets: Your BNB Chain Companion** + +Forget switching between apps. With Telegram bot wallets, you can seamlessly manage your BNB and interact with the BNB Chain ecosystem directly within your chats. + +| Name | Telegram Link | SDK Doc | +| ----------------- | -------------------------- | ------------------------------------------------------------ | +| CodexField Wallet | https://t.me/codexfieldbot | https://www.npmjs.com/package/codexfield-wallet-connector?activeTab=readme | +| UXUY Wallet | https://t.me/UXUYbot | https://docs.uxuy.com/uxuy-connect/quickstart/ | + +### **Telegram Authentication: A Developer's Dream** + +If you're a developer building on BNB Chain, streamlining user onboarding is key. [Privy's SDK](https://docs.privy.io/guide/dashboard/telegram) and [Particle wallet](https://developers.particle.network/guides/wallet-as-a-service/waas/auth/tg-quickstart) let you integrate secure Telegram logins into your app, making it frictionless for users to connect their Telegram identity with your platform. + + +### **Telegram MiniApp EVM Wallet Connection: A Developer's SDK** +In your telegram mini app, you can also use the wallet connection SDK to allow your users to connect with their EVM wallets + +| Name | SDK Doc | +| -------------------------- | ------------------------------------------------------------ | +| OKX Wallet Connection | https://www.okx.com/web3/build/docs/sdks/okx-wallet-integration-introduction | +| Bitget Omni Wallet Connect | https://web3.bitget.com/en/docs/dapp/telegram-webapps-wc.html | + + +### **Embrace the Future of Web3 on Telegram** + +The convergence of BNB Chain and Telegram opens up a world of possibilities. Whether you're a user looking for convenience or a developer building the next big dApp, these Telegram integrations offer a powerful way to engage with the decentralized world. + +**Remember:** Always do your own research and stay informed about the latest developments in the Web3 space! + + + diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.001.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.001.png new file mode 100644 index 0000000000..fccc6127cd Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.001.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.002.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.002.png new file mode 100644 index 0000000000..e13c82182a Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.002.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.003.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.003.png new file mode 100644 index 0000000000..751ccc56b8 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.003.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.004.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.004.png new file mode 100644 index 0000000000..3e242b35ab Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.004.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.005.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.005.png new file mode 100644 index 0000000000..223196476e Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.005.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.006.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.006.png new file mode 100644 index 0000000000..edf5a8d21a Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.006.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.007.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.007.png new file mode 100644 index 0000000000..bee0779be0 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.007.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.008.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.008.png new file mode 100644 index 0000000000..b3f7bdbf24 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.008.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.009.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.009.png new file mode 100644 index 0000000000..92accd699d Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.009.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.010.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.010.png new file mode 100644 index 0000000000..5701857ed0 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.010.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.011.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.011.png new file mode 100644 index 0000000000..70f5471ff2 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 11.011.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.001.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.001.png new file mode 100644 index 0000000000..6d99e3d350 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.001.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.002.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.002.png new file mode 100644 index 0000000000..dfb2f4cc2e Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.002.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.003.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.003.png new file mode 100644 index 0000000000..73578f2829 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.003.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.004.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.004.png new file mode 100644 index 0000000000..0d3ea24561 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.004.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.005.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.005.png new file mode 100644 index 0000000000..a872edb511 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.005.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.006.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.006.png new file mode 100644 index 0000000000..68f3d0e1e7 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.006.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.007.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.007.png new file mode 100644 index 0000000000..5db7b1a578 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.007.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.008.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.008.png new file mode 100644 index 0000000000..5ad8c48f04 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.008.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.009.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.009.png new file mode 100644 index 0000000000..14502be8a3 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.009.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.010.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.010.png new file mode 100644 index 0000000000..c11aad7741 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.010.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.011.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.011.png new file mode 100644 index 0000000000..97ab672f18 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.011.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.012.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.012.png new file mode 100644 index 0000000000..7027b0d954 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.012.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.013.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.013.png new file mode 100644 index 0000000000..65e34f8b6a Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.013.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.014.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.014.png new file mode 100644 index 0000000000..b824d5f2ae Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.014.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.015.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.015.png new file mode 100644 index 0000000000..fb4f180276 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.015.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.016.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.016.png new file mode 100644 index 0000000000..7c2b1bf42e Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.016.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.017.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.017.png new file mode 100644 index 0000000000..1dde151773 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.017.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.018.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.018.png new file mode 100644 index 0000000000..c93cad42c8 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.018.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.019.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.019.png new file mode 100644 index 0000000000..52f8e5c888 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.019.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.020.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.020.png new file mode 100644 index 0000000000..08f57f65ae Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.020.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.021.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.021.png new file mode 100644 index 0000000000..0b2d99c65b Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.021.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.022.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.022.png new file mode 100644 index 0000000000..ad220ef423 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.022.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.023.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.023.png new file mode 100644 index 0000000000..fbaa01c219 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 12.023.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.001.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.001.png new file mode 100644 index 0000000000..8e5bf0ac95 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.001.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.002.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.002.png new file mode 100644 index 0000000000..f5c5dda54c Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.002.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.003.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.003.png new file mode 100644 index 0000000000..bac80ec3ab Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.003.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.004.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.004.png new file mode 100644 index 0000000000..845b3c3b4b Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.004.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.005.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.005.png new file mode 100644 index 0000000000..4fbbb2cd6b Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.005.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.006.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.006.png new file mode 100644 index 0000000000..d424a3b75c Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.006.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.007.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.007.png new file mode 100644 index 0000000000..d560c87eac Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.007.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.008.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.008.png new file mode 100644 index 0000000000..9515c0db8a Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 21.008.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.001.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.001.png new file mode 100644 index 0000000000..8e5bf0ac95 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.001.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.002.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.002.png new file mode 100644 index 0000000000..bdac36fd1d Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.002.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.003.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.003.png new file mode 100644 index 0000000000..989ac74347 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.003.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.004.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.004.png new file mode 100644 index 0000000000..29c6bc9cc5 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.004.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.005.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.005.png new file mode 100644 index 0000000000..a42696af98 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.005.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.006.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.006.png new file mode 100644 index 0000000000..79ebd9fe42 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.006.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.007.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.007.png new file mode 100644 index 0000000000..b4706aade4 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.007.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.008.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.008.png new file mode 100644 index 0000000000..e2b81d3cc3 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.008.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.009.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.009.png new file mode 100644 index 0000000000..329959d681 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 221.009.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.001.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.001.png new file mode 100644 index 0000000000..8fb46f2ca3 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.001.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.002.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.002.png new file mode 100644 index 0000000000..feb1440c93 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.002.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.003.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.003.png new file mode 100644 index 0000000000..3904ad3aca Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.003.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.004.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.004.png new file mode 100644 index 0000000000..1198de52aa Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.004.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.005.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.005.png new file mode 100644 index 0000000000..b97a4f327c Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.005.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.006.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.006.png new file mode 100644 index 0000000000..1dfcdc191c Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.006.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.007.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.007.png new file mode 100644 index 0000000000..d7bd51afc0 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.007.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.008.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.008.png new file mode 100644 index 0000000000..61aaddc47d Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.008.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.009.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.009.png new file mode 100644 index 0000000000..dd0db64ef2 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.009.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.010.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.010.png new file mode 100644 index 0000000000..91deb04478 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.010.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.011.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.011.png new file mode 100644 index 0000000000..68688555a9 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.011.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.012.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.012.png new file mode 100644 index 0000000000..d622864e59 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 222.012.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.001.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.001.png new file mode 100644 index 0000000000..6d99e3d350 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.001.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.002.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.002.png new file mode 100644 index 0000000000..dfb2f4cc2e Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.002.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.003.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.003.png new file mode 100644 index 0000000000..73578f2829 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.003.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.004.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.004.png new file mode 100644 index 0000000000..b723f652dc Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.004.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.005.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.005.png new file mode 100644 index 0000000000..e036a683f2 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.005.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.006.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.006.png new file mode 100644 index 0000000000..1a730fddb5 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.006.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.007.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.007.png new file mode 100644 index 0000000000..ea2c156e47 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.007.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.008.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.008.png new file mode 100644 index 0000000000..edd679c7ab Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.008.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.009.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.009.png new file mode 100644 index 0000000000..a711dd1067 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.009.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.010.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.010.png new file mode 100644 index 0000000000..c11aad7741 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.010.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.011.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.011.png new file mode 100644 index 0000000000..97ab672f18 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.011.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.012.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.012.png new file mode 100644 index 0000000000..7c2b1bf42e Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.012.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.013.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.013.png new file mode 100644 index 0000000000..1dde151773 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.013.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.014.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.014.png new file mode 100644 index 0000000000..c93cad42c8 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.014.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.015.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.015.png new file mode 100644 index 0000000000..52f8e5c888 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.015.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.016.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.016.png new file mode 100644 index 0000000000..08f57f65ae Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.016.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.017.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.017.png new file mode 100644 index 0000000000..3727a292a1 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.017.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.018.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.018.png new file mode 100644 index 0000000000..faea025882 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.018.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.019.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.019.png new file mode 100644 index 0000000000..c93dab5d96 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 3.019.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.001.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.001.png new file mode 100644 index 0000000000..8e5bf0ac95 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.001.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.002.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.002.png new file mode 100644 index 0000000000..2edfa4b317 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.002.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.003.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.003.png new file mode 100644 index 0000000000..067facc169 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.003.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.004.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.004.png new file mode 100644 index 0000000000..8f7363b802 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.004.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.005.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.005.png new file mode 100644 index 0000000000..5a9804dcfd Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.005.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.006.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.006.png new file mode 100644 index 0000000000..6aec751ce2 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.006.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.007.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.007.png new file mode 100644 index 0000000000..6bbce50613 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.007.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.008.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.008.png new file mode 100644 index 0000000000..87b7d41644 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.008.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.009.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.009.png new file mode 100644 index 0000000000..4ec7ca4bc1 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.009.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.010.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.010.png new file mode 100644 index 0000000000..c43838cc33 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.010.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.011.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.011.png new file mode 100644 index 0000000000..21f573fe47 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.011.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.012.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.012.png new file mode 100644 index 0000000000..6f75366050 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.012.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.013.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.013.png new file mode 100644 index 0000000000..33ba84c268 Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.013.png differ diff --git a/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.014.png b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.014.png new file mode 100644 index 0000000000..2d0c1248bd Binary files /dev/null and b/docs/showcase/tokenization/account preparation/Company Tokenization Tutorial 4.014.png differ diff --git a/docs/showcase/tokenization/account-preparation.md b/docs/showcase/tokenization/account-preparation.md new file mode 100644 index 0000000000..b80877c2c4 --- /dev/null +++ b/docs/showcase/tokenization/account-preparation.md @@ -0,0 +1,317 @@ +--- +title: Account Preparation +--- + +Welcome to the BNB Chain Tokenization Tutorial. + +Tokenization is a process by which you create a digital token that can be traded on a blockchain. Tokenization has opened up a new way for businesses to create new revenue streams and help small and medium-sized businesses (SMEs) to access funding and grow their businesses. + +BNB Chain's multi-chain framework, including BSC, opBNB, and Greenfield, offers scalability, low costs, and secure data storage, making it ideal for SMEs to start their tokenization journey. + +There are different sceneraios of tokenization, but in general, you need to prepare a wallet account and buy some crypto before you start create token. + +In this toturial we will focus on the account preparation steps, help you set up your wallet and buy crypto to pay fees. + +## 1 Preparation + +### 1.1 Set Up Wallet + +A Web3 wallet is essential to start your tokenization. You need to confirm the operations as well as pay service fees using the web3 wallet. Also, a web3 wallet account is your identity during the whole process. + +In this guide, we suggest you use Trust Wallet or Metamask to create your first Web3 wallet account: + +- Trust Wallet () +- MetaMask ( ) + +#### 1.1.1 Trust Wallet + +##### Step 1: Install the Wallet Extension + +We suggest you use the Chrome extension to create your wallet, since most of the tokenization tools provide only a desktop version, they cannot be used very well on your mobile phone. + +Follow these steps to get started: + +1) **Download and install Chrome browser** + +Here is the download link: + +- Google Chorme windows 64: + +- Google Chorme windows 32: + +- Google Chorme mac: + + +2) **Visit the Trust Wallet Official Website** + +* Go to the [Trust Wallet](https://trustwallet.com/) website. + +* Click on the “Download” button and choose the extension compatible with Chrome. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 11.001.png) + +3) **Add the Extension**: + +* Click the “Add to Chrome” button and confirm the installation. + +##### Step 2: Create a New Wallet Account + +Once the extension is installed, you need to create a new Trust Wallet account: + +1) **Open the Extension**: Click on the Trust Wallet icon in your browser’s toolbar to open the extension. + +2) **Start Setup**: Click the ‘Get Started’ button to begin, and click on “Create a New Wallet” to set up your wallet. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 11.002.png) + +3) **Set Password**: Pick a password and confirm it to create your account. + +##### Step 3: Backup your Wallet Account + +Backing up your wallet is vital to protect your assets. Click the action bar on the trust wallet interface. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 11.003.png) + +1)**Show Seed Phrase**: Trust Wallet will generate a seed phrase (12 or 24 words) for you. This phrase is crucial for wallet recovery, so click the “Show” button, write it down, and store it securely offline. Do not share this phrase with anyone. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 11.004.png) + +2)**Confirm Seed Phrase**: To ensure you have recorded the seed phrase correctly, Trust Wallet will ask you to confirm it by selecting the words in the correct order. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 11.005.png) + +Once your wallet is set up, you can start using token-issuing tools to create tokens. + +#### 1.1.2 MetaMask + +##### Step 1: Install the Wallet Extension + +1)**Download and install Chrome browser** + +Here is the download link: + +- Google Chorme windows 64: + +- Google Chorme windows 32: + +- Google Chorme mac: + +2)**Add Metamask extension**: + +Visit the Chrome Web store + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 11.006.png) + +Click the “Add to Chrome” button and confirm the installation. + +##### Step 2: Create a New Wallet Account + +Once the extension is installed, you need to create a new MetaMask account: + +1) **Open the Extension**: Click on the MetaMask Wallet icon in your browser’s toolbar to open the extension. + +2) **Start Setup**: Agree on the terms of use, and click on “Create a New Wallet” to set up your wallet. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 11.007.png) + +3) **Set Password**: Pick a password and confirm it to create your account. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 11.008.png) + +##### Step 3: Backup your Wallet Account + +Backing up your wallet is vital to protect your assets. Click on “Secure my wallet” to get your recovery phrase. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 11.009.png) + +1) **Show Seed Phrase**: MetaMask Wallet will generate a seed phrase (12 or 24 words) for you. This phrase is crucial for wallet recovery, so click the “Reveal Secret Recovery Phase” button, write it down, and store it securely offline. Do not share this phrase with anyone. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 11.010.png) + +2) **Confirm Seed Phrase**: To ensure you have recorded the seed phrase correctly, MetaMask Wallet will ask you to confirm it by selecting the words in the correct order. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 11.011.png) + +Once your wallet is set up, you can start buy cryptos. + +### 1.2 Buy Crypto +Tokenization requires service fees, which need to be paid by crypto.You can discover numerous service providers within your wallet. We will instruct you on how to commence purchasing crypto from your Wallet. +In this guide, we suggest you use Trust Wallet or Metamask to start buying crypto: + +- Trust Wallet () +- MetaMask ( ) + +#### 1.2.1 Trust Wallet + +##### Step 1: Login to your wallet + +The Trust Wallet extension allows you to buy crypto using fiat. Follow these steps to get started: + +1) **Open Trust Wallet Extension** + +Click the Trust Wallet Icon in your chrome, and usually, it will open directly. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.001.png) + +2) **Enter Password** + +If you did not login for a while, Trust Wallet might ask you to enter your password to login + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.002.png) + +##### Step 2: Choose network and crypto + +Trust Wallet provides different vendors for you to choose from, you can use them to buy crypto with fiat. + +1) **Click Buy&Sell button** + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.001.png) + +2) **Choose network and crypto** + +Choose BNB on BNB Smart Chain + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.003.png) + +##### Step 3: Choose vender + + Select your vendor. Here we can see Trust Wallet provides several different vendors, we suggest using MoonPay to continue + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 12.004.png) + +##### Step 4: Enter Credit Card Information + +1) **Select Payment Method**: + - Choose “Credit Card” as your payment method. + +2) **Enter Credit Card Details**: + - Fill in your credit card details, including the credit card number, expiration date, CVV code, and billing address. Ensure all information is accurate to avoid payment issues. + +3) **Complete Identity Verification**: + - Depending on MoonPay’s requirements, you may need to complete identity verification, such as uploading identification documents or confirming your identity via SMS verification. + +##### Step 5: Confirm and Complete Purchase + +1) **Review Transaction Details**: + - Carefully review the transaction details, including the purchase amount, wallet address, and payment method. + +2) **Confirm Transaction**: + - Click the “Confirm” or “Complete Purchase” button to finalize the transaction. +![](./company-tokenization-tutorial/Company Tokenization Tutorial 12.006.png) + + +3) **Wait for Transaction Processing**: + - After completing the transaction, you will receive a confirmation email or notification. The purchased BNB will be sent to the wallet address you provided. Processing times may vary depending on network congestion. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 12.007.png) + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 12.008.png) + + +4) **View your BNB in your wallet** + +You can now see your transaction is complete. The BNB should be received by your Trust Wallet. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 12.009.png) + + + +#### 1.2.2 MetaMask + +##### Step 1: Login to your wallet and Add BNB network +The MetaMask Wallet did not set BNB Chain Network as default, so to start, you need to add BNB network. + +1) **Login to your Metamask Wallet** + +Click the MetaMask Icon in your chrome, and usually, it will open directly. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.008.png) + +If you did not login for a while, MetaMask might ask you to enter your password to login + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.009.png) + +Once Login, you need to add BNB Chain Network to your wallet + +2) **Click Add Network** + +Usually you will see you are under Etherum network, click on the Etherum icon and it will guide you to a select network page, if you did not see BNB Chain underneath, click Add network button. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.010.png) + +3) **Add BNB Chain network** + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.011.png) + +4) **Approve to add BNB Chain to your wallet** + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.012.png) + +5) **Switch to BNB chain network** + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.013.png) + +##### Step 2: Choose network and crypto +Metamask provides different vendors for you to choose from, you can use them to buy crypto with fiat. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.014.png) + +1) **Click buy button** + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.008.png) + +2) **Choose network and crypto**, choose BNB chain first, and then select BNB token + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.015.png) + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.016.png) + +##### Step 3: Choose country and fiat + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.017.png) + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.018.png) + +##### Step 4: Choose vender +1) Select your payment method + - We suggest using “Debit or Credit” which has a relatively lower service fee. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.019.png) + +2) Select your vendor. + +- Here we can see MetaMask provides several different vendors, we suggest using MoonPay to continue + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.020.png) + +##### Step 5: Enter Credit Card Information +1) **Select Payment Method**: + + Choose “Credit Card” as your payment method. + +2) **Enter Credit Card Details**: + + Fill in your credit card details, including the credit card number, expiration date, CVV code, and billing address. Ensure all information is accurate to avoid payment issues. + + +3) **Complete Identity Verification**: + +Depending on MoonPay’s requirements, you may need to complete identity verification, such as uploading identification documents or confirming your identity via SMS verification. + +##### Step 6: Confirm and Complete Purchase + +1) **Review Transaction Details**: + + Carefully review the transaction details, including the purchase amount, wallet address, and payment method. + +2) **Confirm Transaction**: + + Click the “Confirm” or “Complete Purchase” button to finalize the transaction. + +3) **Wait for Transaction Processing**: + + After completing the transaction, you will receive a confirmation email or notification. The purchased BNB will be sent to the wallet address you provided. Processing times may vary depending on network congestion. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.022.png) + + diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.001.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.001.png new file mode 100644 index 0000000000..fccc6127cd Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.001.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.002.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.002.png new file mode 100644 index 0000000000..e13c82182a Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.002.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.003.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.003.png new file mode 100644 index 0000000000..751ccc56b8 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.003.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.004.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.004.png new file mode 100644 index 0000000000..3e242b35ab Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.004.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.005.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.005.png new file mode 100644 index 0000000000..223196476e Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.005.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.006.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.006.png new file mode 100644 index 0000000000..edf5a8d21a Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.006.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.007.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.007.png new file mode 100644 index 0000000000..bee0779be0 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.007.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.008.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.008.png new file mode 100644 index 0000000000..b3f7bdbf24 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.008.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.009.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.009.png new file mode 100644 index 0000000000..92accd699d Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.009.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.010.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.010.png new file mode 100644 index 0000000000..5701857ed0 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.010.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.011.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.011.png new file mode 100644 index 0000000000..70f5471ff2 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 11.011.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.001.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.001.png new file mode 100644 index 0000000000..6d99e3d350 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.001.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.002.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.002.png new file mode 100644 index 0000000000..dfb2f4cc2e Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.002.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.003.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.003.png new file mode 100644 index 0000000000..73578f2829 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.003.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.004.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.004.png new file mode 100644 index 0000000000..0d3ea24561 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.004.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.005.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.005.png new file mode 100644 index 0000000000..a872edb511 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.005.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.006.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.006.png new file mode 100644 index 0000000000..68f3d0e1e7 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.006.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.007.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.007.png new file mode 100644 index 0000000000..5db7b1a578 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.007.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.008.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.008.png new file mode 100644 index 0000000000..5ad8c48f04 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.008.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.009.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.009.png new file mode 100644 index 0000000000..14502be8a3 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.009.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.010.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.010.png new file mode 100644 index 0000000000..c11aad7741 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.010.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.011.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.011.png new file mode 100644 index 0000000000..97ab672f18 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.011.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.012.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.012.png new file mode 100644 index 0000000000..7027b0d954 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.012.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.013.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.013.png new file mode 100644 index 0000000000..65e34f8b6a Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.013.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.014.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.014.png new file mode 100644 index 0000000000..b824d5f2ae Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.014.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.015.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.015.png new file mode 100644 index 0000000000..fb4f180276 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.015.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.016.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.016.png new file mode 100644 index 0000000000..7c2b1bf42e Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.016.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.017.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.017.png new file mode 100644 index 0000000000..1dde151773 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.017.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.018.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.018.png new file mode 100644 index 0000000000..c93cad42c8 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.018.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.019.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.019.png new file mode 100644 index 0000000000..52f8e5c888 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.019.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.020.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.020.png new file mode 100644 index 0000000000..08f57f65ae Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.020.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.021.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.021.png new file mode 100644 index 0000000000..0b2d99c65b Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.021.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.022.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.022.png new file mode 100644 index 0000000000..ad220ef423 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.022.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.023.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.023.png new file mode 100644 index 0000000000..fbaa01c219 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 12.023.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.001.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.001.png new file mode 100644 index 0000000000..8e5bf0ac95 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.001.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.002.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.002.png new file mode 100644 index 0000000000..f5c5dda54c Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.002.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.003.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.003.png new file mode 100644 index 0000000000..bac80ec3ab Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.003.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.004.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.004.png new file mode 100644 index 0000000000..845b3c3b4b Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.004.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.005.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.005.png new file mode 100644 index 0000000000..4fbbb2cd6b Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.005.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.006.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.006.png new file mode 100644 index 0000000000..d424a3b75c Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.006.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.007.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.007.png new file mode 100644 index 0000000000..d560c87eac Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.007.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.008.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.008.png new file mode 100644 index 0000000000..9515c0db8a Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 21.008.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.001.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.001.png new file mode 100644 index 0000000000..8e5bf0ac95 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.001.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.002.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.002.png new file mode 100644 index 0000000000..bdac36fd1d Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.002.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.003.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.003.png new file mode 100644 index 0000000000..989ac74347 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.003.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.004.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.004.png new file mode 100644 index 0000000000..29c6bc9cc5 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.004.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.005.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.005.png new file mode 100644 index 0000000000..a42696af98 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.005.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.006.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.006.png new file mode 100644 index 0000000000..79ebd9fe42 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.006.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.007.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.007.png new file mode 100644 index 0000000000..b4706aade4 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.007.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.008.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.008.png new file mode 100644 index 0000000000..e2b81d3cc3 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.008.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.009.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.009.png new file mode 100644 index 0000000000..329959d681 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 221.009.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.001.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.001.png new file mode 100644 index 0000000000..8fb46f2ca3 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.001.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.002.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.002.png new file mode 100644 index 0000000000..feb1440c93 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.002.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.003.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.003.png new file mode 100644 index 0000000000..3904ad3aca Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.003.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.004.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.004.png new file mode 100644 index 0000000000..1198de52aa Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.004.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.005.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.005.png new file mode 100644 index 0000000000..b97a4f327c Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.005.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.006.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.006.png new file mode 100644 index 0000000000..1dfcdc191c Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.006.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.007.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.007.png new file mode 100644 index 0000000000..d7bd51afc0 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.007.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.008.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.008.png new file mode 100644 index 0000000000..61aaddc47d Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.008.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.009.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.009.png new file mode 100644 index 0000000000..dd0db64ef2 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.009.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.010.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.010.png new file mode 100644 index 0000000000..91deb04478 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.010.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.011.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.011.png new file mode 100644 index 0000000000..68688555a9 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.011.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.012.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.012.png new file mode 100644 index 0000000000..d622864e59 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 222.012.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.001.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.001.png new file mode 100644 index 0000000000..6d99e3d350 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.001.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.002.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.002.png new file mode 100644 index 0000000000..dfb2f4cc2e Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.002.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.003.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.003.png new file mode 100644 index 0000000000..73578f2829 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.003.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.004.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.004.png new file mode 100644 index 0000000000..b723f652dc Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.004.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.005.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.005.png new file mode 100644 index 0000000000..e036a683f2 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.005.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.006.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.006.png new file mode 100644 index 0000000000..1a730fddb5 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.006.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.007.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.007.png new file mode 100644 index 0000000000..ea2c156e47 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.007.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.008.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.008.png new file mode 100644 index 0000000000..edd679c7ab Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.008.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.009.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.009.png new file mode 100644 index 0000000000..a711dd1067 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.009.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.010.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.010.png new file mode 100644 index 0000000000..c11aad7741 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.010.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.011.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.011.png new file mode 100644 index 0000000000..97ab672f18 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.011.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.012.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.012.png new file mode 100644 index 0000000000..7c2b1bf42e Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.012.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.013.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.013.png new file mode 100644 index 0000000000..1dde151773 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.013.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.014.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.014.png new file mode 100644 index 0000000000..c93cad42c8 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.014.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.015.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.015.png new file mode 100644 index 0000000000..52f8e5c888 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.015.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.016.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.016.png new file mode 100644 index 0000000000..08f57f65ae Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.016.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.017.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.017.png new file mode 100644 index 0000000000..3727a292a1 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.017.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.018.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.018.png new file mode 100644 index 0000000000..faea025882 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.018.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.019.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.019.png new file mode 100644 index 0000000000..c93dab5d96 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 3.019.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.001.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.001.png new file mode 100644 index 0000000000..8e5bf0ac95 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.001.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.002.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.002.png new file mode 100644 index 0000000000..2edfa4b317 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.002.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.003.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.003.png new file mode 100644 index 0000000000..067facc169 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.003.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.004.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.004.png new file mode 100644 index 0000000000..8f7363b802 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.004.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.005.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.005.png new file mode 100644 index 0000000000..5a9804dcfd Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.005.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.006.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.006.png new file mode 100644 index 0000000000..6aec751ce2 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.006.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.007.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.007.png new file mode 100644 index 0000000000..6bbce50613 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.007.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.008.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.008.png new file mode 100644 index 0000000000..87b7d41644 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.008.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.009.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.009.png new file mode 100644 index 0000000000..4ec7ca4bc1 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.009.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.010.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.010.png new file mode 100644 index 0000000000..c43838cc33 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.010.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.011.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.011.png new file mode 100644 index 0000000000..21f573fe47 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.011.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.012.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.012.png new file mode 100644 index 0000000000..6f75366050 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.012.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.013.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.013.png new file mode 100644 index 0000000000..33ba84c268 Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.013.png differ diff --git a/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.014.png b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.014.png new file mode 100644 index 0000000000..2d0c1248bd Binary files /dev/null and b/docs/showcase/tokenization/company-tokenization-tutorial/Company Tokenization Tutorial 4.014.png differ diff --git a/docs/showcase/tokenization/company-tokenization.md b/docs/showcase/tokenization/company-tokenization.md new file mode 100644 index 0000000000..2e1ac7f72b --- /dev/null +++ b/docs/showcase/tokenization/company-tokenization.md @@ -0,0 +1,753 @@ +--- +title: Showcase - Company Tokenization Tutorial +--- + +Welcome to the BNB Chain Tokenization Tutorial. + +Tokenization is a process by which you create a digital token that can be traded on a blockchain. Tokenization has opened up a new way for businesses to create new revenue streams and help small and medium-sized businesses (SMEs) to access funding and grow their businesses. + +BNB Chain's multi-chain framework, including BSC, opBNB, and Greenfield, offers scalability, low costs, and secure data storage, making it ideal for SMEs to start their tokenization journey. + +It generally takes 4 steps to tokenize your company: + +1) Preparation + + 1. Setup Wallet + 2. Buy Crypto + +2) Token Launch + + 1. Create Token + 2. Presale + +3) Withdrawal + +4) Reward Distribution + +## 1 Preparation + +Go to [Account Preparation Tutorial](./account-preparation.md) to get prepared before starting your tokenization journey. + +## 2 Token Launch + +After all the preparation work, you are now ready to create your token. + +### 2.1 Create Token + +To create a token, you only need to configure a few basic parameters. + +We suggest these two service providers since they provide one-stop service with rich features: + +- PinkSale ( ) +- TokenFi ( ) + +#### 2.1.1 PinkSale + +PinkSale allows you to create a token and manage your token all in one platform, which provides convenience to token issuers. + +##### Step 1: Login with your wallet + +1) **Connect your Wallet** + + Enter , choose “MetaMask” or “Trust Wallet”, use the wallet you just created in chapter 1.1 setup wallet + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 21.001.png) + +##### Step 2: Create Token + +1) **Select Create Token** + + Click Create token on the left navigation bar, you should be able to see the landing page as follow + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 21.002.png) + +2) **Enter Token information** + +Here is how to set each parameter: + +**Chain**: It means the blockchain infrastructure where your token will be created and running all the time. Here we suggest you choose **BNB Chain.** + +**Type**: It means token design mechanism, which contains several parameters, are typically employed to establish the mechanism by which the investors of the token will obtain the financial reward.Here we suggest you choose **Standard.** + +**Name:** This is ideally a human readable name such as "ACE Coffee Coin". + +**Symbol**: The token symbol is comparable to its ticker symbol, typically four or more characters are used such as "ACE". + +**Total supply**: The amount of tokens that get minted at token creation. Usually you will not increase the supply after token creation, so it will be the total supply of your token at all times. The supply is usually determined by the desired token denomination (i.e. the nominal value per token). + +For example, for a bond offering with a nominal amount of USD 10 million and a denomination of USD 100,000 the supply would have to be 100 tokens. + +**Decimals**: Values can be 0-18, when 0 is used, the token is not divisible. We suggest you set it as “**18**”. + +3) **Confirm Transaction** + +Click the create token button then your wallet will be invoked. Confirm with your wallet, please notice you need to pay service fee using BNB, you should follow chapter 1.2 buy crypto to charge your wallet account in advance. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 21.003.png) + +##### Step 3: Check Your Token + +You can see your token address and other basic information as follow + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 21.004.png) + +#### 2.1.2 TokenFi + +##### Step 1: Login with your wallet + +Enter , choose “MetaMask” or “Trust Wallet” + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 21.005.png) + +##### Step 2: Create Token + +**1. Select Token Type**: + +Click the ERC-20 token, you should be able to see the landing page as follow: + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 21.006.png) + +**2. Enter Token information** + +Enter token information recording to your demand + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 21.007.png) + +Here is how to set each parameter: + +**Type**: It means token standard, we suggest you choose **ERC-20**. ERC-20 is a token standard which is most commonly used in company tokenization scenario, you do not need to understand the standard to continue your process, nevertheless, if you want to know more about the token standard, you can visit for more information. + +**Logo**: The image icon of your token, it will show up on all your token promotion pages, we suggest you use images that are highly related to your company’s business so that investors can get more information from your logo image. You should prepare the image beforehand, and make sure that you have the copyright of your image. + +**Name:** This is ideally a human readable name such as "ACE Coffee Coin". + +**Symbol**: The token symbol is comparable to its ticker symbol, typically four or more characters are used such as "ACE". + +**Initial supply**: The amount of tokens that get minted at token creation. It should be no bigger than Max Supply. + +**Max Supply**: The sum up amount of tokens that you will mint all time. We suggest you do not increase the supply after token creation, so the max supply will be set as the same as the initial supply. + +The supply is usually determined by the desired token denomination (i.e. the nominal value per token). + +For example, for a bond offering with a nominal amount of USD 10 million and a denomination of USD 100,000 the supply would have to be 100 tokens. + +**Decimals**: Values can be 0-18, when 0 is used, the token is not divisible.We suggest you set it as **18**. + +**Treasury Wallet:** where the token will be sent to after the tokens are created. It is default set as the wallet address you used to login. Which means all the created tokens will be sent to your current wallet address. + +**Features and tokenomics:** This part is optional advanced features**,** which contains several parameters, are typically employed to establish the mechanism by which the investors of the token will obtain the financial reward.Here we suggest you **skip** this part. If you want to know more about this part, you can visit for more guidance. + + +**3. Confirm Transaction** + +Click the create token button then your wallet will be invoked. Confirm with your wallet, please notice you need to pay service fee using BNB, you should follow chapter 1.2 buy crypto to charge your wallet account in advance. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 21.007.png) + +##### Step 3: Check Your Token + +You can see your token address and other basic information as follow + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 21.008.png) + +### 2.2 Presale + +Now that your token has been created, you can invite your early investors to join your presale activities. Investors can buy your token through the presale link you created, you can quickly raise early-stage funding through pre-sales to develop your business. + +It’s suggested that you use the same service providers to manage your presale. Here we suggest two service providers: + +- PinkSale ( ) +- TokenFi ( ) + +#### 2.2.1 PinkSale + +##### Step 1: Login with your wallet + +Visit and choose “MetaMask” or “Trust Wallet” to login. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 221.001.png) + +##### Step 2: Create Presale + +1) After login, choose launchpad>create presale in left navigation bar. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 221.002.png) + +Here are the parameters you need to input: + +**Address**: Input your token address,if you created your token using PinkSale, it should be filled in automatically. Or you can find it at your token creation page. + +**Currency**:The token you will receive for your presale. Here we suggest you choose **BNB**. + +**Fee Option**: Pinksale will charge your some fees for presale, Here we suggest you to choose **5% BNB**, which means PinkSale will charge 5% of all your BNB sold as Presale service fees + +**Listing Option**:Usually, you need to create a secondary marketplace for your tokens, so that your investors who have bought your tokens during the presale phase can sell the token to others in the secondary market if they do not want to hold the tokens anymore. You will need to add liquidity to the secondary market so that your investors can trade. By adding liquidity, part of your token pair with BNB will be automatically locked so as to be used to add liquidity in the future. Auto listing means liquidity will be added automatically after Finalize, manual listing means you have to add liquidity manually. By selecting auto listing, your token will be listed at PinkSwap automatically.We suggest you choose **Manual listing** to keep it simple. If you want to choose auto listing, you can visit for more guidance. + +**Pool Type:** It means the type of this round of token sale. Here we suggest you to choose **presale** + +**Affiliate**: It indicates that you want to promote your project together with some KOLs Pinksale suggested. We suggest you **disable the Affiliate** program option.If you want to know more about affiliate, you can visit for more guidance. + +2) Review again and click on “Next”. + +##### Step 3: Add Launchpad Info + +After verifying your token, you need to input the Presale information that you want to raise. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 221.003.png) + +Here are some following important parameters: + +**Presale Rate**: This is similar to token price, it means how many of your tokens an investor can receive if he gives 1 BNB. You must use positive numbers. + +**Whitelist:** Choose "Enable" if you have a whitelist of presale contributors. You can enable/disable the whitelist anytime.We suggest you **disable** the whitelist to keep it simple. If you want to know more about affiliate, you can visit for more guidance. + +**Soft cap:** Soft cap means the least amount of tokens you need to sell for this presale to launch successfully. SoftCap must be greater than or equal to 25% of the hard cap. + +**Hard cap**: It means the amount of tokens for your presale. Once you sell the amount of tokens, your presale will automatically stop + +**Refund types:** you can choose refund or burn from the dropdown list. Here we suggest you choose **Refund** + +**Minimum buy BNB:** how many bnb one investor need to pay at least in order to participate + +**Maximum buy BNB:**how many bnb can one investor buy at most + +**Start Time**: the start time of your presale, you can select now or later. + +**End Time**: the end time of your presale. Please make sure the start time is before the end time. + +**Vesting Contributor**: Vesting For Contributors is a feature on PinkSale that helps projects to ensure long term price stability by locking away the tokens of presale investors for a period of time. It prevents presale investors from selling all their tokens at once at listing time, which causes too much sell pressure and crashes the price. To make it simple, we suggest you **disable** it. + +##### Step 4: Add Additional Info + +Now that you have almost setup all the information you need for your presale, we suggest you add some additional info about your project so that your investors can know more about your company, your business, and be more willing to participate in your presale. + + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 221.004.png) + +There are some notes for this step: + +- Logo URL and website are required fields, cannot be blank. You can’t complete this step without those. +- Logo URL must end with a supported image extension: png, jpg, jpeg or gif. + +For example:[ ](https://www.pinkswap.finance/pinkswap.png) + +##### Step 5: Confirm with your wallet + +This is the final step. You can review all the information one last time before submitting, after you have made sure that everything is perfect, or you can go back to the previous step to make any changes. Click “Approve Spending Token” and "Confirm" on Metamask. After that, click "Submit". + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 221.005.png) + +After clicking on “Submit”, MetaMask/TrustWallet will now ask you to confirm the deal. It will also show you the fee that you are required to pay for the presale service. If you agree, then click on the “Confirm” button to finish the process. + +##### Step 6: Check Your Presale Status + +You can view your presale status as follow: + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 221.006.png) + + +##### Step 7: Invite your community to buy + +Guide your community members to [https://www.pinksale.finance/launchpads](https://www.pinksale.finance/#/launchpads) + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 221.007.png) + +Your community members can find your project through searching by token name, they can find the detail page of your presale as follows. Enter the amount of token they want to buy, and confirm with their wallets. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 221.008.png) + +Now that you need to wait for enough community members to buy your token until your soft cap has been reached. Then you can finalized the presale pool. If the hard cap has been reached, your presale will be finalized automatically. + +After you have finalized the presale pool, your community member can claim the token. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 221.009.png) + +After claiming a token, your community member should be able to see the token they bought in their wallet. + +#### 2.2.2 TokenFi + +TokenFi also provides a launchpad for you to create a presale for your tokens. + +##### Step 1: Login to TokenFi Launchpad with your wallet + +Open , Click Connect Wallet to Login + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 222.001.png) + +Sign the message + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 222.002.png) + +##### Step 2: Input token information + +1) Select BNB network + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 222.003.png) + +**2)** Choose “I will provide my own token” and click 'Next' to proceed with your launchpad setup. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 222.004.png) + +3) Input your token address, you can find it at previous steps. + +##### Step 3: Input Presale Information + +1) Define your project’s funding targets by entering the details below: + +**Token Price**: Specify the price per token, e.g. 1 BNB per token. + +**Soft Cap**: Enter the minimum token amount you aim to raise. This is the lowest funding goal required to consider the fundraising a success. + +**Hard Cap**: Set the maximum token amount you wish to raise. This should not exceed the total available supply minus any tokens reserved for the treasury. + +**Available Supply**: Note that the hard cap cannot surpass the available supply of 2500 tokens. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 222.005.png) + +Click the 'Next' button once all fields are filled to continue setting up your project. + +2) Configure your fundraising parameters by following these steps: + +**Maximum Tokens per Wallet**: Input the maximum number of tokens that can be purchased by a single wallet. Ensure this aligns with your fundraising goals and token distribution strategy. + +**Fundraise Start Date**: Choose the date and time when your fundraising will begin. This is the moment from which participants can start purchasing tokens. + +**Fundraise End Date**: Set the date and time when your fundraising will conclude. After this time, no more tokens can be purchased. + +Then click “Next”. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 222.005.png) + +3) Set up your token release schedule efficiently: + +**TGE (Token Generation Event)**: Set the percentage of tokens allocated and the specific date and time for release during the TGE. This initial allocation is crucial for the market introduction of your token. + +**Allocation Percentage**: Input the percentage of total tokens you want to allocate during the TGE. + +**TGE Date**: Select the date and time when these tokens will become available. + +**Allocation Tracker**: Observe the progress bar to ensure your allocations do not exceed the total supply. + +**Add New Release Date**: Click this button to schedule additional token releases, specifying new dates and allocation percentages. + +Click the 'Next' button once all fields are filled to continue setting up your project. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 222.006.png) + +##### Step 4: Review and Confirm with your wallet + +Review each section carefully before proceeding: + +**General Information**: + +- **Blockchain**: The blockchain network selected for the project. + +**Token Information**: + +- **Name**: The official name of your token. + +- **Symbol**: The designated ticker symbol. + +- **Decimals**: The decimal precision for transactions. + +- **Max Supply**: Total number of tokens created. + +- **Reserved for Treasury**: Tokens allocated for future project needs. + +**Goals**: + +- **Price Currency**: The currency used for pricing tokens. + +- **Token Price**: Price per token. + +- **Soft Cap**: Minimum funds targeted. + +- **Hard Cap**: Maximum funds targeted. + +**Fundraising Setup**: + +- **Max Vesting per Wallet**: The maximum token amount a single wallet can hold. + +- **Fundraise Period**: The duration of the fundraising campaign. + +**Release Schedule**: + +Details of token distribution, including percentages and specific dates for each type of vesting. + +**Payment Setup**: + +**Accepted Tokens**: List of cryptocurrencies accepted for payment. + +**Additional Settings**: + +**Blocked Countries**: Countries restricted from participating in the project. + +Once you have confirmed that all details are correct and finalized, press 'Confirm' to launch your project. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 222.007.png) + +This is the final step. You can review all the information one last time before submitting, after you have made sure that everything is perfect, or you can go back to the previous step to make any changes. Click “Approve” and "Confirm" on Metamask. After that, click "Submit". + +##### Step 5: Check Your Presale Status + +On the 'My Projects' screen, find your project and click “View Details” to update and refine your project details. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 222.008.png) + +On the 'Edit Project' screen, follow these steps to update and refine your project details: + +Click “Edit Details”: Begin by accessing the editing mode for your project. + +**Add Launchpad Summary**: Summarize your project to provide a quick overview for potential investors. + +**Link Social Media**: Connect your social media accounts to broaden your reach and engage more effectively with your audience. + +**Input Website and Whitepaper Links**: Provide links to your project's website and Whitepaper, offering deeper insight into your project's objectives and developments. + +**Provide a Detailed Description**: Expand on the details of your project, highlighting key information and unique selling points to attract interest. + +**Save Your Changes**: After updating the information, click 'Save' to apply the changes. Your project is now optimized and ready to attract funding on the TokenFi Launchpad. + + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 222.009.png) + +##### Step 6: Invite your community to buy + +Guide your community members to + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 222.010.png) + +Your community members can find your project through searching by token name, they can find the detail page of your presale as follows. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 222.011.png) + +Your community member can then click “Invest” to go to the Invest page,enter the amount they want to invest on the Invest page and review the transaction details. + +Now that you need to wait for enough community members to buy your token until your soft cap has been reached. Then you can finalized the presale pool. If the hard cap has been reached, your presale will be finalized automatically. + +After you have finalized the presale pool, your community member can claim the token. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 222.012.png) + +After claiming a token, your community member should be able to see the token they bought in their wallet. + +## 3 Withdrawal + +When enough investors purchase your token and your presale succeeded, you will receive an amount of BNB in return. You can exchange your BNB for Fiat, withdraw fiat to your bank account to expand your actual operation or production. + +Service providers you may choose: + +- TrustWallet () +- MetaMask ( ) + +### 3.1 TrustWallet + +##### Step 1: Login + +The Trust Wallet extension allows you to sell BNB to fiat. Follow these steps to get started: + +1) **Open Trust Wallet Extension** + +Click the Trust Wallet Icon in your chrome, and usually, it will open directly. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.001.png) + +2) **Enter Password** + +If you did not login for a while, Trust Wallet might ask you to enter your password to login + + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.002.png) + +##### Step 2: Choose Vendor + +Trust Wallet provides different vendors for you to choose from, you can use them to sell crypto to fiat. + +1) **Click Buy & Sell button** + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.001.png) + +2) **Choose network and crypto** + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.003.png) + +3) **Select your vendor** + +Here we can see Trust Wallet provides several different vendors.we suggest you use moonpay to continue + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.004.png) + +##### Step 3: Login to vender and add your bank account + +1) **Enter your email address** + +2) **Add your bank details** + +![Step 3 on how to sell cryptocurrency.](./company-tokenization-tutorial/Company Tokenization Tutorial 3.005.png) + +3) **Review your order** + +* MoonPay shows you the estimated price for your crypto and a summary of the fees. + +* Accept [Terms of Use](https://www.moonpay.com/legal/terms_of_use). + +* Click “Sell Now” to confirm your order. + +![Step 4 on how to sell cryptocurrency.](./company-tokenization-tutorial/Company Tokenization Tutorial 3.006.png) + +4) **Ready to Pay** + +* Next, MoonPay will generate a wallet for you to send your cryptocurrency to. MoonPay will also email you instructions on how to pay for your order. + +* To see the wallet for your order, tap View deposit details. + +* You can directly copy the deposit wallet address by selecting the "Copy" icon. +![Step 6 on how to sell cryptocurrency.](./company-tokenization-tutorial/Company Tokenization Tutorial 3.007.png) + +##### **Step 4: Send Your Crypto to Vendor** + +1) Open Trust Wallet Extension + +2) Click “Send” + +3) Choose the cryptocurrency (BNB) + +4) Enter the Mercuryo’s Address and the amount you want to sell + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.008.png) + +5) Complete the transaction in your wallet. + +##### Step 5: Check your bank account + +Mercuryo takes your cryptocurrency from there When you send it to the given address. You’ll receive a bank transfer shortly after your cryptocurrency is received. Read the [Processing Time](https://support.moonpay.com/customers/docs/when-will-i-receive-my-cryptocurrency) article to learn how long bank transfers take in different regions. + +Once your transaction is complete, Mercuryo will send you a confirmation email. Click on See complete deposit instructions to access our tracker. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.009.png) + +### 3.2 MetaMask + +##### Step 1: Login + +The MetaMask Wallet extension allows you to sell crypto to fiat. Follow these steps to get started: + +1) **Open Metamask Extension** + +Click the MetaMask Icon in your chrome, and usually, it will open directly. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.010.png) + +2) **Enter Password** + +If you did not login for a while, MetaMask might ask you to enter your password to login + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.011.png) + + +##### Step 2: Choose network and crypto + +Metamask provides different vendors for you to choose from, you can use them to sell crypto to fiat. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.012.png) + +1) **Click buy & sell button,** make sure you are under BNB chain network + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.010.png) + +2) **Choose network and crypto**, choose BNB chain first, and then select BNB token + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.013.png) + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.014.png) + +##### Step 3: Choose your country and fiat + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.015.png) + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.016.png) + +##### Step 4: Choose Vender + +Select your vendor. Here we can see MetaMask provides several different vendors, we suggest using MoonPay to continue + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.017.png) + +##### Step 5: Log in to vender and add your bank account + +1) **Enter your email address** + +2) **Add your bank details** + +![Step 3 on how to sell cryptocurrency.](./company-tokenization-tutorial/Company Tokenization Tutorial 3.005.png) + +3) **Review your order** + +* MoonPay shows you the estimated price for your crypto and a summary of the fees. + +* Accept [Terms of Use](https://www.moonpay.com/legal/terms_of_use). + +* Click “Sell Now” to confirm your order. + +![Step 4 on how to sell cryptocurrency.](./company-tokenization-tutorial/Company Tokenization Tutorial 3.006.png) + +4) **Ready to Pay** + +* Next, MoonPay will generate a wallet for you to send your cryptocurrency to. MoonPay will also email you instructions on how to pay for your order. + +* To see the wallet for your order, tap View deposit details. + +* You can directly copy the deposit wallet address by selecting the "Copy" icon. + +![Step 6 on how to sell cryptocurrency.](./company-tokenization-tutorial/Company Tokenization Tutorial 3.007.png) + +##### Step 6:Send Your Crypto to Vendor + +1) Open Trust Wallet Extension + +2) Click “Send” + +3) Choose the cryptocurrency (BNB) + +4) Enter the MoonPay’s Address and the amount you want to sell + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 3.018.png) + +5)Complete the transaction in your wallet. + +##### Step 7: check your bank account + +1) MoonPay takes your cryptocurrency from there When you send it to the given address. You’ll receive a bank transfer shortly after your cryptocurrency is received. Read the [Processing Time](https://support.moonpay.com/customers/docs/when-will-i-receive-my-cryptocurrency) article to learn how long bank transfers take in different regions. + +2) Once your transaction is complete, MoonPay will send you a confirmation email. Click on See complete deposit instructions to access our tracker. + +![A window that shows the transaction is completed.](./company-tokenization-tutorial/Company Tokenization Tutorial 3.019.png) + +## 4 Reward Distribution + +When your business earns profits, it is crucial to reward your early investors. This creates a sustainable tokenization cycle, enabling you to utilize tokenization again in the future for the growth of your business. + +You can give your investors dividends when your business gets profit through Airdrop tokens. + +Service providers you may choose: + +- Pink Sale ( ) + +#### 4.1 PinkSale + +PinkSale allows you to create airdrop, so that your investors can claim airdrop to get their reward + +##### Step 1: Login with your wallet + +Choose “MetaMask” or “Trust Wallet” + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.001.png) + +##### Step 2: Create New Airdrop + +1) Go to[ ](https://www.pinksale.finance/#/airdrop/create)[https://www.pinksale.finance/airdrop/create](https://www.pinksale.finance/#/airdrop/create) + +2) Paste your token address into the “Token address” section. After that, your token name, symbol and decimals will be shown. Make sure everything is correct and then click on “Next”. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.002.png) + +3) After selecting your token, you will need to input the Airdrop information. + +Here are some following important parameters: + +**Airdrop Title**:Create a meaningful name for your reward distribution. + +**Logo URL**:Logo URL must end with a supported image extension: png, jpg, jpeg or gif. You can upload your image using[ ](https://upload.pinksale.finance/) to get the link to your logo. + +**Website:** Paste your company’s website url here. + +These three parameters cannot be blank. While others like social links and descriptions can be empty. + +Finish all the information, and then click “Create New Airdrop”. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.003.png) + +After clicking on the “Create New Airdrop” button, MetaMask/TrustWallet will now ask you to confirm the transaction. It will also show you the fee that you are required to pay for that transaction. If you agree, then click on the “Confirm” button to finish the process. + +4) You will be redirected to this page: + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.004.png) + +##### Step 3: Set Allocation + +Prepare a list of airdrop addresses then click on “Set Allocations” + +After clicking on “Set Allocations”, you will see a pop-up box. Here, you can add addresses and amounts to your “Users allocation” list. Addresses are separated by a new line. The amount of each user is separated by comma (,) + +You should ask your community members to give you their wallet address beforehand. The below list can be used as an example: + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.005.png) + +Click on “Add Allocations” when you are done inputting the addresses. MetaMask will now ask you to confirm the transaction. It will also show you the fee that you are required to pay for that transaction. If you agree, then click on the “Confirm” button to finish the process. + +After successfully adding airdrop allocations, those allocations will be shown on the airdrop page. + +##### Step 4. Set Vesting + +After clicking on “Set Vesting”, you will see a pop-up box. Below are some important parameters: + +**TGE release percent (%)**: The percentage of the first batch of airdrop tokens to be released. Please note that this is expressed in percentage, not number of tokens. + +**Cycle release percent (%)**: How many % of airdrop tokens will be released each cycle following the first TGE release percent batch. Please note this is expressed in percentage, not in number of tokens. + +**Cycle (days)**: How long, in days, between each batch of vested tokens is released. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.006.png) + +Click on “Set Vesting” when you are done inputting the numbers, then MetaMask will now ask you to confirm the transaction. It will also show you the fee that you are required to pay for that transaction. If you agree, then click on the “Confirm” button to finish the process. + +##### Step 5: Start Airdrop + +1) Before starting the airdrop, you must[ ](https://docs.pinksale.finance/exclude-fees-dividends-max-tx-on-bscscan)[exclude fees, dividends, max tx](https://docs.pinksale.finance/exclude-fees-dividends-max-tx-on-bscscan) for airdrop address. You can find your airdrop address on your airdrop page. Before you finalize your presale, you need to access your contract address from BSCScan or you can click on the token address on your launchpad page. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.007.png) + +2) Go to Contract -> Write contract -> Connect to Web3 to connect your wallet, you need to use owner address. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.008.png) + +3) Ctrl + F, Search “exclude”, then input your presale address, then click on "Write", to exclude all fee/tax, max TX, rewards for presale address. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.007.png) + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.009.png) + +4) After clicking on the “Write” button, MetaMask will now ask you to confirm the transaction. It will also show you the fee that you are required to pay for that transaction. If you agree, then click on the “Confirm” button to finish the process. If you see exclude (bool), please input “true” + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.010.png) + +5) Sometimes contract doesn’t have “exclude” but "exempt" instead, Search “exempt”, then input your presale address, then click on "Write" to exclude all fee/tax, max TX, rewards for presale address. + +6) After you have successfully exclude fees for airdrop address, you can go back to your airdrop page by this link[ ](https://www.pinksale.finance/#/airdrops/own) - Created By You - View Airdrop + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.011.png) + +7) Then click on “Start Airdrop” + +8) You will see how many tokens will be used for airdrop here (total airdrop tokens + 1% fee). Now you can choose to start now: + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.012.png) + +Or start with a specific time like this: + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.013.png) + +10) Click on "Approve", MetaMask will now ask you to confirm the transaction. It will also show you the fee that you are required to pay for that transaction. If you agree, then click on the “Confirm” button to finish the process. + +##### Step 6: Guide your investors to claim airdrop + +You need to guide your community members to claim airdrop so that they can get their reward. + +1) guide your community members to this link[ ](https://www.pinksale.finance/#/airdrops/my) - My Airdrops - View Airdrop. they can see airdrops which they joined here.Please remind them to login with the same wallet address they have shared to you previously. + +![](./company-tokenization-tutorial/Company Tokenization Tutorial 4.014.png) + +2) Check claimable tokens then click on “Claim” + +3) MetaMask/Trust Wallet will now ask you to confirm the transaction. It will also show you the fee that you are required to pay for that transaction. If you agree, then click on the “Confirm” button to finish the process. + diff --git a/docs/showcase/tokenization/index.md b/docs/showcase/tokenization/index.md new file mode 100644 index 0000000000..e11c11e2cd --- /dev/null +++ b/docs/showcase/tokenization/index.md @@ -0,0 +1,40 @@ +--- +hide: +- toc + +title: BNB Chain Tokenization Tutorial +--- + + + +
+
+

BNB Chain Tokenization Tutorial

+

Create token with BNB Chain one-stop tokenization service platforms quickly and easily without coding to help your business growth

+
+
+ + + + diff --git a/docs/showcase/tokenization/introduction.md b/docs/showcase/tokenization/introduction.md new file mode 100644 index 0000000000..a894398a09 --- /dev/null +++ b/docs/showcase/tokenization/introduction.md @@ -0,0 +1,41 @@ + +--- +title: BNB Chain Tokenization Tutorial +description: BNB Greenfield is a decentralized storage and blockchain storage solution that simplifies data management and access while connecting data ownership with the DeFi context of BNB Chain. +keywords: [Tokenization, create token, nft, loyalty program, real world asset, RWA, BNB Chain] +sidebar_label: Tokenization Tutorial +--- + + +# BNB Chain Tokenization Tutorial Overview + +Welcome to the BNB Chain Tokenization Tutorial. + +Tokenization is a process by which you create a digital token that can be traded on a blockchain. Tokenization has opened up a new way for businesses to create new revenue streams and help small and medium-sized businesses (SMEs) to access funding and grow their businesses. + +BNB Chain's multi-chain framework, including BSC, opBNB, and Greenfield, offers scalability, low costs, and secure data storage, making it ideal for SMEs to start their tokenization journey. + + + +## Account Preparation + +There are different sceneraios of tokenization, but in general, you need to prepare a wallet account and buy some crypto before you start create token. +The [Account Preparation Tutorial](./account-preparation.md) will help you get prepared before starting your tokenization journey. + + +## Company Tokenization + +Business Owners can create token to help get their business grow and reward their customers back. +The [Company Tokenization Tutorial](./company-tokenization.md) will help you start with the simplest tokenization in a few minutes with no coding. + + +## Real World Asset(RWAs) + +Real World Assets(RWAs) in crypto involve tokenizing physical assets like real estate, receivables, and loans on blockchain. Tokenizing real-world assets (RWAs) involves converting ownership rights of physical assets into digital tokens on a blockchain. It provides liquidity for your tangible assets and creates better cash flow for you. +The [Real World Assets(RWAs) Tokenization Tutorial](./rwa-tokenization.md) will help you tokenize your real world assets at ease. + + +## NFT Loyalty Programs + +NFT Loyalty Programs based on NFTs can replace traditional paper-based systems and physical membership cards by enhancing user experience and user loyalty. +The [NFT Loyalty Programs Tokenization Tutorial](./nft-loyalty-programs.md) will empower your businesses with NFTs. \ No newline at end of file diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 2.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 2.png new file mode 100644 index 0000000000..21a9948007 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 2.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 3.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 3.png new file mode 100644 index 0000000000..293ebdfdd5 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 3.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 4.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 4.png new file mode 100644 index 0000000000..b7ab7b7231 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 4.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 5.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 5.png new file mode 100644 index 0000000000..71bd295b5e Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 5.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 6.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 6.png new file mode 100644 index 0000000000..85f6775c5c Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 6.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 7.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 7.png new file mode 100644 index 0000000000..cea04d3c28 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 7.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 8.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 8.png new file mode 100644 index 0000000000..284cac4c52 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Create NFT 8.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 2.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 2.png new file mode 100644 index 0000000000..551fd3ce6b Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 2.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 3.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 3.png new file mode 100644 index 0000000000..a041b994cd Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 3.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 4.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 4.png new file mode 100644 index 0000000000..34674087be Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 4.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 5.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 5.png new file mode 100644 index 0000000000..04f317a13c Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 5.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 6.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 6.png new file mode 100644 index 0000000000..957077382a Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 6.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 7.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 7.png new file mode 100644 index 0000000000..4545779464 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 7.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 8.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 8.png new file mode 100644 index 0000000000..d62112e10a Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Add Collection 8.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Verify Contract 1.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Verify Contract 1.png new file mode 100644 index 0000000000..118e98158d Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Verify Contract 1.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Verify Contract 2.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Verify Contract 2.png new file mode 100644 index 0000000000..b7b1c86d5d Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Verify Contract 2.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Verify Contract 3.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Verify Contract 3.png new file mode 100644 index 0000000000..d612dd8953 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Verify Contract 3.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Verify Contract 4.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Verify Contract 4.png new file mode 100644 index 0000000000..2059553aea Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Manage NFT - Verify Contract 4.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 1.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 1.png new file mode 100644 index 0000000000..5ada43aa12 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 1.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 2.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 2.png new file mode 100644 index 0000000000..2cd2a1a00e Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 2.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 3.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 3.png new file mode 100644 index 0000000000..10361e132f Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 3.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 4.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 4.png new file mode 100644 index 0000000000..ae7c47dc15 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 4.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 5.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 5.png new file mode 100644 index 0000000000..b11f825709 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 5.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 6.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 6.png new file mode 100644 index 0000000000..de1f925596 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Mint NFT 6.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/View Minted NFT in Portfolio Tracker 1.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/View Minted NFT in Portfolio Tracker 1.png new file mode 100644 index 0000000000..e071656534 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/View Minted NFT in Portfolio Tracker 1.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/View Minted NFT in Portfolio Tracker 2.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/View Minted NFT in Portfolio Tracker 2.png new file mode 100644 index 0000000000..580c846878 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/View Minted NFT in Portfolio Tracker 2.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 1.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 1.png new file mode 100644 index 0000000000..5671aa62d3 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 1.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 2.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 2.png new file mode 100644 index 0000000000..9d03a63984 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 2.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 3.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 3.png new file mode 100644 index 0000000000..11b7b7622b Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 3.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 4.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 4.png new file mode 100644 index 0000000000..b0bb0fef8d Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 4.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 5.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 5.png new file mode 100644 index 0000000000..8e5581aff3 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/Whitelist Addresses 5.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me01.jpg b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me01.jpg new file mode 100644 index 0000000000..d81a7ac2d1 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me01.jpg differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me02.jpg b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me02.jpg new file mode 100644 index 0000000000..1c664a2150 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me02.jpg differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me03.jpg b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me03.jpg new file mode 100644 index 0000000000..b990993f81 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me03.jpg differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me04.jpg b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me04.jpg new file mode 100644 index 0000000000..4e792b939c Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me04.jpg differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me05.png b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me05.png new file mode 100644 index 0000000000..bc90ea2c9b Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me05.png differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me06.jpg b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me06.jpg new file mode 100644 index 0000000000..ffb2a52823 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me06.jpg differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me07.jpg b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me07.jpg new file mode 100644 index 0000000000..eaac7af97d Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me07.jpg differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me08.jpg b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me08.jpg new file mode 100644 index 0000000000..2510b94938 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me08.jpg differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me09.jpg b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me09.jpg new file mode 100644 index 0000000000..4ebefea943 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me09.jpg differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me10.jpg b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me10.jpg new file mode 100644 index 0000000000..85b0d7ae16 Binary files /dev/null and b/docs/showcase/tokenization/nft-loyalty-programs-tutorial/nfts2me10.jpg differ diff --git a/docs/showcase/tokenization/nft-loyalty-programs.md b/docs/showcase/tokenization/nft-loyalty-programs.md new file mode 100644 index 0000000000..29eab0bdc2 --- /dev/null +++ b/docs/showcase/tokenization/nft-loyalty-programs.md @@ -0,0 +1,239 @@ +--- +title: Showcase - NFT Loyalty Programs Tokenization Tutorial +--- + +NFT Loyalty Programs based on NFTs can replace traditional paper-based systems and physical membership cards by enhancing user experience and user loyalty. + +It generally takes 3 steps to create your NFT loyalty program: + +1) Preparation + + 1. Setup Wallet + 2. Buy Crypto + +2) Create NFT + + +3) Distribute NFT + + +There are plenty of tools and service providers in the BNB Chain ecosystem that can help you with the tokenization journey, we carefully select some of the best in our tutorial to guide you through the Web3 way. You can create your token in a few minutes with no coding or any blockchain knowledge. + +## 1 Preparation + +Go to [Account Preparation Tutorial](./account-preparation.md) to get prepared before starting your tokenization journey. + +## 2 Create NFT + +After all the preparation work, you are now ready to create your NFT. + + +To create a token, you only need to configure a few basic parameters. + +We suggest these two service providers since they provide one-stop service with rich features: + +- NFTs2Me ( ) +- Bitbond ( ) + + +### 2.1 NFTs2Me + + +1) **Connect your Wallet** + +Open NFTs2Me and select the “Connect Wallet” option. +Choose your wallet (e.g., MetaMask). The system will ask you to sign a message to verify account ownership. + +![](./nft-loyalty-programs-tutorial/nfts2me09.jpg) + + +2) **Choose BNB Chain** + +Once your wallet is connected, select the BNB Chain as the network to work on. +Make sure your wallet is on the same network to avoid errors. + +![](./nft-loyalty-programs-tutorial/nfts2me03.jpg) + +3) **Create NFT Project(Edition)** + +Create an edition NFT collection in which only customers selected by the company owner will be able to mint NFTs. + +![](./nft-loyalty-programs-tutorial/nfts2me08.jpg) + +4) **Upload Media and Complete the form** + +Business owners then can create an NFT, and decide the name, and media of the NFT. +Customers can mint the NFT for free to receive a brand-new virtual VIP card in the form of a unique NFT, which they can use to access membership benefits. + +![](./nft-loyalty-programs-tutorial/nfts2me06.jpg) + +Enter the name of the collection (e.g., “ACE Milk Tea VIP Card”), a unique symbol to identify it and enter the descripcion. + +Upload an image or multimedia file to represent the NFT, whether it's an image, GIF, or even a short video. + +Select the initial phase to be Presale so that only customers on the Whitelist can claim their NFT. In addition, you have the option to: +Open the collection to everyone with the Public phase, allowing anyone who knows about the NFT to claim it. +Set different prices for WhiteList users and the general public, rewarding early or loyal supporters with discounts. + + +Click “Deploy to BNB Smart Chain” to deploy the collection to the blockchain, then confirm the transaction in your wallet when prompted. + +4) **Sign with your wallet** + +This confirmation will create a smart contract on BNB Chain containing the entire collection. + +Once the process is complete, a modal window will display all the information about the NFT project, including a link to the minting page and a link to the dashboard for managing the project. In the next step, we will use this dashboard to manage the customer whitelist. + +![](./nft-loyalty-programs-tutorial/nfts2me10.jpg) + + + +### 2.2 Bitbond + + +1) **Connect your Wallet** + +Open Bitbond Token Tool and select the “Connect Wallet” option. +Choose your wallet (e.g., MetaMask). The system will ask you to sign a message to verify account ownership. + +![](./nft-loyalty-programs-tutorial/Create NFT 2.png) + + +2) **Choose BNB Chain** + +Once your wallet is connected, select the BNB Chain as the network to work on. +Make sure your wallet is on the same network to avoid errors. + +![](./nft-loyalty-programs-tutorial/Create NFT 4.png) + +3) **Create NFT Project** + +Business owners then can create an NFT, and decide the name, and media of the NFT. +Customers can mint the NFT for free to receive a brand-new virtual VIP card in the form of a unique NFT, which they can use to access membership benefits. + + +Enter the name of the collection (e.g., “ACE Milk Tea VIP Card”), a unique symbol to identify it and enter the descripcion. +Enable Public Minting + + +![](./nft-loyalty-programs-tutorial/Create NFT 5.png) + +Enter Start and End Time, Enable Whitelist + +![](./nft-loyalty-programs-tutorial/Create NFT 6.png) + + +Click “Confirm” then confirm the transaction in your wallet when prompted. + +![](./nft-loyalty-programs-tutorial/Create NFT 7.png) + +4) **Success** + +This confirmation will create a smart contract on BNB Chain containing the entire collection. You will see the pop up if success. + + +![](./nft-loyalty-programs-tutorial/Create NFT 8.png) + +You can then go to dashboard to manage your NFTs + +![](./nft-loyalty-programs-tutorial/Manage NFT - Add Collection 2.png) + +Add Metadata to your NFTs + +![](./nft-loyalty-programs-tutorial/Manage NFT - Add Collection 3.png) + +Upload media or small video + +![](./nft-loyalty-programs-tutorial/Manage NFT - Add Collection 4.png) + +Enter description + +![](./nft-loyalty-programs-tutorial/Manage NFT - Add Collection 5.png) + +Cofirm to complete + +![](./nft-loyalty-programs-tutorial/Manage NFT - Add Collection 6.png) + + + +## 3 Distribute NFT + +Business owners can invite customers to their NFT airdrop activities by sharing the links. When their customers open the link, they can mint the NFT. + +### 3.1 NFTs2Me + +1) **Whitelist** + +Collect the wallet addresses of customers interested in the airdrop. + +![](./nft-loyalty-programs-tutorial/nfts2me07.jpg) + +2) **Setup whitelist** + +Add these addresses to the NFTs2Me platform to create a whitelist, ensuring that only those on this list can claim the NFTs. + +![](./nft-loyalty-programs-tutorial/nfts2me04.jpg) + + +3) **Mint NFT for free** +Customers can mint NFT when they see the minting page link for free. + +![](./nft-loyalty-programs-tutorial/nfts2me02.jpg) + +Customers will open the minting page and connect their wallet. + +![](./nft-loyalty-programs-tutorial/nfts2me01.jpg) + +Once connected, customers will see the “Mint” button. +By clicking "Mint," a wallet window will appear, prompting the account to confirm the transaction. Once the transaction is successfully completed, the NFT will be transferred to the customer. + + + +### 3.2 Bitbond + +1) **Whitelist** + +Go to dashboard to manage your NFT + +![](./nft-loyalty-programs-tutorial/Manage NFT - Add Collection 2.png) + +2) **Setup whitelist** + +Add these addresses to the platform to create a whitelist, ensuring that only those on this list can claim the NFTs. + +![](./nft-loyalty-programs-tutorial/Whitelist Addresses 1.png) + +3) **Confirm with wallet** + +![](./nft-loyalty-programs-tutorial/Whitelist Addresses 3.png) + +You can see the white list if success + +![](./nft-loyalty-programs-tutorial/Whitelist Addresses 5.png) + +4) **Mint NFT for free** + + +Copy the minting page link here and send it to your NFT buyers so they can mint it in their wallet + +![](./nft-loyalty-programs-tutorial/Mint NFT 1.png) + + +Connect Wallet to login, and if the customer address is in the whitelist, they are able to mint for free + +![](./nft-loyalty-programs-tutorial/Mint NFT 2.png) + +Click Mint NFT to Continue + +![](./nft-loyalty-programs-tutorial/Mint NFT 3.png) + +By clicking "Mint," a wallet window will appear, prompting the account to confirm the transaction. + +![](./nft-loyalty-programs-tutorial/Mint NFT 4.png) + +Once the transaction is successfully completed, the NFT will be transferred to the customer. + +![](./nft-loyalty-programs-tutorial/Mint NFT 5.png) + + +By following these steps, you’ll complete the tokenization process for your business and offer a unique loyalty experience through NFTs. diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.001.jpeg b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.001.jpeg new file mode 100644 index 0000000000..4365012ebe Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.001.jpeg differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.002.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.002.png new file mode 100644 index 0000000000..edf5a8d21a Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.002.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.003.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.003.png new file mode 100644 index 0000000000..bee0779be0 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.003.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.004.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.004.png new file mode 100644 index 0000000000..b3f7bdbf24 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.004.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.005.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.005.png new file mode 100644 index 0000000000..92accd699d Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.005.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.006.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.006.png new file mode 100644 index 0000000000..5701857ed0 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.006.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.007.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.007.png new file mode 100644 index 0000000000..70f5471ff2 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.007.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.008.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.008.png new file mode 100644 index 0000000000..c11aad7741 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.008.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.009.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.009.png new file mode 100644 index 0000000000..97ab672f18 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.009.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.010.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.010.png new file mode 100644 index 0000000000..7027b0d954 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.010.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.011.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.011.png new file mode 100644 index 0000000000..65e34f8b6a Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.011.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.012.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.012.png new file mode 100644 index 0000000000..b824d5f2ae Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.012.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.013.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.013.png new file mode 100644 index 0000000000..fb4f180276 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.013.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.014.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.014.png new file mode 100644 index 0000000000..7c2b1bf42e Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.014.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.015.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.015.png new file mode 100644 index 0000000000..1dde151773 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.015.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.016.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.016.png new file mode 100644 index 0000000000..c93cad42c8 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.016.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.017.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.017.png new file mode 100644 index 0000000000..52f8e5c888 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.017.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.018.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.018.png new file mode 100644 index 0000000000..08f57f65ae Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.018.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.019.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.019.png new file mode 100644 index 0000000000..0b2d99c65b Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.019.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.020.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.020.png new file mode 100644 index 0000000000..ad220ef423 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.020.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.021.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.021.png new file mode 100644 index 0000000000..a872edb511 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.021.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.022.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.022.png new file mode 100644 index 0000000000..fbaa01c219 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.022.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.001.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.001.png new file mode 100644 index 0000000000..de124625d3 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.001.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.002.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.002.png new file mode 100644 index 0000000000..b8c8a58fe2 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.002.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.003.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.003.png new file mode 100644 index 0000000000..f4ab4ba068 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.003.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.004.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.004.png new file mode 100644 index 0000000000..a8955d180e Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.004.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.005.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.005.png new file mode 100644 index 0000000000..3bf146c85d Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.005.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.006.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.006.png new file mode 100644 index 0000000000..3ba566beaf Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.006.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.007.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.007.png new file mode 100644 index 0000000000..a59d0d4e1d Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.007.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.008.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.008.png new file mode 100644 index 0000000000..b2336d49b4 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.008.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.009.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.009.png new file mode 100644 index 0000000000..fc645e8aa3 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.009.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.010.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.010.png new file mode 100644 index 0000000000..cb8a0eb8a8 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.010.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.011.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.011.png new file mode 100644 index 0000000000..82aece0751 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.011.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.012.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.012.png new file mode 100644 index 0000000000..f6308e8476 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.012.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.013.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.013.png new file mode 100644 index 0000000000..32b8760dde Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.013.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.014.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.014.png new file mode 100644 index 0000000000..d9d87cd0d7 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.014.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.015.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.015.png new file mode 100644 index 0000000000..1df55e5bb9 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.015.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.001.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.001.png new file mode 100644 index 0000000000..95f62ce81e Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.001.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.002.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.002.png new file mode 100644 index 0000000000..70f0f88e78 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.002.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.003.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.003.png new file mode 100644 index 0000000000..6673049012 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.003.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.004.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.004.png new file mode 100644 index 0000000000..d133a1a761 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.004.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.005.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.005.png new file mode 100644 index 0000000000..937bab254f Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.005.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.007.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.007.png new file mode 100644 index 0000000000..70fd19c8fc Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.007.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.008.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.008.png new file mode 100644 index 0000000000..eeaabb6655 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.008.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.009.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.009.png new file mode 100644 index 0000000000..c8c3e90027 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.009.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.010.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.010.png new file mode 100644 index 0000000000..be3cfb4808 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.010.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.011.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.011.png new file mode 100644 index 0000000000..aa570ac8f4 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.011.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.012.png b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.012.png new file mode 100644 index 0000000000..8b68ffd120 Binary files /dev/null and b/docs/showcase/tokenization/rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.012.png differ diff --git a/docs/showcase/tokenization/rwa-tokenization.md b/docs/showcase/tokenization/rwa-tokenization.md new file mode 100644 index 0000000000..6514d524ea --- /dev/null +++ b/docs/showcase/tokenization/rwa-tokenization.md @@ -0,0 +1,275 @@ +--- +title: Showcase - RWA Tokenization Tutorial +--- + +Welcome to the BNB Chain Real World Asset Tokenization Tutorial. + +Real World Assets (RWA) in crypto involve tokenizing physical assets like real estate, receivables, and loans on blockchain.Tokenizing real-world assets (RWAs) involves converting ownership rights of physical assets into digital tokens on a blockchain. It provides liquidity for your tangible assets and creates better cash flow for you. + +BNB Chain's multi-chain framework, including BSC, opBNB, and Greenfield, offers scalability, low costs, and secure data storage, making it ideal for Enterprises to start their Real World Asset tokenization journey. + +It generally takes 4 steps to tokenize your real world asset: + +1) Asset Preparation + + 1. Legal structuring + 2. Asset custody + +2) Account Preparation + + 1. Setup Wallet + 2. Buy Crypto + +3) Issue Token + +4) Launch Token + + +There are plenty of tools and service providers in the BNB Chain ecosystem that can help you with the tokenization journey, we carefully select some of the best in our tutorial to guide you through the Web3 way. You can create your token in a few minutes with no coding or any blockchain knowledge. + +## 1 Asset Preparation +### 1.1 Legal Structuring + +The asset tokenization journey begins with identifying an asset with strong tokenization potential, such as real estate, fine arts, commodities, and precious metals. Ensure that the asset is eligible for tokenization and complies with relevant regulations. + +The value of the asset is then carefully assessed and documented, following standard financial practices. + +At this step, a legal framework is established to ensure that digital tokens represent valid claims to the underlying real world assets. This involves defining the specific rights associated with the tokens and choosing an appropriate tokenization structure. ‍ + +Two common tokenization structures for real world assets + +The two common tokenization structures include Tokenized Special Purpose Vehicle (“SPV”) and Direct Asset Tokenization: + +- **Tokenized SPV**: Tokenized SPV approach also known as indirect tokenization is a common approach where the asset is held by an entity, either a private limited company or a trust. This entity is then tokenized, and tokens are issued through a pooling of funds from multiple investors, giving investors indirect interests in the underlying RWA. This is often a better approach as it fits within the securities regulations. +- **Direct Asset Tokenization**: The asset itself is directly tokenized and the tokens represent a direct claim on the underlying asset This approach is typically less common due to regulatory challenges and issues such as non-fungibility, lack of regulatory clarity, and limited use cases. + +Each tokenization structure often comes with different licensing requirements. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.001.jpeg)Suggested Service Provider: [InvestaX](https://www.investax.io/) + +### 1.2 Asset Custody +Before digitalization, the underlying asset (RWA) will be custodized to ensure the asset is immobilized and safe kept before its digital representation is created on the blockchain. Most times if it's a tangible movable RWA like whiskey barrels the RWA is securely stored and managed by qualified custodians, trustees, or licensed managers. + +On the other hand, the digital representation i.e. RWA tokens can be either held in i) Self Custodized or ii) 3rd Party licensed custodian. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 1.001.jpeg) + +**Self-custody** + +Self-custody wallets are wallets used to store digital assets providing users full control over their private keys and, consequently, their assets. It is the practice of individuals taking full control and responsibility for storing and managing their own digital assets without relying on third-party intermediaries. + +With self-custody, users hold their own private keys, which are essential for accessing and transacting with their digital assets. Self-custody wallets, which can be software-based (like mobile or desktop applications) or hardware-based (physical devices), allow users to interact directly with blockchain networks, giving them complete ownership and control over their assets. + +While self-custody offers enhanced security and privacy, it also requires users to be vigilant about safeguarding their private keys and recovery phrases, as there is no central authority to recover lost or stolen assets. + +**Custodizing RWA Tokens with a Licensed 3rd Party Custodian** + +Licensed Custodians are regulated and authorized to provide custody services. These custodians are typically subject to stringent regulatory requirements and oversight, ensuring they adhere to high standards of security, operational integrity, and compliance. By leveraging the services of a licensed digital asset custodian, organizations can mitigate the risks associated with holding and managing digital assets, ensuring they are stored securely and in compliance with relevant regulations. + +Some of the security measures adopted are decentralized security protocols and multi-party computation (MPC) to eliminate single points of failure, thereby enhancing the protection against both external and internal threats. Additionally, custodians often implement multi-signature wallets, hardware security modules (HSMs), and key sharding to further safeguard private keys. These technologies are complemented by rigorous compliance with regulatory standards, such as Know Your Customer (KYC) and anti-money laundering (AML) rules, ensuring that custodians meet stringent reporting, auditing, and fraud detection requirements + +There are many different types of assets in the world and how the custodian is handled and regulated is widely different. The issuers should evaluate the custodian's services, such as asset management, trade processing, and asset servicing, to ensure they meet the needs of the RWA. + +Suggested Service Provider: [InvestaX](https://www.investax.io/) + + +## 2 Account Preparation + +Go to [Account Preparation Tutorial](./account-preparation.md) to get prepared before starting your tokenization journey. + +## 3 Issue Token + +After you have successfully completed the asset preparation and account preparation process, you can finally start creating your RWA token now. Here we recommend these two service providers as they possess a simplistic WebUI and explicit documentation, being friendly for beginners to get acquainted with. + +Service providers you may choose: + +- Bitbond ( ) +- Brikken ( ) + +### 3.1 Brickken + +1) Go to the Token Suite sign up page and sigh up using your email account. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.001.png) + +2) Select the type of financial instrument that the digital asset will represent, Equity, Debt, Invoice Factoring or a Revenue Digitization. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.002.png) + +3) Select a Network, here we suggest you choose Binance Smart Chain(BSC). Once you have selected the BNB Chain, please click continue. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.003.png) + +4) Connect your wallet you have just created in Step 2: Account Preparation. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.004.png) + +5) Complete your KYC steps + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.005.png) + +6) Enter your digital asset information. + +Here are the parameters you need to input: + +**Digital Asset Name**: enter the full name of your digital asset + +**Digital Asset Symbol:** enter the abbreviation of your digital asset + +**Import your Digital Asset Logotype**: Upload the logo of your digital asset + +**Address of the company’s wallet**: To make it simple, you can use the wallet address you just created if you are the business owner. Press the Green Icon to confirm the wallet that will manage the digital asset + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.006.png) + +7) Input your digital asset details + +* If applicable, establish a maximum supply for your digital asset. This will ensure that no additional assets can be created in the future, so as to bring trust to your investors. + +* Upload your digital asset legal documents + +* If you have collected the wallet address of existing shareholders, you can allocate the digital assets to existing shareholders by filling in their wallet address in this step. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.007.png) + +8) Confirm the transaction with your wallet + +Use your wallet to confirm the transaction, you will need to pay gas fee and service fee in this step. After your confirm the transaction, you can see the contract address on BNB Chain. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.008.png) + +9) Mange your token on dashboard + +You can login to Briccken dashboard to manage your token after the creation. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.009.png) + +### 3.2 Bitbond + +1) Visit and connect your wallet to login + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.010.png) + +2) Select BNB Chain network + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.011.png) + +3) Choose Defi Token, enter basic setting information + +Here is how to set each parameter: + +**Name:** This is ideally a human readable name such as "Real World Asset No. 001". + +**Symbol**: The token symbol is comparable to its ticker symbol, typically four or more characters are used such as "RWA1". + +**Initial supply**: The amount of tokens that get minted at token creation. Usually you will not increase the supply after token creation, so it will be the total supply of your token at all times. The supply is usually determined by the desired token denomination (i.e. the nominal value per token). + +For example, for a bond offering with a nominal amount of USD 10 million and a denomination of USD 100,000 the supply would have to be 100 tokens. + +**Decimals**: Values can be 0-18, when 0 is used, the token is not divisible. We suggest you set it as “**18**”. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.012.png) + +4) Set advanced token setting + +To make it simply, here we suggest you use the default setting and do not make any changes. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.013.png) + +5) Confirm the transaction with your wallet + +You might need the pay the gas fee and service fee for the creation. ![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.014.png) + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 2.015.png) + +## 4 Launch Token + +In order to distribute your token toward your investors, you need to launch your token towards open or private market. Here we will guide you how to launch your token. + +Service providers you may choose: + +- Bitbond ( ) +- Brikken ( ) + +### 4.1 Brickken + +1) Login to Brickken dashboard and click my digital asset offering on the left navigation bar + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.001.png) + +2) Setup whitelist + +Approve your preferred investor for your digital asset and whitelist your potential investors on BNB chain by + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.005.png) + +3) Setup token offering informations + +Here are the parameters you need to input: + +**Token Offering Name**: enter token offering name, such as “RWA No. 001 token offering round A” + +**Amount of Tokens to issue:** enter the amount of token you want to offer in this round. + +**Offering Start & End Date:** set up the time schedule of your token offering + +**Min & Max amount to raise in USD:** setup the min the max amount to raise for this round of token offering + +**ERC-20 token accepted:** setup the token type you want to raise, i.e. what token can investors use to purchase your RWA token. Here we suggest you choose USDT. + +**Token Price in USD**: set the token price of your token. + +**Min & Max Investment in USD**: setup the min and max investment for one investor to purchase your token. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.007.png) + +4) Confirm with your wallet + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.003.png) + + +### 4.2 Bitbond + +1) Login to Bitbond Dashboard and click create token sale on the left navigation bar. Enter your token address. If you create your token using Bitbond, you can find it on Bitbond dashboard. + + ![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.012.png) + +2) Setup token sale information + +Here are the parameters you need to input: + +**Payment token:** setup the token type you want to raise, i.e. what token can investors use to purchase your RWA token. Here we suggest you choose BNB. + +**Token Price**: set the token price of your token. + +**Soft & Hard Cap:** only when rich soft cap can the token sale be created. If the hard cap was reached, the token sale will automatically finish. + +**Min & Max Investment amount:** setup the min the max amount for per investor to invest in this round of token offering + +**Offering Start & End Date:** set up the time schedule of your token offering ; + +**Lock duration in days:** setup the lock date which means investors need to wait several days for the token to be accepted after their investment. + +**Token Sale Owner:** please enter the account of your wallet if you are the business owner + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.004.png) + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.002.png) + +3) Confirm with your wallet + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.011.png) + +4) Setup white list + +After your token sale have been created, you can mange your whitelist of your investors in the dashboard + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.008.png) + +Enter the address of your investors and confirm with your wallet + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.010.png) + +Your whitelist has been successfully set up. + +![](./rwa-tokenization-tutorial/RWA Tokenization Tutorial 3.009.png) diff --git a/mkdocs.yml b/mkdocs.yml index a98f439635..b264939ca4 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -62,9 +62,11 @@ nav: - Announcements: - Announcements: ./announce/index.md - Upcoming: - - Bohr Hardfork(BSC): ./announce/bohr-bsc.md - - Wright Hardfork(opBNB): ./announce/wright-opbnb.md + - Greenfield Savanna Hardfork: ./announce/savanna-greenfield.md + - Passed: + - Fjord Hardfork(opBNB): ./announce/fjord-opbnb.md + - Wright Hardfork(opBNB): ./announce/wright-opbnb.md - Mongolian Hardfork(Greenfield): ./announce/mongolian-greenfield.md - Veld Hardfork(Greenfield): ./announce/veld-greenfield.md - Second Sunset Hardfork(BC): ./announce/second-sunset-bc.md @@ -74,38 +76,9 @@ nav: - Haber Hardfork(opBNB): ./announce/haber-opbnb.md - Second Sunset Hardfork(BC testnet): ./announce/second-sunset-bc-testnet.md - Final Sunset Hardfork(BC testnet): ./announce/final-sunset-bc-testnet.md - - - BNB Chain Fusion: - - BNB Chain Fusion: ./bc-fusion/index.md - - Overview: ./bc-fusion/overview.md - - Post Fustion: - - Merkle Proof Verification: ./bc-fusion/post-fusion/merkle-tree-verify.md - - Token Recovery: ./bc-fusion/post-fusion/token-recovery.md - - FAQ: ./bc-fusion/post-fusion/faq.md - - For Users: - - Manage Your Assets: ./bc-fusion/users/assets.md - - Manage Your Atomic Swaps: ./bc-fusion/users/swaps.md - - Manage Your TimeLocks: ./bc-fusion/users/timelocks.md - - Manage Your Old Delegations: ./bc-fusion/users/stake-migration.md - - BEP153 and LSD Stake Migration: ./bc-fusion/users/bep153-stake-migration.md - - Manage Your New Delegations: ./bc-fusion/users/new-stake.md - - Participate in Governance: ./bc-fusion/users/gov.md - - For Token Issuers: - - Bind Your Tokens: ./bc-fusion/owners/bind.md - - Cross Chain Liquidity Check and Repair: ./bc-fusion/owners/liquidity-check.md - - For Validators: - - Create New Validators: ./bc-fusion/validators/creation.md - - Migrate Your Validators: ./bc-fusion/validators/migrations.md - - Key Management: ./bc-fusion/validators/key-management.md - - For Developers: - - New Staking: ./bc-fusion/developers/staking.md - - New Governance: ./bc-fusion/developers/gov.md - - Cross Chain Redelegation: ./bc-fusion/developers/crosschain-redelegation.md - - Build-in System Contracts: ./bc-fusion/developers/system-contracts.md - - Native Staking & Governance: - - Staking: ./bc-fusion/validators/staking.md - - Slash: ./bc-fusion/validators/slash.md - - Governance: ./bc-fusion/validators/gov.md + - Bohr Hardfork(BSC): ./announce/bohr-bsc.md + - Altai Hardfork(Gnfd): ./announce/altai-gnfd.md + - Final Sunset of BC (Mainnet): ./announce/final-sunset-bc-mainnet.md - BNB Smart Chain: - BNB Smart Chain: ./bnb-smart-chain/index.md - Overview: ./bnb-smart-chain/overview.md @@ -114,22 +87,28 @@ nav: - Developers: - Quick Guide: ./bnb-smart-chain/developers/quick-guide.md - Dev-Tools: https://www.bnbchain.org/en/dev-tools - - RPC: ./bnb-smart-chain/developers/rpc.md + - JSON-RPC: + - Json Rpc Endpoint: ./bnb-smart-chain/developers/json_rpc/json-rpc-endpoint.md + - Bsc Api list: ./bnb-smart-chain/developers/json_rpc/bsc-api-list.md - Faucet: ./bnb-smart-chain/developers/faucet.md - Node Operators: - Node Best Practices: ./bnb-smart-chain/developers/node_operators/node_best_practices.md - - Full Node: ./bnb-smart-chain/developers/node_operators/full_node.md - - Archive Node: ./bnb-smart-chain/developers/node_operators/archive_node.md - - Fast Node: ./bnb-smart-chain/developers/node_operators/fast_node.md - - Reth Node: ./bnb-smart-chain/developers/node_operators/reth_node.md - - Boot Node: ./bnb-smart-chain/developers/node_operators/boot_node.md - - Docker Image: ./bnb-smart-chain/developers/node_operators/docker.md - - Upgrade Geth: ./bnb-smart-chain/developers/node_operators/upgrade_geth.md - - Node Maintenance: ./bnb-smart-chain/developers/node_operators/node_maintenance.md + - Node Types: + - Full Node: ./bnb-smart-chain/developers/node_operators/full_node.md + - Archive Node: ./bnb-smart-chain/developers/node_operators/archive_node.md + - Fast Node: ./bnb-smart-chain/developers/node_operators/fast_node.md + - Insfrastructure & Setup: + - Boot Node: ./bnb-smart-chain/developers/node_operators/boot_node.md + - Docker Image: ./bnb-smart-chain/developers/node_operators/docker.md + - Maintenance & Upgrades: + - Upgrade Geth: ./bnb-smart-chain/developers/node_operators/upgrade_geth.md + - Node Maintenance: ./bnb-smart-chain/developers/node_operators/node_maintenance.md - EOA Paymaster: - Overview: ./bnb-smart-chain/developers/paymaster/overview.md - Paymaster API Spec: ./bnb-smart-chain/developers/paymaster/paymaster-api.md - Wallet Integration: ./bnb-smart-chain/developers/paymaster/wallet-integration.md + - Try Gasless Transaction: ./bnb-smart-chain/developers/paymaster/wallet-demo.md + - Staking: - Overview: ./bnb-smart-chain/staking/overview.md - User Guide: ./bnb-smart-chain/staking/user-guide.md @@ -137,6 +116,7 @@ nav: - Governance: - Overview: ./bnb-smart-chain/governance/overview.md - User Guide: ./bnb-smart-chain/governance/user-guide.md + - BNB Advocate`s Guide : ./bnb-smart-chain/governance/bnb-kol.md - Temperature Check: ./bnb-smart-chain/governance/temp-check.md - Governance APIs: ./bnb-smart-chain/governance/apis.md - Validator: @@ -149,6 +129,7 @@ nav: - Overview: ./bnb-smart-chain/validator/mev/overview.md - Validator Guide: ./bnb-smart-chain/validator/mev/validator-integration.md - Builder Guide: ./bnb-smart-chain/validator/mev/builder-integration.md + - User Guide: ./bnb-smart-chain/validator/mev/user-guide.md - FAQs: ./bnb-smart-chain/validator/mev/faqs.md - Slashing: - Overview: ./bnb-smart-chain/slashing/overview.md @@ -303,12 +284,24 @@ nav: - Attestation: - BNB Attestation Service: ./showcase/identity/attestation.md - Build your Attestation: ./showcase/identity/attestation-dev.md - - Games: - - Telegram Mini Game on BNB Chain: ./showcase/game/minigame.md + - Telegram Integration: + - Telegram Mini Game on BNB Chain: ./showcase/telegram/minigame.md + - Telegram Wallets: ./showcase/telegram/wallets.md - Wallet: - In-app Wallet and Account Abstraction: ./showcase/wallet/in-app-wallet.md - - + - Tokenization: + - Introduction: ./showcase/tokenization/introduction.md + - Account Preparation: ./showcase/tokenization/account-preparation.md + - Company Tokenization Tutorial: ./showcase/tokenization/company-tokenization.md + - RWA Tokenization Tutorial: ./showcase/tokenization/rwa-tokenization.md + - NFT Loyalty Program Tutorial: ./showcase/tokenization/nft-loyalty-programs.md + - BNB Chain Fusion: + - BNB Chain Fusion: ./bc-fusion/index.md + - Overview: ./bc-fusion/overview.md + - Post Fustion: + - Merkle Proof Verification: ./bc-fusion/post-fusion/merkle-tree-verify.md + - Token Recovery: ./bc-fusion/post-fusion/token-recovery.md + - FAQ: ./bc-fusion/post-fusion/faq.md markdown_extensions: - toc: diff --git a/overrides/main.html b/overrides/main.html index 06b6f9dac7..31fbc2c521 100644 --- a/overrides/main.html +++ b/overrides/main.html @@ -1,11 +1,12 @@ {% extends "base.html" %} +{# {% block announce %}
- BNB Beacon Chain is sunsetting. Check for - more details + announcement goes here
{% endblock %} +#} {% block htmltitle %} {% if page.meta and page.meta.title %}