This seems related to the fact that it was showing 10 tx's of type "Generated". When the user does other types of tx's, those show up and they now report seeing 13 tx's on that Transaction tab. We may have a bug where only the last 10 tx's of type "generated" are shown, in both SD+SDX
This seems related to the fact that it was showing 10 tx's of type "Generated". When the user does other types of tx's, those show up and they now report seeing 13 tx's on that Transaction tab. We may have a bug where only the last 10 tx's of type "generated" are shown, in both SD+SDX
SD/SDX uses "listtransactions" RPC with no arguments, which defaults to only showing the last 10 transactions. Shielded transactions use a different RPC, so it will show all ztx's. This bug is only related to transparent tx's, and since sending to a taddr is not allowed on DragonX or HUSH, this bug only affects mining tx's.
We need use "listtransactions" with non-default arguments in src/rpc.cpp. We want to emulate something like listtransactions "*" 99999 instead of just listtransactions. A better long term change is to use the getalldata RPC but that is a bigger change to SD internals
SD/SDX uses "listtransactions" RPC with no arguments, which defaults to only showing the last 10 transactions. Shielded transactions use a different RPC, so it will show all ztx's. This bug is only related to transparent tx's, and since sending to a taddr is not allowed on DragonX or HUSH, this bug only affects mining tx's.
We need use "listtransactions" with non-default arguments in src/rpc.cpp. We want to emulate something like `listtransactions "*" 99999` instead of just `listtransactions`. A better long term change is to use the `getalldata` RPC but that is a bigger change to SD internals
This is a simple fix that is a good "beginner" issue to work on, @dan_s do you have any interest in working on this, since it mostly affects DragonX users?
This is a simple fix that is a good "beginner" issue to work on, @dan_s do you have any interest in working on this, since it mostly affects DragonX users?
This should be fixed now in dev branch with dbc34dde12
I am seeing more than 10 "generate" transactions now for mining rewards but others can test.
This should be fixed now in `dev` branch with https://git.hush.is/hush/SilentDragon/commit/dbc34dde12181b65e81d1382f6924b0ec63b9aeb
I am seeing more than 10 "generate" transactions now for mining rewards but others can test.
This happened on Windows 10 Home 64bit SDX v1.3.1
This seems related to the fact that it was showing 10 tx's of type "Generated". When the user does other types of tx's, those show up and they now report seeing 13 tx's on that Transaction tab. We may have a bug where only the last 10 tx's of type "generated" are shown, in both SD+SDX
SD/SDX uses "listtransactions" RPC with no arguments, which defaults to only showing the last 10 transactions. Shielded transactions use a different RPC, so it will show all ztx's. This bug is only related to transparent tx's, and since sending to a taddr is not allowed on DragonX or HUSH, this bug only affects mining tx's.
We need use "listtransactions" with non-default arguments in src/rpc.cpp. We want to emulate something like
listtransactions "*" 99999
instead of justlisttransactions
. A better long term change is to use thegetalldata
RPC but that is a bigger change to SD internalsThis is a simple fix that is a good "beginner" issue to work on, @dan_s do you have any interest in working on this, since it mostly affects DragonX users?
This should be fixed now in
dev
branch withdbc34dde12
I am seeing more than 10 "generate" transactions now for mining rewards but others can test.
Calling this fixed, closing