Pages:
Author

Topic: Stratum specs - page 2. (Read 1873 times)

legendary
Activity: 1260
Merit: 1019
June 29, 2017, 06:06:25 AM
#6
Yes, you're right.   From metadata we can of course guess the country and maybe even the place, from
hashrate and other sessions we can guess the hardware and power consumption, from reconnects we
can guess some operations on site etc.

In fact I am asking these questions not as MitM between POOL and ASIC
I am interested - what kind of information can obtain POOL_ADMIN about ALL OTHER POOLS
if connect some his own ASICs to concurrent pools.

I want to discuss possible attack vector after segwit activation. Do not know
how to call it. Something like "witness-data-withholding attack". Pushing the mined block
without witness data to pre-segwit network and listening the actions on it from other pools
gives some interesting advantages to dishonest pool admin.
newbie
Activity: 9
Merit: 0
June 29, 2017, 05:49:19 AM
#5
I think that we can get the hash-of-previous-block from protocol data.

Yes, you're right.   From metadata we can of course guess the country and maybe even the place, from hashrate and other sessions we can guess the hardware and power consumption, from reconnects we can guess some operations on site etc.
legendary
Activity: 1260
Merit: 1019
June 29, 2017, 05:06:46 AM
#4
Miner id (in some pools it's just an address, so payments can be tracked), miner password
in this pool, current time, that's basically all of interesting information.
I think that we can get the hash-of-previous-block from protocol data.
Because we need it to put in 80-bytes header for current block

And the hash-of-previous-block gives us at least the network we are connected to and
currently running blockheight (I had to say that we can use another sources of information
except sniffing)
newbie
Activity: 9
Merit: 0
June 29, 2017, 04:52:37 AM
#3
Thanks a lot. I will read it later. Is is up-to-date?
Nope  Smiley    Moreover, some pools have some small differences in protocol, with specially tweaked miners software.   But generally the doc is ok.

Quote
c) What information about network and pool can be obtained from sniffing?

Miner id (in some pools it's just an address, so payments can be tracked), miner password in this pool, pool current time, how many submissions miner does (its performance and thus its revenue), that's basically all of interesting information.

Quote
d) Can the user be sure that he mines a block by his pool? (The dishonest pool can proxy
users' hashrate to another pool in case)

Nope.   The miner build mutual trust with the pool by having flow of payments.    Other than that, you can not be sure on anything in the internet except blockchains  Smiley
legendary
Activity: 1260
Merit: 1019
June 29, 2017, 04:29:39 AM
#2
Thanks a lot. I will read it later. Is is up-to-date?

c) What information about network and pool can be obtained from sniffing?
d) Can the user be sure that he mines a block by his pool? (The dishonest pool can proxy
users' hashrate to another pool in case)
legendary
Activity: 1260
Merit: 1019
June 29, 2017, 03:42:29 AM
#1
Let assume that a USER has running ASIC connected to a POOL

1) Can the USER by sniffing the TRAFFIC (data sent from a pool) monitor such things as
a) currently mining blockheight
b) coinbase transaction data (scriptSig)

2) How does ASIC <---> POOL protocol works? Is it http longpoll or socket connection?
Pages:
Jump to: