miracle2k / miracle2k/ripple-python

Can't submit offline signed transaction to my ripple node

Open
#8 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
48
Forks
30
PR merge metrics
No merged PRs in 30d

Description

I am testing transaction submitting operations with my ripple testnet node, but I can't submit offline signed transaction to my testnet node. Firstly I prepare some transaction data:

{ 'Account': 'rU6sW4Vp8FFeoobZaxMpbDYuCkJyVG8DMf', 'Amount': '12345599', 'Destination': 'rw47Lr3B1hFvTC2vXFBb6nyZGjntKGDNPf', 'TransactionType': 'Payment', 'Sequence': 1, 'Fee': '12' }

Then call sign_transaction(tx, secret_key) method. It returns:

{'Account': 'rU6sW4Vp8FFeoobZaxMpbDYuCkJyVG8DMf', 'Amount': '12345599', 'Destination': 'rw47Lr3B1hFvTC2vXFBb6nyZGjntKGDNPf', 'TransactionType': 'Payment', 'Sequence': 1, 'Fee': '12', 'Flags': 2147483648, 'SigningPubKey': '02A1E296BFBF7F06DF12F0D093AE350FCB1766A16BF1042F870F6B46BBEBB4EA4C', 'TxnSignature': '3044022047C37B978457D653911EF9A55F537AEDAADE434C7EE80B090D50911CCC7BC6950220512530903CF534638C86A1DEDE630D9D6C24D17A99559860B9E5925644182D6D' }

After I get TxnSignature value, I call Ripple RPC method submit and provide tx_blob with TxnSignature value:

'{ "method": "submit", "params": [{ "tx_blob": "3044022001069CB1E37DFF7EE5735686E3B8B71E5A85452E0C8794B23813523F3F8515C70220503D1B2A31AAC319241D003813A9F9AF2BD2C722C5FD8A1D9547900A8057C9AD" }] }'

The result is this error:

{'result': {'error': 'invalidTransaction', 'error_exception': 'Non-object in array', 'request': {'command': 'submit', 'tx_blob': '3044022001069CB1E37DFF7EE5735686E3B8B71E5A85452E0C8794B23813523F3F8515C70220503D1B2A31AAC319241D003813A9F9AF2BD2C722C5FD8A1D9547900A8057C9AD'}, 'status': 'error'}}

What I do wrong? And how can I fix this problem? Thank you for you help very much!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the sign_transaction entry point and the Ripple RPC submit call, then trace how the signed transaction is represented when tx_blob is supplied. Compare that representation with the invalidTransaction response shown in the issue. Done means identifying the relevant correction and verifying it with an appropriate test or reproducible submission.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.