mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-27 23:25:51 +00:00
Fix a usage of wallet.sequence
This commit is contained in:
@@ -9,7 +9,6 @@ Django==3.2.19
|
||||
ECPy==1.2.5
|
||||
h11==0.12.0
|
||||
httpcore==0.13.6
|
||||
# httpx==0.23.0
|
||||
idna==3.2
|
||||
image==1.5.33
|
||||
pifacedigitalio==3.0.5
|
||||
|
||||
@@ -2,17 +2,23 @@
|
||||
import os
|
||||
my_secret = os.getenv("MYSECRET")
|
||||
from xrpl.wallet import Wallet
|
||||
wallet = Wallet(seed=my_secret, sequence=16237283)
|
||||
print(wallet.classic_address) # "raaFKKmgf6CRZttTVABeTcsqzRQ51bNR6Q"
|
||||
wallet = Wallet.from_seed(seed=my_secret)
|
||||
print(wallet.classic_address) # "raaFKKmgf6CRZttTVABeTcsqzRQ51bNR6Q"
|
||||
|
||||
# For offline signing, you need to know your address's next Sequence number.
|
||||
# Alternatively, you could use a Ticket in place of the Sequence number.
|
||||
# This is useful when you need multiple signatures and may want to process transactions out-of-order.
|
||||
# For details, see: https://xrpl.org/tickets.html
|
||||
sequence = 0
|
||||
|
||||
from xrpl.models.transactions import Payment
|
||||
from xrpl.utils import xrp_to_drops
|
||||
my_payment = Payment(
|
||||
account=wallet.classic_address,
|
||||
account=wallet.address,
|
||||
amount=xrp_to_drops(22),
|
||||
fee="10",
|
||||
destination="rPT1Sjq2YGrBMTttX4GZHjKu9dyfzbpAYe",
|
||||
sequence=wallet.sequence, # this needs to be incremented upon every successful transaction
|
||||
sequence=sequence,
|
||||
)
|
||||
print("Payment object:", my_payment)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user