-
Notifications
You must be signed in to change notification settings - Fork 30
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update g_multiSignature_dapp_Guide.md
- Loading branch information
Showing
1 changed file
with
41 additions
and
48 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,87 +1,80 @@ | ||
| # NULS Multi-Sign DApp Guide | ||
| # NULS Multi-Sign DApp Guide | ||
|
|
||
| ## What is multi-sign? | ||
| ## What is Multi-Sign? | ||
|
|
||
| Multi-signature, also known as multisigi, which is a digital signature that allows multiple users to sign one transaction. To address in a simpler way, an account that is owned, managed, signed by more than one party. | ||
| Multi-Signature, also known as Multi-Sign, is a digital signature that allows multiple users to sign a single transaction. In simpler terms, it refers to an account owned, managed, and signed by more than one party. | ||
|
|
||
| In most cases, there is only one private key that manages a single account, which we call it 1/1. Multisig is different,it goes m/n, “n” refers to the amount of private keys that are authorized to sign for the account, transactions only take effect when the number of signatures reaches to “m”. In this case, “m” must be less than or equal to “n”. | ||
| In traditional cases, a single private key manages a single account, denoted as 1/1. Multi-Sign is different; it's represented as m/n, where "n" is the number of authorized private keys to sign for the account, and transactions are only effective when the number of signatures reaches "m". Here, "m" must be less than or equal to "n". | ||
|
|
||
| ## How is Multi-Sign Applied? | ||
|
|
||
| ## How is multisig applied in cases | ||
| Multi-Signature finds application in various areas of account authority management. Examples include: | ||
|
|
||
| Multi-signature has many uses in account authority management | ||
| For example: | ||
| - **Assets Management:** Multi-Sign greatly enhances security by allowing multiple individuals to manage a single account using different private keys, reducing the risk of asset attacks. | ||
|
|
||
| * Assets management:. Multi-sigi greatly enhances security level by allowing multiple people managing one account using different private keys, which lowers the risks of assets being attacked. | ||
| - **Account Recovery:** By managing an account with Multi-Signatures, even if one signatory loses their private key, the others can still access the account protected by multi-sig. | ||
|
|
||
| * By managing one account with multi-signatures, even if one of the signatories lost the private key, the rest of them can still get access to the account that is being protected by multi-sig. | ||
| - **Department Authorization:** Certain matters require approval and signatures from multiple departments before taking effect, providing transparency and traceability to all parties. | ||
|
|
||
| * Department Authorization; A matter that must be approved and signed by multiple departments before it takes effects. Every signature can be traced and it is transparent to all parties. | ||
| ## Supported Assets | ||
|
|
||
| ## Assets that supported | ||
| Our multi-sig is available as a DApp, compatible with the NULS and NerveNetwork blockchains. The DApp can manage assets on NULS and Nerve mainnets, as well as assets bridged from Ethereum, Polygon, Arbitrum, BSC, Heco, OEC, Cronos, and other blockchains to NULS through NerveBridge (currently excluding NRC20 assets). | ||
|
|
||
|
|
||
| Our multi-sig comes as a DApp, which is compatible to NULS and NerveNetwork blockchain The DApp can be used to manage NULS and Nerve mainnet asset and assets bridged from Ethereum/Polygon/Arbitrum/BSC/Heco/OEC/Cronos and other blockchains to NULS through NerveNridge(currently not supports NRC20 assets ) | ||
|
|
||
| ## A quick starter on Multisig DApp | ||
|
|
||
| How to use Multi-sig DApp in NULS network | ||
| ## Quick Starter on Multi-Sign DApp | ||
|
|
||
| ### Connect Wallet | ||
| To get access to [multi-sig](https://sign.nuls.io)，connect wallet by Nabox or Metamask. | ||
| Click & [Down extension wallet](https://chrome.google.com/webstore/detail/nabox-wallet/nknhiehlklippafakaeklbeglecifhad?hl=zh-CN&authuser=2) | ||
|
|
||
|  | ||
| To access [ Multi-Sign DApp](https://sign.nuls.io), connect your wallet through Nabox or Metamask. Click to [Download Nabox Wallet](https://nabox.io/) | ||
|
|
||
| After successfully connecting to the wallet, click【Generate multi-chain address】to sign up, this will automatically generate a NULS address and a Nerve address and directly lead you to the operation UI. Our multi-sig DApp is enabled with the following functions. | ||
|  | ||
|
|
||
| - Create Multisig account address | ||
| - Create Multi-sig transactions | ||
| - Signning | ||
| After connecting the wallet successfully, click **Generate multi-chain address** to sign up. This will automatically generate a NULS address and a Nerve address, leading you to the operation UI. The multi-sig DApp includes the following functions: | ||
|
|
||
| - Create Multi-Sign account address | ||
| - Create Multi-Sign transactions | ||
| - Signing | ||
|
|
||
| ### Create Multi-sig account address | ||
| ### Create Multi-Sign Account Address | ||
|
|
||
| A multi-sig account address is required, before you can use the multi-sig DApp. | ||
| A multi-sig account address is required before using the multi-sig DApp. | ||
|
|
||
| - Input public keys in the first box and separate them with dots, the system will automatically identify every public key. | ||
| - Input private key one by one, click “+” to add more. | ||
| - Input public keys in the first box, separating them with dots. The system will automatically identify each public key. | ||
| - Input private keys one by one and click “+” to add more. | ||
|
|
||
| After submitting public keys, you will need to select a number of the minimal signatures. Minimal signatures set a minimal number of accounts used to confirm a multisig transaction. For example, if a multisig account is managed by 3 people, the minimal signatures number is 2, which is to say, confirmations from 2 people are required to enable a transaction. Otherwise the transation would fail | ||
| After submitting public keys, select the minimum number of signatures required. This sets the minimal number of accounts needed to confirm a Multi-Sign transaction. For example, if a Multi-Sign account is managed by 3 people, the minimum signatures number is 2, meaning confirmations from 2 people are required to enable a transaction. Otherwise, the transaction would fail. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| After submitting information, click “Generate address” to create a multisig account address | ||
| After submitting information, click **Generate address** to create a Multi-Sign account address. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| ### Create Multisig Transactions | ||
| ### Create Multi-Sign Transactions | ||
|
|
||
| To create a multisig transaction, users need to select a multisig address that starts the transactions. | ||
| To create a Multi-Sign transaction, users need to select a Multi-Sign address to initiate the transaction. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| Select assets that you want to transfer - select amount of transfer and receiving address - create transaction | ||
| Select the assets you want to transfer, specify the amount, and enter the receiving address. Then, create the transaction. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| After creating the transaction, a multisig HEX will be generated. Copy the HEX and send it to the other signers to confirm. | ||
| After creating the transaction, a Multi-Sign HEX will be generated. Copy the HEX and send it to other signers for confirmation. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| ### Signatures | ||
|
|
||
| Signature function The user will sign the received multi-signature transaction HEX, and the user's role at this time is one of the signers. The user pastes the received HEX into the input box, and the tool will automatically parse the data of the multi-signature transaction and display it. | ||
| ### Signatures | ||
|
|
||
| Note: After the first signer completes the signature, a new HEX will be generated, the second signer will copy the new HEX and so on | ||
| The user will sign the received Multi-Signature transaction HEX, acting as one of the signers. Paste the received HEX into the input box, and the tool will automatically parse the data of the Multi-Signature transaction. | ||
|
|
||
| Note: After the first signer completes the signature, a new HEX will be generated. The second signer will copy the new HEX, and so on. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| After transaction is parsed, you will be able to check the status of transaction based on the information of “signed quality” and “signature still required” | ||
| After parsing the transaction, check the status based on the information of "signed quantity" and "signatures still required." | ||
|
|
||
|  | ||
|  | ||
|
|
||
| If the current signer is the last signer that is authorized to sign the transaction (For example, if a transaction that requires two signers has already been signed once and it is being signed now, this makes the current signer the second/last signer). After all signatures are completed, the transaction will be broadcasted in the blockchain and will be confirmed in few minutes) | ||
| If the current signer is the last authorized to sign the transaction, and after all signatures are completed, the transaction will be broadcasted on the blockchain and confirmed in a few minutes. | ||
|
|
||
|  | ||
|  |