|
What I will do is look at the blockchain to see when the first fraudulent PoS stake took place. Then I will take the most recent release of Pivx that includes zerocoin and fork it before the first fraudulent block. In my opinion this causes the less damage of all options we have.
|
|
|
|
|
There is a bug that allows huge amounts to be generated. Looking how to fix this now. I will probably do a rollback if the chain. Anyone else has suggestions?
Update: Trading and wallet on CoinExchange is suspended
|
|
|
|
Yet another wrong conclusion: "so it was the reason of crashing" There are many (environment specific) reasons why something can crash without even writing to the log. Wallets compiled with wrong dependencies for example can cause segmentation faults. In most cases this would not write any log record to debug.log. How about telling people that you are the fuckup here and not me? PoS blocks are generated and validated just as PoW blocks. This warning message (not even an error) can be caused by someone who modified the source code of the wallet to let it function in their advantage. As you see in the message it did not work. The block was rejected and thats only a positive thing. Nothing special or wrongNow I ask you again: So if your conclusion is "it's problem of codebase or blockchain" then please explain where the problem is. You must be very knowledgeable about blockchains to draw such a conclusion with this level of certainty. Even certain enough to tell people in public that you do not trust me? So show us your knowledge and explain to us why this is a blockchain problem as you conclude.
What is the problem with that? Its just normal behaviour. A block is generated that does not meet the consensus rules and is therefor rejected. Thats it. Nothing special or wrong. So if your conclusion is "it's problem of codebase or blockchain" then please explain where the problem is. You must be very knowledgeable about blockchains to draw such a conclusion with this level of certainty. Even certain enough to tell people in public that you do not trust me? So show us your knowledge and explain to us why this is a blockchain problem as you conclude. You are the first person that tells me that the AMS wallet crashes all the time after switching to PoS. Did you see anyone else complaining about it on the AMS topic? Did you even try to run it on another computer before posting? My guess is that its a local computer problem. The reindex of blocks does not happen here and I have it running on 5 different computers. None of them crash nor require reindex on start.
How that (screenshot) can be local PC problem? it's problem of codebase or blockchain  what generated blocks if AMS already is full PoS ? wallet automatically generates pos blocks so it should not generate wrong blocks that messages is last string from wallet log file, so it was the reason of crashing |
|
|
|
PoS blocks are generated and validated just as PoW blocks. This warning message (not even an error) can be caused by someone who modified the source code of the wallet to let it function in their advantage. As you see in the message it did not work. The block was rejected and thats only a positive thing. Nothing special or wrongNow I ask you again: So if your conclusion is "it's problem of codebase or blockchain" then please explain where the problem is. You must be very knowledgeable about blockchains to draw such a conclusion with this level of certainty. Even certain enough to tell people in public that you do not trust me? So show us your knowledge and explain to us why this is a blockchain problem as you conclude.
What is the problem with that? Its just normal behaviour. A block is generated that does not meet the consensus rules and is therefor rejected. Thats it. Nothing special or wrong. So if your conclusion is "it's problem of codebase or blockchain" then please explain where the problem is. You must be very knowledgeable about blockchains to draw such a conclusion with this level of certainty. Even certain enough to tell people in public that you do not trust me? So show us your knowledge and explain to us why this is a blockchain problem as you conclude. You are the first person that tells me that the AMS wallet crashes all the time after switching to PoS. Did you see anyone else complaining about it on the AMS topic? Did you even try to run it on another computer before posting? My guess is that its a local computer problem. The reindex of blocks does not happen here and I have it running on 5 different computers. None of them crash nor require reindex on start.
How that (screenshot) can be local PC problem? it's problem of codebase or blockchain what generated blocks if AMS already is full PoS ? wallet automatically generates pos blocks so it should not generate wrong blocks |
|
|
|
What is the problem with that? Its just normal behaviour. A block is generated that does not meet the consensus rules and is therefor rejected. Thats it. Nothing special or wrong. So if your conclusion is "it's problem of codebase or blockchain" then please explain where the problem is. You must be very knowledgeable about blockchains to draw such a conclusion with this level of certainty. Even certain enough to tell people in public that you do not trust me? So show us your knowledge and explain to us why this is a blockchain problem as you conclude. You are the first person that tells me that the AMS wallet crashes all the time after switching to PoS. Did you see anyone else complaining about it on the AMS topic? Did you even try to run it on another computer before posting? My guess is that its a local computer problem. The reindex of blocks does not happen here and I have it running on 5 different computers. None of them crash nor require reindex on start.
How that (screenshot) can be local PC problem? it's problem of codebase or blockchain |
|
|
|
You are the first person that tells me that the AMS wallet crashes all the time after switching to PoS. Did you see anyone else complaining about it on the AMS topic? Did you even try to run it on another computer before posting? My guess is that its a local computer problem. The reindex of blocks does not happen here and I have it running on 5 different computers. None of them crash nor require reindex on start. @ale22: Its postponed to a later time, but what makes you think it requires additional work? To make a long story short, I will do additional testing before Solaris gets into PoS. Just to make sure everything works well as we think it does at the moment and will be after switching to PoS. As a developer I don't trust the team, it's clear there are problems and the situation it's pretty scary, they postponed the Zerocoin implementation from february to april but devs are not working, check yourself guys, in GitHub repository ( https://github.com/Solaris-Project/Solaris/) the latest commit was ONE MONTH AGO (Latest commit 5294ddf on 28 Jan), too much in this field, expecially if you have to respect a promise...... I also don't trush that developer KEESDEWIT, he can't make working stable his first coin AMS (Amsterdam Coin) its wallet crashes all the time after switch to PoS and I suppose XLR possible will have same problem since PIVX codebase is not tested enough and need an experienced dev with free time to support it and fix at time, that KEESDEWIT is not such dev obviously. Also how I already said many times - after restart the wallet (AMS, XLR, any coin on PIVX codebase) it needs to reindex all blocks. Well for now it takes ~10 minutes, but in the future (with more blocks) it will take more and more time! It needs to be fixed, so PIVX codebase should be fixed before use on serious projects. |
|
|
|
PoS runs smooth. OP updated. Block explorer back in business. No more chain splits. Now heading for zerocoin implementation. See ya guys.
Thank you Keesdewit, great job. When zerocoin will be implemented ? Do we have to do swap due to this zerocoin ? are you going to have a road-map ? Price is moving up due to these news and also people are staking instead of selling their coins. Peace ! No swap, no difficulty. Just an update that includes zerocoin as PIVX has. |
|
|
|
|
PoS runs smooth. OP updated. Block explorer back in business. No more chain splits. Now heading for zerocoin implementation. See ya guys.
|
|
|
|
This issue could not be found by testing and required immediate action. Dont spit out new mandatory updates day by day - do Proper testing THEN release, for exchanges, pools, node hosting providers that means ALOT of extra work because you guys dont test properly if something works or not that is a sure cut way long term for some to stop running support for your coin, if this keeps repeating... Mandatory update (28 January 2017)
<SNIP>
and what was that issue then? The issue was that under some conditions the miner can pay less masternode reward and keep them theirselve. |
|
|
|
This issue could not be found by testing and required immediate action. Dont spit out new mandatory updates day by day - do Proper testing THEN release, for exchanges, pools, node hosting providers that means ALOT of extra work because you guys dont test properly if something works or not that is a sure cut way long term for some to stop running support for your coin, if this keeps repeating... |
|
|
|
My masternode is stuck at block 151199. I've stopped and restarted it but it still won't move past 151199.
Anyone know what's happening?
Thanks,
-Knightly
Just restart it and it will go back in sync |
|
|
|
My miners keep on digging but my wallet stuck on sync @ block 151199. Restart doesn't make difference. Any solution?
BTW. Good job to dev team!
If possible, can you start the wallet like this: solaris-qt.exe -connect=35.197.213.197:60020 |
|
|
|
is it neccessary to restart the masternode if I get this? ./solaris-cli getblocktemplate error: {"code":-7,"message":"Out of memory"} If it is on the right block height (currently 151247) then its ok to keep it running. |
|
|
|
Message to mining poolsPlease restart your wallet daemon. On our side the "Out of memory" error went away after a restart and we see the block template: {
"capabilities" : [
"proposal"
],
"version" : 3,
"previousblockhash" : "0000000000278d58d97d9ed6b700adb830a34bb2cb5bf5e7bdc5bd1dc988b3ca",
"transactions" : [
{
"data" : "010000000221b4dd36b8eefbb15cae4557034101aa5da182b372d2dd8ab9c955901f425ed6000000006b48304502210092896ef785480c02e45e016ade1939e2caf34ef6c50ce6fe4559083cd78842ac022030c6efa8a63b1d87a6a892eb7ff7795b9140a5c0c52a20b1010340f97e31d6f6012102be7cf1f70801b4c234fd33814aaabcc3ea2ae8d64bd7c9b3612082ab25b4ef04ffffffffc74c66c901d1be33cf8170c9452cc2a8c720ddc65d29cb0daf039fb49fc9c080000000006b483045022100fa02a50f86c699b1b5bdfb211659009acdf7cb40e30290d39fdcc876bf1690750220176ca4835ce5e647806f2d20ee24c7dfbf3b80981f79044d898527861677b088012102533312b68b80d07be75518d41437d51acfa23fc69792b84d4660eb466b6cdaa2ffffffff0206d6080c000000001976a91490347a54449145090730496efb9e7fe4211dec6d88ac49197700000000001976a914b07a3128d378cd9b54be95c39f52ac7a09c8f62f88ac00000000",
"hash" : "da35b7a89767ff96c032416b4f24cb82ac67cabaaa46ab327da42c63f130c7a0",
"depends" : [
],
"fee" : 10000,
"sigops" : 2
},
{
"data" : "0100000003812fafd34e957d8b0cd0b14d16cc117ec6973071dc3d3c2c20a513f6e877c41ab20000006b4830450221009434543d2fb5c8cc688e37419cc6c95f713cf2c7a7ca440ea8a7e8afdd29d3ec0220418a8abcacfc8bba7859ad0a43b241deb94f1ed9d6aeef40a10038756bf8ec910121020035958a16cd12a5d4e80c8013d37b50136d464e12ed2404567936d078971845ffffffff812fafd34e957d8b0cd0b14d16cc117ec6973071dc3d3c2c20a513f6e877c41ac00000006a473044022019c54b2cdded01162ae1b8d0851d7652d68d28b1497a955d06f59ce4093d132802205e68d24db9cea2274008d27b47313190fdc43b1d7b403ee3678cdd68d7d0ba4001210296b1fb4d8c23bff49f26db7ff139152b70df453f8b79e2463f81dd58207aa781ffffffff12bb305a68f5cea3ab6a2a072d422492aab5abefba875356afcbc9f105bd8ec9040000006b483045022100f3c54b83851756fdfd1ef2a36f20ec8481e3dbb878b4d10f18b8fad880ec78370220155da0254f9337080466a8c9bcdc6c2080d3572508e05a24b7f21ab9a4670135012103fdb73c8afff58e23cd0b8f30f15daa3faf21079ffb4b6844759e6c39d5e404eaffffffff02804a5d05000000001976a9141137c97a60487038e4344dbf2451bca6cd2d222988ac4c570f00000000001976a914c0d94a27c488df1dc72736eee17cfe86225ccab788ac00000000",
"hash" : "4846abddf4c8fab73c4058ca0dfb244701d0339e7e7856e1896ede7014b489f0",
"depends" : [
],
"fee" : 66169,
"sigops" : 2
}
],
"coinbaseaux" : {
"flags" : ""
},
"coinbasevalue" : 200000000,
"coinbasetxn" : {
"data" : "01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff0503a04e0200ffffffff025681f207000000002321037e8b3c3869a4dad245e6afb28bc9f080c1057752f531b072e5619983d74a6dabacaa40f903000000001976a9140a8f67456e9f6e99be56a1bc274fee8beb64676888ac00000000",
"hash" : "7b9b58f699e18534a5e4f89e6a9940883fae3303a4aaa9518b3612253ad9543e",
"depends" : [
],
"fee" : -76169,
"sigops" : 2
},
"longpollid" : "0000000000278d58d97d9ed6b700adb830a34bb2cb5bf5e7bdc5bd1dc988b3ca2",
"target" : "00000000009f9300000000000000000000000000000000000000000000000000",
"mintime" : 1517038041,
"mutable" : [
"time",
"transactions",
"prevblock"
],
"noncerange" : "00000000ffffffff",
"curtime" : 1517044497,
"bits" : "1c009f93",
"height" : 151200,
"votes" : [
],
"payee" : "SNFqabwd7p35aWLGrpLax8zpgpbUeRKTjA",
"payee_amount" : 66666666,
"masternode_payments" : true,
"enforce_masternode_payments" : true
}
Still looking at the cause
|
|
|
|
Sync stuck on block 151199. More than an hour nothing happens. I see that it's not just me such problems.
We are looking into this issue at the moment. |
|
|
|
I restarted and still having problem, but another
solaris-cli getblocktemplate
error: {"code":-7,"message":"Out of memory"}
I have the same We are looking into this issue at the moment. |
|
|
|
|
Show Posts
