SaintFrantic
|
|
May 10, 2014, 09:07:18 AM |
|
The Wallet is stuck at Block 225250. Is there way to fully update it.
|
|
|
|
Obfuscode
|
|
May 10, 2014, 09:54:13 AM |
|
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?
Hi, can you share your audits please? in the means of responsible disclosure, mail me: f0o at obfuscode dot net Thanks! - f0o
|
|
|
|
SaintFrantic
|
|
May 10, 2014, 10:10:55 AM |
|
The Wallet is stuck at Block 225250. Is there way to fully update it.
Any ideas.
|
|
|
|
Obfuscode
|
|
May 10, 2014, 10:21:38 AM |
|
The Wallet is stuck at Block 225250. Is there way to fully update it.
Any ideas. For the impatient people again: This issue is because of a 32bit float calculation problem happening on 32bit systems. 64bit *Nix systems that compile the wallets themselves do not experience this issue. The current Windows-Wallet is 32bit and thus contain the issue. Temporary solution (for the impatient):Compile the wallet yourself using a 64bit system & build-environment. //Edit: For the patient people: Grab a beer, let us work through the tests. If we update now to DGWv3 we're even earlier than the creator of it. Give us some time to mature the codebase please. Rome wasnt built over 1 night either
|
|
|
|
Jonesd (OP)
Legendary
Offline
Activity: 1876
Merit: 1014
|
|
May 10, 2014, 11:31:56 AM |
|
The Wallet is stuck at Block 225250. Is there way to fully update it.
Any ideas. For the impatient people again: This issue is because of a 32bit float calculation problem happening on 32bit systems. 64bit *Nix systems that compile the wallets themselves do not experience this issue. The current Windows-Wallet is 32bit and thus contain the issue. Temporary solution (for the impatient):Compile the wallet yourself using a 64bit system & build-environment. //Edit: For the patient people: Grab a beer, let us work through the tests. If we update now to DGWv3 we're even earlier than the creator of it. Give us some time to mature the codebase please. Rome wasnt built over 1 night either And Rome still stands
|
Co-Founder and Managing Partner of Block Bastards
|
|
|
SaintFrantic
|
|
May 10, 2014, 11:56:41 AM |
|
The Wallet is stuck at Block 225250. Is there way to fully update it.
Any ideas. For the impatient people again: This issue is because of a 32bit float calculation problem happening on 32bit systems. 64bit *Nix systems that compile the wallets themselves do not experience this issue. The current Windows-Wallet is 32bit and thus contain the issue. Temporary solution (for the impatient):Compile the wallet yourself using a 64bit system & build-environment. //Edit: For the patient people: Grab a beer, let us work through the tests. If we update now to DGWv3 we're even earlier than the creator of it. Give us some time to mature the codebase please. Rome wasnt built over 1 night either And Rome still stands Yes, it does. But in the same time Rome had burnt down many time in matter of night as well. I appreciate what have you done so far.Thanks guys. I'll be waiting for the update.
|
|
|
|
Jonesd (OP)
Legendary
Offline
Activity: 1876
Merit: 1014
|
|
May 10, 2014, 01:03:01 PM |
|
The Wallet is stuck at Block 225250. Is there way to fully update it.
Any ideas. For the impatient people again: This issue is because of a 32bit float calculation problem happening on 32bit systems. 64bit *Nix systems that compile the wallets themselves do not experience this issue. The current Windows-Wallet is 32bit and thus contain the issue. Temporary solution (for the impatient):Compile the wallet yourself using a 64bit system & build-environment. //Edit: For the patient people: Grab a beer, let us work through the tests. If we update now to DGWv3 we're even earlier than the creator of it. Give us some time to mature the codebase please. Rome wasnt built over 1 night either And Rome still stands Yes, it does. But in the same time Rome had burnt down many time in matter of night as well. I appreciate what have you done so far.Thanks guys. I'll be waiting for the update. hehe, nice one
|
Co-Founder and Managing Partner of Block Bastards
|
|
|
SaintFrantic
|
|
May 10, 2014, 06:55:50 PM |
|
The Wallet is stuck at Block 225250. Is there way to fully update it.
Any ideas. For the impatient people again: This issue is because of a 32bit float calculation problem happening on 32bit systems. 64bit *Nix systems that compile the wallets themselves do not experience this issue. The current Windows-Wallet is 32bit and thus contain the issue. Temporary solution (for the impatient):Compile the wallet yourself using a 64bit system & build-environment. //Edit: For the patient people: Grab a beer, let us work through the tests. If we update now to DGWv3 we're even earlier than the creator of it. Give us some time to mature the codebase please. Rome wasnt built over 1 night either And Rome still stands Yes, it does. But in the same time Rome had burnt down many time in matter of night as well. I appreciate what have you done so far.Thanks guys. I'll be waiting for the update. hehe, nice one Thanks, Jonesd.
|
|
|
|
chiznitz
|
|
May 11, 2014, 02:42:31 AM |
|
Ok so it looks like we're on different fork somehow.
"version" : 80404, "protocolversion" : 70003, "walletversion" : 60000, "blocks" : 229240,
A bunch of deposits that were confirmed went to unconfirmed this morning. I've deleted the blockchain and peers.dat and did a resync and Im still unable to get to the proper chain.
Anyone else notice anything?
|
|
|
|
ouchmefoot
|
|
May 11, 2014, 03:10:47 AM |
|
Sent a large number of coins to AllCoin.com 12 hours ago using the new wallet but they never arrived. I think that is why they are updating their wallet atm Now my wallet refuses to sync and I am down 55k QB Not happy!
|
PostCoin:PYrnF6rLzvERtS73rRc76fpP4QCKP2WJS4
|
|
|
chiznitz
|
|
May 11, 2014, 03:16:23 AM |
|
Sent a large number of coins to AllCoin.com 12 hours ago using the new wallet but they never arrived. I think that is why they are updating their wallet atm Now my wallet refuses to sync and I am down 55k QB Not happy! Well I wonder what issue they are having. I have the new wallet and I'm unable to get on the same blockchain at CryptoALTeX
|
|
|
|
Jonesd (OP)
Legendary
Offline
Activity: 1876
Merit: 1014
|
|
May 11, 2014, 06:27:55 AM |
|
ANNOUNCEMENT The problem seems to have been fixed, but we will need a new hardfork for this! At the moment we urge you to not make withdrawels or deposits and wait for the exchanges and wallets to update. We expect to do this today.
|
Co-Founder and Managing Partner of Block Bastards
|
|
|
Obfuscode
|
|
May 11, 2014, 06:40:39 AM |
|
Hi, We had to give up the Main-Net of QuarkBar because of an irrevocable hardfork during the last emergency patch. We had to wage whether to give up the Forked-Net or the Main-Net. The Forked-Net holds most nodes and exchanges whereas the Main-Net holds 2 pools. The Damages would be greater if we continued the Main-Net. We have a fund of about 20k QB to repay serious damages. Please email us with your TX/Trade/Details and you will get your fair share from the Damages-Fund. Cheers, QuarkBar Developers, Coin Revival Foundation, Obfuscode.Net Team
|
|
|
|
Obfuscode
|
|
May 11, 2014, 07:11:27 AM |
|
We just rolled out the new version on the Nodes. "version" : 80500, "protocolversion" : 70004,
We have a hybrid-node that translates blocks from 70003 into 70004 until Block#232500 (DGWv3 is used after then) Current Blockheight on reference systems: 229771 Reference nodes: addnode=162.243.248.229 addnode=46.246.25.91
|
|
|
|
SaintFrantic
|
|
May 11, 2014, 07:27:14 AM |
|
We just rolled out the new version on the Nodes. "version" : 80500, "protocolversion" : 70004,
We have a hybrid-node that translates blocks from 70003 into 70004 until Block#232500 (DGWv3 is used after then) Current Blockheight on reference systems: 229771 Reference nodes: addnode=162.243.248.229 addnode=46.246.25.91
What's happening then? All that I mined in the last 2 days is gone?
|
|
|
|
ouchmefoot
|
|
May 11, 2014, 08:01:10 AM |
|
will my 55k QB come back? its been in my wallet for 2 weeks until yesterday
|
PostCoin:PYrnF6rLzvERtS73rRc76fpP4QCKP2WJS4
|
|
|
Obfuscode
|
|
May 11, 2014, 08:03:58 AM |
|
...
What's happening then? All that I mined in the last 2 days is gone?
Depends on what chain you mined. If you mined in the Main-Net then yes, it's gone but we will repay you from the 20k repayment-funds. The issue happened with the emergency patch where one or two nodes initially didnt dump their blockchains and published wrong blockchains. Sadly this 'Forked' network had become bigger than the Main-Net so to avoid higher loss we all agreed on making this 'Forked' network the new official network. This issue correlated with the 32bit issue which escalated the offset between those two parallel networks by masquerading the flaw for another day. Until we gathered enough information we passed the Point-of-no-return. We had to weight the potential losses of each chain and came to the conclusion that it would ultimately hurt, if not even kill, the market if we would stick to the Main-Net at all costs. We're deeply sorry that this happened and that we have to carry it out on the shoulders of our miners, the backbone of the network.
|
|
|
|
Obfuscode
|
|
May 11, 2014, 08:05:24 AM |
|
will my 55k QB come back? its been in my wallet for 2 weeks until yesterday
What blockheight does your wallet have? If it's above 232000 then it's in the Main-Net and you will get a share from the repayment-funds. if it's below 230000 then you're on the Forked-Net and they should still exist.
|
|
|
|
SaintFrantic
|
|
May 11, 2014, 08:05:33 AM |
|
...
What's happening then? All that I mined in the last 2 days is gone?
Depends on what chain you mined. If you mined in the Main-Net then yes, it's gone but we will repay you from the 20k repayment-funds. The issue happened with the emergency patch where one or two nodes initially didnt dump their blockchains and published wrong blockchains. Sadly this 'Forked' network had become bigger than the Main-Net so to avoid higher loss we all agreed on making this 'Forked' network the new official network. This issue correlated with the 32bit issue which escalated the offset between those two parallel networks by masquerading the flaw for another day. Until we gathered enough information we passed the Point-of-no-return. We had to weight the potential losses of each chain and came to the conclusion that it would ultimately hurt, if not even kill, the market if we would stick to the Main-Net at all costs. We're deeply sorry that this happened and that we have to carry it out on the shoulders of our miners, the backbone of the network. I have no idea which chain was.It was on your pool.
|
|
|
|
Obfuscode
|
|
May 11, 2014, 08:07:09 AM |
|
... I have no idea which chain was.It was on your pool.
I'm sorry to tell you but your funds are on a different fork now, Please PM or Email me your username and I will send you your share from the repayment funds
|
|
|
|
|