Source has been updated on github. Old clients will be rejected on new nodes so please update the wallets ASAP.
Why the hell can't you do proper update commits to github? That said http://pawn.coinpools.de:7061/static/ is on the new wallet now. |
|
|
|
To all the pools operators please update your source with the new one in order for the stucked block to be solved.
Is this now really changed?? several pools already changed to this source, but it has only a reward change of 8 hours ago (which pools already have now) main.cpp block reward changed 8 hours ago There is still no change other than this little bugfix in block reward, which isn't relevant at block 8021 at all. There is definitely something wrong which has nothing to do with subsidy changes. And after the last posts I think the devs have no clue what is going on. So, still broken, I don't really know why. But as dev I'd certainly have a closer look at the KGW timewarp attack, see https://bitcointalk.org/index.php?topic=552895.0and at the block time of the last block found. |
|
|
|
April 4th: Automatic checkpointing introduced.
Update ASAP to v. 1.3.0.0
Does this update fix the KGW timewarp attack? |
|
|
|
Hyperbole much?
Yes, always  At least let's see what the devs say once they get back on here. Block 8021 was found at 21:41 GMT yesterday. Since then nobody cared to tell us what is actually broken nor how to fix it. Instead the OP says something of "updated wallet". But when you look at github there is a source which has no changes for two days (besides a small fix to the subsidy function which seems relevant only for block 9000 itself and then blocks 200000 and beyond). So, what do you make of this? |
|
|
|
TO ALL THE MINING POOLS:
When the blockchain gets stucked please disable the pool so that the workers/miningsoftware goes in failover!
There is nothing to failover to at the moment. Coindaemon broken. Game over. |
|
|
|
now which block ？
Still 8021. There are only ~15MHs pools which have fixed wallet. Quick use of some mining calculators: At 15 MHs and a diff of 6.3 it should take roughly 0.02 days = 30 minutes to find a block. So there still is something terribly wrong here. For example: the majority of not updated wallets rejecting the valid found blocks - as there was no change in version number nor in protocol version with the last fix. (Just my quick guess, of course.) |
|
|
|
You have to put the config file in the pawncoin application dir. With Windows thats normally c:\users\<name>\Appdata\Roaming\Pawncoin
Did as you said, still not syncing? No real idea then. Perhaps your (windows) firewall stopping the wallet network traffic? Or try to delete everything besides pawncoin.conf and wallet.dat (backup first if you have any coins!) from the application dir and restart the wallet. Last resort: Do they provide a pawncoind.exe cmd version? Open a command line window in admin mode, start pawncoind.exe with -printtoconsole parameter and watch what it is doing. If there's only the qt gui client you could try the parameter with it, too. Depends on the version of the coin daemon if this works for you or not. (sorry, no windows client here, can't try for myself) |
|
|
|
Saved it as pawncoin.conf.
Put that file in the "release" map I downloaded
Nothing happens when I open the wallet?
What am I doing wrong?
You have to put the config file in the pawncoin application dir. With Windows thats normally c:\users\<name>\Appdata\Roaming\Pawncoin |
|
|
|
Why isn't the existing source on github properly updated with a commit? |
|
|
|
what a rollercoaster  |
|
|
|
One block I think before hard fork
Now, we expect blocks averaging 5 minutes and a reward of 12.5 is it working on any pool yet? it has forked and difficulty went up from 10xx to 713 instead to 46 Block 5400 is still normal re-target. KGW starts with 5401. And blockreward will stay at 25 until block 5450. Nobody knows why, but thats what I understood from source. |
|
|
|
Maybe ppl are frustrated because of slow blocks? Let's see what happens when KGW starts to work.
Yeah, 5% of Icelanders claiming coins and not getting them, because diff is broken. And if they get them, they can't spend them. Thats how you build trust in your coin, especially with people new to crypto currency.  |
|
|
|
I don't think 1604 is low enough to help. Needs to be about 1000 to atttract the multi-pools because the price has fallen too much. So, another 8 slow blocks, unfortunately.
Seems you're right. I wonder how the wallet calculates the networkhashps value one can see with getinfo cmd. Because it seems to be very far off reality. With 3.6GH/s as displayed the network should find a block about every 15 minutes, if I got the math right. In reality the last block is now almost two hours old. |
|
|
|
This is a crucial time for AUR so it would seem to be a good idea. Balduro, please PM me if you want to communicate to the pool owner directly.
It seems like we simply got lucky. Block 5383 was found by p2pool, and diff should be down 33% to 1605 now. I'm not really sure why the wallet RPC command getinfo still shows 2406.9. It seems like it gets the diff of the last block found, not the diff for the next block after computing the diff retarget... (one could consider this a bug  ) |
|
|
|
I mean CPU mining.. just run a wallet, click "mining" and "start mining". Mining with CPU is not very profitable, but If enougt ppl do it, transaction time will be tolerable :-)
That's an interesting thought, The facebook page have 4k people.. how much power each computer can add? Interesting. I just clicked on mininig and start in my wallet. But it happens: nothing. Problem seems to be that the wallet is repeatedly stating "out of sync", apparently because of hundreds of unconfirmed transactions. Could it be that lots of people do have this problem, and so mining drops even further because of wallets out of sync?? Update: Restarting auroracoin-qt does help. Mining gives me about 10kH (not-so-old AMD Hexacore). So no, adding 4-5k people cpu-mining would be roughly 50MH and won't change a thing. |
|
|
|
Now it needs to be decided how to get there. Seems like from the devs the decision is to decide nothing, just wait... Three blocks to go, then the diff will readjust to about 1,613 (if it's right what was said some posts ago). Hopefully this will take not much longer than another day. |
|
|
|
|
Show Posts
