hi all ...

energy with style ...

thats what we will be bringing soon ...

digital dzyne ...

#crysx #ddz

nice setup - though will get very hot and noisy around mining time ...

can neaten it up - but you will also find that the throttling will happen faster than normal due to the accelerated heat build up - being so close to the wall ...

pokeytex - followed you on twitter ...

now im stalking ... hehehe ...

#crysx

what is it you actually do mate? ...

#crysx

looks like it is guys ...

lets what happens in the next few hours ...

if its an attack - some ddos attacks can last for many hours - if not a lot longer - before they find ways to mitigate it ...

bleutrade has been around a while now - so im hoping for a positive outcome ...

#crysx

aika ...

remove ALL addnodes in the conf ... all of them ...

the only seeds the wallets needs to START syncing from - are the official ones ... they are all on the right chain ...

it will get the current peers from those wallets - and kick in the sync further ... you know that mate ...

do NOT add any nodes to the conf ... just let the latest wallet 1.2.1.0 do its thing ..

we really appreciate your support with this ...

tanx mate ...

#crysx

djm34 created lyra2rev2 ...

he has always had the leading hand with this and the neoscrypt algo ...

cuda and these algos have been his forte for a long time now ...

#crysx

then you are doing it wrong teddybeer ...

crackfoo goes to great measures to make sure his pool ( and epsylon with yiimp -who codes it now ) does not make these mistakes ... it does occasionally happen - but crackfoo is usually on the ball with it ...

as for getting paid in a different coin - thats due to zpool ( actually yiimp is the pool software thats being used ) recognizes your address as a joincoin address ...

to ensure you get paid in egc ( or any coin for that matter ) - make sure you have the paramter in the password area ...

for example ( in ccminer ) ...


notice is used this example to demonstrate a different algo with the same payout and put in the quark port and algo instead - as zpool will payout in egc as long as have the <valid-egc-address> for your username and the correct c= parameter for your payout coin ...

for those using sgminer - or amd equivalent - the same is necessary for egc payout in the username and password parameters ...

#crysx

what wallet version were you using? ...

#crysx

with regards to knowing where you are at - in linux its easy ... windows is a little more complicated to keep track of ...

in linux ...

find the debug log file - which is normally ~/.evergreencoin/debug - and tail ( or mutlitail ) it ...


or ...


in windows ...

find the debug log file and do a similar thing - though windows does not have ve a tail or mutlitail application that i know of ... but you can view the debug.log file - and keep checking it every so often ...

the file will be found in your EverGreenCoin folder where your wallet.dat is located also ...

this debug.log contains ALL the details that the wallet / daemon needs ... do NOT look at it as an issue if there are - errors and disconnections and banning ip etc - this is normal functionality of the wallet / daemon - and the debug.log file is for us that require it to see what is happening so that we can 'debug' any issue that may arise ...

i hope this helps further ...

btw - the latest hash check i have in all seeds are ...


this of course is in linux - so do what you do for your own method of finding the block hash - either through the wallet or daemon ...

i have mine as an executable and service in linux - so i dont have the './' - and dont need it to check ... but mine is not a normal installation either ...

#crysx

that would only cool a percentage of the heat dissipated - as the heat is actually blown out to the extremities of the cards ( either end ) ...

what ever was done - its obviously worked ...

but my curiosity gets the better of me - always ... as pedestal fans cannot be the only things cooling this setup - they are just not powerful enough ...

#crysx

very nice ...

though im curious as to how your cooling works with the gpus so close together ...

i use the same motherboards but gigabyte 750ti oc lp cards ... with the gigabyte 980ti g1 and extreme cards also ... farmamd is completely down and all cards are boxed at the moment ...

my setup is very different and not so compact and use nothing but aluminium and steel with 'customboard' compressed fire retarded shelves - purely due to the heat dissipation ( which im currently working on and developing a much more efficient cooling system ) and temperatures these machine get to ...

its impressive nonetheless ... especially the compactness ...

great work ...

#crysx

agreed ...

it seems to be the best way to work - so if steven is willing do so - he will ...

are you now retired from coding? ... or still at it? ...

we have been looking at the coins we now have in arsenal of projects - and rebasing granite ( and eventually ozziecoin - ozc ) is not going to be an easy task ... these issues with forks are not helping our time frames either ...

but hopefully - it will be put to bed soon ... especially if there is expert help around - experienced in such issues ...

#crysx

tanx mate ...

a huge change coming soon ...

cant wait to get it started ...

#crysx

all the hardcoded seeds mate - at least i can speak on behalf of the granite ones ... they are all on the right chain ...

just compile the latest git and bootstrap it ...

as for the community - the amount of previous version wallets being used amazes me ...

we have compiled the latest windows wallets for all to download ( no osx ones yet ) - and linux / daemon users compile their own from the uptodate git - and yet the versions that show on most of the seeds are early versions ...

the next version of the update to the code should ( and probably will ) include a mandatory update that will change a few things - including a lockout of previous versions for the sake of the blockchain and all this forking - yes i meant that as a pun also ...

if everyone complies and updates the wallet - there is less risk of it forking ... not a complete guarantee - but NO wallet is guaranteed that ...

we are doing a LOT behind the scenes - and as im not as eloquent as steven when addressing these issues - i will say that those who want to dump and leave have every right to - as much as those who want to stay and stick it out in this rough time ...

this is NOT an exact science - so be patient ... thats all ...

if not - there are so many other coins that will take your money and rip you senseless for that money ... many many many out there ... some are legitimate projects - as is this one - with people who give a damn about not only the code and coin and project - but about the community and what needs to be done to minimize the issues that arise - to make it a less bumpy ride FOR the community ...

steven might not say it - and probably wont like me saying it - but stop stressing and bear with us ... but moreso - work with us ... update those damned wallets ... or - dont bother - it really is up to you ...

we will still be here - working on it ...

#crysx

hi all ...

it seems that the restore of the production system for aws was a success - and they managed to get the instance running again ...

well done - and many tanx - aws ...

a new daemon with the latest code has been recompiled and started on the server - so the long process of the blockchain resync has begun ...

being a pool wallet - there are many thousands of transactions that need to be processed within the wallet - and we expect this process to take the better part of 7hours ... this can be seen via the block update on the pool ( current block window - http://grn-pool.granitecoin.com/ ) and when it gets to the latest block shown on the explorer ( https://chainz.cryptoid.info/grn/ ) - the pool will be back in action ...

stratum will be activated in a few minutes ...

if there are any issues that anyone encounters after the sync has finished - please post here and let us know ...

much appreciated for the patience while this issue was being resolved ...

#crysx

hi all ...

the official granite pool is down - at no fault of our own ...

here is the official aws post below ...

-------

[RESOLVED] Connectivity Issues in AP-SOUTHEAST-2
On June 4th at 10:25 PM PDT a significant number of EC2 instances and EBS volumes within a single Availability Zone in the AP-SOUTHEAST-2 Region experienced a loss of power. Beginning at this same time, EC2 API calls in the AP-SOUTHEAST-2 Region experienced increased error rates and latencies as well as delays in propagation of instance state data in the affected Availability Zone. Instances and volumes in the other Availability Zones in the AP-SOUTHEAST-2 Region were unaffected. At 11:46 PM PDT, power was restored to the facility and instances and volumes started to recover. At 1:00 AM PDT, 80% of the affected instances and volumes had been recovered by our automated systems. At 2:45 AM PDT the increased error rates and latencies for the EC2 APIs and the delayed propagation of instance state data were fully resolved. A couple of unexpected issues prevented our automated systems from recovering the remaining instances and volumes. The team was able to fix these issues, and by 8:00 AM PDT, all but a small number of instances and volumes were recovered. Since 8:00 AM PDT our teams have been working to recover these remaining instances and volumes. Most of these instances are hosted on hardware which was adversely affected by the loss of power. While we will continue to work to recover any affected instances or volumes, we recommend replacing any remaining affected instances or volumes if possible. Please see http://aws.amazon.com/instance-help for assistance working with non-responding instances.

-------

what this has done is crash the instance itself - and they have yet to recover the this instance - even though they have fixed their power and production issues ...

this has left us with a predicament that we are trying to resolve currently ...

we are trying to recreate a new instance - based on the last automatic backup of the previous instance ...

this may not work as the backup was made based on the corrupt instance that is what the granite pool is at the moment - a mess ...

we will rebuild a new instance - and currently the new daemon and blockchain are syncing in an effort to retrieve as much transactions as we can ... but this also means that the mpos database may have corrupted also - and as such - transactions could be lost in the process ...

there is no simple solution for this except to restore from an old backup that seems to be still working ( september 2015 ) - and hope that the system can rebuild itself from there ...

we have made quite a few changes since that working backup - with regards to the bonuses for miners and the pool and the settings of the pool ... if the back up works and gets back up and running - we will set the changes back on the pool - and will make sure an alternative measure is taken if indeed this happens again with aws ...

three new pools will be built - each with a different focus - which will happen when the redevelopment of granite starts again in a week or so ... this does not mean they will all be mpos based - but it does mean will have a gamut of pools to work with - regardless of whether this happens again or not ...

support from aws is VERY limited - without paying a large sum of money to get the support - even though its THEIR issue that caused this problem ... so we will work around this within the coming months ...

im still in search of a pool dev to join our ranks - so that these pools will be serviced and maintained and improved - inhouse and on a regular basis ...

a new thread seems imminent - as there doesnt seem to be any way of getting the 'chrysophylax' profile back ...

we do apologize for the hold up - and we will get the pool back up as soon as humanly possible ...

in the meantime - please use the other existing pools to mine granite ( and ozziecoin with some ) ... aikapool - ispace - steakcloud - miningpoolhub - yiimp - zpool ...

if i have left any pools out - ill ammend this post - with links also ... right now - back to the damage control of the pool ...

much appreciated ...

#crysx

awesome grumpy ...

much appreciated ...

retweeting now - and following ...

i appreciate ALL and everyones help ...this actually helps with the support for all the seednodes also - and promotes egc at the same time ...

crypto helping crypto ... these will be the days ...

tanx again ...

#crysx

hehehe ...

those bonus blocks were something huh? ... 100kgrn each in 10 blocks ...

well - ill be putting 70kgrn as part of the promo - and will help in anyway possible ...

tanx much ...

#crysx

watching ...

mining a little also - see how it goes ...

#crysx

its very much appreciated steven - the votes will also be very much appreciated ...

if its ok with you - id like to offer a giveaway of granite through egc and a wallet that you control to give out to anyone interested in gaining some grn as well ...

this will obviously be at you discretion - as this IS the egc thread ...

id be happy to send you 25kgrn for the initial giveaway - if you are happy ( and have the time ) to take that on ...

voting for granite on cryptopia would mean that if we do get in - would mean the second good exchange we will be on ( outside of bleutrade ) ...

once again - very much appreciated ...

#crysx