[ANN][GRE] GreenCoin - A Blockchain-Based Social Carbon Ecosystem

[biodieselchris]

Good evening.

I/o coin will be available after you upgrade the source code of the wallet. Unfortunately the developers are not in a hurry to send the updates - therefore, in order to avoid the loss of users, the network is not available.
If you have updated the source code of the coin, send it to us and we will promptly correct the problem on the coin.

Thank you for contacted the support.
                                                                                                              Say thanks   0.00100000 BTC

Was their response to you for I/O coin or GRE? Not sure. In any event, there is no wallet update or new code to send them; Yobit simply needs to reload the block chain. Our best assessment of the problem to date was there was a few wallets with big balances staking and making it look like a 51% attack was occurring, which caused the software prototcol to ban the nodes. For those out there that have balances over ~100M, please don't stake all your coins over this amount or split them into different wallets and stake them on separate machines. This will help avoid the issue in the future.

Ahmed has said he will release a version of the coin that eliminates the PoW at some point in the future, however, which may help to further strengthen the coin (he can provide more details on this).

[biodieselchris]

Good evening.

I/o coin will be available after you upgrade the source code of the wallet. Unfortunately the developers are not in a hurry to send the updates - therefore, in order to avoid the loss of users, the network is not available.
If you have updated the source code of the coin, send it to us and we will promptly correct the problem on the coin.

Thank you for contacted the support.
                                                                                                              Say thanks   0.00100000 BTC

Was their response to you for I/O coin or GRE? Not sure. In any event, there is no wallet update or new code to send them; Yobit simply needs to reload the block chain. Our best assessment of the problem to date was there was a few wallets with big balances staking and making it look like a 51% attack was occurring, which caused the software prototcol to ban the nodes. For those out there that have balances over ~100M, please don't stake all your coins over this amount or split them into different wallets and stake them on separate machines. This will help avoid the issue in the future.

Ahmed has said he will release a version of the coin that eliminates the PoW at some point in the future, however, which may help to further strengthen the coin (he can provide more details on this).

But I think now a discussion with yobit and asking for re-sync from the developers side will make it working.
May be send them the link the latest code even if they are using the latest.

Considering CO2 Price of 0.05+/Kg GRE is worth anywhere above 0.00010000 btc.
http://www.synapse-energy.com/sites/default/files/2016-Synapse-CO2-Price-Forecast-66-008_0.pdf

We should make it happen for that distribution of the coins need to be enhanced.
A tipping system or something like that in Reddit may kick start it.

Also should lobby in other exchanges to list.

Yobit - I'll ping them though I'm still a little nervous given that the network has had variable staking difficulty again recently. Ahmed was planning a new release soon with PoW eliminated (as opposed to just 0 reward) though I don't have timing on that yet. It would be better to have any forking done prior to re-listing or new listings.

Thanks fro the link - that is a great CO2 pricing summary. Interesting reading.

I like your GRE/BTC exchange rate forecast 

[IMJim]

Definitely agree, should wait until updated wallet comes until trying to get on any other exchanges.  Could do more harm than good if problems persist.

[mrbodz]

if anyone has a linux box, it'd be helpful if you could compile the latest source code and see if it syncs OK. I've added some checkpoints on the bad blocks to try and eliminate the issue

[psycodad]

if anyone has a linux box, it'd be helpful if you could compile the latest source code and see if it syncs OK. I've added some checkpoints on the bad blocks to try and eliminate the issue

Seems to work fine:

Code:

{
    "version" : "v1.2.1-52-gbf6bdd4",
    "protocolversion" : 60018,
    "walletversion" : 60000,
    "balance" : x.y,
    "newmint" : 0.00000000,
    "stake" : 6496.11000000,
    "blocks" : 116525,
    "timeoffset" : 0,
    "moneysupply" : 2080156641.00000000,
    "connections" : 4,
    "proxy" : "",
    "ip" : "x.x.x.x",
    "difficulty" : {
        "proof-of-work" : 0.00114389,
        "proof-of-stake" : 26122472.09693514
    },
    "testnet" : false,
    "keypoololdest" : 1452011478,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00000000,
    "errors" : ""
}

[mrbodz]

Awesome so thats narrowed down the issue, Will push out an update to disable POW as soon as i get a chance, aswell as adding in some more checkpoints

Ahmed

[biodieselchris]

For those having issues

add connect=greencoin.crypto-expert.com to your config file

That will ensure you stick to the chain of the main node,

Ahmed

<add connect=greencoin.crypto-expert.com to your config file>
or
<connect=greencoin.crypto-expert.com to your config file>
or
<addnode=greencoin.crypto-expert.com to your config file>

Which one?

I took it as meaning:

Code:

connect=greencoin.crypto-expert.com

though I've just been using:

Code:

addnode=greencoin.crypto-expert.com

and including some of the others I see here (click on "node list"), because I feared the "connect" may be limiting if that particular node was getting DoS?   http://bitcoin.stackexchange.com/questions/10764/what-is-the-difference-between-the-bitcoind-command-line-options-addnode-and

This has been working for me.

[IMJim]

I took it to mean the same as Chris did.  Seemed everything was working fine with my current config, pasted below.....but I now seem to be having a problem connecting to network.  Having sent a handful from one wallet to another earlier today and never saw the transaction come through, I suspect one of my wallets or both had forked again.  Cleared everything but my wallet and config file, but now I seem to have problems getting a connection to network at all.  Playing with it I have managed to get 1 connection a couple times, but that quickly dropped to zero never having pulled any of the block chain at at all.

Here's my exact config file as it's been the last week or two, just in case I too have something wrong in it........


addnode=107.178.113.62
addnode=152.7.70.66
addnode=152.7.71.158
addnode=107.170.102.55
addnode=168.63.241.137
addnode=76.120.208.5
addnode=109.155.62.64
addnode=178.62.224.174
addnode=211.99.134.28
addnode=152.7.70.147
addnode=5.135.108.204
addnode=82.200.205.39
addnode=45.55.173.83
addnode=37.59.13.37
addnode=148.251.67.240
addnode=142.4.209.20
addnode=212.71.235.114
addnode=73.54.141.32
addnode=5.135.108.204
addnode=162.243.118.225:11036
addnode=23.92.53.139:11036
addnode=152.7.70.213:11036
addnode=80.69.77.111
addnode=78.47.219.10:9333
addnode=144.76.225.228:9333
addnode=94.23.59.145:9333
addnode=82.229.26.235:9333
addnode=88.185.82.120:9333
addnode=213.163.64.208:9333
addnode=104.238.140.30:10333
addnode=38.109.218.118:9333
connect=greencoin.crypto-expert.com

[IMJim]

These are the current nodes in blockchain nodelist that's why you are now not able to connect.
This nodelist forks/goes offline frequently so depending on those ips are not safe.
Another thing is that, the greencoin.crypto-expert.com is not accessible for me most of the time.
So inshort this issue need to be address asap.

addnode=101.182.168.159
addnode=111.92.47.27
addnode=212.243.7.37
addnode=37.187.88.140
addnode=45.55.250.196
addnode=50.159.71.79
addnode=50.205.123.50
addnode=50.34.139.183
addnode=59.97.46.149
addnode=67.161.120.48

So are these the ones I should now drop into my config file?  Why do these IPs keep changing and how do we know what should be current in config file?

[mrbodz]

aslong as you've got a connection you dont need to change anything. I've taken the crypto-expert node offline as i do some work on the server and possibly bring up a more permanent node.

Ahmed

[biodieselchris]

These are the current nodes in blockchain nodelist that's why you are now not able to connect.
This nodelist forks/goes offline frequently so depending on those ips are not safe.
Another thing is that, the greencoin.crypto-expert.com is not accessible for me most of the time.
So inshort this issue need to be address asap.

addnode=101.182.168.159
addnode=111.92.47.27
addnode=212.243.7.37
addnode=37.187.88.140
addnode=45.55.250.196
addnode=50.159.71.79
addnode=50.205.123.50
addnode=50.34.139.183
addnode=59.97.46.149
addnode=67.161.120.48

So are these the ones I should now drop into my config file?  Why do these IPs keep changing and how do we know what should be current in config file?

Jim, when there is staking turmoil some of the nodes change if some bad players come. We haven't really confirmed if this is the case or not, but worth pointing out. I mentioned above in the thread that "connect" will dump all of your "addnode"'s in favor of the one connection, so if Ahmed is working on the coin and takes his node down then maybe all of your other addnode's aren't helping you.

I have a client running right now and here are the peers:

Code:

"addr" : "37.187.88.140:11517",
"addr" : "149.202.137.169:11517",
"addr" : "212.243.7.37:11517",
"addr" : "45.55.250.196:11517",
"addr" : "50.34.139.183:11517",
"addr" : "67.161.120.48:11517",

and from the block explorer:

Code:

addnode=111.92.47.27
addnode=212.243.7.37
addnode=37.187.88.140
addnode=45.55.250.196
addnode=50.159.71.79
addnode=50.205.123.50
addnode=50.34.139.183
addnode=67.161.120.48

As far as getting 1 node off and on, there's a protocol written into the software to try and ban "bad players", e.g. if the protocol is sensing an attempt to 51% attack it can ban the node for awhile. I've found if you wait 24 hours and try downloading the blockchain from scratch with  a fresh list of addnodes in the conf file that you get it to sync. Sometimes it stops during the download, and you simply close and re-open to restart the chain downloading. This has been working for me lately.

[Cranky4u]

aslong as you've got a connection you dont need to change anything. I've taken the crypto-expert node offline as i do some work on the server and possibly bring up a more permanent node.

Ahmed

anychance of having the "confirmed fork node" up 100%?

[mrbodz]

there's no confirmed fork. But the main greencoin seed node likely will be up 100% once i've finished the work im doing atm
(Its better for people to connect to each other rather than the main seed node, It'll help to make sure everything isnt relying on a single point)

Ahmed

[Emperor-]

I'm confused!
Can someone just post the .conf that we SHOULD be using?

[mrbodz]

if your NOT connected then copy biodieselchris's configuration file

If you ARE connected, then dont change what you have

AHmed

[Emperor-]

As I said i'm very confused. Chris has posted and quoted so many times with different .confs that I don't know which to use. Can you just report the one we SHOULD be using TODAY? I'm connected but it's always only with "1 active connection" 

[Emperor-]

and remove all the others? I have about 70 in my .conf

[Emperor-]

I replaced my .conf file with the nodes listed above. I deleted everything except my .conf and wallet.dat and restarted. I let it resync it cought up, when i debug and do "getblokccount" it is reporting block 95706 but the website (https://chainz.cryptoid.info/gre/#!network) says block 119854. If I click the "node list" button on the website my ip is listed in the nodes. How is is possible that i'm forked (at 95706) but yet i'm listed as a node on the website?

[Emperor-]

I resolved it. The solution was to delete everything except .conf and .exe let the blockchain download with a new wallet.dat then delete that new wallet.dat and restore my old one. Then I had to force the prog to rescan with the -rescan switch. That seems to have resolved the issue.

[biodieselchris]

I resolved it. The solution was to delete everything except .conf and .exe let the blockchain download with a new wallet.dat then delete that new wallet.dat and restore my old one. Then I had to force the prog to rescan with the -rescan switch. That seems to have resolved the issue.

it's currently a pain in the ass but I'm glad you got it. The pending update will hopefully help greatly.

On the positive side, all of these coins essentially work the same way so having this knowledge is helpful for alt-cryptos in general.