From 0244f5d26e9df102f8f53eb36c892fd86510373d Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Mon, 13 Jun 2016 18:38:06 -0700 Subject: [PATCH] rebuild multisign html --- tutorial-multisign.html | 60 +++-------------------------------------- 1 file changed, 3 insertions(+), 57 deletions(-) diff --git a/tutorial-multisign.html b/tutorial-multisign.html index 6d5bb3a902..79dfdcebe3 100644 --- a/tutorial-multisign.html +++ b/tutorial-multisign.html @@ -215,25 +215,7 @@ Connecting to 127.0.0.1:5005

3. Send SignerListSet transaction

Sign and submit a SignerListSet transaction in the normal (single-signature) way. This associates a SignerList with your Ripple address, so that a combination of signatures from the members of that SignerList can multi-sign later transactions on your behalf.

In this example, the SignerList has 3 members, with the weights and quorum set up such that multi-signed transactions need a signature from rsA2LpzuawewSBQXkiju3YQTMzW13pAAdW plus at least one signature from the other two members of the list.

-

<<<<<<< HEAD -Caution: Never submit a secret key to a server you do not control. Do not send a secret key unencrypted over the network. -======= -Caution: Never submit a secret key to a server you do not control. Do not send a secret key unencrypted over the network.

-
-
-
-
-
-
-
-

callouts

-
-
-
-
-
-
-
+

Caution: Never submit a secret key to a server you do not control. Do not send a secret key unencrypted over the network.

$ rippled submit shqZZy2Rzs9ZqWTCQAdqc3bKgxnYq '{
 >     "Flags": 0,
 >     "TransactionType": "SignerListSet",
@@ -397,25 +379,7 @@ Connecting to 127.0.0.1:5005
 
(This transaction creates an accounting relationship from rEuLyBCvcw4CFmzv8RepSiAoNgF8tTGJQC to rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh with a maximum balance of 100 USD.)

 
2. Get one signature

 
Use the sign_for command with the secret key and address of one of the members of your SignerList to get a signature for that member.

-
<<<<<<< HEAD
-Caution: Never submit a secret key to a server you do not control. Do not send a secret key unencrypted over the network.
-=======
-Caution: Never submit a secret key to a server you do not control. Do not send a secret key unencrypted over the network.

-

-

-

-

-

-

-

-
callouts

-

-

-

-

-

-

-

+
Caution: Never submit a secret key to a server you do not control. Do not send a secret key unencrypted over the network.

 
$ rippled sign_for rsA2LpzuawewSBQXkiju3YQTMzW13pAAdW <rsA2L..'s secret> '{
 >     "TransactionType": "TrustSet",
 >     "Account": "rEuLyBCvcw4CFmzv8RepSiAoNgF8tTGJQC",
@@ -468,25 +432,7 @@ Connecting to 127.0.0.1:5005
 
  • In parallel: Use the sign_for command with the original JSON for the transaction. Each response has a single signature in the Signers array.
    • 
 
  • In serial: Use the sign_for command with the tx_json value from the previous sign_for response. Each response adds a new signature to the existing Signers array.
    • 
 
-
    <<<<<<< HEAD
-Caution: Never submit a secret key to a server you do not control. Do not send a secret key unencrypted over the network.
-=======
-Caution: Never submit a secret key to a server you do not control. Do not send a secret key unencrypted over the network.
    
-
    
-
    
-
    
-
    
-
    
-
    
-
    
-
    callouts
    
-
    
-
    
-
    
-
    
-
    
-
    
-
    
+
    Caution: Never submit a secret key to a server you do not control. Do not send a secret key unencrypted over the network.
    
 
    $ rippled sign_for rUpy3eEg8rqjqfUoLeBnZkscbKbFsKXC3v <rUpy..'s secret> '{
 >    "Account" : "rEuLyBCvcw4CFmzv8RepSiAoNgF8tTGJQC",
 >    "Fee" : "30000",