version : long
timestamp : long
deadline : long
publisher : String
fee : long
tags : map<string>
(optional field)commands : list<map>
(commands are formed as for signature)version : long
network : String
timestamp : long
deadline : long
publisher : String
type : String
data : map
reference : string
(optional field)note : string
(optional field)publisher
field. Each type of command has its own rules for determining who should sign it (if the command requires a signature at all).A
has set the accounts B
and C
in the multisignature, then the signatures of accounts B
and C
are expected in the transaction (taking into account their multisignature settings).B
has set multisignature to account C
, then only account C
is expected to sign in the transaction (taking into account its multisignature settings).C
has set multisignature to accounts C
and D
, then the signatures of accounts C
and D
are expected in the transaction (EDS forC
and for D
, taking into account the multisignature settings).D
has not set multisignature, then the transaction must have two EDS: one from account C
and one from accountD
.