how many minutes for each block to be solved?
EDIT: appears to be 2 minutes. is that the target?
where to view difficulty and next adjustment?
Topic: [ANN] [PPC] PPCoin 0.2.0 Release - Upgrade Required (Read 6549 times)
Any windows bunnies available?
-- Smoov
-- Smoov
Network appears to have successfully switched to the new network protocol. If you experience any problem please report here. You shouldn't be seeing the process tx message exception in debug log any more. Instead you might be seeing something about MESSAGESTART NOT FOUND and this is expected.
Reminder that upgrade to 0.2.0 before Monday is required.
Network protocol will be switched automatically at some time around Monday September 10th 18:00:00 UTC. Nodes that have not upgraded before the switch will be disconnected from the main network.
I will monitor the protocol switch and give updates on Monday.
Network protocol will be switched automatically at some time around Monday September 10th 18:00:00 UTC. Nodes that have not upgraded before the switch will be disconnected from the main network.
I will monitor the protocol switch and give updates on Monday.
Reminder that upgrade to 0.2.0 is required before next Monday
Upgrade is required before Monday September 10th. Nodes that have not upgraded before this deadline will be disconnected from the main ppcoin network.
Is this true?
520 confirmation?
Bitcoin atleast needs 6 confirmation & that too called very slow.
Seems ppcoin wont be used in anywhere, coz it will take years to get confirmation alone.
520-block maturity only applies to block minting. For Bitcoin this parameter is 120-block maturity.520 confirmation?
Bitcoin atleast needs 6 confirmation & that too called very slow.
Seems ppcoin wont be used in anywhere, coz it will take years to get confirmation alone.
As for user transactions how many confirmations you wait is entirely up to you and market concensus. Generally speaking the larger amount you send/receive the more confirmations you should consider waiting. Currently the network is protected by central checkpointing so transactions are pretty safe. In the future it would be decentralized and work similarly to Bitcoin.
Is this true?
520 confirmation?
Bitcoin atleast needs 6 confirmation & that too called very slow.
Seems ppcoin wont be used in anywhere, coz it will take years to get confirmation alone.
520-block maturity only applies to block minting. For Bitcoin this parameter is 120-block maturity.520 confirmation?
Bitcoin atleast needs 6 confirmation & that too called very slow.
Seems ppcoin wont be used in anywhere, coz it will take years to get confirmation alone.
As for user transactions how many confirmations you wait is entirely up to you and market concensus. Generally speaking the larger amount you send/receive the more confirmations you should consider waiting. Currently the network is protected by central checkpointing so transactions are pretty safe. In the future it would be decentralized and work similarly to Bitcoin.
Its only the mined blocks that take 550 confirmations, transactions take less confirmations i believe
I've been mining at your pool for days now with the same username as here.
Still no verified balance.
Pretty sure my solo blocks didn't take this long to mature.
Any chance you could have a look at what is going on?
Thanks
Still no verified balance.
Pretty sure my solo blocks didn't take this long to mature.
Any chance you could have a look at what is going on?
Thanks
It can take a few days for blocks to be verified.
I have been solo mining full speed for a couple-few days and as of now I have 111,789 PPC and only 8,975 have matured into a balance.
The PPC project in the beta stage, so as the coin matures and comes closer to the release stage, these issues should be taken care of.
Is this true?
520 confirmation?
Bitcoin atleast needs 6 confirmation & that too called very slow.
Seems ppcoin wont be used in anywhere, coz it will take years to get confirmation alone.
I have an idea, and am not sure why I didn't think of it.
I'm going to make a web-wallet that lets you put in your remote RPC. This will let you control your wallet remotely.
I will create a LIVE SHA256 of the site + tarball'ed SHA256 so you know I'm not saving your information.
This...will be coded one day. I've got a lot of people trying to contact me at once. Which explains why the pool's site has been jacked up for the past few days. >.>
I'm going to make a web-wallet that lets you put in your remote RPC. This will let you control your wallet remotely.
I will create a LIVE SHA256 of the site + tarball'ed SHA256 so you know I'm not saving your information.
This...will be coded one day. I've got a lot of people trying to contact me at once. Which explains why the pool's site has been jacked up for the past few days. >.>
Not sure I follow you. Don't you need to save user rpc username and password in a database? Sounds dangerous to me.
I have an idea, and am not sure why I didn't think of it.
I'm going to make a web-wallet that lets you put in your remote RPC. This will let you control your wallet remotely.
I will create a LIVE SHA256 of the site + tarball'ed SHA256 so you know I'm not saving your information.
This...will be coded one day. I've got a lot of people trying to contact me at once. Which explains why the pool's site has been jacked up for the past few days. >.>
I'm going to make a web-wallet that lets you put in your remote RPC. This will let you control your wallet remotely.
I will create a LIVE SHA256 of the site + tarball'ed SHA256 so you know I'm not saving your information.
This...will be coded one day. I've got a lot of people trying to contact me at once. Which explains why the pool's site has been jacked up for the past few days. >.>
Not sure I follow you. Don't you need to save user rpc username and password in a database? Sounds dangerous to me.
I have an idea, and am not sure why I didn't think of it.
I'm going to make a web-wallet that lets you put in your remote RPC. This will let you control your wallet remotely.
I will create a LIVE SHA256 of the site + tarball'ed SHA256 so you know I'm not saving your information.
This...will be coded one day. I've got a lot of people trying to contact me at once. Which explains why the pool's site has been jacked up for the past few days. >.>
I'm going to make a web-wallet that lets you put in your remote RPC. This will let you control your wallet remotely.
I will create a LIVE SHA256 of the site + tarball'ed SHA256 so you know I'm not saving your information.
This...will be coded one day. I've got a lot of people trying to contact me at once. Which explains why the pool's site has been jacked up for the past few days. >.>
I don't see anything in the link somehow. Do you still have trouble with balance? If so please describe in detail how did you upgrade and what you see in getinfo and listtransactions.
Does this include the bugfixes luke-jr merged into his copy?
-MarkM-
-MarkM-
No. 0.2.0 is still based on Bitcoin v0.6.3. Besides qt gui is not supported yet.
Hi Sunny king
Good job on the latest release, just upgraded with no problems
Good job on the latest release, just upgraded with no problems
Does this include the bugfixes luke-jr merged into his copy?
-MarkM-
-MarkM-
Hello Sunny King,
Congratulations on the 0.2 PPCoin release, successfully installed and upgraded on win 7 x64 here to... i shall be upgrading the windows GUI I made for PPCoin Wallet as well and will be releasing here.... http://ppcointalk.org/index.php?q=node/11
Many thanks
Congratulations on the 0.2 PPCoin release, successfully installed and upgraded on win 7 x64 here to... i shall be upgrading the windows GUI I made for PPCoin Wallet as well and will be releasing here.... http://ppcointalk.org/index.php?q=node/11
Many thanks
I freshly built from github on OSX and get endless exceptions:
ProcessMessages(tx, 226 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
ProcessMessages(tx, 226 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
As mentioned in a different post, I believe this is to be expected and will only cease after the protocol switch on the 10th.
Cheers
I freshly built from github on OSX and get endless exceptions:
ProcessMessages(tx, 226 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
ProcessMessages(tx, 226 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
Jump to: