[ANN] Eloipool - FAST Python3 pool server software - GBT/stratum/dyntarget/proxy

[tomaszsz]

is eloipool  resistant to this type of sabotage? 


https://bitcointalk.org/index.php?topic=94392.msg1043633#msg1043633

[1715057246]

1715057246

[1715057246]

1715057246

[1715057246]

1715057246

[Luke-Jr]

is eloipool  resistant to this type of sabotage?

No, that problem's inherent in Bitcoin itself.

[tomaszsz]

so any PPS pool is vulnerable not only eloipool  ?

[Luke-Jr]

so any PPS pool is vulnerable not only eloipool  ?

It's not really a PPS-only problem. Any pool is vulnerable period.

[tomaszsz]

and what about  Stratum is it ok ? or GBT  is better ? 

[Luke-Jr]

and what about  Stratum is it ok ? or GBT  is better ?

Stratum is just ASIC-friendly getwork. GBT solves that problem as well as the more important decentralization concern: https://en.bitcoin.it/wiki/Getblocktemplate

[DavinciJ15]

and what about  Stratum is it ok ? or GBT  is better ? 

So cgminer does not work with this pool back end?

[Luke-Jr]

and what about  Stratum is it ok ? or GBT  is better ? 

So cgminer does not work with this pool back end?

cgminer still works with getwork. BFGMiner does everything cgminer does and more (including GBT support)

[kano]

and what about  Stratum is it ok ? or GBT  is better ? 

So cgminer does not work with this pool back end?

cgminer still works with getwork. BFGMiner does everything cgminer does and more (including GBT support)

BarbieMiner still works with getwork.

Meanwhile ...

Hmm - well a good example of this so called 'more' is the MMQ driver.

Luke-jr wrote it for BarbieMiner and then sent pull requests to cgminer.
The cgminer pull requests didn't work - and he didn't send the pull requests that fixed that.

... however ... there is only one driver in cgminer that falsifies it's hash rate - the MMQ driver - coz the code Luke-jr wrote for BarbieMiner (and cgminer) falsifies it by up to 5% over and still does in both miners.
(I haven't rewritten the mining loop to fix this yet)
So yeah there's a good example of his 'more' for you ...

Though, cgminer fully supports Stratum ... yet BarbieMiner doesn't ... I guess that's called more also?

Hmm, what dictionary do you use to define the word 'everything' ?

[Luke-Jr]

Just a note that updating Eloipool within the next week or so is critical to surviving the subsidy halving.
Previous code had 50 BTC hard-coded in the "blank" coinbase.

[mrb]

Just a note that updating Eloipool within the next week or so is critical to surviving the subsidy halving.
Previous code had 50 BTC hard-coded in the "blank" coinbase.

Shhh! I predict at least some pools will have bugs and will continue to pay out as before the halving.

[Luke-Jr]

Just a note that updating Eloipool within the next week or so is critical to surviving the subsidy halving.
Previous code had 50 BTC hard-coded in the "blank" coinbase.

Shhh! I predict at least some pools will have bugs and will continue to pay out as before the halving.

Perhaps, but that won't be helped by pools producing invalid blocks

[Luke-Jr]

Been a while since I first announced Eloipool, so I'm updating the first post with new features

Most notable is support for dynamic share targetting in various modes (fractional, power-of-two (zero bit count), and bdiff rounded).
Combined with GBT, this is what pools need to support ASICs.
Additionally, Eloipool now supports the (pre-BIP draft) stratum mining protocol.
These new features were sponsored by Inaba/EclipseMC.

Also, a little background on the "loop" branch that's been sitting in the repository for a while:
This branch is designed to increase Eloipool's support of the GBT protocol on the upstream side.
Basically, you can run Eloipool as a "sub-pool" to any other GBT-enabled pool.
As of tonight, it is up to date with the final GBT protocol specifications, and works somewhat with both Eligius and BitMinter upstreams.
The main problems left to address are upstream longpolling support and properly dealing with upstreams when sending out the initial new block notifications (currently these produce and accept invalid work).
If you'd like to try this branch out, create a fresh clone of Eloipool and use git checkout loop[/url] to get the loop branch.
Customize your configuration as follows:

• CoinbasePrefix must be reasonably long to avoid collisions with upstream coinbase data.
• WorkQueueSizeLongpoll must be (0, 0) for now.
• It is a good idea to enable DelayLogForUpstream and use {upstreamResult} in your share log.
• Set ExpectedUpstreamLatency to a number of seconds of expected delay between your pool server and the upstream server.

I've been developing this on my own spare time. Donations, bounties, or outright hiring me to improve it is welcome.
General "loop"-related donations can be sent to 14VUob11S77JmrnShEKXPWttg8s6FvW12W.

[TAiS46]

Help with

Code:

# Network ID for the primary blockchain
UpstreamNetworkId = b'\xF9\xBE\xB4\xD9'  # testnet

is that correct?

and another failure

Code:

Traceback (most recent call last):
  File "eloipool.py", line 149, in <module>
    from merklemaker import merkleMaker
  File "/tmp/eloipool/merklemaker.py", line 448
    self._makeOne(self.clearMerkleRoots.put, self.curClearMerkleTree, height=self.currentBlock[1], False)
SyntaxError: non-keyword arg after keyword arg

Edit: Fixed the error, changed some thing in the File.

Next error:

Code:

2012-11-29 12:44:43,877 merkleMaker     WARNING Transaction-longpoll requested 100 seconds ago, and still not ready. Is your server fast enough to keep up with your configured WorkQueueSizeRegular maximum? (doing longpoll merkle roots)
2012-11-29 12:44:43,878 merkleMaker     WARNING Haven't updated the merkle tree in at least 100 seconds! Is your server fast enough to keep up with your configured work queue minimums? (doing longpoll merkle roots)

[Luke-Jr]

Yeah, that's what happens when I try to fix a rare edge race condition when I have a fever over 39 C/103 F.

Just ignore that top commit for now and I'll fix it when I get better

[TAiS46]

Oh ok just to let you know what I changed:

Code:

        def _makeOne(self, putf, merkleTree, checkBlock, height):
                MT = self.currentMerkleTree
                myblock = self.currentBlock
                MR = self.makeMerkleRoot(MT, height=height)
                if checkBlock:
                        # Only add it if the block hasn't changed in the meantime, to avoid a race
                        if self.currentBlock != myblock:
                                return
                else:
                        # Only add it if the height hasn't changed in the meantime, to avoid a race
                        if self.currentBlock[1] != height:
                                return
                putf(MR)

        def makeClear(self):
                self._doing('clear merkle roots')
                self._makeOne(self.clearMerkleRoots.put, self.curClearMerkleTree, False, height=self.currentBlock[1])

        def makeNext(self):
                self._doing('longpoll merkle roots')
                self._makeOne(self.nextMerkleRoots.put, self.nextMerkleTree, False, height=self.currentBlock[1] + 1)

        def makeRegular(self):
                self._doing('regular merkle roots')
                self._makeOne(self.merkleRoots.append, self.currentMerkleTree, True, height=self.currentBlock[1])

switches the args: height=self.currentBlock[1], False


Are the Transaction-Longpoll warnings also a failure from you?
I search the whole time for the fix

[Luke-Jr]

Are the Transaction-Longpoll warnings also a failure from you?
I search the whole time for the fix

No, that was (if it's what I think you're referring to) a bugfix; it wasn't actually doing what it needed to be doing.

[TAiS46]

Ok, keep me updated.
Maybe I will use your software for a bitcoin-24.com pool
get well soon

[TAiS46]

no fix and this moment, does not work

[dreamwatcher]

TAiS46,

I have it running, and with a couple of Alt coins.

You need to completely revert the last commit, That involved taking a section out and putting code back in.

I also disabled some of the more extraneous options in the config file and am running it as a basic GBT pool. The GBT long-polls are right on time, and I haven't see any of my rigs complain yet.

Luke,

I have to admit Luke, I am impressed. After all the crappy and abandoned code that usually involved ancient oddball dependencies I have have spent way to much time on over last few months. Eloipool is a breath of fresh air.

I only lost half my hair going through this code.  

Anyway, Hope you are feeling better and I look forward to further development on Eloipool. I think my next project will be a pool and it looks like it will be based on Eloipool.