Add clean support for multiple transaction signatures (#11)

* Revamp all tools to allow tx multiple signatures

* Update documentation

Author: Fabrice Bascoulergue

CONTRIBUTING.md

@@ -1,7 +1,7 @@
 # Contributing
 
 When contributing to this repository, please first discuss the change you wish to make via issue,
-email, or any other method with the owners of this repository before making a change. 
+email, or any other method with the owners of this repository before making a change.
 
 Please note we have a code of conduct, please follow it in all your interactions with the project.
 
@@ -10,7 +10,7 @@ Please note we have a code of conduct, please follow it in all your interactions
 1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
 2. Update the README.md with details of changes to the interface, this includes new environment variables, exposed ports, useful file locations and container parameters.
 3. Increase the version numbers in any examples files and the README.md to the new version that this Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
-4. You may merge the Pull Request in once you have the approval of one core team member, or if you  do not have permission to do that, you may request a reviewer to merge it for you.
+4. You may merge the Pull Request in once you have the approval of one core team member, or if you do not have permission to do that, you may request a reviewer to merge it for you.
 
 ## Code of Conduct
 
@@ -25,19 +25,19 @@ nationality, personal appearance, race, religion, or sexual identity and orienta
 Examples of behavior that contributes to creating a positive environment
 include:
 
-* Using welcoming language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+-   Using welcoming language
+-   Being respectful of differing viewpoints and experiences
+-   Gracefully accepting constructive criticism
+-   Focusing on what is best for the community
+-   Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
+-   The use of sexualized language or imagery and unwelcome sexual attention or advances
+-   Trolling, insulting/derogatory comments, and personal or political attacks
+-   Public or private harassment
+-   Publishing others' private information, such as a physical or electronic address, without explicit permission
+-   Other conduct which could reasonably be considered inappropriate in a professional setting
 
 ### Our Responsibilities
 
@@ -50,14 +50,14 @@ threatening, offensive, or harmful.
 
 ### Scope
 
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. 
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
 Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. 
+representative at an online or offline event.
 Representation of a project may be further defined and clarified by project maintainers.
 
 ### Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at contact [ at ] lum.network. 
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at contact [ at ] lum.network.
 All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances.
 The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
 Further details of specific enforcement policies may be posted separately.
@@ -70,4 +70,4 @@ members of the project's leadership.
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
 
 [homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+[version]: http://contributor-covenant.org/version/1/4/

docs/README.md

@@ -158,12 +158,15 @@ const fee = {
 const account = await testnetClient.getAccount(wallet.getAddress());
 // Create the transaction document
 const doc = {
-    accountNumber: account.accountNumber,
     chainId,
     fee: fee,
     memo: 'my transaction memo',
     messages: [sendMsg],
-    sequence: account.sequence,
+    signers: [{
+        accountNumber: account.accountNumber,
+        sequence: account.sequence,
+        publicKey: wallet.getPublicKey(),
+    }],
 };
 // Sign and broadcast the transaction using the client
 const broadcastResult = await clt.signAndBroadcastTx(w1, doc);

docs/lib/classes/lumclient.md

@@ -285,15 +285,15 @@ ___
 
 ### signAndBroadcastTx
 
-▸ **signAndBroadcastTx**(`wallet`: [*LumWallet*](lumwallet.md), `doc`: [*Doc*](../interfaces/lumtypes.doc.md)): *Promise*<BroadcastTxCommitResponse\>
+▸ **signAndBroadcastTx**(`wallet`: [*LumWallet*](lumwallet.md) \| [*LumWallet*](lumwallet.md)[], `doc`: [*Doc*](../interfaces/lumtypes.doc.md)): *Promise*<BroadcastTxCommitResponse\>
 
 Signs and broadcast the transaction using the specified wallet and messages
 
 #### Parameters:
 
 Name | Type | Description |
 :------ | :------ | :------ |
-`wallet` | [*LumWallet*](lumwallet.md) | signing wallet   |
+`wallet` | [*LumWallet*](lumwallet.md) \| [*LumWallet*](lumwallet.md)[] | signing wallet or wallets for multi signature   |
 `doc` | [*Doc*](../interfaces/lumtypes.doc.md) | document to sign and broadcast as a transaction    |
 
 **Returns:** *Promise*<BroadcastTxCommitResponse\>
@@ -302,15 +302,15 @@ ___
 
 ### signTx
 
-▸ **signTx**(`wallet`: [*LumWallet*](lumwallet.md), `doc`: [*Doc*](../interfaces/lumtypes.doc.md)): *Promise*<Uint8Array\>
+▸ **signTx**(`wallet`: [*LumWallet*](lumwallet.md) \| [*LumWallet*](lumwallet.md)[], `doc`: [*Doc*](../interfaces/lumtypes.doc.md)): *Promise*<Uint8Array\>
 
 Signs the messages using the provided wallet and builds the transaction
 
 #### Parameters:
 
 Name | Type | Description |
 :------ | :------ | :------ |
-`wallet` | [*LumWallet*](lumwallet.md) | signing wallet   |
+`wallet` | [*LumWallet*](lumwallet.md) \| [*LumWallet*](lumwallet.md)[] | signing wallet or wallets for multi signature   |
 `doc` | [*Doc*](../interfaces/lumtypes.doc.md) | document to sign    |
 
 **Returns:** *Promise*<Uint8Array\>

docs/lib/classes/lumpaperwallet.md

@@ -67,7 +67,7 @@ ___
 
 ### privateKey
 
-• `Private` `Optional` **privateKey**: *undefined* \| *Uint8Array*
+• `Optional` **privateKey**: *undefined* \| *Uint8Array*
 
 ___