[POT]PotCoin - Banking for the Legal Cannabis Industry ✦ ✦ ✦Grow With Us ✦ ✦ ✦

[CartmanSPC]

http://xpool.net is on the right chain.

[1714925467]

1714925467

[1714925467]

1714925467

[1714925467]

1714925467

[Panadacoin]

potcoin is disabled on bittrex is this due to the update?

Let's hope that. I am really interested as in when the POS becomes active.

they need to hurry up and get things fixed

[sigwo]

I'm not sure there is a 'right' chain. I have the same block height as potchain.net but show the error message in the daemon....

[GlassyEyed]

looks like cann is underfire again https://bitcointalk.org/index.php?topic=1139399.0

[rdyoung]

i run goldmin.es and we have the newest wallet, however it looks like the chainz block explorer is not up to date.

are we the only pool that updated?!

http://potchain.net/  is up and running

Am I the only one that site is acting funky with? What I assume is the potcoin logo on the right hand side is broken and the latest txs never load.

[elitemobb]

I get the same thing. Logo image is broken. Block height is showing 930664. But thats in line with my desktop wallet and altnuts mining pool.

EDIT: It does seem the block height is tracking properly.

[ny2cafuse]

I created a pull request on github to block old wallets via a minimum protocol version check.  The version was changed in previous commits, but then changed back.  Not quite sure why that happened.

https://github.com/potcoin/Potcoin/pull/1

-Fuse

Anyone on the old wallet could rent mining rigs and fork the chain.  Merge the pull request, recompile the wallets, and we can stop worrying about all this "right fork" confusion.  Force wallets to be on the right fork.

-Fuse

[clarkjhaley13]

So just downloaded the new wallet and have it syncing. If I try to add a conf file though it gives me the wallet qt closed error.

Any help on this please?

[tolikkk]

So just downloaded the new wallet and have it syncing. If I try to add a conf file though it gives me the wallet qt closed error.

Any help on this please?

get up this in its config file and try again


addnode=122.57.97.7
addnode=128.199.177.5
addnode=137.135.57.119
addnode=146.185.131.162
addnode=148.251.19.213
addnode=171.100.31.47
addnode=178.188.27.146
addnode=178.32.251.114
addnode=178.33.209.212
addnode=188.126.216.12
addnode=188.33.197.183
addnode=192.99.35.133
addnode=201.229.74.147
addnode=201.229.80.55
addnode=204.152.215.162
addnode=217.66.158.41
addnode=24.201.11.124
addnode=45.50.58.160
addnode=45.55.13.246
addnode=45.55.171.187
addnode=45.55.77.26
addnode=46.101.240.105
addnode=46.188.1.45
addnode=67.164.34.115
addnode=71.170.82.181
addnode=71.49.170.87
addnode=72.173.141.238
addnode=75.71.16.15
addnode=78.56.42.41
addnode=83.222.45.113
addnode=84.215.6.143
addnode=86.161.219.21
addnode=88.198.10.165
addnode=92.30.247.86
addnode=96.234.202.80

[richiela]

    "version" : 80701,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "blocks" : 931868,
    "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."

We're still blocked until this is resolved...

thanks,
richie@bittrex

[rdyoung]

    "version" : 80701,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "blocks" : 931868,
    "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."

We're still blocked until this is resolved...

thanks,
richie@bittrex

According to redrhino on reddit, this is essentially a false flag. Its showing that error because someone is still running the old version, if you use the flag -disablesafemode when running the daemon it will turn that message off.
https://www.reddit.com/r/potcoin/comments/3f7wqs/oopsit_did_it_again/ctm5x4w

[ny2cafuse]

    "version" : 80701,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "blocks" : 931868,
    "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."

We're still blocked until this is resolved...

thanks,
richie@bittrex

According to redrhino on reddit, this is essentially a false flag. Its showing that error because someone is still running the old version, if you use the flag -disablesafemode when running the daemon it will turn that message off.
https://www.reddit.com/r/potcoin/comments/3f7wqs/oopsit_did_it_again/ctm5x4w

And if you adjusted the minimum protocol version, the old clients wouldn't even connect to the new chain.  You wouldn't have to worry about old nodes, malicious or otherwise.

-Fuse

[rdyoung]

   "version" : 80701,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "blocks" : 931868,
    "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."

We're still blocked until this is resolved...

thanks,
richie@bittrex

According to redrhino on reddit, this is essentially a false flag. Its showing that error because someone is still running the old version, if you use the flag -disablesafemode when running the daemon it will turn that message off.
https://www.reddit.com/r/potcoin/comments/3f7wqs/oopsit_did_it_again/ctm5x4w

And if you adjusted the minimum protocol version, the old clients wouldn't even connect to the new chain.  You wouldn't have to worry about old nodes, malicious or otherwise.

-Fuse

Thank you for telling me what you have posted multiple times, going so far as to quote yourself just to mention it again.

Have YOU contacted any of devs directly? Your not going to get anywhere by repeatedly spamming this thread with that idea. YOU need to reach out to them and offer to help.

Here is another thought, why don't you compile your own version of the wallet/daemon with that protocol and see if anyone else is willing to upgrade. Or, ya know, you could wait until POSv kicks in and this will be a moot point as POW blocks won't be accepted by the upgraded clients.

[ny2cafuse]

Thank you for telling me what you have posted multiple times, going so far as to quote yourself just to mention it again.

Have YOU contacted any of devs directly? Your not going to get anywhere by repeatedly spamming this thread with that idea. YOU need to reach out to them and offer to help.

Here is another thought, why don't you compile your own version of the wallet/daemon with that protocol and see if anyone else is willing to upgrade. Or, ya know, you could wait until POSv kicks in and this will be a moot point as POW blocks won't be accepted by the upgraded clients.

They would have gotten a notification for the pull request.  People keep talking about forks and out of date node issues.  The protocol change was made in the code and then removed, for whatever reason.  So while POSV would be a nail in the old node coffin, the fact of the matter is that people can't move coin off the exchanges right now, including me.  Additionally, the excitement of the changes being made, and the increased interest in supporting POT, is waning because there is no clear message being made about the issues people are reporting.

I've made a suggestion.  Yes, it was numerous times... good for you for being able to keep track of things.  However, I've had a vested interest in POT off and on again over the last year or so, and I'd just like to know that things are being handled properly.  Fact of the matter is that using the -disablesafemode flag doesn't resolve the alleged fork issues right now, or the possibility of launching a fork attack on the chain.

Just my $0.02.

-Fuse

[rdyoung]

Thank you for telling me what you have posted multiple times, going so far as to quote yourself just to mention it again.

Have YOU contacted any of devs directly? Your not going to get anywhere by repeatedly spamming this thread with that idea. YOU need to reach out to them and offer to help.

Here is another thought, why don't you compile your own version of the wallet/daemon with that protocol and see if anyone else is willing to upgrade. Or, ya know, you could wait until POSv kicks in and this will be a moot point as POW blocks won't be accepted by the upgraded clients.

They would have gotten a notification for the pull request.  People keep talking about forks and out of date node issues.  The protocol change was made in the code and then removed, for whatever reason.  So while POSV would be a nail in the old node coffin, the fact of the matter is that people can't move coin off the exchanges right now, including me.  Additionally, the excitement of the changes being made, and the increased interest in supporting POT, is waning because there is no clear message being made about the issues people are reporting.

I've made a suggestion.  Yes, it was numerous times... good for you for being able to keep track of things.  However, I've had a vested interest in POT off and on again over the last year or so, and I'd just like to know that things are being handled properly.  Fact of the matter is that using the -disablesafemode flag doesn't resolve the alleged fork issues right now, or the possibility of launching a fork attack on the chain.

Just my $0.02.

-Fuse

I am not a programmer, but my understanding is that all of this will be moot when the transition to POSv happens. Maybe they should contact the reddcoin devs and ask for help, I don't remember this happening with the POW->POSv transition with rdd, then again, laudney, the lead dev for rdd is the one who designed POSv, so he may have had an advantage in that. Yes, right now someone can fork the chain, but what does an intentional fork get them? other than a headache for those that get onto the wrong chain. They are also on a clock, we have only a couple of weeks left before it transitions and after that the forking of the chain shouldn't be possible.

[ny2cafuse]

I am not a programmer, but my understanding is that all of this will be moot when the transition to POSv happens. Maybe they should contact the reddcoin devs and ask for help, I don't remember this happening with the POW->POSv transition with rdd, then again, laudney, the lead dev for rdd is the one who designed POSv, so he may have had an advantage in that. Yes, right now someone can fork the chain, but what does an intentional fork get them? other than a headache for those that get onto the wrong chain. They are also on a clock, we have only a couple of weeks left before it transitions and after that the forking of the chain shouldn't be possible.

Which is why plugging any holes now is important.  If the devs want to gain some community support and backing during this transition, they need to keep things tidy.

I just want a word as to what the plan is.  If the devs are going to ride it out, then so be it.  If they want to clean things up, awesome.  They just need to make it known what their stance is on what's going on.

-Fuse

[rdyoung]

I am not a programmer, but my understanding is that all of this will be moot when the transition to POSv happens. Maybe they should contact the reddcoin devs and ask for help, I don't remember this happening with the POW->POSv transition with rdd, then again, laudney, the lead dev for rdd is the one who designed POSv, so he may have had an advantage in that. Yes, right now someone can fork the chain, but what does an intentional fork get them? other than a headache for those that get onto the wrong chain. They are also on a clock, we have only a couple of weeks left before it transitions and after that the forking of the chain shouldn't be possible.

Which is why plugging any holes now is important.  If the devs want to gain some community support and backing during this transition, they need to keep things tidy.

I just want a word as to what the plan is.  If the devs are going to ride it out, then so be it.  If they want to clean things up, awesome.  They just need to make it known what their stance is on what's going on.

-Fuse

It appears their stance is MUM. They refused to answer any questions as to the status of POSv when being called out on it on reddit, despite one of the devs or friend of the devs being a regular contributor the subreddit. They do claim that they are working on a fix, what exactly that entails, they haven't said.

[richiela]

For the record... we will not disable safe mode to run the wallet.  It is there for a reason and disabling is bad security practice.  As for the comment about forks, it's detrimental for an exchange, not just an inconvenience.  We are in contact with the devs who have told us a fix is coming.  Until then, the wallet will remain disabled here;  please do not ask us to re-enable unsafely.  We will not do it.

Thanks,
richie@bittrex

[marcetin]

PotCoin crowd funded node is up!

https://bitnodes.net/node/194-135-85-149/

Cheers!

[nubbins7]

I don't no whats going on with the windows wallet but i had made a withdrawal from a mining pool
and the POT did not make it to my wallet well there be an updated wallet soon?