-
Notifications
You must be signed in to change notification settings - Fork 211
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
Invalid ring signatures on non-XMR coin #13
Comments
Probably because of the xmr changes. Maybe try this branch I just created that I think worked with monero before they went to ringct. https://github.com/clintar/node-cryptonote-util/tree/forknote_comp |
When I initially tried your suggestion, I saw the same issue - invalid ring signature. I tried reverting to a I re-synced the daemon blockchain and reset simplewallet, and now all is well! It seems it was all a wallet or daemon error the whole time. Somehow the data got corrupted is my best guess. However, I AM now using your forknote_comp branch. I'm not sure if that fixed things. I'm hesitant to try reverting to your original cryptonote-util branch to find out. It's possible the original branch somehow broke or corrupted the blockchain or wallet. For now, I think we can consider this solved. Thanks so much. |
Issues persisted until the coin core was updated to Bytecoin v2.1. Problems are now resolved. It would seem that the cryptonote foundation fork has issues over time with block sizes, likely related to memory corruption due to the nondeterministic and sporadic nature of the issue. Historic problem text below to help others that may experience this issue in the future. I may have spoken too soon! It ran great for about 500 blocks. Now, while the pool has continued mining up to block 1560, remote daemons are stuck at block 1510ish and complain of the following:
Bad TXN in question:
Of which the offending portion seems to be:
As far as I can tell, these issues always begin with the pool daemon complaining about a block size that is too big. The problem is that simplewallet in RPC mode will sporadically, about every 4-8 hours, produce a bad transaction. The bad txn seems to follow a notification about the blockchain producing a block that is too large. The system it's running on initially complains of an error like so in the daemon:
After that, the next transaction that is attempted to be sent fails:
I am not sure if the blockchain or daemon is auto truncating the block since it's too big, leading to further downstream issues. This causes a fork eventually and stops the daemon from making more blocks. |
Hello,
I attempted to use your pool for a new CryptoNote fork. It worked great for unlocking and hashing blocks, and hashed over 75 blocks without complaint - but it is sending bad transactions that complain of invalid ring signatures in the daemon. Payments process without error in the pool itself.
(payments_info.log)
Therefore the pool is unusable and all payouts unsent. I also saw a daemon complaint about an invalid unlock time specified in a txn, although I did correctly set the
config.blockUnlocker.depth
value.Looking at the code in
lib/paymentProcessor.js
, it looks like it simply sends queries to the simplewallet RPC, so I'm not sure why it's creating invalid ring signatures. Are there specific portions of thecryptonote-util
branch that encode for coin specific vars?Is there any logging in place to reveal the exact RPC data going to the wallet to send payments?
Thanks so much.
The text was updated successfully, but these errors were encountered: