Why do stakes cause a rise in diff? Just wondering
I think the way PoS was originally designed (ie ppcoin) was to reduce power usage over time. My understanding is that over time there is more PoS blocks and less PoW blocks, which in theory reduces power cost, but I guess time will tell. With PHS this is magnified of course greatly. |
|
|
|
|
I am testing beta2 client and will release later if it behaves. If that goes well and the client is stable for some time we should see even less chance for forks and orphans. Will also notify exchanges at this time.
|
|
|
|
Yeah, if you have access to your Firewall/Router settings... Something strange happened with my wallets couple of days ago: The one - with only about 850 coins got about 130 PHS from POS The other one - with about 4500 coins - got less than 100 PHS?!? ( That happend after the fork drama. ) Can anyone explane it to me, please? I don't get it.  I have added uPNP capability to the QT client which will auto open your ports on supported routers, I haven't made the bins yet will be included in beta2 client. (goto settings>options>network>use upnp) or you can make your own bins with it now. https://github.com/palmd/philosopherstonethere is so many forks that would be my guess,.. |
|
|
|
I'll give the pool another try. The last one was quite close to my estimates.
the problem of this pool originally was a derped client which had bad connectivity and many blocks were rejected,. recently its because the difficulty is very high so is variance, although block history seems about right now and lately Thats pretty accurate. Weirdness was all caused by forks. I was told many times on this thread that my pool payed way less than what they thought it should have payed, i didnt know why, now it is clear that the forks were responsible. You are welcome any time at phs.minar.cc  yes this is true the client was the problem the first week+, not to mention bad nodes rejecting blocks  Solo miners with rejected blocks experienced this as well. always pump up connections and forward ports if you solo-mine |
|
|
|
|
Wanted potential miners and savers to know.. the difficulty rise may be caused by lots of stakes coming in. If this is the case, it will only get worse as time goes on and curtail PoW block production more and more as the stakes increase in number. Basically it means the sooner you miner and start your stake the better off you will be. Also means mine now and kick back, live on interest later.
|
|
|
|
I'll give the pool another try. The last one was quite close to my estimates.
the problem of this pool originally was a derped client which had bad connectivity and many blocks were rejected,. recently its because the difficulty is very high so is variance, although block history seems about right now and lately |
|
|
|
This needs to die... so tat diff will drop and ppl will stop having issues syncing.
When can these bad nodes be blocked?
As far as dif.. it may go much higher in near future mine when ya can |
|
|
|
This needs to die... so tat diff will drop and ppl will stop having issues syncing.
When can these bad nodes be blocked?
Ya I am aware there is a few active but dying forks, if they don't upgrade or go away we can get rid of them with client update in near future |
|
|
|
Here is how i lost all my PHS.
I had mined 450 PHS.
Had problems with syncing, but eventually I was about 2k blocks from beeing synced and all my phs were @ stakes.
I tried using the 1.0 client to sync then revert to 1.2 deleted all but my wallet.
Coins gone, all of them. The transactions that coins come in from the pools are visible and verified but 0 coins present!
what can I do peolple, this is really frustrating....
nayone wishing to put me back in the game: 9mpEEX3zTMuPNFbyzk7isVSKLck4Nh2M5M
But what I really want is a way to get the coins I mined back!
I am not sure depends when you got the coins, I would not count them gone just yet, maybe someone else can help you , I would just delete everything but wallet and run new client see what happens (backup wallet first of course) |
|
|
|
Was chain fast this time? and no problems? |
|
|
|
Just a heads up to miners (and solo miners). I did some update to increase connectivity and also added back upnp to the Qt client, will have a windows bin later today or tomorrow with these upgrades. being on the new client and with these updates will ensure your submitted blocks don't get 'rejected' source ready at: https://github.com/palmd/philosopherstoneAlso of note to miners: there is a problem with difficulty being too high and if/when this can be fixed will let you know before the new client comes out to prepare for lots more coins. stay tuned. I thought the rise in DIFF was unusual for such a Young Blockchain... is this slowing mining of new Coin??? Should it self adjust as blocks are delayed from expected mining schedule??? please keep us uptodate...THanks for the Great work. It's a bug, stable client and nodes is more important for now, however. You can notice it most when difficulty shoots up very very high 20-30 500-1000Mhash, etc, for short periods, anything is possible  |
|
|
|
Just a heads up to miners (and solo miners). I did some update to increase connectivity and also added back upnp to the Qt client, will have a windows bin later today or tomorrow with these upgrades. being on the new client and with these updates will ensure your submitted blocks don't get 'rejected' source ready at: https://github.com/palmd/philosopherstoneAlso of note to miners: there is a problem with difficulty being too high and if/when this can be fixed will let you know before the new client comes out to prepare for lots more coins. stay tuned. |
|
|
|
Ill upgrade the pool with that source, is it safe to just replace the binary? Get a clean chain ! Remember orphans and forks are cause by the older clients/nodes so this will help with that, also the next update will reduce risk of fork/orphan moreso. Chain should update very fast this time too. |
|
|
|
Too soon, because there are some things that must be done. This should be applied before going to production. But we can't do it without a developer's direct participation. johntawakiYou need to generate two key pairs using makekeypair RPC call. One for alerts and one for checkpoints. If you publish the public keys here, we will be able to update the source and binary builds while you are unavailable.  P.S. And don't forget to keep your private keys in the safe place. Oh, I see. Would you guys mind sending me a PM when this is done so I could know when to update the exchange's client? Thanks Will do , newer client should be in good shape as long as the old ones upgrade, still have lots of older nodes =p Will pm you when client is update again and thanks. |
|
|
|
Too soon, because there are some things that must be done. This should be applied before going to production. But we can't do it without a developer's direct participation. johntawakiYou need to generate two key pairs using makekeypair RPC call. One for alerts and one for checkpoints. If you publish the public keys here, we will be able to update the source and binary builds while you are unavailable. P.S. And don't forget to keep your private keys in the safe place. sounds like more fun stuff for today |
|
|
|
I guess that our mission is done. All what we need now is more patched nodes, it's the matter of time.
Hell smoke break time Thanks would never of caught that.... Since there is still mining nodes on version 1.0 even... anyway to block them or just rule them out over time I guess? |
|
|
|
Using previous build: 17:00:14

getblockhash 11674
17:00:14

0495887c1ed10f623656b0e097ec1add338fcffea4e1f1b7488e8095e99f4d85
09:01:31  getblockhash 11674 09:01:31  0495887c1ed10f623656b0e097ec1add338fcffea4e1f1b7488e8095e99f4d85 new |
|
|
|
|
Show Posts
