Skip to content
This repository was archived by the owner on Jan 13, 2023. It is now read-only.

Commit 1056793

Browse files
committed
extended Generating multisignature address chapter
1 parent 0d21e45 commit 1056793

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

docs/multisig.rst

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,13 @@ Generating multisignature address
1414

1515
In order to use multisignature functionality, a special multisignature address must be created. It is done by adding each key digest in agreed order into digests list. At the end, last participant is converting digests list (Curl state trits) into multisignature address.
1616

17-
Here is the example where digest is created:
17+
.. note::
18+
19+
Each multisignature addresses participant has to create its own digest locally. Then, when it is created it can be safely shared with other participants, in order to build list of digests which then will be converted into multisignature address.
20+
21+
Created digests should be shared with each multisignature participant, so each one of them could regenerate address and ensure it is OK.
22+
23+
Here is the examples where digest is created:
1824

1925
.. code-block:: python
2026
@@ -47,6 +53,11 @@ And here is example where digests are converted into multisignature address:
4753
# has a single value.
4854
multisig_address = cma_result['address'] # type: MultisigAddress
4955
56+
.. note::
57+
58+
As you can see in above example, multisignature addresses is created from list of digests, and in this case **order** is important. The same order need to be used in **signing transfer**.
59+
60+
5061

5162

5263
Prepare transfer

0 commit comments

Comments
 (0)