forked from XRPLF/rippled
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fixes for pseudo tx relaying and fees
parent f64cf91 author Valentin Balaschenko <13349202+vlntb@users.noreply.github.com> 1736802518 +0000 committer Valentin Balaschenko <13349202+vlntb@users.noreply.github.com> 1738008707 +0000 gpgsig -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEfrrtWa+LJEJ1XMcuyguytSYMMyoFAmeX6IMACgkQyguytSYM MyoL0RAAw9BSki6NO1DMxTv/VKT1TzzbvPmGhcRCmXJzbMobJHiJBtXO6wKcMY8t +pZcj5+56N2JimSIWJfvoZgrze3cwUgdMXuAGhy0+bbGCgPRp5WEc8hVerk8o62S 9x2kwqRHCDx2JlNpaqyVv+QdgOVCOqug2nCBbW7VYp/ElAX/yeJM+uuH0r2BnsaS rixujqrlp1noPZhGKJUyM1VaiyI61xFFBpD/oyps9jk4l9frd72Fa41Q8/h75ixH ij04wqNE4GEfi0HKKAbu8fNYIdTy9hHeN8Hzblf7J7wZwFDooXIWftR5HkeQbgrD F8mMRlHXFmOLjFrnv+i8LpNFBlhe4DDILzTMXBM7u9TZRSepwrJxZb5TKJuz9q72 aDeXQ2FITNry4s7pVm/X0ZBdH9qdFn8wuJWGIsPlYhmvzT9d6qLCnSZ/NAYhXIxC oBDXfldzVx+1zFz1Ab9KFRl4Dx2drNC18CUXcZdXJVGFZEug26xE5795Tf1SJ1N8 u5JWrfGQZ2SItJOofYbNKm5jbqpEQQWq0V36uYRZ/hWROocMtKWl3E3cU2RDFVjT MILVHGIGBPoOa0ZT5ufHeZCvW2fdfPFlOFXlS6ixTNu3IRzNhY7Ri2Fxfk5EKd8P uDlceyhBeDgiZUOtyoOHm462jQrJ44JxA+QoJv34DikjI/42ZQg= =0wkh -----END PGP SIGNATURE----- fix fee from feeInvalidSignature to feeUnwantedData update release notes feeMediumBurdenPeer and feeInvalidSignature context details Improve pseudo-transaction peer message handling: * Before: Pseudo-transactions received from a peer will fail the signature check, even if they were requested (using TMGetObjectByHash), because they have no signature. This causes the peer to be charge for an invalid signature. * After: Pseudo-transactions, are put into the global cache (TransactionMaster) only. If the transaction is part of a TMTransactions batch, the peer is charged the equivalent of one trivial request per transaction. If not, the peer is charged an unwanted data fee. These fees will not be a problem in the normal course of operations, but should dissuade peers from behaving badly by sending a bunch of junk. Tell the overlay about pseudo transactions, but don't relay them * If reduce relay is enabled, it will queue up the tx id for peers that also have it enabled so they can ask for it later if they need it. Log higher resource charges with higher log levels Include context on (some) resource charges Add context to all Peer charges stop relaying pseudo-tx increased dropThreshold and feeHighBurdenPeer increased the fees fixing formatting fixing unit test missing header fix fee init - missing ctor code refactoring addressing review comment update levelization fixing formatting Limit the size of outgoing mtLEDGER_DATA / TMLedgerData messages Update include/xrpl/resource/detail/Logic.h Co-authored-by: Ed Hennis <ed@ripple.com> Update src/xrpld/overlay/detail/OverlayImpl.cpp Co-authored-by: Ed Hennis <ed@ripple.com> code refactoring assert on update removing assert renaming removing spaces adding spaceship operator unit test update revert fee logging release notes and typo fix Update src/xrpld/overlay/detail/PeerImp.cpp Co-authored-by: Ed Hennis <ed@ripple.com> Update src/xrpld/overlay/detail/OverlayImpl.cpp Co-authored-by: Ed Hennis <ed@ripple.com> finished refactoring relay adding extra debug logs remove dynamic fees Update src/xrpld/overlay/detail/OverlayImpl.cpp Co-authored-by: Ed Hennis <ed@ripple.com> Update src/xrpld/overlay/detail/OverlayImpl.cpp Co-authored-by: Ed Hennis <ed@ripple.com> Update src/xrpld/overlay/detail/OverlayImpl.cpp Co-authored-by: Ed Hennis <ed@ripple.com> var def static getStream temp removal charge update cleanup 1
- Loading branch information
Showing
30 changed files
with
329 additions
and
162 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.