Lex Pool (A rewritten pool based on uray source)
-
This post is deleted!
-
This post is deleted!
-
@Merlin44 implicit here doesn't matter. the project is released by uray under the gnu public license. because lex has contributed to the project his code is under the license, but he retains the copyright to it. you need to acknowledge the copyright to his code as well as uray's. the size of the contribution doesn't matter.
https://www.gnu.org/licenses/gpl-faq.en.html
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
Uhh, what is going on here again. Merlin44 please make your own thread about your fork in the software section. I will push all the messages about you and your fork there.
Disclaimer: I haven't read through it yet.I cleaned up and banned Merlin because he didn't want to open an own thread for his fork. I gave him the chance, but he denied. He showed me clearly it is not about to improve the code.
If anybody wants to see his own hidden posts here again - send me a message.
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
And the Ban Hammer has spoken!
-
Frankly I'm glad I dont have to waste my time and read through the diatribe but I will say there is a failed attempt
to discredit @Lexicon for his awesome work and to deter him from continuing.
For THOSE who lurk:
Not gonna happen...Cheers! and support/use Lex's code.
:-)
-
Boom
well now thats over...
just uploaded another commit. this one adds the x-header creepsky for creepskys fork on the uray miner hes been working on

im also working on another bug fix. this ones related to api calls. and should get it finished tonight.
and a quick thank you for the guys on this thread supporting me
-
@Lexicon said in Lex Pool (A rewritten pool based on uray source):
Boom
And IP Blocked from my systems .....
-
hi all,
recommended mandatory update has been pushed.
this update limits the use of post requests over port 80. before this update any post requests made to a uray pool for any api call was forwarded straight to the wallet. and the result relayed back to whoever was sending the request.
this plugs that huge hole. its never a good idea to fully open up an API like this. i beleive the code was originally written by uray. and cant believe i missed it up untill now. but lates better than never i suppose


