It was 8:14 PM in here in California, so it was a pretty good for anyone in the Americas or Asia. Not so much for Eastern Europe.
Difficulty is back down to 400. Looks like things are evening out. People sure do panic quickly.
Clearly you don't understand the problem. This isn't the usual "KGW setting diff too high for a short while early on" problem. The linear diff on this is broken. It's only "evening out" at the moment because hashrate is dropping. Any other spikes before KGW will do the same again. Nobody's panicking. The coin needs fixing and it's best to act quickly. This is absolutely correct - there is ZERO damping in the diff adjustment. If it manages to keep unsticking now, it'll drop like a stone, hit practically zero, then suddenly spike again to some outrageous value. It's not a one-off, it's what happens when you use an undamped retargeting method every block. BTW, had to find a VM with Boost1.54 to build the Windows wallet (without spending time getting it sorted for 1.55) for the alternate chain, but it's in-hand, I'll get it out before I go and sleep (ugghh, sweet, sweet sleep...) KGW: Yes! Of course! August 28, 2013! That was the day I invented time-dilated difficulty gravitational wells. The black holes of difficulty formulas! I remember it vividly. I was standing on the edge of my toilet about to upload a standard fork, the porcelain was wet, I slipped, hit my head on the sink, and when I came to I had a revelation! A vision! A picture in my head! A picture of this!  This is what makes time-dilated difficulty formulas possible: the Kimoto Gravity Well! It's taken me nearly sixty six years and my entire family fortune to realize the vision of that day. KGW = 1 + (0.7084 * pow((double(PastBlocksMass)/double(144)), -1.228)); Marty, we don't have much time, we must release it upon the universe today. The future of Megacoin depends on it. KGW = 1 + (0.7084 * pow((double(PastBlocksMass)/double(144)), -1.228)) |
|
|
|
It was 8:14 PM in here in California, so it was a pretty good for anyone in the Americas or Asia. Not so much for Eastern Europe.
Difficulty is back down to 400. Looks like things are evening out. People sure do panic quickly.
Clearly you don't understand the problem. This isn't the usual "KGW setting diff too high for a short while early on" problem. The linear diff on this is broken. It's only "evening out" at the moment because hashrate is dropping. Any other spikes before KGW will do the same again. Nobody's panicking. The coin needs fixing and it's best to act quickly. Obviously someone who hasn't been paying attention.  Seriously, difficulty WILL be that high when so many people are mining it at such high hash-power. Pool owners should have expected it, and I'm sure the dev team expected this to happen, but not to this extent. KGW is meant to do this, to prevent insta-mining and multi-pools from clogging up the network. Learn how things work before you say something. If you think you have it figured out, I'd like to see what you've come up with. Show me what you mean, otherwise, don't post something useless without evidence to back it. It just makes sense. Data I fixed it
Still don't see it. |
|
|
|
i thing sumpool is dodgy to say the least... second highest hash on the pool, got no coins ever unconfirmed or otherwise... no reply from owner. clicked on dashboard a few times and they redirected me to some chinese airline ticketing agency... wtf
I think you need to you need to stop spreading lies about people and take a break kid. Give things time, and stop expecting immediate answers. I never said anyone was dodgy, cheating, lying, or stealing from their members. It's people like you who cause problems in the community, and you should re-word your post and sit on your hands until you have something intelligent to share. Preferably using good grammar. |
|
|
|
|
I think the pool owners who have reset their pools and removed pi-coin from their users' accounts need to apologize, and reimburse them for the loss incurred due to the hasty decisions made by said pool owners.
|
|
|
|
3:14 utc, really good launch time
no you fail
You're a bit late to the party. Have a seat in the back. |
|
|
|
There should be a re-launch
Well, IMO that's not really fair on miners who mined blocks 1-720. I rolled back as little as possible under the circumstances. Of course, it's a consensus thing, and if people want a relaunch, all they have to do is not mine either chain. You might want to fix your pool and put it back on the correct block-chain. As I said it would... the network regulated itself and difficulty is back down. I hope you backed everything up before you jacked it up, otherwise your miners will be pissed. |
|
|
|
Speaking of which... sumpool... you owe me 1006 pi-coin. lol  |
|
|
|
When is this going to hit so I can inform my PIM (Partner in Mining).
He is at his house sound asleep, and will awaken very PISSED OFF because he has 6MH/s running at Hashing.at, and is currently #1 in hashing power on the server.
He has quite the stake, and will need some sort of clear-cut explanation.
Besides, your pool has 16 confirmations left to clear block 767... and pay-out.
No action is necessary from him at the moment. As if I do this he will just start mining on the new chain automatically. Yeah is 16 from 30 though  Remember how I said patience? Yeah... as pool owners, you guys need to realize that applies to you too. As I said 16, it is now 15. Give it a minute. Difficulty is dropping and the network is regulating itself. You guys are jumping the gun and you're going to royally #$%# things up for this launch. EDIT As I said... see the post above. |
|
|
|
Rolling it back about 5 or so blocks to 775 for the fix would be a better idea than cutting out 55 more blocks than necessary. The difficulty only jumped during the last several blocks.
 |
|
|
|
|
When is this going to hit so I can inform my PIM (Partner in Mining).
He is at his house sound asleep, and will awaken very PISSED OFF because he has 6MH/s running at Hashing.at, and is currently #1 in hashing power on the server.
He has quite the stake, and will need some sort of clear-cut explanation.
Besides, your pool has 16 confirmations left to clear block 767... and pay-out.
|
|
|
|
There should be a re-launch
agreed |
|
|
|
sumpool,
I had 1006 unconfirmed pi on my account, and it is all of a sudden missing.
Can you please explain?
LOOK Re: [ANN][PI] piCoin - The Math Cryptocurrency - Just Launched at 3:14 UTC Today at 07:12:37 AM Reply with quote #377 Quote from: duazo on Today at 07:09:30 AM This fix looks good to me. So few blocks have been mined since 720, that I think pulling this chain now would be a good idea. Diff is broken at the moment - the longer it's left this way, the more people will lose out. Best to nip it in the bud now and get KGW running. Well, I kept as much of the chain as I thought sane under the circumstances (not much time or people will stop mining and the coin will die) - I couldn't tell accurately how late I could cut the chain, since the published block explorer isn't working. Hopefully I minimized coin loss as much as possible, as anything mined up until block 719 will be valid on the new fork. https://pi.crunchhharder.net is gradually catching up with the broken blockchain, but we need two things if this chain is to be adopted: 1. Enough hashrate at CrunchHarder to orphan the 60 blocks that led to the broken sky-high difficulty. 2. Other pools to build and deploy the wallet from https://github.com/Paul-Bradley/projectpiCoinThat doesn't mean it has been labeled OFFICIALLY yet. If you want to do that, then your pool needs to be updated. Currently it shows: PPLNS Target 4000000
Round Shares [Submitted shares since last found block (ie. round shares)]
Est. Shares 7,057,975 (done: 0.21%)
Pool Valid 14,498
Your Valid 0
Pool Invalid 0 (0.00%)
Your Invalid 0 (0.00%)
PI Estimates
Block 0.00000000
Fees 0.00000000
Donation 0.00000000
Payout 0.00000000
Network Info
Difficulty 1,723.13839023
Est Next Difficulty 349.97954140 (Change in 10 Blocks)
Est. Avg. Time per Block 25 minutes 45 seconds
Current Block 780 |
|
|
|
This fix looks good to me. So few blocks have been mined since 720, that I think pulling this chain now would be a good idea. Diff is broken at the moment - the longer it's left this way, the more people will lose out. Best to nip it in the bud now and get KGW running.
Well, I kept as much of the chain as I thought sane under the circumstances (not much time or people will stop mining and the coin will die) - I couldn't tell accurately how late I could cut the chain, since the published block explorer isn't working. Hopefully I minimized coin loss as much as possible, as anything mined up until block 719 will be valid on the new fork. https://pi.crunchhharder.net is gradually catching up with the broken blockchain, but we need two things if this chain is to be adopted: 1. Enough hashrate at CrunchHarder to orphan the 60 blocks that led to the broken sky-high difficulty. 2. Other pools to build and deploy the wallet from https://github.com/Paul-Bradley/projectpiCoinI've built the new daemon but the problem is ... there's currently around 70 MH/s at my pool ( http://pi.hashing.at/) and I can't just switch people over without some sort of agreement. However if we don't switch ... I don't see this coin getting fixed by the dev anytime soon ... and mining at 1700 difficulty is ... block 767 was solved on your pool... which I have a 1,208.2 pi stake in... If we were to do this... would I lose all of that? Will I be able to earn it back quickly? |
|
|
|
|
sumpool,
I had 1006 unconfirmed pi on my account, and it is all of a sudden missing.
Can you please explain?
|
|
|
|
Pool Efficiency 99.80%
Current Active Workers 24
Current Difficulty 2573.73161268
Est. Next Difficulty 535.75568006 (Change in 1 Blocks)
Est. Avg. Time per Round (Network) 25 minutes 8 seconds
Est. Avg. Time per Round (Pool) 85 hours 44 minutes 30 seconds
Est. Shares this Round 10542005 (done: 0.98%)
Next Network Block 780 (Current: 779)
Last Block Found 777
Best Efficiency and First pool
0% fee auto-pay:5 minuets
I can't receive your any email from your pool when I mine brightcoin. coins also in your pool. what I used is yahoo email and many other email address also in the same in qq group chat!!!! I want to know why? Look junk mail  |
|
|
|
https://github.com/Paul-Bradley/projectpiCoin - I unstuck the blockchain and rolled it back to block 720 where KGW kicks in. Obviously, anyone is welcome to not mine this chain, but it's better than a stuck one and I didn't want to waste my time setting up a pool then not have a blockchain!!! We're hashing this (unstuck) chain now at https://pi.crunchharder.netDevs - pull request in your inbox! Windows wallet coming in a minute... PPLNS Target 17
Round Shares [Submitted shares since last found block (ie. round shares)]
Est. Shares 1 (done: 102400%)
Pool Valid 1,024
Your Valid 0
Pool Invalid 0 (0.00%)
Your Invalid 0 (0.00%)
PI Estimates
Block 0.00000000
Fees 0.00000000
Donation 0.00000000
Payout 0.00000000
Network Info
Difficulty 0.00024414
Est Next Difficulty 0.00003948 (Change in 1 Blocks)
Est. Avg. Time per Block 32 minutes 21 seconds
Current Block 721  |
|
|
|
OK guys (and gals), Here is what is happening, to the best of my knowledge. It seems that there were more people interested in jumping on this coin than the dev team anticipated, in the sense of dedicated hashing power. IMHO, I think KGW should have been implemented from the start, if it wasn't... I honestly can't tell since difficulty has been in the 2000+ range for a few blocks now. To be blunt, for those of you who are waiting for confirmations to get your coins, do not freak out. You will get paid, it just takes time, as with all cryptos. The network needs to settle first, it's on a very high spike. For those posting about getting their coins, please be patient. For those posting about current difficulty and block times... everyone else sees the same thing. For those who are just watching the story unfold... I'm making popcorn, and mining. I think I'll go play a few games or go to bed... haven't decided. Seriously though, patience is a virtue when a new coin is launched these days, as there are so many people out there that are figuring out that jumping on a new coin as soon as it launches is their best bet at banking on cryptos. I'm in it for the long-haul, but if anyone needs any help setting up miners, getting started, please let me know. I have already helped many others with settings on many different algorithms, many different miners, many different coins, on many different operating systems, gpu/cpu combinations, etc. Linux, Windows... I hate MAC so you guys can just bite the bullet and build a PC... the only way to mine efficiently. Linux is the way to go for mining. Windows is okay at best unless it is your main rig. 7870 with hynix memory settings for cgminer 3.7.2: GPU: 945MHz RAM: 1375MHz VDDC: 1.219V Auto-Fan 400KH/s Linux/SMOS/BAMT ~370KH/s Windows 7870 with elyria memory settings for cgminer 3.7.2: GPU: 945MHz RAM: 1400MHz VDDC: 1.219V Auto-Fan 400KH/s Linux/SMOS/BAMT ~370KH/s Windows These are what I use. I run both on: "api-listen" : true,
"intensity" : "20,20",
"vectors" : "1",
"worksize" : "256",
"kernel" : "scrypt",
"auto-fan" : true,
"temp-cutoff" : "90",
"temp-overheat" : "85",
"temp-target" : "70",
"gpu-fan" : "60-100",
"expiry" : "30",
"gpu-dyninterval" : "7",
"log" : "5",
"queue" : "1",
"retry-pause" : "5",
"scan-time" : "30",
"scrypt" : true,
"temp-hysteresis" : "3",
"shares" : "0",
"shaders" : "1280,1280",
"thread-concurrency" : "15232,15232",
"gpu-thread" : "1",
"gpu-engine" : "945,945",
"lookup-gap" : "2",
"gpu-powertune" : "20",
"gpu-memclock" : "1400,1350" |
|
|
|
We're aware of the very high network hashrate and difficulty at this moment. We are diligently looking into this anomaly and will keep people updated. If this turns out to be a major issue we will fix it.
With that being said, I think I should point something out to people. Please do not pool jump at the moment.
It will not make things any better, in fact, it won't do anything.Please allow time for the DEV team to remedy the situation, if they need to step in, please wait for their instructions. |
|
|
|
Thank you much Kind Sir!  And all these little kids in here thought I was being a troll... honestly... [trollface.jpg] |
|
|
|
The proof is in the math.
Do the math... prove me wrong if you think you can.
There is a simple fix to this issue ... editing the configuration file and setting the correct amount of coins, generated by each block ... which is 314159 as you pointed out. It just seems people are ignorant ... I mean ... it takes like what ... 10 seconds to change a number ? By the way ... Current Difficulty: 2573.73161268 ... Someone buy this man a beer. |
|
|
|
|
Show Posts
??
