[ANN][GRE] GreenCoin | On Bittrex now!

[ncsupanda]

My wallet has been saying 'No block source available' for more than two days. It's stuck at block 148599. Do I need to update the wallet, and if so from where?

Please do a getinfo and give me the version, please.

Version 80602

Ah, protocol version. Begins with a 7.

[ncsupanda]

btw any binary update ? i run 80602 / 70002

The updated wallets have been added to the OP. Should be version 70006. 70006 is fixed, and will deny any connections to protocol version 70005.

Please be sure you are using the new wallet, 70006 and NOT 70005.

Note when I say version here I am referring to PROTOCOL version. I believe the wallet version is now 90100 (in class and can confirm soon).

[ncsupanda]

thx, i'm ok now, 90100 / 70006
what about weminealtcoins.net/com ?

We are still working on both the back and front end, but you can view it as we work on it at:

weminealtcoins.com:3333/static/

[Stinky_Pete]

OK, so my current protocol is 70002

I downloaded from the link at http://www.grcoin.com/pages/help and got 70002 again.

I've downloaded from the mega link at https://bitcointalk.org/index.php?topic=636548.0 even though the large type at the top of the page states "There will be a hard fork soon to finish implementing Merged Mining. The wallet links will be updated as soon as our official pool has changed over. Thank you for your patience." Are the wallet links updated? How am I supposed to know I am getting the most recent release? Even putting the version somewhere would help.

The mega version keeps giving a 'Failed to read block' error when I try to start the wallet. I still have no idea which version I have, but the icon is different. I am going to backup the wallet, delete the blockchain and download again.

I'm not impressed.

[ncsupanda]

OK, so my current protocol is 70002

I downloaded from the link at http://www.grcoin.com/pages/help and got 70002 again.

I've downloaded from the mega link at https://bitcointalk.org/index.php?topic=636548.0 even though the large type at the top of the page states "There will be a hard fork soon to finish implementing Merged Mining. The wallet links will be updated as soon as our official pool has changed over. Thank you for your patience." Are the wallet links updated? How am I supposed to know I am getting the most recent release? Even putting the version somewhere would help.

The mega version keeps giving a 'Failed to read block' error when I try to start the wallet. I still have no idea which version I have, but the icon is different. I am going to backup the wallet, delete the blockchain and download again.

I'm not impressed.

You have to delete the chainstate, blocks, and database folder. The error is caused by conflicting blocks; just redownload the blockchain by deleting those folders and reopening.

I have't written out my formal report on the hard fork; I'll push it as soon as I can. I went ahead and updated the links, apologies for not mentioning it; You have the correct version if the icon is different (I will reflect that change in the OP).

I'm sorry that you aren't impressed; I've sacrificed the last two days of my life (I'm a senior in college) including skipping class to make sure that our coin doesn't get stuck in the hard fork (which it did - and I then fixed it). I hope that you gain more confidence as I work harder with our pool ops to improve the coin. Thank you.

[ncsupanda]

thx, i'm ok now, 90100 / 70006
what about weminealtcoins.net/com ?

We are still working on both the back and front end, but you can view it as we work on it at:

weminealtcoins.com:3333/static/

tested, running smooth...
but payout stats show double amount,
we all know why but maybe better fix that

It will be added to the list to fix on github; It's a p2p script fix. Will do, thank you!

[ncsupanda]

Hey all,

I wanted to describe the issues that took place over the last 72 hours, what was done to fix them, and where we will go from here.

At block 148,599 the GreenCoin network changed to our newest version, which was 90100, protocol version 70005. We merged from our beta test branch to our main branch, generated the Wallets for all platforms, and switched. What we didn't know was that there were issues with the test branch. Mainly:

-Rather than test on a testnet in our test branch, one of my co-developers generated a brand new genesis block, which led to our blockchains disagreeing (this led to us being stuck at block 29).
-Also, we did a difficulty recalculation in our beta branch that was pushed to our main branch.

Both of the above errors were fixed, and those details can be found in the commits on our main branch. We also were able to (with the help of ahmedbodi, thank you again) update GreenCoin to where we now have a custom P2Pool that works with our foundation function (our 50% split).

I am monitoring the coin as we move forward and I'm excited for GreenCoin to have this new functionality. Merged Mining will begin at block 150,000, and note that if you're on Protocol version 70005, you need to update as the new wallet will deny any incoming connections from you (yet you can still connect to the old version).

Let me know of any concerns, and thank you for being patient!

[biodieselchris]

OK, so my current protocol is 70002

I downloaded from the link at http://www.grcoin.com/pages/help and got 70002 again.

I've downloaded from the mega link at https://bitcointalk.org/index.php?topic=636548.0 even though the large type at the top of the page states "There will be a hard fork soon to finish implementing Merged Mining. The wallet links will be updated as soon as our official pool has changed over. Thank you for your patience." Are the wallet links updated? How am I supposed to know I am getting the most recent release? Even putting the version somewhere would help.

The mega version keeps giving a 'Failed to read block' error when I try to start the wallet. I still have no idea which version I have, but the icon is different. I am going to backup the wallet, delete the blockchain and download again.

I'm not impressed.

Sorry I haven't pushed the compiled wallets to the website server yet, I'll get this done ASAP.

[Vitalogy]

Why you all updating your pools, can you make the minimum difficulty = 128? This is to make it compatible again with NiceHash. See this post for details: https://bitcointalk.org/index.php?topic=562238.msg8777393#msg8777393

[ncsupanda]

Why you all updating your pools, can you make the minimum difficulty = 128? This is to make it compatible again with NiceHash. See this post for details: https://bitcointalk.org/index.php?topic=562238.msg8777393#msg8777393

The vardiff on our MPOS pool was set like this; I honestly wasn't sure what our p2pool is set as. I'll be sure that the vardiff is set as suggested. Thank you.

[james42]

I'm trying to setup a pool, is there anything I need to do in particular to get it to accept blocks that I've found?

[ncsupanda]

I'm trying to setup a pool, is there anything I need to do in particular to get it to accept blocks that I've found?

Yes, and it depends. What kind of pool (p2pool, MPOS, etc)?

Note that at this time you have to use a special stratum and special p2pool. I will link the p2pool here, and the regular stratum is under development.

https://github.com/ahmedbodi/p2pool-dev-fee

[james42]

So unlike a standard coin that takes a percentage, you need special stratums to manage it

[ncsupanda]

So unlike a standard coin that takes a percentage, you need special stratums to manage it

Correct, because of the fact that it isn't a standard charity value. Instead, the stratum has to allow for the sending of the 50% as part of the coinbase, instead.

[Freenhult]

Why you all updating your pools, can you make the minimum difficulty = 128? This is to make it compatible again with NiceHash. See this post for details: https://bitcointalk.org/index.php?topic=562238.msg8777393#msg8777393

The vardiff on our MPOS pool was set like this; I honestly wasn't sure what our p2pool is set as. I'll be sure that the vardiff is set as suggested. Thank you.

The problem with setting the min-diff that high is that there are still a significant amount of miners that mine with less than 1 MH/s out there on alt-coins. There are very few people that mine with paid-miners or have large rigs. I have set the starting diff to 128, and the low end to 32; however many times people don't understand why they are not submitting shares with their GPU.

P2pool doesn't have a vardiff strategy, it simply has a set share level relative to the difficulty I believe. Ergo, anyone with low power will likely submit few shares and those with big miners will see a good amount. If you're worried about paying for miners and mining on the pool, then point them to the p2pool address, otherwise I'll likely leave the Stratum stuff set as it is. Keep in mind, p2pool is LONG-Poll.

[Freenhult]

I'm trying to setup a pool, is there anything I need to do in particular to get it to accept blocks that I've found?

If you message me, I can help you get setup.

[ncsupanda]

At this point, everyone MUST be operating on the new version. Merged Mining has begun so the chain is effectively different.

If you haven't, update NOW.

Thanks all.

[ncsupanda]

surprise, no payouts from weminealtcoins.com:3333 blocks 1501**
everything was fine not long before,
i still see my address on the list, but no coins coming last hour

Can you give me your address?

Also, we are updating the block explorer.

[ncsupanda]

surprise, no payouts from weminealtcoins.com:3333 blocks 1501**
everything was fine not long before,
i still see my address on the list, but no coins coming last hour

Can you give me your address?

Also, we are updating the block explorer.

pm'd

Looking into it. Also, please let me know your intended payout and I will personally pay you the GRE that you lose as a result of this error. Thank you.

[ncsupanda]

surprise, no payouts from weminealtcoins.com:3333 blocks 1501**
everything was fine not long before,
i still see my address on the list, but no coins coming last hour

Can you give me your address?

Also, we are updating the block explorer.

pm'd

Looking into it. Also, please let me know your intended payout and I will personally pay you the GRE that you lose as a result of this error. Thank you.

forget it, not much, you may easily see my 30MH on the pool graph,
i stopped for couple hours then tried for about 40 min
to check if everything is fine, and suprisingly it's not.
the question is what's up with the pool or my wallet or what?

GreenCoin has a very complicated subsidy function that hasn't been used, and what people don't know is that the pool software actually determines how to send payments (and in the case of a p2pool actually does the math to distribute those payments).

If you have that 30 MH/s, I suggest solo mining and ensuring you get the coins that way. I am working to improve the function, which we can see here:

Code:

 greencoin=math.Object(
+        P2P_PREFIX='fbc0b6db'.decode('hex'),
+        P2P_PORT=11036,
+        ADDRESS_VERSION=38,
+        RPC_PORT=21036,
+        RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
+		'greencoinaddress' in (yield bitcoind.rpc_help()) and
+		not (yield bitcoind.rpc_getinfo())['testnet']
+        )),
+        SUBSIDY_FUNC=lambda height: __import__('gre_subsidy').GetBlockBaseValue(height),
+        POW_FUNC=lambda data: pack.IntType(256).unpack(__import__('ltc_scrypt').getPoWHash(data)),
+        BLOCK_PERIOD=63, # s
+        SYMBOL='GRE',
+	CONF_FILE_FUNC = lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'greencoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/greencoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.greencoin'), 'greencoin.conf'),
+        BLOCK_EXPLORER_URL_PREFIX='https://ccc.hashaxe.com/explorer/block/',
+        ADDRESS_EXPLORER_URL_PREFIX='https://ccc.hashaxe.com/explorer/address/',
+        TX_EXPLORER_URL_PREFIX='https://ccc.hashaxe.com/explorer/tx/',
+        SANE_TARGET_RANGE=(2**256//1000000000 - 1, 2**256//1000 - 1),
+        DUMB_SCRYPT_DIFF=2**16,
+        DUST_THRESHOLD=1e8,
+	CHARITY_ADDRESS='AD3325CA903AC90A5D936358C1C34609A030DFEB'.decode('hex')