I'm trying to point my S9's at NiceHash for SHA256 mining. Unfortunately I'm seeing a large percentage of rejects (around 30%). Most of the rejects seem to be duplicate shares: 2016-11-07 08:26:41,291 INFO [Pool-NiceHash-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 32768.0) from s92@192.168.80.102 on NiceHash. Booo !!!!. Error: JsonRpcError [code_=22, message=Duplicate share., traceback=null]
2016-11-07 08:26:45,510 INFO [Pool-NiceHash-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 32768.0) from s91@192.168.80.101 on NiceHash. Booo !!!!. Error: JsonRpcError [code_=22, message=Duplicate share., traceback=null]
I tried to work around this by enabling and disabling extranonce and by setting a reasonable minimum difficulty. I also tried both syntaxes for specifying the extranonce to NiceHash (i.e. adding "#xnsub" and "/#xnsub" to the URL). I've also tried a single worker behind the proxy, in case the issue is related to multiple workers. Nothing I change seems to help. When I point the S9s directly at NiceHash, they work fine with almost no rejects. But of course that defeats the purpose of a proxy. Any recommendations for getting this proxy to work with NiceHash? i have been using this proxy for a long time now with the nicehash system ... i have not had any real issues - except for the idle disconnection issues which has been fixed ... though the proxy works - it has never been tested with any asic miner ... what is the s9 - scrypt? ... sha256d? ... which port are you mining on? ... how long are you mining for? ... are these errors immediate or after sometime? ... these are some of things i think will answer the issues ... at least i hope  ... #crysx was there a fix for the idle disconnection issue? yup ... it turned out that it was not from the stratum proxy at all - it was the nicehash stratums banning the ip for 10mins at a time ( or longer if you stay connected ) for having no miner through the open connection ... only way you can get around that is to connect and disconnect the miner when idle ... or - get whitelisted on the nicehash list ... the will whitelist your ip - only if you have a good reason to have the connections active there all the time ... otherwise the stratum just puts you on the ban list ... #crysx |
|
|
|
i decided to recompile with your changes to the test node - and its all working exceedingly well ... its the only system that has these latest changes ... and this is after all the seednodes were compiled to 1.4.0.0 ... so tanx a heap for the extra work that i now have to do for all the seednodes ... ... steven was having a bit of a giggle when he was telling me about the changes - and also suggested i wait before the full upgrade to the latest for all the seednodes ... so im lucky its only the single test node im upgrading  ... hehehe ... Hi crysx, I figured I would share with you and others precisely how I build a hardened EverGreenCoin daemon since the guidance in doc/build-unix.txt had led me astray. Here is a diff of my hardened makefile.unix. --- makefile.unix 2016-11-10 12:08:16.596121994 -0600
+++ makefile.gentoo 2016-11-10 12:08:17.796194427 -0600
@@ -4,8 +4,10 @@
# x15 Version by mammix2 (mammix2@hotmail.com)
-USE_UPNP:=0
+USE_UPNP:=-
USE_IPV6:=1
+STATIC=1
+PIE=1
LINK:=$(CXX)
ARCH:=$(system lscpu | head -n 1 | awk '{print $2}')
@@ -91,7 +93,7 @@
#
-DEBUGFLAGS=-g
+DEBUGFLAGS=
ifeq (${ARCH}, i686) 'ldd evergreencoind' returns linux-vdso.so.1 (0x00007ffdce1fc000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fa3c241d000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa3c2200000)
libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/libstdc++.so.6 (0x00007fa3c1e89000)
libm.so.6 => /lib64/libm.so.6 (0x00007fa3c1b83000)
libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/libgcc_s.so.1 (0x00007fa3c196c000)
libc.so.6 => /lib64/libc.so.6 (0x00007fa3c15bf000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa3c2621000) 'scanelf -e evergreencoind' returns TYPE STK/REL/PTL FILE
ET_DYN RW- R-- RW- /usr/bin/evergreencoind 'hardening-check evergreencoind' returns evergreencoind:
Position Independent Executable: yes
Stack protected: yes
Fortify Source functions: yes
Read-only relocations: yes
Immediate binding: yes evergreencoin.conf recommendations noirc=1
synctime=0
cppolicy=strict The server must be running ntpd if synctime=0 has been set within evergreencoin.conf. Static Libraries of OpenSSL, Boost, GMP and ZLIB must all be available in order to build EverGreenCoin statically. Notice: No UPnP support has been included (per the makefile specification). The above process is optimized for a headless evergreencoind binary which uses only the command line. Best Regards, -Chicago this is how egc daemons are built on all the seednodes - statically and without upnp support also ... this was a necessity for me as the redhat based systems ( centos 7 x64 - in this case ) had crippled openssl implementations ... where redhat legal removed the ecc required to build the daemons ... so i was left with no choice but to build statically every time ... its a better implementation in my opinion also ... so the scripts we use - build the applications first - then the daemon ... and all of them build at reasonably the same time ... but those extra conf parameters are not used ... id be interested to see how well they work with the current test node i have running with 1.4.1.0 ... tanx for all the info - those parameters in the conf are new to me ... so its always good to learn something new ... ... #crysx |
|
|
|
hi all ... a few moments ago - the official goldblocks pool underwent some changes ... the new daemon was compiled and transitioned over to the pool ... this transition was seamless and downtime was no more than 7seconds ... this caused very minor disruption to mining and was so tiny a time windows - that the pool didnt even skip a beat ... the stratum was still receiving hashes and as soon as the daemon came back on line - all was back to normal again ... so now the pool is running on the latest code ... below are some of the stats copied directly from the admin page of the pool - so please excuse the tardiness of the data ... further - the umbrella we are now working from is fully functional - and the dns addresses are now changed - but the ports stay the same ... so when mining - the new addresses are as follows ... change from
http://goldblocks.granitecoin.com/
to
http://goldblocks.chainworksindustries.com/
that is the only transition that is required - as all the other settings are exactly the same ... this change is permanent - and the granitecoin.com domain and dns will be switched off within the coming week ... so please miners - change your addresses - as the granitecoin.com domain will no longer be used for the mining addresses ... it will be dedicated purely for the granite project / coin - and will be part of the greater http://chainworksindustries.com/ website when it comes online - after the new granite site is fully published and completed ... goldblocks will have a place in the cwi site also ... all the mining pools for our own projects and the projects we support as well as pools we like to set up internally - will be set up from the following address ... http://pool.chainworksindustries.com/
@darkgold - please change these settings accordingly in the website ... these changes are permanent ... we are also in the process of rebuilding the entire stratum back end - which will be announced shortly on our thread ... https://bitcointalk.org/index.php?topic=1563601 ... the dev that is doing the full rebuild is the developer that built the python stratum backend originally ... much appreciated - and happy mining ... #crysx thanks @crysx, we appreciate that. I made a changes to website and op, there is one small change that need to be changed: In pool, in help page, are still old addressess and stratums: http://goldblocks.chainworksindustries.com/index.php?page=gettingstartedhttp://goldblocks.chainworksindustries.com/index.php?page=gettingstartedtanx ... ill get to that very soon ... please note to all - the http://goldblocks.granitecoin.com/ address will cease in 7days time ... so please change the address settings in your miner to http://goldblocks.chainworksindustries.com/ ... much appreciated all ... and very much appreciated darkgold ... update - all done ... we will need to change a few things on there when there is a chance - as the info from the pool page is outdated ... willing to help darkgold? ... #crysx |
|
|
|
hi all ... if all goes well - we should have 12 seednodes up and running by tomorrow afternoon ( gold coast - queensland - australia time ) and a total of 16 from the cwi network fully functional ... always in contact with steven - always working together - always keeping an eye on whats happening ... we will strengthen this backbone - one full node at a time - one constantly running daemon at a time - one open wallet at a time ... together - we make good on the strength that is the community and network that keeps this project moving forward ... have some patient - and hope that everything works out with the compilations and the syncs ... we really are doing our best to keep up ... and of course you have an awesome dev overseeing all this ... #crysx Hi crysx, This is pretty great! Thank you so much. The new nodes will help a great deal towards consensus. Checkout the latest commits to the repository for patches to enable Position Independent Executable builds, for hardening, if you are so inclined. Best Regards, -Chicago hi chicago ... i just did ... nice work mate ... i decided to recompile with your changes to the test node - and its all working exceedingly well ... its the only system that has these latest changes ... and this is after all the seednodes were compiled to 1.4.0.0 ... so tanx a heap for the extra work that i now have to do for all the seednodes ... ... steven was having a bit of a giggle when he was telling me about the changes - and also suggested i wait before the full upgrade to the latest for all the seednodes ... so im lucky its only the single test node im upgrading ... hehehe ... the seednodes - this is somethign that has been discussed and im sure steven will be bringing to attention when he has the tiem ... but for now - i can mention that the seednodes that were originally slated are no longer 12 - they are in total 18 currently - with tthe provision to go to a full 25 when the other systems are provisioned ... further to that - when the deal with the isp is complete - they will all be located in separate datacenters - globally ... which means that ALL the cwi seednodes for granite - ozziecoin - evergreencoin - berncash - donationcoin will be globally distributed and be a failover if any one or more seednodes go down ... even if dns is down - the peers contained in current peers.dat files will still be able to locate all the seednodes via ip address ... the only ones that will be affected in such a circumstance are the new wallet users ... and even then - steven always seems to have an updated peers file - and a complete uptodate snapshot ... so if all else fails - that can still be a major support for newcomers ... this is the basis that we want with the cwi infrastructure - to make sure that nothing we can foresee in the future issues will taint the accessibility of the wallets ... thats the goal anyway ... so as soon as steven gives the go ahead - all seednodes will be recompiled to the latest source - and then we need to discuss the coinage for constant staking of the seednodes and the consequential support for the blockchain ( in the worst case scenario ) as a result of the weight the seednodes would have ... in any case - im sure steven will attend to these and many more things when he has the time ... anyway - paperwork for the new contract i start on monday ... then off to compile another two coins for support within the cwi infrastructure ... #crysx |
|
|
|
hi all ... a few moments ago - the official goldblocks pool underwent some changes ... the new daemon was compiled and transitioned over to the pool ... this transition was seamless and downtime was no more than 7seconds ... this caused very minor disruption to mining and was so tiny a time windows - that the pool didnt even skip a beat ... the stratum was still receiving hashes and as soon as the daemon came back on line - all was back to normal again ... so now the pool is running on the latest code ... below are some of the stats copied directly from the admin page of the pool - so please excuse the tardiness of the data ... v1.1.0.0-g32a928e 70049 60000 30 OK 468301 1
Host Protocol Identity Connected Traffic
62.47.197.122:49605 70049 GoldB:1.1.0 11/11/2016 17:58:54 0.173 MB
104.172.24.79:49580 70049 GoldB:1.0.0 11/11/2016 17:58:56 0.041 MB
104.131.21.16:27920 70049 GoldB:1.1.0 11/11/2016 17:59:06 0.031 MB
82.39.101.246:27920 70049 GoldB:1.0.0 11/11/2016 17:59:13 0.035 MB
144.76.238.2:27920 70049 GoldB:1.0.0 11/11/2016 17:59:23 0.024 MB
81.103.212.107:27920 70049 GoldB:1.0.0 11/11/2016 17:59:24 0.040 MB
108.61.10.90:27920 70049 GoldB:1.0.0 11/11/2016 17:59:25 0.037 MB
75.170.220.154:27920 70049 GoldB:1.0.0 11/11/2016 17:59:45 0.062 MB
5.189.180.41:46904 70049 GoldB:1.1.0 11/11/2016 17:59:50 0.034 MB
149.56.154.75:40160 70049 GoldB:1.1.0 11/11/2016 17:59:55 0.025 MB
87.203.111.224:15569 70049 GoldB:1.0.0 11/11/2016 18:00:00 0.048 MB
62.47.197.122:49731 70049 GoldB:1.0.0 11/11/2016 18:00:35 0.051 MB
86.203.35.239:51488 70049 GoldB:1.0.0 11/11/2016 18:00:37 0.034 MB
93.104.209.17:27920 70049 GoldB:1.0.0 11/11/2016 18:00:47 0.029 MB
178.219.162.59:19287 70049 GoldB:1.0.0 11/11/2016 18:01:05 0.036 MB
79.141.118.75:61510 70049 GoldB:1.0.0 11/11/2016 18:02:46 0.034 MB
45.249.89.180:54107 70049 GoldB:1.1.0 11/11/2016 18:03:15 0.023 MB
92.211.203.187:51994 70049 GoldB:1.0.0 11/11/2016 18:03:52 0.008 MB
82.149.20.231:49975 70049 GoldB:1.1.0 11/11/2016 18:04:38 0.098 MB
79.141.118.75:61772 70049 GoldB:1.1.0 11/11/2016 18:04:41 0.026 MB
71.93.116.184:50919 70049 GoldB:1.0.0 11/11/2016 18:05:09 0.026 MB
77.119.130.245:3963 70049 GoldB:1.0.0 11/11/2016 18:05:33 0.033 MB
94.195.9.15:64805 70049 GoldB:1.0.0 11/11/2016 18:06:35 0.125 MB
93.79.198.241:13094 70049 GoldB:1.0.0 11/11/2016 18:06:53 0.026 MB
79.17.161.36:61187 70049 GoldB:1.0.0 11/11/2016 18:09:24 0.011 MB
14.207.63.191:5819 70049 GoldB:1.0.0 11/11/2016 18:10:41 0.010 MB
98.255.181.199:61376 70049 GoldB:1.0.0 11/11/2016 18:12:07 0.009 MB
62.36.238.107:54959 70049 GoldB:1.0.0 11/11/2016 18:12:16 0.009 MB
188.230.177.121:60662 70049 GoldB:1.1.0 11/11/2016 18:13:05 0.005 MB
202.80.213.147:63348 70049 GoldB:1.0.0 11/11/2016 18:14:23 0.007 MB
further - the umbrella we are now working from is fully functional - and the dns addresses are now changed - but the ports stay the same ... so when mining - the new addresses are as follows ... change from
http://goldblocks.granitecoin.com/
to
http://goldblocks.chainworksindustries.com/
that is the only transition that is required - as all the other settings are exactly the same ... this change is permanent - and the granitecoin.com domain and dns will be switched off within the coming week ... so please miners - change your addresses - as the granitecoin.com domain will no longer be used for the mining addresses ... it will be dedicated purely for the granite project / coin - and will be part of the greater http://chainworksindustries.com/ website when it comes online - after the new granite site is fully published and completed ... goldblocks will have a place in the cwi site also ... all the mining pools for our own projects and the projects we support as well as pools we like to set up internally - will be set up from the following address ... http://pool.chainworksindustries.com/
@darkgold - please change these settings accordingly in the website ... these changes are permanent ... we are also in the process of rebuilding the entire stratum back end - which will be announced shortly on our thread ... https://bitcointalk.org/index.php?topic=1563601 ... the dev that is doing the full rebuild is the developer that built the python stratum backend originally ... much appreciated - and happy mining ... #crysx |
|
|
|
This coin has a nice amount of connections. Maybe will be fine.  we have been keeping nodes open with our own fork for over a year - and i think the other team has also ... thats the only reason ... apart from that - it would be a nice thing ... but i have no faith in the original dev - only our team ( 'theteam' ) and the other team actually have any stability ... we were all going to work together - but we knew the original dev was a greedy scumbag - that would ruin the project as soon as we all started ... thankfully though - its thevictimofuktyranny that owns all the coins - and not the original dev ... so all good so far ... but ho hum ... thats life ... #crysx |
|
|
|
I'm trying to point my S9's at NiceHash for SHA256 mining. Unfortunately I'm seeing a large percentage of rejects (around 30%). Most of the rejects seem to be duplicate shares: 2016-11-07 08:26:41,291 INFO [Pool-NiceHash-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 32768.0) from s92@192.168.80.102 on NiceHash. Booo !!!!. Error: JsonRpcError [code_=22, message=Duplicate share., traceback=null]
2016-11-07 08:26:45,510 INFO [Pool-NiceHash-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 32768.0) from s91@192.168.80.101 on NiceHash. Booo !!!!. Error: JsonRpcError [code_=22, message=Duplicate share., traceback=null]
I tried to work around this by enabling and disabling extranonce and by setting a reasonable minimum difficulty. I also tried both syntaxes for specifying the extranonce to NiceHash (i.e. adding "#xnsub" and "/#xnsub" to the URL). I've also tried a single worker behind the proxy, in case the issue is related to multiple workers. Nothing I change seems to help. When I point the S9s directly at NiceHash, they work fine with almost no rejects. But of course that defeats the purpose of a proxy. Any recommendations for getting this proxy to work with NiceHash? i have been using this proxy for a long time now with the nicehash system ... i have not had any real issues - except for the idle disconnection issues which has been fixed ... though the proxy works - it has never been tested with any asic miner ... what is the s9 - scrypt? ... sha256d? ... which port are you mining on? ... how long are you mining for? ... are these errors immediate or after sometime? ... these are some of things i think will answer the issues ... at least i hope ... #crysx |
|
|
|
Thanks for the node list(s)....  if permanent seeds are what is required to give wallets ease of sync - and the dev i swilling to hardcode them - then please pm me and we can work something out ... this will stop the search for nodes dead in its tracks - so no one has to go looking for them due to issues with sync ... this can be setup before the next version of the wallet is released - and there will be no need for messing around with the cong file ... in fact it would be better to have all the 'addnode' parameters deleted from the conf file altogether if the dev contacts and negotiates to hardcode ... tanx ... #crysx |
|
|
|
as for the excess coins ... my opinion has been and always will be the same ... put them all in a dev fund - and use them for progression of the project ... web - dev payments - purchases - infrastructure - etc ...
I still insist on burning most of them and saving some as bounty fund (the results of the poll agree with me ) The number is discussable, maybe we should open another poll for it. 6 million is fine, in my opinion. i express the same opinion when this subject arises - so my opinion wont change ... it will be up to you and the community of course - but burning coins as far as im concerned should only be done when exchanging other coins ... but - again - its the majority consensus ... ill be working on the backend tomorrow ... so a few things will change - but will be rock solid when its finished ... #crysx |
|
|
|
b3.poolinat0r.com - info on recent disabled jobs
I have fixed the problems on the pool. Nothing realy bad happened, it just needed some manual fixes. Payouts are reenabled and all found block since stopped jobs are payed/accounted.
Thank you for the info and work. http://b3.poolinat0r.com/index.phphi limx ... could you add me to skype mate? ... we need a chat i think ... tanx ... #crysx |
|
|
|
if you want good solid support - GIVE good solid support ...
I don't give linux support. Instead of writing long messages you can fix the makefile yourself. I have told you that you need to rename some files. Here is a youtube video to get you started: https://www.youtube.com/watch?v=Q1Lnp_Xx7z4I have users who use the spreadminer #9 on linux without any problems. ok sp ... so be it ... tanx for the links also ... #crysx |
|
|
|
yup ...
I have never promised linux support, but in the spreadminer I was kind to supply the sourcecode so that you could compile it yourself. That is pretty good for a 0.1BTC donation (back in january 2015 when bitcoin was trading below $300) For $30 you got a profitable miner that I updated for free 9 times. Take a look at Claymore and the linux support for Zcash. It is not there any more. i dont give a damn about the claymore miner ... YOU promised support for the spreadminer and free upgrades ( for the donors ) - including the source - no matter HOW MUCH was paid for it ... that is what you should uphold now - you word sp ... simple ... you just recently advertised in the spreadcoin thread ( and i backed you of course ) - that your miner is still the fastest and you are looking for 0.1btc ... it doesnt matter HOW MUCH btc was worth back then or now ... you are STILL asking 0.1btc for it ... so you are NOT supporting a product that you will supply to those that are in the mining for spreadcoin ... wtf sp? ... you cant just go back on your word and go back on the promises made to people that PAID for the miner ( YOUR CUSTOMERS ) and expect no backlash of any sort ... ive been waiting for these miner upgrades to be sent to me for how long now sp? ... 7months ... thats how long ... and still nothing ... because YOU are too busy with building yourself a fortune and forgetting who helped ( and still to this day are helping ) you get there ... you really dont think im going to just lay here do you? ... i was one of the major contributors to your evolution from code pimp to farm mogul ... you even mentioned that a couple of times in this thread - way back ... if you want good solid support - GIVE good solid support ... instead you do this ... thats the only way to do business ... had you stuck to your word instead of your guns - you have a very very very loyal following ... instead - you constantly get this crap now ... dont think im enjoying this - its a pain in the bum ... BUT - i want a miner i can readily compile that i paid for over and over again when i supported every one of your 'optimized private' miners - even when i didnt use them due to windows ... yet i continued to support and pay for these things i never used ... loyalty sp - something you obviously know nothing about - is what i work with on a daily basis ... learn it - and one day you will have a powerful adversary turn friend ... #crysx |
|
|
|
|
hi all ...
im posting here to keep up to date with it all ...
interesting to see how this will all pan out ...
as for the excess coins ... my opinion has been and always will be the same ... put them all in a dev fund - and use them for progression of the project ... web - dev payments - purchases - infrastructure - etc ...
#crysx
|
|
|
|
btw - did mention a few hundred times already that the spreadminer-spmod9 STILL doesnt compile ... how about supplying a product that works - when we pay for it and boost your farm cashflow ...
You payed for speadminer #1 and got 8 free updates. In the latest update you need to fix the makefile because some of the filenames have changed. I have made a cuda 8.0 build for you for free. (exe file) 1. Compare the visual studio project file from version 7 to version 9 2. Add the changes in the makefile by renaming the files like I have done in the Windows project file It will take you 10 minutes. yup ... and tanx for supporting your donors and supporters all the way with KEEPING your word sp ... free upgrades for the life of spreadminer ... upgrades that DONT compile ... upgrades that are supposed to work almost out of the box ... upgrades that YOU are to support - not ME ... you even sent other donors to ME to help them compile YOUR mistakes ... seriously mate - you really need to check yourself ... and see the type of person you have become ... the sp i supported and knew BACK THEN was a real person caring for the community - working for a real corporation - helping those in need - not palming off jobs to others that YOU were supposed to support ... saying you are sending stuff over that NEVER arrive ... why on earth do you think i stopped supporting you? ... why do you think SO many here have turned their back on you? ... you are NOT the person i met here a while back ... back then - the real sp was a decent person ( rs - yes i have always known who you are but have never exposed it ... just out of respect ) ... i dunno who the hell you are now mate ... charging for products that you have no longer any need for ... bragging about your farm - yet still charging for apps ... seriously ... just supply a product worth compiling and fulfill your duty to paying 'donors' for products that are supposed to work ffs ... you want to always chant about all the work you have done - but NEVER mention ANY of the hours and testing and time off mining and work that WE - the testers - have done to help you debug these damned miners ... wake up mate - smell the crap you have just surrounded yourself with ... #crysx |
|
|
|
Yeah, it fairly obvious what the research is doing. Ripple style consolidation of large volume of coin in one place - that one place operates in non-profit or low profit directive mode to provide price stability to the wider investor community. Compared to various POS % rates or values by varying staking period. Exchange listing funding and maintenance. POS wallet.bat peak maintenance methods. Reliability of Wallet-QT over long-term staking. Simultaneously, to zero developer input or activity. Looking at different rise and fall events to stimulate random interest of non-investors. Learnt a lot from this coin nice ... i too have learned a great deal ... hence - chainworks industries - and all that cwi encompasses ... especially granite ... the new rebase is a massive one - with things that have never been seen before in project ... ive also learned that there are many many many disgustingly unscrupulous devs out there - that have nothing better to do than tear shreds off a community that supports them ... this is why chainworks industries was born - and why my team and i did not follow through with the full redevelopment of this coin ... we all could have worked well together - but there was no way we were willing to work alongside a shady dev who still had control of the threads and coins ... now at least we know its NOT the dev that has the coins - its you ... so feeling much better about that now ... anyway - lets see how this all goes now ... i started with the coin redevelopment AGES ago - but stopped as soon as the original became the common thief ... and he had the gall to ask for money to release the thread and the git ... pffft! ... as if he would - even if we HAD the bct to pay for it ... anyway - onwards and upwards ... see you around mate ... ... #crysx |
|
|
|
To keep supporting the ones that paid you.
And after I release #4, the opensource will be optimized by somebody else. And you still loose.  No, dear. WE still loose, especially if we pay YOU to keep developing kernels for YOUR farm. Who really losses it's you; 0.2 (didn't remember if I paid you more before, another 0.1 for another kernel..) instead of a potential collaboration in the long term, I am creating a farm in iceland and needed honest devs. You will be totally delisted from my projects, regarding mining and any other venture. Good for you indeed Take care, you won't get any more dime from me. As bensam said, your words doesen't make any sense, anymore (like this thread) nikolaj - i did this a long time ago ... sp got 'donation' after 'donation' from me - as well as mining - as well as buying private miners - as well as massive amounts of time and effort testing these miners he has released ... and he STILL refuses to fix the spreadminer-spmod9 saying that its good exercise for me to fix his mistakes in the makefile ... come on ... sp - read above mate ... look and learn that the community members that once were behind you 100% - are now totally against you because you have become the ONE thing you said you would never be - one hell of a greedy bastard ... the last couple of months have been great - as we have made leaps and bounds surpassing your hashrates with our miner ... for MONTHS ... you heard right ... ive asked and asked and asked for your help and for the sources / miners you promised - until i gave up ... which is what built that farm you have - completely off our backs ... and you wont even supply us a miner that compiles? ... you have a broken source and you supply that? ... then tell me i need to fix it? ... hehehe ... if that isnt pure and utter gluttony on your part - i dunno what is ... retire - and live off what you make from this farm of yours ... because soon - thefarm and the design and the hashrate - is going to make your look a kiddies toy ... im just waiting for the 1080ti to be released before i bulk buy and build ... btw - did mention a few hundred times already that the spreadminer-spmod9 STILL doesnt compile ... how about supplying a product that works - when we pay for it and boost your farm cashflow ... nikolaj - i would be happy to discuss further developments with you mate ... you sound like an honest hard worker ... let me know - maybe we could do something here ... #crysx |
|
|
|
I don't see anything weird here tbh
...
Yes, all the seednodes do appear fine also. I too noticed a lower connection count about 24 hours ago but, only < 10 fewer than the normal on average across the seednodes. Though they do seem to be returning to normal levels now. I have moved a more recent snapshot to our web server, http://evergreencoin.org/729617snap.zip should anyone need it. Snapshotting is much faster than re-syncing over the network. Though you do have to download 1 large (~500 MB) file first. Follow these instrustions, but use the more recent snapshot I have linked as opposed to the one linked in those instructions. I have moved a fresh peers.dat with 38 peers as well to http://evergreencoin.org/peers.dat should that be useful to anyone with a low connection count. Remember, 1) close your wallet. 2) overwrite peers.dat 3) launch your wallet. 4) patience. Sorry to those experiencing any issue. Measures are being actively taken to further strengthen the network and myself and community members are investigating in-depth and monitoring closely. Of course, thanks to those assisting and offering help to others. hi all ... if all goes well - we should have 12 seednodes up and running by tomorrow afternoon ( gold coast - queensland - australia time ) and a total of 16 from the cwi network fully functional ... always in contact with steven - always working together - always keeping an eye on whats happening ... we will strengthen this backbone - one full node at a time - one constantly running daemon at a time - one open wallet at a time ... together - we make good on the strength that is the community and network that keeps this project moving forward ... have some patient - and hope that everything works out with the compilations and the syncs ... we really are doing our best to keep up ... and of course you have an awesome dev overseeing all this ... #crysx |
|
|
|
Just to let you guys know, I'm still here, and am looking forward to the future of Spreadcoin.
I still have a couple thousand Spreadcoins and I might buy quite a bit more than that in a few months.
Anyway, keep up the great development Georgem.
Hey, e1ghtSpace How is sunny Australia? If you can get an interview with Craig Wright ( I think he lives in Sydney) and have him talking about SPR for about 15 minutes on your YouTube channel, I'm sure we can get a 5,000 SPR bounty together Seriously, good to see you around these parts again ditto mate ... im in gold coast now - but hi ya anyway ... as for craig - what a dumbass ... im always here - always watching - occasionally commenting ... and as for mining ... ahem ... #crysx |
|
|
|
again? ...
and so the crap doesnt stop ...
amazing ...
so who has been compiling the MASSIVE amount cypher over the last year? ...
just curious as to when the 'development' will happen - and when that dump of over 2million cypher will happen also ... all this in the hands of ONE person ...
yup - we can read the blockchain too you know ...
good luck getting anything outta this - when the pump and dump happens ...
we have moved on to much much MUCH larger projects - that have DECENT and RELIABLE devs ...
ill still watch what happens here ...
#crysx
Those belong to me, not the developers! Bought them up as a research project on the longevity of POS systems and wallet-qts. But, if you read the ANN - it would be pretty obvious. read the ann? ... hahaha ... ok mate ... like it says anything different to when the dev shafted the first - and second - and then third - and tried the fourth ... now the thread is reopened - and he is doing what exactly? ... developing? ... making advancements? ... making adjustments? ... making some noise to bring the costs up and then drop a bomb on people? ... at the very least these coins are in your pocket mate - so im at least partially at ease with the fact that they are not in his hands ... so how has the research gone? ... what was the end result? ... and after almost a year - what is the outcome? ... would be interesting to see what you were researching actually ... i know you are invested in many coins - especially driving the slg project as hard as you can ... so if you used this coin as a research project - what was the basis? ... im interested ... #crysx |
|
|
|
This is one big project, following...
you know it ... considering you are the one designing the graphics and building the website ... #crysx |
|
|
|
|
Show Posts
