Need help, updated the pool daemon to the latest version, produces this: 2017-May-22 21:36:17.718727 INFO [54.223.133.248:18870 OUT] Tx verification failed simplewallet original coin, no payments- 017-May-22 21:41:03.021484 ERROR [BlockchainSynchronizer] Failed to query blocks: NodeErrorCategory:5, Internal node error How to fix it? Tx verification failed - someone trying to send invalid transaction and your node is not including it into the transaction pool on the second error - are you using the new simplewallet? |
|
|
|
I can do nothing more to protect you than telling you the binaries are edited. If you still download and run those you probably deserve to loose your money/information |
|
|
|
I have pretty bad news for the people who downloaded forknote from the scammer's link.
The md5 of the executable files is different from the original forknote binaries. You probably have a virus if you downloaded it.
scammer's forknote.exe:
MD5 (forknoted.exe) = 7ca584adfb91ac1a537c116ddb38438e
original forknote.exe:
MD5 (forknoted.exe) = e6d464b15fd29caf4b3e59ca8914b24f
If you downloaded and run any of the scammer's binaries take actions fast and protect your money/information
its win im on linux I am pretty sure if all the windows binaries are edited, it's the same for the linux and mac binaries |
|
|
|
|
I have pretty bad news for the people who downloaded forknote from the scammer's link.
The md5 of the executable files is different from the original forknote binaries. You probably have a virus if you downloaded it.
scammer's forknote.exe:
MD5 (forknoted.exe) = 7ca584adfb91ac1a537c116ddb38438e
original forknote.exe:
MD5 (forknoted.exe) = e6d464b15fd29caf4b3e59ca8914b24f
|
|
|
|
|
I have pretty bad news for the people who downloaded forknote from the scammer's link.
The md5 of the executable files is different from the original forknote binaries. You probably have a virus if you downloaded it.
scammer's forknote.exe:
MD5 (forknoted.exe) = 7ca584adfb91ac1a537c116ddb38438e
original forknote.exe:
MD5 (forknoted.exe) = e6d464b15fd29caf4b3e59ca8914b24f
If you downloaded and run any of the scammer's binaries take actions fast and protect your money/information
|
|
|
|
I withdraw from topia its locked now. So 12 hours left, huh? i wanna cry ...
Are you really gonna send all your coins because of unverified post on bitcointalk? I just checked the XCI blockchain and there is no double spending on it. And all of the xci pools are running fixed version from quite a while. |
|
|
|
|
In case you guys still do not do it - please use Forknote v2.0.1.1 for pools/exchanges/wallets or implement the security fix from the bytecoin repository (or forknote repository). We already contacted Minergate and Hitbtc to update to Forknote or implement our fix, but we have no confirmation are did they actually fixed this
|
|
|
|
|
Since there is a possibility for a lot of scamming to come around:
If anyone wants to check any Forknote supported chain for double spending - just delete the checkpoints in your config file, delete the blockchain and sync from block 0. You need the latest Forknote version to check.
|
|
|
|
DO NOT LISTEN TO user SLB he is BIPCOIN dev team member and relish the failure of XCI coin
SWAP TIME ENDS SOON
I will love to see the transaction hashes of the double spending. If anyone wants to check any Forknote supported chain for double spending - just delete the checkpoints in your config file, delete the blockchain and sync from block 0. You need the latest Forknote version to check. |
|
|
|
Can the bitcoal blockchain be scanned for prior double-spending?
Can we monitor what percentage of peers are using 2.0.1.1+?
Might it be time to purposely initiate a hard fork? (Which would also be a good time to discuss the possibility of changing max coins or plotting another end game; but the choices would have to be fast.)
It may or may not take some or all of the above for exchanges to open wallets again.
All pools are using 2.0.1.1. I haven't scanned the blockchain for double spendings before the update, but scanning is easy. You just need to remove all checkpoints and sync from 0 |
|
|
|
|
no swap is needed. Pools/exchanges, just use forknote with the xci config until there are official binaries.
|
|
|
|
After extensive check I cannot explain a loss of ~50,000 bitcoal. Was blockchain modified? My Wallet file was corrupted. I checked from various backups, and then resynced from keys from 0. I am mining again and no problems for a week now.
Latest update of forknoted and simplewallet. as above
Ubuntu Server 14.04
Wallet is not on miner machine.
THX
Don
There was a fork quite a while ago, because the new version implemented some additional transaction checks. Please all update to the newest Forknote version if you still haven't. It fixes a potential double spending issue: https://github.com/forknote/forknote/releases/tag/2.0.1.1 |
|
|
|
Disclosure of a Major Bug in CryptoNote Based Currencies https://getmonero.org/2017/05/17/disclosure-of-a-major-bug-in-cryptonote-based-currencies.htmlIn Monero we've discovered and patched a critical bug that affects all CryptoNote-based cryptocurrencies, and allows for the creation of an unlimited number of coins in a way that is undetectable to an observer unless they know about the fatal flaw and can search for it.
We patched it quite some time ago, and confirmed that the Monero blockchain had NEVER been exploited using this, but until the hard fork that we had a few weeks ago we were unsure as to whether or not the entire network had updated.
Once we were certain that the network had updated, we notified all active and affected CryptoNote coins, including CryptoNote themselves, Bytecoin, Forknote, Boolberry, DashCoin, and DigitalNote.
Note that, at this time, only Monero, Aeon, Boolberry, and Forknote have updated. We have given the other currencies as much time as possible, but cannot hold back disclosure any longer.
We strongly caution against anyone using, trading, exchanging, or running services involving the following currencies affected by this issue: Bytecoin, DashCoin, DigitalNote Bytecoin need bugfix immediately. when this article has been written? Just when Bytecoin rise to be just below his small brother Monero? why we have not seen this information until now? Anyway it is just a matter of time for Bytecoin to kick Monero from the 9th place. Let enjoy the Ride. We were informed on 25.04. I can assume all devs were informed on this date, based on the communication between us. Also, in the message, it was specifically noted the disclosure will be in mid May. |
|
|
|
Disclosure of a Major Bug in CryptoNote Based Currencies https://getmonero.org/2017/05/17/disclosure-of-a-major-bug-in-cryptonote-based-currencies.htmlIn Monero we've discovered and patched a critical bug that affects all CryptoNote-based cryptocurrencies, and allows for the creation of an unlimited number of coins in a way that is undetectable to an observer unless they know about the fatal flaw and can search for it.
We patched it quite some time ago, and confirmed that the Monero blockchain had NEVER been exploited using this, but until the hard fork that we had a few weeks ago we were unsure as to whether or not the entire network had updated.
Once we were certain that the network had updated, we notified all active and affected CryptoNote coins, including CryptoNote themselves, Bytecoin, Forknote, Boolberry, DashCoin, and DigitalNote.
Note that, at this time, only Monero, Aeon, Boolberry, and Forknote have updated. We have given the other currencies as much time as possible, but cannot hold back disclosure any longer.
We strongly caution against anyone using, trading, exchanging, or running services involving the following currencies affected by this issue: Bytecoin, DashCoin, DigitalNote Bytecoin need bugfix immediately. You can use Bytecoin with forknote daemon. We run fixed daemon on Democats (Forknote) and we informed Hitbtc, Minergate and Cryptopia about the fix PS: Dashcoin is not in the list, because it's updated |
|
|
|
slb, I have a question for you. I have a lot of unconfirmed blocks on the pool, the network finds seldom blocks, and coins are unavailable. If I update the client, then a new dаemon with an old wallet is incompatible and I will lose coins. How here to be?
The wallet file is compatible. You must update simplewallet to use the new version tho. If you have backups of the wallets you have nothing to worry about. What i do on democats is just stopping daemon + simplewallet, then replace with the new version and start them again. It works fine 95% of the time. Sometime something goes wrong with simplewallet and it corrupts the wallet on exit. In such case you must replace the wallet file with the *.tmp file and that's it. PS: you can delete the old blockchain, since from Forknote v2 we use rocksdb and the old blockchain is not compatible |
|
|
|
A security fix was pushed to github: https://github.com/forknote/forknoteIssue was discovered by Monero Lab and they kindly noticed me about this case. I strongly advice everyone who run Forknote daemons or daemons of compatible blockchains to update to it ASAP. PS: this post will include binaries in a few hours. |
|
|
|
Thanks, upgraded forknoted but now get block synchronization error from wallet. The wallet opens to prompt. but will not sync. Daemon works. my local pool miner works but cannot get wallet to sync.
try to 'reset' the wallet |
|
|
|
|
Show Posts
