Bitcoin Forum
November 02, 2024, 09:06:46 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 [16] 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 »
  Print  
Author Topic: [ANN] Stratum mining protocol - ASIC ready  (Read 146049 times)
beekeeper
Sr. Member
****
Offline Offline

Activity: 406
Merit: 250


LTC


View Profile WWW
November 21, 2012, 03:12:27 PM
 #301

python on win7 64 bits have the same issue with redirections.

25Khs at 5W Litecoin USB dongle (FPGA), 45kHs overclocked
https://bitcointalk.org/index.php?topic=310926
Litecoin FPGA shop -> http://ltcgear.com
antirack
Hero Member
*****
Offline Offline

Activity: 489
Merit: 500

Immersionist


View Profile
November 21, 2012, 03:16:03 PM
 #302

I am on Ubuntu.

It works now, for some reason it only works directly in a bash shell but not in a GNU Screen session.
slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
November 25, 2012, 09:41:42 PM
 #303

I just changed "official" documentation of Stratum protocol at https://mining.bitcoin.cz/stratum-mining to reflect recent discussion about changing the difficulty.

Specifically I added following sentence to chapter "Server can occasionally ask miner to change share difficulty":

Quote
This means that difficulty 2 will be applied to every next job received from the server.

Although I understand this is not breath-taking and verbose explanation, it is basically enough to fix recently discussed issues about difficulty changes.

Reasoning for this change is described here: https://bitcointalk.org/index.php?topic=108533.msg1344456#msg1344456 and this change is backward compatible with all existing mining software (cgminer, proxy, poclbm). It should be also compatible with existing pool implementations (at least with BtcGuild implementation, and I'm not aware of any reason why it should break other implementations), so it is up to poolops if their Stratum pools will gain from this change.

DrHaribo
Legendary
*
Offline Offline

Activity: 2730
Merit: 1034


Needs more jiggawatts


View Profile WWW
November 25, 2012, 10:17:14 PM
 #304

Thanks, Slush. Just in time for my server implementation Grin

▶▶▶ bitminter.com 2011-2020 ▶▶▶ pool.xbtodigital.io 2023-
DrHaribo
Legendary
*
Offline Offline

Activity: 2730
Merit: 1034


Needs more jiggawatts


View Profile WWW
December 01, 2012, 11:49:01 AM
 #305

Is the X-Stratum HTTP header documented somewhere?

What should be the contents?

How should it be interpreted by miners? As "stratum is there, if you want it" or "stratum is there, switch to that"

▶▶▶ bitminter.com 2011-2020 ▶▶▶ pool.xbtodigital.io 2023-
slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
December 01, 2012, 12:32:53 PM
 #306

Is the X-Stratum HTTP header documented somewhere?

I don't think so. It should be "getwork extension", but I'm not aware of any process how to "standardize it". Maybe just edit wiki? :-)

Quote
What should be the contents?

stratum+tcp://url:port

Quote
How should it be interpreted by miners? As "stratum is there, if you want it" or "stratum is there, switch to that"

Existing miners (cgminer, poclbm) implement it as "Stratum is there, switch to that". Thanks to this, users (who don't understand difference between getwork/stratum) don't need to change anything in their config, just update miner.

slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
December 01, 2012, 12:45:57 PM
 #307

I edited bitcoin.it wiki: https://en.bitcoin.it/wiki/Getwork

DrHaribo
Legendary
*
Offline Offline

Activity: 2730
Merit: 1034


Needs more jiggawatts


View Profile WWW
December 01, 2012, 07:38:37 PM
 #308

I edited bitcoin.it wiki: https://en.bitcoin.it/wiki/Getwork

Thanks Smiley

So current miners try GBT first, and if it has a Stratum HTTP header they switch to Stratum. If GBT fails completely they switch to getwork, which could also have a Stratum header, but that is never looked at if GBT is supported.

If you implement both GBT and Stratum, the server will decide the default by including a Stratum HTTP header in GBT responses or not.

▶▶▶ bitminter.com 2011-2020 ▶▶▶ pool.xbtodigital.io 2023-
DrHaribo
Legendary
*
Offline Offline

Activity: 2730
Merit: 1034


Needs more jiggawatts


View Profile WWW
December 02, 2012, 12:23:18 PM
 #309

Currently testing Stratum at BitMinter: https://bitcointalk.org/index.php?topic=27062.msg1372864#msg1372864

▶▶▶ bitminter.com 2011-2020 ▶▶▶ pool.xbtodigital.io 2023-
slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
December 02, 2012, 12:25:09 PM
 #310

So current miners try GBT first, and if it has a Stratum HTTP header they switch to Stratum.

I have no idea how it works with GBT in miners. That X-Stratum is for getwork protocol...

-ck
Legendary
*
Offline Offline

Activity: 4284
Merit: 1645


Ruu \o/


View Profile WWW
December 02, 2012, 12:27:50 PM
 #311

So current miners try GBT first, and if it has a Stratum HTTP header they switch to Stratum.

I have no idea how it works with GBT in miners. That X-Stratum is for getwork protocol...
GBT is all done in http so the headers can just as easily contain x-stratum as getwork does, and cgminer will still switch to stratum if it finds the header in gbt comms.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
December 02, 2012, 12:28:58 PM
 #312

Thanks ckolivas, good to know.

slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
December 02, 2012, 11:14:29 PM
 #313

Stratum proxy 1.2.0 has been released. Changelog:

* Fixes major bug in C extension for calculating midstate (thanks verement for bug report & pull request).
* Fixes network issues - proxy now actively reconnects after two minutes of pool inactivity (also disconnect miners to indicate connection issues).
* Fixes get_version message.

DrHaribo
Legendary
*
Offline Offline

Activity: 2730
Merit: 1034


Needs more jiggawatts


View Profile WWW
December 03, 2012, 09:53:02 AM
 #314

What would be recommended server behavior in the case that, after authentication, a worker's credentials are no longer valid. For instance due to the password changing, the worker being deleted, the user being banned or the user account deleted.

And does it make sense to implement more commands than the ones in the docs at bitcoin.cz?

▶▶▶ bitminter.com 2011-2020 ▶▶▶ pool.xbtodigital.io 2023-
-ck
Legendary
*
Offline Offline

Activity: 4284
Merit: 1645


Ruu \o/


View Profile WWW
December 03, 2012, 09:54:35 AM
 #315

What would be recommended server behavior in the case that, after authentication, a worker's credentials are no longer valid. For instance due to the password changing, the worker being deleted, the user being banned or the user account deleted.

And does it make sense to implement more commands than the ones in the docs at bitcoin.cz?
I'd say just drop the connection since that would mandate they try to reauthorise.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
DrHaribo
Legendary
*
Offline Offline

Activity: 2730
Merit: 1034


Needs more jiggawatts


View Profile WWW
December 04, 2012, 12:28:55 AM
 #316

I'd say just drop the connection since that would mandate they try to reauthorise.

Yeah, will do that.

Didn't see this until now: https://en.bitcoin.it/wiki/Stratum

Are all those RPC methods documented somewhere?

▶▶▶ bitminter.com 2011-2020 ▶▶▶ pool.xbtodigital.io 2023-
slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
December 04, 2012, 09:30:14 AM
 #317

https://github.com/luke-jr/bfgminer/issues/186

Do we have any nice solution how to provide enough information for miners to inspect block templates, but prevent pool from overloading? As I see now, these two requirements are going against each other.

slush (OP)
Legendary
*
Offline Offline

Activity: 1386
Merit: 1097



View Profile WWW
December 04, 2012, 09:34:28 AM
 #318

Didn't see this until now: https://en.bitcoin.it/wiki/Stratum
Are all those RPC methods documented somewhere?

AFAIK docs is only there:
https://docs.google.com/a/palatinus.cz/spreadsheet/ccc?key=0Al5UmiyYRxBudENwV2pVVmJsOEJMM1VnSDdHM0JhZlE#gid=0

There's reference implementation of some of them:
https://github.com/slush0/stratum-mining-proxy/blob/master/mining_libs/client_service.py


-ck
Legendary
*
Offline Offline

Activity: 4284
Merit: 1645


Ruu \o/


View Profile WWW
December 04, 2012, 09:43:39 AM
 #319

https://github.com/luke-jr/bfgminer/issues/186

Do we have any nice solution how to provide enough information for miners to inspect block templates, but prevent pool from overloading? As I see now, these two requirements are going against each other.
luke-jr's code is intentionally checking far too often, trying to make stratum look worse than GBT. Enough of his crap, don't let his influence ruin stratum too.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
Graet
VIP
Legendary
*
Offline Offline

Activity: 980
Merit: 1001



View Profile WWW
December 04, 2012, 09:56:47 AM
 #320

https://github.com/luke-jr/bfgminer/issues/186

Do we have any nice solution how to provide enough information for miners to inspect block templates, but prevent pool from overloading? As I see now, these two requirements are going against each other.
luke-jr's code is intentionally checking far too often, trying to make stratum look worse than GBT. Enough of his crap, don't let his influence ruin stratum too.
+1

| Ozcoin Pooled Mining Pty Ltd https://ozcoin.net Double Geometric Reward System https://lc.ozcoin.net for Litecoin mining DGM| https://crowncloud.net VPS and Dedicated Servers for the BTC community
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 [16] 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!