@@ -5,7 +5,7 @@ If you want to perform a state-changing operation on the Terra blockchain such a
5
5
sending tokens, swapping assets, withdrawing rewards, or even invoking functions on
6
6
smart contracts, you must create a **transaction ** and broadcast it to the network.
7
7
8
- An :class: `StdTx<terra_sdk.core.auth.data. tx.StdTx > ` is a data object that represents
8
+ An :class: `StdTx<terra_sdk.core.tx.Tx > ` is a data object that represents
9
9
a transaction. It contains:
10
10
11
11
- **msgs **: a list of state-altering messages
@@ -42,7 +42,7 @@ Once you have your Wallet, you can simply create a StdTx using :meth:`Wallet.cre
42
42
43
43
.. code-block :: python
44
44
45
- from terra_sdk.core.auth import StdFee
45
+ from terra_sdk.core.fee import Fee
46
46
from terra_sdk.core.bank import MsgSend
47
47
48
48
tx = wallet.create_and_sign_tx(
@@ -52,7 +52,7 @@ Once you have your Wallet, you can simply create a StdTx using :meth:`Wallet.cre
52
52
" 1000000uluna" # send 1 luna
53
53
)],
54
54
memo = " test transaction!" ,
55
- fee = StdFee (200000 , " 120000uluna" )
55
+ fee = Fee (200000 , " 120000uluna" )
56
56
)
57
57
58
58
And that's it! You should now be able to broadcast your transaction to the network.
@@ -101,7 +101,7 @@ Signing transactions manually
101
101
-----------------------------
102
102
103
103
Below is the full process of signing a transaction manually that does not use ``Wallet ``.
104
- You will need to build a :class: `StdSignMsg<terra_sdk.core.auth.data. tx.StdSignMsg > `,
104
+ You will need to build a :class: `StdSignMsg<terra_sdk.core.. tx.SignDoc > `,
105
105
sign it, and add the signatures to an ``StdTx ``.
106
106
107
107
A StdSignMsg contains the information required to build a StdTx:
@@ -128,7 +128,7 @@ A StdSignMsg contains the information required to build a StdTx:
128
128
chain_id = " columbus-4" ,
129
129
account_number = 23982 ,
130
130
sequence = 12 ,
131
- fee = StdFee (200000 , " 120000uluna" ),
131
+ fee = Fee (200000 , " 120000uluna" ),
132
132
msgs = [MsgSend(
133
133
mk.acc_address,
134
134
RECIPIENT ,
@@ -157,7 +157,7 @@ Applying multiple signatures
157
157
158
158
Some messages, such as ``MsgMultiSend ``, require the transaction to be signed with multiple signatures.
159
159
You must prepare a separate ``StdSignMsg `` for each signer to sign individually, and then
160
- combine them in the ``signatures `` field of the final :class: `StdTx<terra_sdk.core.auth.data. tx.StdTx > ` object.
160
+ combine them in the ``signatures `` field of the final :class: `StdTx<terra_sdk.core.. tx.Tx > ` object.
161
161
Each ``StdSignMsg `` should only differ by ``account `` and ``sequence ``, which vary according to the signing key.
162
162
163
163
.. note ::
@@ -167,7 +167,7 @@ Each ``StdSignMsg`` should only differ by ``account`` and ``sequence``, which va
167
167
.. code-block :: python
168
168
169
169
from terra_sdk.client.lcd import LCDClient
170
- from terra_sdk.core.auth import StdFee
170
+ from terra_sdk.core.fee import Fee
171
171
from terra_sdk.core.bank import MsgMultiSend
172
172
from terra_sdk.key.mnemonic import MnemonicKey
173
173
@@ -187,7 +187,7 @@ Each ``StdSignMsg`` should only differ by ``account`` and ``sequence``, which va
187
187
)
188
188
189
189
msgs = [multisend]
190
- fee = StdFee (200000 , " 12000uluna" )
190
+ fee = Fee (200000 , " 12000uluna" )
191
191
memo = " multisend example"
192
192
193
193
# create unsigned_tx #1
0 commit comments