-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server provided fee is incorrect #229
Comments
ghost
assigned JoelKatz
Dec 20, 2013
rec
pushed a commit
to rec/rippled
that referenced
this issue
Sep 9, 2015
ximinez
added a commit
to ximinez/rippled
that referenced
this issue
Feb 8, 2017
Specifically to demonstrate that XRPLF#229 is resolved.
This issue has been resolved, and I have the unit tests to prove it. #2010 |
ximinez
added a commit
to ximinez/rippled
that referenced
this issue
Feb 10, 2017
ximinez
added a commit
to ximinez/rippled
that referenced
this issue
Feb 23, 2017
ximinez
added a commit
to ximinez/rippled
that referenced
this issue
Feb 25, 2017
seelabs
pushed a commit
to seelabs/rippled
that referenced
this issue
Mar 1, 2017
seelabs
pushed a commit
to seelabs/rippled
that referenced
this issue
Mar 1, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a client requests that a trusted rippled server fill in the "Fee" field, it fills in a hard coded value that comes from the cfg file rather than looking at the ledger. This is in RPCHandler::transactionSign, using FEE_DEFAULT.
The text was updated successfully, but these errors were encountered: