I believe there is some sort of double spending attack going on. I was awoken by a balance audit check for quarkbar. I've checked some transactions and noticed many transactions from the past few days go to 0 confirmations.
Anyone else seeing anything like this?
Topic: CLOSED..... - page 57. (Read 123130 times)
ANNOUNCEMENT
We are now also on Twitter and Facebook! Follow and like us!
We are now also on Twitter and Facebook! Follow and like us!
CRYPTOCOIN REVIVAL FONDATION ANNOUNCEMENT
We had a good discussion online and decided to focus on Quarkbar right now.
We will do the following things:
1. Fix the problem with DarkGravityWave v2, by patching it to version 3 in progress
2. Promote Quarkbar on Twitter and Facebook Done
3. Create a website (Shursight arranged hosting and URL) Done
4. Use site and social media for more attention and giveaways in progress
5. Create site for Cryptocoin Revival Foundation
Heard some good things about this coin but didn't know it went down hill with the old dev, did he just disappear or dumped then ran?
He just disappeared, so we took over.
Heard some good things about this coin but didn't know it went down hill with the old dev, did he just disappear or dumped then ran?
Quick Update:
DGWv2 uses double float precision numbers which dont translate well between architectures.
So wallets compiled for 32bit CPUs (like the current windows wallet) is returning a flawed Proof-Of-Work and thus cannot sync.
A new 64bit-only windows wallet will be released tomorrow as temporary fix.
DGWv3 is being rolled out asap.
- f0o
PS: Calm your horses there's no reason for all the panic
DGWv2 uses double float precision numbers which dont translate well between architectures.
So wallets compiled for 32bit CPUs (like the current windows wallet) is returning a flawed Proof-Of-Work and thus cannot sync.
A new 64bit-only windows wallet will be released tomorrow as temporary fix.
DGWv3 is being rolled out asap.
- f0o
PS: Calm your horses there's no reason for all the panic
ANNOUNCEMENT
I think it would be good to have an IRC discussion tomorrow. I will create a coin revival foundation channel for this. I will post the link tomorrow.Topics:
- how to select coins
- gpucoin
- qubitcoin
- quarkbar
- duckduckcoin
Time: 1630 GMT (1230 EST, 1830 BERLIN)
LINK: TBD
Meeting is about to start at irc://freenode/coinrevival
Is it worth it to wait now? Old purse killed, the new does not work. Done everything to kill the coin.
Correction: The windows wallet is not working due to a float failure of DGWv2, DGWv3 is being implemented at the moment.
Less flaming, more reading facts
- f0o
Just a small hiccup
Is it worth it to wait now? Old purse killed, the new does not work. Done everything to kill the coin.
Correction: The windows wallet is not working due to a float failure of DGWv2, DGWv3 is being implemented at the moment.
Less flaming, more reading facts
- f0o
Is it worth it to wait now? Old purse killed, the new does not work. Done everything to kill the coin.
addnode=23.226.130.190
Did you setup a node? I think have a bounty for that. :-) PM me your wallet.
QB address: QPMPLgDKY57EsXaWwEtzXp1qYYYGkbYT1B
Thanks
Will send it once we have the transactions working again
THIS IS A GOOD COIN, I HOPE IT CAN BE WELL
We're working on it!
THIS IS A GOOD COIN, I HOPE IT CAN BE WELL
ANNOUNCEMENT
I think it would be good to have an IRC discussion tomorrow. I will create a coin revival foundation channel for this. I will post the link tomorrow.Topics:
- how to select coins
- gpucoin
- qubitcoin
- quarkbar
- duckduckcoin
Time: 1630 GMT (1230 EST, 1830 BERLIN)
LINK: TBD
I am now stuck 25 hours out of date and counting. block 225055 it is showing 1 connection but will not sync. It has been open for more then an hour. This is a windows 64 bit wallet
Yes this might be because the wallets are compiled as 32bit binaries...
Darn... I dont want to alter the code without any agreement with JonesD...
I'm very sorry but I can't fix this until after tomorrow's meeting :/
Darn... I dont want to alter the code without any agreement with JonesD...
I'm very sorry but I can't fix this until after tomorrow's meeting :/
Please don't worry, I can wait as long as necessary.
Further I'm going to try to avoid another hardfork. My plan is to make a minor change that only affects 32bit versions of the wallet, so all exchanges/pools/miners (64bit ppl) dont need to hardfork again.
I have a bad news, same problem with Win8 64bit. Stuck on 225393 block.
received block 00000045d431e0de4c8b01a572207d718d06c49357741e422c8895a195a451ee
DarkGravityWave2 RETARGET
nTargetTimespan = 4200 nActualTimespan = 3947
Before: 1d5b1062 0000005b10620000000000000000000000000000000000000000000000000000
After: 1d5769ff 0000005769ffd45cc974d1d0c546d815bbdf6630e6b6a5ee071af5578ffca806
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 46.246.25.91:31616 (0 -> 100) DISCONNECTING
received block 00000045d431e0de4c8b01a572207d718d06c49357741e422c8895a195a451ee
DarkGravityWave2 RETARGET
nTargetTimespan = 4200 nActualTimespan = 3947
Before: 1d5b1062 0000005b10620000000000000000000000000000000000000000000000000000
After: 1d5769ff 0000005769ffd45cc974d1d0c546d815bbdf6630e6b6a5ee071af5578ffca806
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 74.221.221.48:31616 (0 -> 100) DISCONNECTING
Yes this might be because the wallets are compiled as 32bit binaries...
Darn... I dont want to alter the code without any agreement with JonesD...
I'm very sorry but I can't fix this until after tomorrow's meeting :/
- f0o
Further I'm going to try to avoid another hardfork. My plan is to make a minor change that only affects 32bit versions of the wallet, so all exchanges/pools/miners (64bit ppl) dont need to hardfork again.
I have a bad news, same problem with Win8 64bit. Stuck on 225393 block.
received block 00000045d431e0de4c8b01a572207d718d06c49357741e422c8895a195a451ee
DarkGravityWave2 RETARGET
nTargetTimespan = 4200 nActualTimespan = 3947
Before: 1d5b1062 0000005b10620000000000000000000000000000000000000000000000000000
After: 1d5769ff 0000005769ffd45cc974d1d0c546d815bbdf6630e6b6a5ee071af5578ffca806
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 46.246.25.91:31616 (0 -> 100) DISCONNECTING
received block 00000045d431e0de4c8b01a572207d718d06c49357741e422c8895a195a451ee
DarkGravityWave2 RETARGET
nTargetTimespan = 4200 nActualTimespan = 3947
Before: 1d5b1062 0000005b10620000000000000000000000000000000000000000000000000000
After: 1d5769ff 0000005769ffd45cc974d1d0c546d815bbdf6630e6b6a5ee071af5578ffca806
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 74.221.221.48:31616 (0 -> 100) DISCONNECTING
Maybe you should go to c:/users/(username)/appdata/roaming and delete everything except wallet.dat. Then download the new version and let it synch.
This doesn't help. No one connection. Stuck on 225393
The problem is not solved. Error repeated in windows 7 - 64. What to do?
GOOD job, i like QB and have more than 100K, i hope it can be on more exchange but not only allcoin
I agree, maybe bittrex would consider to add Quarkbar.
Jump to: