|
the blockchain is totally stuck. This happens from time to time (based around whatever error is in the coin or too few stakers or whatever the problem is) and will probably continue to be an issue off and on until the fork. But hang in there.
|
|
|
|
|
thanks Ahmed. We are still trying with this project. Hopeful for a good hard fork and then we can do the exchanges and make some in-roads on marketing the concept further.
|
|
|
|
|
It sounds like maybe someone else would be better at running this coin experiment than me.
|
|
|
|
|
The blockchain looks like it got stuck on block 122057 about 10 hours ago. Ahmed thinks there is a difficulty algo issue and was committed to working on it after spending some time on another coin. This looks like it will go forward in the near future. I'll let him update about that, and we are all looking forward to it.
My sensibility on yobit: the deposit has been closed for quite some time and there probably exists some total amount of coin within their trading ecosystem that is a small microcosm of all existing GRE that traders are just sending back and forth. I have little doubt that with a strengthened coin update, along with the marketing component and web upgrades (facelift and ability to handle orders of magnitude more users) that I've been working on with other collaborators, we could back up the project with real value in a matter of a couple of months or less.
|
|
|
|
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. |
|
|
|
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: "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: 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. |
|
|
|
|
I forked off last night. Woke up this morning with a bunch of question mark transactions and then staking once a minute. Noticed the block height didn't match the explorer's. Will clear out the Roaming folder tonight, re-download anm see if it re-syncs.
Has anyone forked off recently? The network appears to be fine anyway.
|
|
|
|
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: connect=greencoin.crypto-expert.com
though I've just been using: 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-andThis has been working for me. |
|
|
|
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.pdfWe 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  |
|
|
|
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). |
|
|
|
Chris has noticed that restarting greencoin client numrous times can force it to sync further along.
Ahmed
correct, and I got the Foundation wallet synced so I made the payouts in arrears over the last 2 days. It may be helpful if folks that want to trade ping Yobit and let them know they can re-sync at this time. |
|
|
|
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
thanks ahmed, hoping the syncing issues die down a bit. I've held onto the daily payouts since 6/2 because I've been going through a long stretch where i cannot connect the wallet. I've been downloading a new block chain but it gets stuck around block 95,000. Will keep trying. |
|
|
|
Lol that was massive  I just hope the buy orders will follow the big leap  Looks like we are holding above .10 cents. That might be the new resistance test. Well I'm pretty sure that there will be some greedy ppl who will do the best they can to crash the price (they already started doing it), but sooner or later the true value/price of Solarcoin will become a fact. We are getting more people involved with the concept of the coin - the team behind it is great so far. Once the big players get involved and invest some big money everything will come in place - there wont be any cheap Solarcoins for sure. We are slowly getting there  I hope Poloniex and other big exchanges add us soon. Btw ~30 BTC injection atm and we will be trading at ~0.50 USD. So little BTC for such a big leap Anyway we will see what tomorrow will bring - anything can happen, but so far so good  Really really exciting year not only for Solarcoin, but for Bitcoin too - I can't wait for the halving next month SLR could easily be $1-5 per coin, considering it's incentivizing $150 worth of power (1 MWh @ $0.15 per kWh). It does put a lot of trust into the reserve though, which even at $1 has a valuation of $97.5B. So SLR upside resistance on price, IMHO, has a lot to do with the transparency of the Foundation and the massive trust one must place in an organization not to misappropriate coins, need to secure the private keys from theft, etc. Even at $0.10, you're looking at 97.5 * $0.1 = $10B in reserve coin value, which is a lot of responsibility. |
|
|
|
Some of the wallets on YoBit are on the corrupted blockchain; transactions to these are lost. YoBit is currently resetting their chain...
are folks able to use Yobit again? I don't trade the coin so let me know. |
|
|
|
Hey guys I think something went wrong with the hard fork. I havn't been giving much attention to my wallet since I installed the new update: Here is my problem. Before the update everything worked 100% with no issues. However now (even though I am running the correct version of the wallet) I continuously get a message at the bottom saying: Mandatory update to 2.1.1 I already deleted everything in my %appdata% folder and completely reinstalled the wallet twice. Staking works and I am getting stakes although less frequent and much larger than usual. Anyway does anyone else have this issue. I also tried deleting the peers.dat file but no luck. For some reason The wallet thinks im not on the newest version. I sent some coins to another wallet and checked on the block explorer so im on the correct chain for sure. but it's sill weird.  some of the peers are on version 7000 still, for example: "addr" : "106.71.248.46:60835"
|
|
|
|
I didn't stake for a while (since early May). I mostly had 0.1's to 0.5's coming in earlier this month, and now it's like 1.2-2.0 coins per stake.
anyone notice anything odd with staking?
I notice with getinfo the coin supply has been the same today: "coinsupply" : 34145512 and doesn't match the block explorer: 34,309,432 SLR (but this isn't a clickable # so not sure where it comes from) https://chainz.cryptoid.info/slr/I suppose the explorer is Total Supply (with reserve) - 98B, but if so it's off by 500k or so. I'm just curious how it works. I thought maybe I was off on another chain, but the heights match. |
|
|
|
|
I didn't stake for a while (since early May). I mostly had 0.1's to 0.5's coming in earlier this month, and now it's like 1.2-2.0 coins per stake.
anyone notice anything odd with staking?
|
|
|
|
If you use the daohub.org to create DAO via Eth, they want you to send ETH to some addy, 0x123.....
So who owns the private key for the newly created DAO and how do you access them? I feel like ETH just sent off into the ether ... I'm still a little confused.
Don't worry. As long as you use the right kind of wallet (i.e. myetherwallet or MIST) then the DAO becomes automatically associated with your sending address and is associated with the private key of your send address. Only you should have control of that private key. The whole process is automated. When you are using an exchange like Bittrex then obviously they are in charge of the private key so you have to trust them. I c, thx! |
|
|
|
|
If you use the daohub.org to create DAO via Eth, they want you to send ETH to some addy, 0x123.....
So who owns the private key for the newly created DAO and how do you access them? I feel like ETH just sent off into the ether ... I'm still a little confused.
|
|
|
|
|
Hey folks, regarding some of the connection rejection issues we've had, it may have something to do with the system clock of certain nodes. System time being off beyond the allowable drift is a known issue. The fact that the block time is off explains one of the curious errors we've been seeing in the debug.log file: “block with too little proof-of-stake." Time is part of the equation for work.
If everyone who has a client running could make sure their system clock was accurate that would be helpful.
|
|
|
|
|
Show Posts
