Setting things up
XRP Ledger accounts
First XRPL interaction
Activate Existing XRPL Account on Test Network
Connecting and Interacting with XRP Ledger: account_info
Interacting with XRP Ledger using JSON-RPC
Error Handling and Best Practices
Basics of XRP and Issued Currency
Signing Payment Transaction
Assignment Solution
Verifying Signature
Submit Transaction Signature To XRP Ledger
Subscription Methods
Subscription Methods To Build Responsive App
Transaction Verification
Balance Detail
Transaction Cost
Measures to Avoid Ledger Spamming
Source And Destination Tags
AccountSet Transaction: Domain, Gravatar
AccountSet Transaction: SetFlag, ClearFlag
Deposit AuthorizationTokens, transactions
Issuing Token on XRPL
Token(IOU): Payment Transaction
Commands To Fetch TrustLine Information
Freeze a TrustLine
Issuer: Transfer Fees
More about TrustLine
Currency Code In Hex Format
Removing a TrustLine
Require authorization FlagLedger features
AccountDelete Transaction
Tickets: Theory
TicketCreate Transaction
Delete Ticket ObjectSetRegularKey
SetRegularKey: The Concept
Assigning RegularKey
Change RegularKey
Remove RegularKey
Blackhole An AccountMultiSigning
MultiSigning: The Concept
Replace SignerListSigning Payment Transaction
Intro
Sign a payment transaction offline, and analyse the signature.
Video
Topics covered
- Derive rAddress from familySeed.
- Payment TransactionType.
- Learn about all the fields in a Payment Transaction.
- Learn more about payload signature.
References
- Payment Transaction
Possible Error
When you change isValidAddress to isValidSeed, if you start getting error like below:
(node:33872) UnhandledPromiseRejectionWarning:
TypeError: AddressCodec.isValidSeed is not a functionThen please run below command:
npm install xrpl-accountlib --saveReason for the error: The older version of xrpl-accountlib library had this bug which was later fixed.
The above solution updates xrpl-accountlib library and also saves the version changes to your package.json file present in your project folder.
Easy Solution
I can go to XRPL-JS-TS-demo repository right now and change the version of xrpl-accountlib and push the changes. But I want you to encounter this error and then fix it with above solution. That way you know where to look for when you encounter similar problems in any of your projects in future.
Note:
If both Account and Destination are same in a transaction(i.e., both sender and receiver address are same), then it fails with following error code: temREDUNDANT.
But if you are a custodian of user funds and want to handle transactions where the sender and receiver accounts are same, then check the use-case section of Source And Destination Tags tutorial.
← Previous
Basics of XRP and Tokens
Next →
Assignment Solution
- Signing Payment Transaction
- Intro
- Video
- Topics covered
- References
- Possible Error
- Easy Solution
- Note:
