Topic: [ANN] [PASC] PascalCoin, true deletable blockchain - V3 Hardfork on block 210000 - page 193. (Read 990783 times)
February 03, 2017, 03:51:29 AM
Polo temporarily disables deposit and withdrawal of Pascal.
February 03, 2017, 03:46:41 AM
I cannot get the pool synched back to the "other" chain, looks like not everyone has updated and there are still invalid blocks sent which are rejected by the newer daemon.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
The Clockerror is known since years. The Problem is the DEV... Before i puplished a source of a coin i must review more and more times the code.
The Problem is... the dev is burning real money with his shit code...
How did the dev make any real money on this coin? Get your facts straight
There was NO ICO and NO PREMINE. All the dev has is the coins in wallet 0 and that's all.
First people complained about premines, then they complained about ICOs, and now they complain about coins without premines and without ICOs.
Better read what i write... I didnt say the dev make money... i say he is burning money from us with his shitcode...
Everyday a bug... people loosing the trust and sell... this is money burning because of a not professionel DEV...
Next time you download a piece of software read the Terms. For PascalCoin its
THIS IS EXPERIMENTAL SOFTWARE. Use it for educational purposes only.
I don't understand why you are complaining something tells me you aren't mining PASC or even holding any PASC coins.
February 03, 2017, 03:44:18 AM
Lost 100 Pascal due to this..stupid not to mention also transfers was going from a valid blockchain due to invalid over autopayment in the wrong blockchain maybe lost forever.
How you could reintroduce a bug of bitcoin they had many years ago? This is amateurish.
Ocminer: What about the coins from valid chain that have been transfered due to autopayment when pool was on wrong chain? Are these valid also lost? They should still be there right?
How you could reintroduce a bug of bitcoin they had many years ago? This is amateurish.
Ocminer: What about the coins from valid chain that have been transfered due to autopayment when pool was on wrong chain? Are these valid also lost? They should still be there right?
February 03, 2017, 03:40:20 AM
there is one of the latest block #59292 by suprnova – does it mean that suprnova error is fixed by now?
February 03, 2017, 03:32:39 AM
I cannot get the pool synched back to the "other" chain, looks like not everyone has updated and there are still invalid blocks sent which are rejected by the newer daemon.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
OC miner.
Others miners, just like me, did not have their withdrawals confirmed at Polo. What will be done?
The coins are all lost unfortunately, we've mined hot air on the wrong chain.
February 03, 2017, 03:31:51 AM
I cannot get the pool synched back to the "other" chain, looks like not everyone has updated and there are still invalid blocks sent which are rejected by the newer daemon.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
thanks for the actions taken, 1 hours ago i had Unconfirmed: 249.6551 PASC, does it mean they are gone now ?
Unfortunately yes, all mined on the wrong chain.
February 03, 2017, 03:29:41 AM
I cannot get the pool synched back to the "other" chain, looks like not everyone has updated and there are still invalid blocks sent which are rejected by the newer daemon.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
thanks for the actions taken, 1 hours ago i had Unconfirmed: 249.6551 PASC, does it mean they are gone now ?
yes
February 03, 2017, 03:26:14 AM
I cannot get the pool synched back to the "other" chain, looks like not everyone has updated and there are still invalid blocks sent which are rejected by the newer daemon.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
thanks for the actions taken, 1 hours ago i had Unconfirmed: 249.6551 PASC, does it mean they are gone now ?
February 03, 2017, 03:24:08 AM
I cannot get the pool synched back to the "other" chain, looks like not everyone has updated and there are still invalid blocks sent which are rejected by the newer daemon.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
The Clockerror is known since years. The Problem is the DEV... Before i puplished a source of a coin i must review more and more times the code.
The Problem is... the dev is burning real money with his shit code...
How did the dev make any real money on this coin? Get your facts straight
There was NO ICO and NO PREMINE. All the dev has is the coins in wallet 0 and that's all.
First people complained about premines, then they complained about ICOs, and now they complain about coins without premines and without ICOs.
Better read what i write... I didnt say the dev make money... i say he is burning money from us with his shitcode...
Everyday a bug... people loosing the trust and sell... this is money burning because of a not professionel DEV...
February 03, 2017, 03:23:10 AM
I think what happened was that since not everybody upgraded their wallet to 1.4.3, it was fine until a miner cheated attempted the "time sync hack" and then while on one chain it was accepting blocks while on the other it was blocking any new blocks until 30-90 seconds into the future have passed. So the new block got accepted on one chain but blocked on the other and they got separted.
This happened 10 hours ago, why didn't anyone notice something earlier?
Its alot of wasted hashrate for half a days work.
This happened 10 hours ago, why didn't anyone notice something earlier?
Its alot of wasted hashrate for half a days work.
If this is what happened its neglect on the part of the pools that did not upgrade fast enough , all they had to do was upgrade their wallet, its hard to belive that they did not do this asap
and for the separate chain to get so long if this theory is correct it would seem they took hours to upgrade their wallet.
February 03, 2017, 03:22:04 AM
I cannot get the pool synched back to the "other" chain, looks like not everyone has updated and there are still invalid blocks sent which are rejected by the newer daemon.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
The Clockerror is known since years. The Problem is the DEV... Before i puplished a source of a coin i must review more and more times the code.
The Problem is... the dev is burning real money with his shit code...
How did the dev make any real money on this coin? Get your facts straight
There was NO ICO and NO PREMINE. All the dev has is the coins in wallet 0 and that's all.
First people complained about premines, then they complained about ICOs, and now they complain about coins without premines and without ICOs.
February 03, 2017, 03:21:33 AM
I cannot get the pool synched back to the "other" chain, looks like not everyone has updated and there are still invalid blocks sent which are rejected by the newer daemon.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
OC miner.
Others miners, just like me, did not have their withdrawals confirmed at Polo. What will be done?
February 03, 2017, 03:19:21 AM
Please don't feed the trolls.
You 're cancelling our ignore status.
You 're cancelling our ignore status.
February 03, 2017, 03:18:42 AM
What will Polo now do? they accepted allready wrong coins...
I think Polo did not accept wrong coins. I made a withdrawal from Suprnova to Polo and even TXid does not exist on Pascal Blockchain explorer:
TX id = 00000000C86F0400721500003030424530353939314236443146434245343043
Edit:
One valid TX id before fork:
00000000C86F04006B1200004232374244393939444144363432313334353634
... well, a lot of wasted energy if we won´t get our coins from supernova 2 our wallets.
DUDE! Enough
Shit happens and bastards win (like usual).
February 03, 2017, 03:18:24 AM
I cannot get the pool synched back to the "other" chain, looks like not everyone has updated and there are still invalid blocks sent which are rejected by the newer daemon.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
The Clockerror is known since years. The Problem is the DEV... Before i puplished a source of a coin i must review more and more times the code.
The Problem is... the dev is burning real money with his shit code...
February 03, 2017, 03:18:01 AM
now its better to sell... no one knows what Polo will do... I think they prefer suprnova
I think most traders dont realize what is happening and we will see a big crash today...
The Coin was just a joke and dev is not good... Polo hyped it and dev has now a big problem...
Everyday somethink goes wrong and other must do the job because dev dont know how to handle it...
I think one day Dev will run away
Everyday somethink goes wrong and other must do the job because dev dont know how to handle it...
I think one day Dev will run away
Let the market crash
What will Polo now do? they accepted allready wrong coins...
LOL the funny think is Price is still high at Polo... Normally it must be on the Floor now...
DUDE! Enough
February 03, 2017, 03:15:15 AM
I cannot get the pool synched back to the "other" chain, looks like not everyone has updated and there are still invalid blocks sent which are rejected by the newer daemon.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions
I'll try to get switched to a backup node running the old version.
February 03, 2017, 03:14:24 AM
guess it's official
suprnova stopped sending work to miner
suprnova stopped sending work to miner
... though the cheaters won !
You know the saying: Shit happens :-)
LOL the funny think is Price is still high at Polo... Normally it must be on the Floor now...
February 03, 2017, 03:12:22 AM
guess it's official
suprnova stopped sending work to miner
suprnova stopped sending work to miner
... though the cheaters won !
You know the saying: Shit happens :-)
LOL the funny think is Price is still high at Polo... Normally it must be on the Floor now...
February 03, 2017, 03:11:47 AM
What will Polo now do? they accepted allready wrong coins...
I think Polo did not accept wrong coins. I made a withdrawal from Suprnova to Polo and even TXid does not exist on Pascal Blockchain explorer:
TX id = 00000000C86F0400721500003030424530353939314236443146434245343043
http://explorer.pascalcoin.org/findoperation.php?ophash=00000000C86F0400721500003030424530353939314236443146434245343043
Edit:
One valid TX id before fork:
00000000C86F04006B1200004232374244393939444144363432313334353634
http://explorer.pascalcoin.org/findoperation.php?ophash=00000000C86F04006B1200004232374244393939444144363432313334353634
Jump to: