|
mustyoshi
|
 |
July 22, 2013, 09:25:34 PM |
|
Some weird stuff going on, weird block delays. What if we've hit the boundry between what the network can handle, and what the difficulty expects us to handle, and that's why we are flip flopping between mining and waiting.
|
|
|
|
|
|
|
|
Each block is stacked on top of the previous one. Adding another block to the top makes all lower blocks more difficult to remove: there is more "weight" above each block. A transaction in a block 6 blocks deep (6 confirmations) will be very difficult to remove.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
AgentME
Member
 Offline
Activity: 84
Merit: 10
|
|
July 22, 2013, 09:26:47 PM |
|
Some weird stuff going on, weird block delays. What if we've hit the boundry between what the network can handle, and what the difficulty expects us to handle, and that's why we are flip flopping between mining and waiting.
A few really large transactions seem to be causing performance issues with mining for some reason. |
|
|
|
|
Sunny King (OP)
Legendary
Offline
Activity: 1205
Merit: 1010
|
|
July 22, 2013, 09:27:31 PM |
|
It is not an attack. It's an issue in the miner that doesn't handle large block efficiently. A fix is being tested. Both the stock miner and mikaelh's miner are impacted.
|
|
|
|
|
|
mustyoshi
|
|
July 22, 2013, 09:29:07 PM |
|
It is not an attack. It's an issue in the miner that doesn't handle large block efficiently. A fix is being tested. Both the stock miner and mikaelh's miner are impacted.
I tried taking the creation of a new block template outside of the loop, and it still seems to be affecting me. |
|
|
|
|
|
TheSeven
|
|
July 22, 2013, 09:41:26 PM |
|
It is not an attack. It's an issue in the miner that doesn't handle large block efficiently. A fix is being tested. Both the stock miner and mikaelh's miner are impacted.
Looks like I "broke" Primecoin by accident. Oh crap. Anything I can do to help fix this up? Might double spending the funds in smaller transactions help resolve this? If so, what's the easiest way to do this, now that the offending TXNs are lingering around in my wallet? Or can someone somehow just forcibly mine them to get rid of them? Why aren't those TXNs being mined (but relayed) in the first place? I sent them with stock primecoind with stock fee settings. I feel like that really shouldn't happen... How long are these going to float around in mempools if we don't do anything about it? |
My tip jar: 13kwqR7B4WcSAJCYJH1eXQcxG5vVUwKAqY
|
|
|
AgentME
Member
Offline
Activity: 84
Merit: 10
|
|
July 22, 2013, 09:46:55 PM |
|
It is not an attack. It's an issue in the miner that doesn't handle large block efficiently. A fix is being tested. Both the stock miner and mikaelh's miner are impacted.
Looks like I "broke" Primecoin by accident. Oh crap. Anything I can do to help fix this up? Might double spending the funds in smaller transactions help resolve this? If so, what's the easiest way to do this, now that the offending TXNs are lingering around in my wallet? Or can someone somehow just forcibly mine them to get rid of them? Why aren't those TXNs being mined (but relayed) in the first place? I sent them with stock primecoind with stock fee settings. I feel like that really shouldn't happen... How long are these going to float around in mempools if we don't do anything about it? I assume things will temporarily fix themselves for now as soon as the last of these large transactions get encoded into the blockchain. And then soon there will probably be updated builds of primecoin that fix its handling of large transactions. |
|
|
|
|
|
96redformula
|
|
July 22, 2013, 09:47:11 PM |
|
It is not an attack. It's an issue in the miner that doesn't handle large block efficiently. A fix is being tested. Both the stock miner and mikaelh's miner are impacted.
Looks like I "broke" Primecoin by accident. Oh crap. Anything I can do to help fix this up? Might double spending the funds in smaller transactions help resolve this? If so, what's the easiest way to do this, now that the offending TXNs are lingering around in my wallet? Or can someone somehow just forcibly mine them to get rid of them? Why aren't those TXNs being mined (but relayed) in the first place? I sent them with stock primecoind with stock fee settings. I feel like that really shouldn't happen... How long are these going to float around in mempools if we don't do anything about it? How much did you move  |
|
|
|
|
|
TheSeven
|
|
July 22, 2013, 09:48:30 PM |
|
It is not an attack. It's an issue in the miner that doesn't handle large block efficiently. A fix is being tested. Both the stock miner and mikaelh's miner are impacted.
Looks like I "broke" Primecoin by accident. Oh crap. Anything I can do to help fix this up? Might double spending the funds in smaller transactions help resolve this? If so, what's the easiest way to do this, now that the offending TXNs are lingering around in my wallet? Or can someone somehow just forcibly mine them to get rid of them? Why aren't those TXNs being mined (but relayed) in the first place? I sent them with stock primecoind with stock fee settings. I feel like that really shouldn't happen... How long are these going to float around in mempools if we don't do anything about it? I assume things will temporarily fix themselves for now as soon as the last of these large transactions get encoded into the blockchain. And then soon there will probably be updated builds of primecoin that fix its handling of large transactions. IIUC the problem is that these transactions aren't going to be mined into blocks if the miner runs an unmodified primecoind. So these will be around for a while if we don't take care of them somehow :/ |
My tip jar: 13kwqR7B4WcSAJCYJH1eXQcxG5vVUwKAqY
|
|
|
|
maco
|
|
July 22, 2013, 09:56:44 PM |
|
PRIMECOIN NETWORK GETTING DDOS ATTACK?
I dropped 90% in PPS. (PC, and all servers)
|
|
|
|
|
|
TheSeven
|
|
July 22, 2013, 10:00:03 PM |
|
PRIMECOIN NETWORK GETTING DDOS ATTACK?
I dropped 90% in PPS. (PC, and all servers)
See a few posts above: We know what's happening, and a fix is being worked on. For now everyone is affected by it to the same degree, so it isn't really much to worry about. |
My tip jar: 13kwqR7B4WcSAJCYJH1eXQcxG5vVUwKAqY
|
|
|
|
TheSeven
|
|
July 22, 2013, 10:01:37 PM |
|
Looks like the transaction was finally mined by someone.
I'm not quite sure why, but things should be fine for now.
We just need to prevent this from happening again in the future.
|
My tip jar: 13kwqR7B4WcSAJCYJH1eXQcxG5vVUwKAqY
|
|
|
|
maco
|
|
July 22, 2013, 10:09:33 PM |
|
Looks like the transaction was finally mined by someone.
I'm not quite sure why, but things should be fine for now.
We just need to prevent this from happening again in the future.
It looks all good now. Thanks |
|
|
|
|
8bitPunk
Member
Offline
Activity: 70
Merit: 10
|
|
July 22, 2013, 10:25:18 PM |
|
Block spacing is back under 1 min - network returning to normal
|
BTC 18bPunkuginRBm1Xz9mcgj8mWJnHDAW5Th | Ł LTCgXEdyBdoQ9WdF6JHi7Pa2EWtzbDjG76 | Ψ ATEBiTLkLpAYeW5hQknUfSvnb7Abbgegku
|
|
|
Sunny King (OP)
Legendary
Offline
Activity: 1205
Merit: 1010
|
|
July 22, 2013, 10:42:45 PM |
|
|
|
|
|
|
AgentME
Member
Offline
Activity: 84
Merit: 10
|
|
July 22, 2013, 10:53:34 PM |
|
I've gotten this error occasionally while mining today, on both Linux and Windows. I'm using mikaelh's hp6 lately, so I don't know if the issue is unique to it. checkqueue.h:171: CCheckQueueControl<T>::CCheckQueueControl(CCheckQueue<T>*) [with T = CScriptCheck]: Assertion `pqueue->nTotal == pqueue->nIdle' failed. |
|
|
|
|
8bitPunk
Member
Offline
Activity: 70
Merit: 10
|
|
July 22, 2013, 10:54:42 PM |
|
Thanks Sunny - that's quite a significant change so I appreciate your ability to turn it around this quickly. |
BTC 18bPunkuginRBm1Xz9mcgj8mWJnHDAW5Th | Ł LTCgXEdyBdoQ9WdF6JHi7Pa2EWtzbDjG76 | Ψ ATEBiTLkLpAYeW5hQknUfSvnb7Abbgegku
|
|
|
|
mikaelh
|
|
July 22, 2013, 10:54:53 PM |
|
Looks good at first glance. It's getting late for me, so I'll port it to my tree in the morning. |
|
|
|
|
|
FiiNALiZE
|
|
July 22, 2013, 10:57:16 PM |
|
Looks good at first glance. It's getting late for me, so I'll port it to my tree in the morning. Let me know how it goes. I'm not going to update until I know it's stable. |
|
|
|
|
96redformula
|
|
July 22, 2013, 11:13:24 PM |
|
I keep crashing on Linux no matter what build I am using....  . Primecoind just stops even with the new build that was just posted..... |
|
|
|
|
|
maco
|
|
July 22, 2013, 11:23:46 PM |
|
I ran out of money on my digital ocean account, but I will add in $5 just to test this out. Thanks Sunny!
|
|
|
|
|
|
