search

XRPLF / rippled

Decentralized cryptocurrency blockchain daemon implementing the XRP Ledger protocol in C++
https://xrpl.org
ISC License
4.54k stars 1.47k forks source link

[transaction] (Version: [1.12.0) #4865

Open xiongjiabing opened 10 months ago

xiongjiabing commented 10 months ago

{ "result": { "error_message": "Not synced to the network.", "request": { "tx_blob": "120000220000000024000000002e3e6910db201b0sdfdsfdsf511886e614000000002c66409684000000000000bb8732103bad647c4aa357316f6c71f41b42d080c1ed7a5a7ebdecc4130ad4f4534e2fb2e845044a0ee1448772c9", "command": "submit" }, "error_code": 17, "error": "noNetwork", "status": "error" } }

hi team, I get this error when I submit a transaction. Since I didn't get a txId, I was worried that the transaction might end up being successful. could you explain this error message?

ximinez commented 10 months ago

https://xrpl.org/server-doesnt-sync.html

https://xrpl.org/reliable-transaction-submission.html

xiongjiabing commented 10 months ago

Is this being attacked？I see a lot of transactions happening and the amounts are small，e.g. 0.000001 XRP

xiongjiabing commented 10 months ago

like an inscription transaction?

scottschurr commented 10 months ago

There are reasons to believe its these scammers: https://xrp20coin.com/en. And, no, as I understand it inscriptions do not work with XRP Ledger drops.

xiongjiabing commented 10 months ago

thank u so much, Like the transaction above, is it possible for it to reach the ledger？ Since "error_message": "Not synced to the network.",

xiongjiabing commented 10 months ago

and subsequent transactions are normal

intelliot commented 10 months ago

In the case where rippled's response includes "error_message": "Not synced to the network.", the transaction should not reach the ledger as a result of that particular request.

For this particular example tx, given that the tx_blob has been shared publicly in this GitHub issue, it is possible for anyone to submit it now. So if this tx is still valid (e.g. based on Sequence, LastLedgerSequence, etc) then it can reach the ledger - though not because of the "submit" that you ran earlier.

To reiterate, reliable transaction submission is intended to handle this and many other kinds of errors.