[member=5782]mhps[/member]
If you are on Peerunity 0.2.0 you must upgrade to Peerunity 0.2.1
You’re missing two key things:
- Today is May 3rd. Sunny only re-enabled checkpoints yesterday, May 2nd. It takes a while for the forked network to see the checkpoints, accept them, and re-transmit them.[/quote]
The propagation should takes minutes. Plus as shown above the client is stuck at sync’ing to checkpoints.
[quote=“sandakersmann, post:61, topic:3875”][member=5782]mhps[/member]
If you are on Peerunity 0.2.0 you must upgrade to Peerunity 0.2.1[/quote]
My Peerunity has been uptodate. Plus the problem I reported a few posts ago were all on the official client.
[member=5782]mhps[/member]
Ok. Shut down your client. Keep the connect= nodes I posted earlier in your ppcoin.conf. Delete everything in your datadir except wallet.dat and ppcoin.conf. Start the client and re-download the blockchain.
Edit: Everyone should sync up on the correct chain as fast as possible. There will be many people not doing this and the rest of us need to carry the network in the meantime.
[quote=“sandakersmann, post:64, topic:3875”][member=5782]mhps[/member]
Ok. Shut down your client. Keep the connect= nodes I posted earlier in your ppcoin.conf. Delete everything in your datadir except wallet.dat and ppcoin.conf. Start the client and re-download the blockchain.[/quote]
Been doing that with the Pi. Will report back when fnished.
Some how, no one seems to understand 520 block confirmations for 1 single block, takes 3.6 days before it comes official.
Yes, on a healthy network, with the majority of clients sync’d to the right chain, you’re right.
I shouldn’t need to tell you that the network is currently fragmented, because it is… So you’re seeing unpredictable results at the current time, for two reasons:
- There is still tons of PeerUnity 0.2.0 clients running (and they shouldn’t be)
- All official ppcoin 0.5.3 and peerunity 0.2.1 clients are having a hard time seeing 520 block confirmations right now, because there aren’t enough up to date nodes making 520 confirmations.
I stand by what I said. 7-14 days from May 2nd, when checkpointing was enabled by Sunny, all of this will be water under the bridge and things will make more sense. 
mhps I respect you, but you’re running around like your hair is on fire [The Sims scenario], and instead of contributing to the solution, you’re exasperating the problem.
Be calm. Everything is fine. It’s going to work. You’ll see.
Final Q&A question:
Q: Peercoin was released 2012-08-19 18:00:00 UTC… This is the first major “issue” it has had in almost 4 years. What do you have to say about that?
A: It is a temporary issue, that it is going to resolve itself quite nicely, if people stop freaking out. In a month from now, this is going to be a big nothing situation.
Yes, on a healthy network, with the majority of clients sync’d to the right chain, you’re right.
I shouldn’t need to tell you that the network is currently fragmented, because it is… So you’re seeing unpredictable results at the current time, for two reasons:
- There is still tons of PeerUnity 0.2.0 clients running (and they shouldn’t be)
- All official ppcoin 0.5.3 and peerunity 0.2.1 clients are having a hard time seeing 520 block confirmations right now, because there aren’t enough up to date nodes making 520 confirmations.[/quote]
I have 24 0.5.x nodes connected. I believe the checkpoint should reach me as fast as a new block message. That said i don’t really know exactly how a checkpoint message is relayed. Do you?
I stand by what I said. 7-14 days from May 2nd, when checkpointing was enabled by Sunny, all of this will be water under the bridge and things will make more sense. :)mhps I respect you, but you’re running around like your hair is on fire [The Sims scenario], and instead of contributing to the solution, you’re exasperating the problem.
Be calm. Everything is fine. It’s going to work. You’ll see.
That is not the point. i am posting logs and reporting issues as a community service. The devs may not see all the aspects (or why we end up where we are now?). Evidences are what informed improvement is based on.
so, for some reason latest clients running ppcoind 0.5.3 and peerunity 0.2.1 fail to verify signature of inputs for this transaction:
{
“txid” : “9c125157e9d246823885a93537ed42590cf19c8acb746ea4940999b7cf7b6bc7”,
“version” : 1,
“time” : 1462036138,
“locktime” : 0,
“vin” : [
{
“txid” : “fd38483a2029469fecdecfc08526b9e7d6635945d74adc92dc836aa7f6ea1291”,
“vout” : 1,
“scriptSig” : {
“asm” : “304a0285000000002100d1c453ddcaae9215a24fc86d50916b66117839d163402d9ed21a1f4aba3173e302200ce3d43a4c4841a340c267c9fa1f3aa43c1e51c0d5043e91a85c954e14c6b91f01 03d4b1beb94313fc4395e38b4ba4ea74f62c5ecec2454c49cbf21d4262803b5469”,
“hex” : “4c4d304a0285000000002100d1c453ddcaae9215a24fc86d50916b66117839d163402d9ed21a1f4aba3173e302200ce3d43a4c4841a340c267c9fa1f3aa43c1e51c0d5043e91a85c954e14c6b91f012103d4b1beb94313fc4395e38b4ba4ea74f62c5ecec2454c49cbf21d4262803b5469”
},
“sequence” : 4294967295
}
],
“vout” : [
{
“value” : 0.11000000,
“n” : 0,
“scriptPubKey” : {
“asm” : “OP_DUP OP_HASH160 c9aa8544c830b866e519c1245465b395863ef444 OP_EQUALVERIFY OP_CHECKSIG”,
“hex” : “76a914c9aa8544c830b866e519c1245465b395863ef44488ac”,
“reqSigs” : 1,
“type” : “pubkeyhash”,
“addresses” : [
“PSyVFWTXLsgQKp65PmgmNqgwh4CBae71kv”
]
}
}
]
}
can you please state your OS? what openssl version do you have
Sunny King, if you read this thread. I’ve tried to tell people to be patient, and they won’t. They’re disregarding the 520 block confirmation 3.6 day thing “per block” and want chain sync happening instantly.
Please address their concerns. Either validate what I said, or validate their impatience.
with all due respect, ppcman, what difference would 520 confirmations do to reorganization of blockchain if verifysignature fails on one of the blocks?
i can confirm that verifysignature fails in my ppcoin test for transaction 9c125157e9d246823885a93537ed42590cf19c8acb746ea4940999b7cf7b6bc7, problem seem to exist in block 234613 
here’s the test:
diff --git a/src/test/script_tests.cpp b/src/test/script_tests.cpp
index 745df4b..963f097 100644
--- a/src/test/script_tests.cpp
+++ b/src/test/script_tests.cpp
@@ -114,6 +114,25 @@ read_json(const std::string& filename)
BOOST_AUTO_TEST_SUITE(script_tests)
+BOOST_AUTO_TEST_CASE(script_dubious)
+{
+ unsigned char chTo[] = {1, 0, 0, 0, 98, 236, 39, 87, 1, 114, 62, 74, 50, 35, 61, 126, 3, 42, 58, 247, 85, 117, 200, 24, 62, 42, 183, 226, 200, 37, 113, 128, 182, 6, 231, 181, 165, 166, 89, 240, 34, 1, 0, 0, 0, 72, 71, 48, 68, 2, 32, 9, 27, 112, 141, 116, 173, 6, 13
3, 22, 103, 254, 163, 75, 101, 153, 74, 9, 136, 70, 131, 117, 22, 16, 68, 200, 246, 210, 247, 77, 73, 66, 177, 2, 32, 30, 244, 146, 228, 213, 43, 144, 40, 58, 193, 120, 72, 55, 95, 88, 236, 122, 52, 155, 162, 0, 152, 254, 187, 214, 33, 170, 118, 72, 3, 186, 98, 1, 255,
255, 255, 255, 3, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 203, 100, 2, 0, 0, 0, 0, 35, 33, 3, 44, 57, 253, 162, 105, 96, 181, 35, 46, 82, 32, 249, 66, 252, 156, 214, 190, 113, 12, 235, 208, 251, 184, 133, 246, 101, 251, 39, 175, 192, 153, 228, 172, 0, 203, 100, 2, 0, 0, 0, 0, 35,
33, 3, 44, 57, 253, 162, 105, 96, 181, 35, 46, 82, 32, 249, 66, 252, 156, 214, 190, 113, 12, 235, 208, 251, 184, 133, 246, 101, 251, 39, 175, 192, 153, 228, 172, 0, 0, 0, 0, 0};
+ unsigned char chFrom[] = {1, 0, 0, 0, 88, 95, 34, 87, 3, 38, 187, 221, 58, 77, 170, 121, 39, 173, 134, 230, 135, 15, 8, 106, 50, 175, 21, 108, 228, 61, 238, 108, 20, 90, 51, 7, 204, 119, 194, 153, 197, 4, 0, 0, 0, 107, 72, 48, 69, 2, 32, 21, 65, 115, 78, 116, 220, 41, 34, 233, 192, 30, 25, 59, 168, 35, 189, 250, 74, 88, 79, 219, 15, 104, 235, 45, 101, 184, 249, 12, 132, 149, 48, 2, 33, 0, 207, 113, 77, 124, 81, 65, 42, 60, 75, 204, 199, 194, 90, 251, 125, 0, 85, 29, 75, 26, 7, 248, 183, 201, 130, 118, 66, 67, 157, 8, 124, 68, 1, 33, 2, 255, 157, 111, 234, 125, 30, 181, 87, 180, 77, 53, 250, 203, 115, 39, 154, 156, 141, 225, 217, 163, 53, 203, 29, 227, 139, 49, 30, 206, 60, 17, 168, 255, 255, 255, 255, 90, 47, 158, 133, 194, 154, 122, 62, 43, 108, 149, 90, 48, 254, 75, 177, 50, 82, 60, 105, 92, 79, 241, 6, 26, 84, 147, 109, 136, 10, 71, 145, 35, 0, 0, 0, 107, 72, 48, 69, 2, 32, 95, 195, 206, 125, 115, 193, 208, 253, 61, 30, 150, 10, 161, 45, 51, 154, 231, 132, 17, 64, 150, 167, 58, 113, 163, 155, 145, 166, 185, 163, 184, 210, 2, 33, 0, 146, 71, 213, 85, 47, 234, 200, 249, 229, 78, 206, 12, 89, 197, 229, 23, 117, 25, 21, 21, 200, 125, 62, 8, 106, 71, 170, 112, 38, 43, 239, 86, 1, 33, 3, 43, 45, 43, 145, 209, 252, 101, 56, 255, 115, 233, 215, 199, 94, 77, 103, 129, 34, 238, 236, 72, 163, 184, 11, 0, 35, 63, 24, 91, 155, 136, 121, 255, 255, 255, 255, 103, 170, 13, 15, 84, 203, 78, 84, 194, 137, 137, 35, 228, 204, 225, 243, 218, 198, 68, 226, 249, 232, 108, 1, 104, 35, 218, 44, 53, 159, 161, 73, 7, 0, 0, 0, 107, 72, 48, 69, 2, 32, 21, 73, 164, 43, 105, 119, 0, 241, 65, 134, 148, 205, 112, 125, 224, 230, 144, 17, 206, 49, 46, 71, 255, 188, 239, 140, 155, 104, 49, 27, 122, 57, 2, 33, 0, 225, 245, 254, 1, 119, 246, 242, 148, 61, 6, 139, 109, 19, 160, 246, 179, 92, 214, 217, 189, 112, 246, 31, 116, 226, 143, 147, 5, 172, 10, 251, 185, 1, 33, 2, 74, 5, 190, 229, 117, 14, 132, 121, 18, 172, 76, 192, 186, 104, 217, 0, 61, 74, 98, 49, 215, 211, 176, 252, 64, 84, 74, 180, 74, 245, 235, 177, 255, 255, 255, 255, 2, 17, 39, 0, 0, 0, 0, 0, 0, 25, 118, 169, 20, 111, 165, 179, 70, 122, 64, 210, 30, 51, 42, 133, 85, 232, 77, 0, 8, 32, 140, 118, 116, 136, 172, 192, 212, 1, 0, 0, 0, 0, 0, 25, 118, 169, 20, 201, 170, 133, 68, 200, 48, 184, 102, 229, 25, 193, 36, 84, 101, 179, 149, 134, 62, 244, 68, 136, 172, 0, 0, 0, 0, 0};
+
+
+ vector<unsigned char> vch(chTo, chTo + sizeof(chTo) -1);
+ CDataStream stream(vch, SER_DISK, CLIENT_VERSION);
+ CTransaction txTo;
+ stream >> txTo;
+
+ vector<unsigned char> vch2(chFrom, chFrom + sizeof(chFrom) -1);
+ CDataStream stream2(vch2, SER_DISK, CLIENT_VERSION);
+ CTransaction txFrom;
+ stream2 >> txFrom;
+
+ BOOST_CHECK_MESSAGE(VerifySignature(txFrom, txTo, 0, true, 0), "verifySignature should pass.");
+}
+
BOOST_AUTO_TEST_CASE(script_valid)
{
// Read tests from test/data/script_valid.jsonHow to configure the number of connected nodes in the ppcoin.conf file? Some tell me it’s limited to 8 nodes, others seem to configure it as needed.
[quote=“sandakersmann, post:50, topic:3875”]…and if that does not work try this instead:
connect=24.155.192.146
connect=31.178.239.144
connect=51.9.56.81
connect=62.163.212.157
connect=68.105.170.159
connect=74.208.68.83
connect=75.128.211.140
connect=76.74.177.224
connect=78.8.188.249
connect=93.80.182.24
connect=96.243.149.37
connect=98.115.147.74
connect=104.236.180.129
connect=107.170.43.92
connect=107.170.209.76
connect=113.17.90.227
connect=128.199.159.68
connect=142.4.218.174
connect=146.185.137.249
connect=149.210.215.250
connect=158.69.225.143
connect=176.9.16.102
connect=176.31.122.170
connect=178.62.105.210
connect=178.248.97.26
connect=192.95.56.199
connect=198.15.127.242
connect=198.245.63.205[/quote]
I did that, downloaded blockchain and as previously client is stuck at block 234612
[quote=“J2Pool, post:30, topic:3875”]Downloaded the Blockchain 4 times, made sure I was connected to nodes on the current block, stops at 234612, current block is 234769… how do you get this POS Peerunity wallet to come up to date?!? :
Going to point my 55TH back at BTC until the developers figure out a fix…[/quote]
I don’t understand why do you insist on using Peerunity as it is not the official client. As you are a miner it makes no difference to you.
Nothing works for me. I installed peerunity 0.2.1 , redownloaded blockchain and this client also cannot pass through block 234612:
peerunityd getinfo
{
“version” : “v0.2.1”,
“protocolversion” : 60006,
“walletversion” : 60000,
“balance” : 0.00000000,
“newmint” : 0.00000000,
“stake” : 0.00000000,
“blocks” : 234612,
“moneysupply” : 23142153.03457200,
“connections” : 24,
“proxy” : “”,
“difficulty” : 405306951.90868342,
“testnet” : false,
“keypoololdest” : 1462362893,
“keypoolsize” : 101,
“paytxfee” : 0.01000000,
“errors” : “WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue.”
}
I went from Peerunity 0.2.1 to PPCoin 0.5.3, still no luck, it automatically re-downloads about once an hour. this sucks. my pool still down 2 days later, good luck getting any of the miners back… >:(
Yep. Same here. Pool is down since Monday. I cannot even send out payouts.
Try these nodes, please:
addnode=76.74.177.224 addnode=107.170.209.76 addnode=113.17.90.227 addnode=75.128.211.140 addnode=78.8.188.249 addnode=178.248.97.26 addnode=176.31.122.170 addnode=95.176.184.9 addnode=79.92.237.75
i checked with getcheckpoint and getblockhash if i was on the correct chain, the hash matches, im now at block 234749, in the chatbox i read https://chainz.cryptoid.info/ppc/ is on the correct chain, but that one is on block 235017, so one of us is on the wrong chain, but who?
edit:
https://chainz.cryptoid.info/ppc/search.dws?q=233524 also shows the same hash, weird ???