Skip to content
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

Using settxfee command in console doesn't work as expected. #1222

Open
RavenAngels opened this issue Dec 14, 2022 · 0 comments
Open

Using settxfee command in console doesn't work as expected. #1222

RavenAngels opened this issue Dec 14, 2022 · 0 comments

Comments

@RavenAngels
Copy link

Describe the issue

Changing the default transaction fee using the console command settxfee does not work as indicated.

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

  1. Set the default fee in the console using settxfee to half the original 0.0001 RVN per kB. Set specifically to 0.000005 RVN per kB.
  2. Send an asset to an address. I did this using a unique asset called LSJI07/DYOR#10
  3. The first transfer has a fee of 0.00404000 RVN.
  4. To check the tx fee had reduced I sent the same asset to a new address to check what the standard fees would be.
  5. I used settxfee to 0.0001 RVN per kB. Screenshot of the commands below.
  6. The current fee was exactly the same value as the initial asset transaction. The tx fee should have been halved or possibly still waiting in the mempool until a miner wants to add it to a block.

Initial transaction and fee explorer link. https://rvn.cryptoscope.io/tx/?txid=2e740066c2f2c4a4d286a1cc28becf0165084d7c14b48eeecbe6723e18bb0870

Second check transaction to verify default fee explorer link. https://rvn.cryptoscope.io/tx/?txid=6f185207748fc014091826e0c41962cc407a8e7b81fc90705a60a179b5a49e3c

Note the fee doesn't change and should...

Expected behaviour

The settxfee command should work when reducing or raising the transaction fees to the level you want to set it at.

Actual behaviour

The default setting is always used rather than the user set tx fee.

Screenshots.

image

What version of Ravencoin are you using?

Raven Core version v4.6.1 (64-bit) official binary.

Machine specs:

  • OS: Windows 10 64 bit
  • CPU: 1800x
  • RAM: 48GB
  • Disk size: 1TB
  • Disk Type (HD/SDD): SSD
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant