Bitcoin Forum
May 25, 2018, 05:26:17 PM *
News: Latest stable version of Bitcoin Core: 0.16.0  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Poll
Question: What type of pool payouts do you prefer?
Bitcoins - 3230 (80.4%)
Bank transfer / USD - 415 (10.3%)
Gold/silver coins and bars - 371 (9.2%)
Total Voters: 4014

Pages: « 1 ... 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 [1054] 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 ... 1142 »
  Print  
Author Topic: [2.5+ EH] Slush Pool (slushpool.com); World's First Mining Pool  (Read 4326807 times)
Gyrsur
Legendary
*
Offline Offline

Activity: 1932
Merit: 1019


#BEL+++


View Profile WWW
August 19, 2015, 04:15:07 PM
 #21061

For those who inexplicably missed it: that's the first, and so far only, block that has its version number set to 536870919 (or 0x20000007 in hex)[1].  That number, in binary, sets a specific set of bits that signals to Bitcoin XT[2] that the block should count as vote in favor of a block size increase[3] as specified in BIP101[4].

Slush announced on facebook that they will be supporting both Bitcoin Core and Bitcoin XT as choices for miners[5].

BS so far and nothing like a prove. where is the hex in the code?

EDIT: it's true. slush's pool mined the first XT block! such a shame!

/** Blocks with version fields that have these bits set activate the bigger-block fork */
const unsigned int SIZE_FORK_VERSION = 0x20000007;
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1527269177
Hero Member
*
Offline Offline

Posts: 1527269177

View Profile Personal Message (Offline)

Ignore
1527269177
Reply with quote  #2

1527269177
Report to moderator
1527269177
Hero Member
*
Offline Offline

Posts: 1527269177

View Profile Personal Message (Offline)

Ignore
1527269177
Reply with quote  #2

1527269177
Report to moderator
1527269177
Hero Member
*
Offline Offline

Posts: 1527269177

View Profile Personal Message (Offline)

Ignore
1527269177
Reply with quote  #2

1527269177
Report to moderator
KNK
Hero Member
*****
Offline Offline

Activity: 679
Merit: 501


View Profile
August 19, 2015, 05:15:11 PM
 #21062

Slush announced on facebook that they will be supporting both Bitcoin Core and Bitcoin XT as choices for miners[5].

Quote from: Slush@facebook
Since tomorrow you'll be able to vote for or vote against this proposal on Slush Pool directly with your miners. Stay tuned!
But it doesn't say how do we vote, yet there is a 'voting block' for XT, which I am personally against. I am sure we will have that option with the next pool update and this is probably just a test for it.

EDIT: it's true. slush's pool mined the first XT block! such a shame!

Slush was the first pool ever, first to implement Stratum and now the first pool implementing XT as an option. All will be fine quite soon (see above), so it's not a shame, but just another first for Slush.

BTC tips: 1KNK1akhpethhtcyhKTF2d3PWTQDUWUzHE
Gyrsur
Legendary
*
Offline Offline

Activity: 1932
Merit: 1019


#BEL+++


View Profile WWW
August 19, 2015, 05:31:46 PM
 #21063

EDIT: it's true. slush's pool mined the first XT block! such a shame!

Slush was the first pool ever, first to implement Stratum and now the first pool implementing XT as an option. All will be fine quite soon (see above), so it's not a shame, but just another first for Slush.

I don't want to be a part of these which mine XT blocks but I did not have a choice! Such a shame!
Adrian-x
Legendary
*
Offline Offline

Activity: 1372
Merit: 1000



View Profile
August 19, 2015, 06:10:48 PM
 #21064

I was DOS from TOR to and I would guess this s temporally. If QT's are assholes that is the only defence. And as far as I know that will change and will be based on number of request from IP and this is just a quick fix... Read mailing list...

And my mistake. We can't say it was a XT block. It could be BIP 101 block...

EDIT: Just looked at the code. What BS. It just uses a list that deprioritized a list of IPs that get dropped if you are DOS attack. And I do see a lot of IPs in the list that were DOSing me... So to say it is a blocking list... I got about 75% of that IPs in days and they are saying it took mouths to map... Real FUD... So I no longer need DROP rules in FW... That makes things batter for TOR not worst... They can now connect and only get drooped if I get DOS again...

EDIT2: It could be called same as pools and nodes doping so called SPAM in SPAM attack. There was a lot of valid ones in there... I know for at lest one since I was affected. But that was all good right? Since you agree that this is SPAM even if it is not...

EDIT3: I'm not sure but are they looking a different code or I'm missing something... Most of the issue had code from months ago not this one... and I think that someone agrees with me http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010388.html Someone jumped too soon... PR war and lies

thanks for that, that's what we are talking about BIP101, I dont care what software nodes use, XT means nothing, it sounds like an ALT and Mikes branding makes it look like one too, I'm sure its just a PR thing. (even got a PM from r/nullc gloating over their victory.)

It's in the general interest of bitcoiners and those that benefit from better money in the future that we are free to make chooses and discuss them, I want to mine blocks that will support BIP101. - unfortunately Bitcoin XT is off topic precisely because it is the only option with a footprint in the Bitcoin space that runs the BIP101 improvement.

calling it an alt is ridiculous.

actually came here to say nice run on luck there :-) - lets change the OP subject line too. (16.42 Ph/s)

Thank me in Bits 12MwnzxtprG2mHm3rKdgi7NmJKCypsMMQw
TheRealSteve
Hero Member
*****
Offline Offline

Activity: 686
Merit: 500

FUN > ROI


View Profile
August 19, 2015, 06:16:10 PM
 #21065

I'd guess they just had to make sure putting that version on actually worked in a live environment before throwing it out there as an option.  Just a guess, though.  All blocks from Slush since (so far) have been version 3 (regular Core version).

KNK
Hero Member
*****
Offline Offline

Activity: 679
Merit: 501


View Profile
August 19, 2015, 07:05:04 PM
 #21066

I don't want to be a part of these which mine XT blocks but I did not have a choice! Such a shame!

Me too, but please read again my full post and specifically the part you have removed from your quote.

I'd guess they just had to make sure putting that version on actually worked in a live environment before throwing it out there as an option.  Just a guess, though.  All blocks from Slush since (so far) have been version 3 (regular Core version).

That's exactly what I meant in my post - this block is just a test and we will have the option to vote pretty soon.

BTC tips: 1KNK1akhpethhtcyhKTF2d3PWTQDUWUzHE
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1344
Merit: 1015


Mine at Jonny's Pool


View Profile WWW
August 19, 2015, 07:16:08 PM
 #21067

What do you mean it was a test?  You want to perform a test, you throw it up on the test network.  What was done here was slush actively pointing miner hash rate to an XT node which constructed and solved a block.  There is no announcement on the website stating that this would occur.  Perhaps this was announced in some social media, but it isn't anywhere on the actual website.  Therefore, miners weren't given the choice - it was made for them.

Of course, if you did indeed happen to know in advance that this was going to occur, and you chose to keep your miners here, then you voted for XT by default.  If you have become aware of this, and continue to mine here, you are indeed voting for XT.  I wonder if you're going to be given the option in your worker setup or somewhere else (like a different URL/port) to choose XT or Core, or if slush will solely mine on XT nodes.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
pekatete
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile WWW
August 19, 2015, 07:23:32 PM
 #21068

As time goes by, it seems more people are voting with their hash for XT (pool hash-rate was approx 14PH yesterday and it is now approx 16PH and growing!).
And yes, the "test" was done without informing pool users, and most likely the announcement to offer the choice to vote for XT was made after the "test", but more important is that the choice is to be offered (and pertinently that the pool hash seems to be growing as the news spreads and the importance of the "test" sinks in).

TheRealSteve
Hero Member
*****
Offline Offline

Activity: 686
Merit: 500

FUN > ROI


View Profile
August 19, 2015, 09:22:43 PM
 #21069

Right now, every Slush Pool miner can vote for larger blocksize.
Simply use one of following mining URL to do so:

stratum+tcp://stratum.bitcoin.cz:3301
stratum+tcp://us-east.stratum.bitcoin.cz:3301
stratum+tcp://eu.stratum.bitcoin.cz:3301
( only difference is the port )

Lucko
Hero Member
*****
Offline Offline

Activity: 826
Merit: 1000



View Profile
August 20, 2015, 12:09:23 AM
 #21070

Right now, every Slush Pool miner can vote for larger blocksize.
Simply use one of following mining URL to do so:

stratum+tcp://stratum.bitcoin.cz:3301
stratum+tcp://us-east.stratum.bitcoin.cz:3301
stratum+tcp://eu.stratum.bitcoin.cz:3301
( only difference is the port )
Now I need to change ports on 33 miners... He didn't make it easy...
edonkey
Legendary
*
Offline Offline

Activity: 1135
Merit: 1000



View Profile
August 20, 2015, 02:54:26 AM
 #21071

Right now, every Slush Pool miner can vote for larger blocksize.
Simply use one of following mining URL to do so:

stratum+tcp://stratum.bitcoin.cz:3301
stratum+tcp://us-east.stratum.bitcoin.cz:3301
stratum+tcp://eu.stratum.bitcoin.cz:3301
( only difference is the port )
Now I need to change ports on 33 miners... He didn't make it easy...

Seems like an alternative set of URLs is the only way to realistically implement a voting system. If they made it account based (for example) then there would be overhead forwarding mining traffic to the appropriate stratum server.

I switched my miners over this afternoon, as soon as I heard about it.

I think the option to vote with your hash power is inspired. Well done Slush!

Was I helpful?   BTC: 18wQtEDmhur2xAd3oE8qgrZbpCDeuMsdQW   LTC: LbqLtkZ6wTSpwHHuv1tG4J7tHajGdH5QFB   DOGE: D9R5ySAP2DARpxuNKd7hN7ANmqFiGwB9G6
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2534
Merit: 1072


Ruu \o/


View Profile WWW
August 20, 2015, 03:41:12 AM
 #21072

He probably should have clarified that it's a vote for XT, not just a larger blocksize.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
pekatete
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile WWW
August 20, 2015, 08:45:29 AM
 #21073

He probably should have clarified that it's a vote for XT, not just a larger blocksize.

Probably not. It is what it is, that which WE are voting on with OUR hash.
There are, I'd imagine, multiple threads discussing THAT distinction where you'd no doubt be on-topic.

-ck
Moderator
Legendary
*
Offline Offline

Activity: 2534
Merit: 1072


Ruu \o/


View Profile WWW
August 20, 2015, 10:28:50 AM
 #21074

He probably should have clarified that it's a vote for XT, not just a larger blocksize.

Probably not. It is what it is, that which WE are voting on with OUR hash.
There are, I'd imagine, multiple threads discussing THAT distinction where you'd no doubt be on-topic.
With all due respect, I think making it clear that it's XT you're mining for by selecting the alternative ports IS on topic for miners who mine on this pool.

EDIT: Respect withdrawn based on your obviously inflammatory response ignoring what the implications of said vote are. It is NOT just a vote for bigger blocks. I'll let others judge for themselves.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
pekatete
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile WWW
August 20, 2015, 10:38:01 AM
 #21075

He probably should have clarified that it's a vote for XT, not just a larger blocksize.

Probably not. It is what it is, that which WE are voting on with OUR hash.
There are, I'd imagine, multiple threads discussing THAT distinction where you'd no doubt be on-topic.
With all due respect, I think making it clear that it's XT you're mining for by selecting the alternative ports IS on topic for miners who mine on this pool.

It is what it is, and very clearly stated, and I quote: Right now, every Slush Pool miner can vote for larger blocksize..
The XT part is what is totally off-topic since it is neither mentioned in the post nor been raised as an issue to slush by any of my fellow pool users. So there, find the thread discussing the merits and demerits of XT, block sizes et al and continue that discussion there.

chiguireitor
Legendary
*
Offline Offline

Activity: 899
Merit: 1000


Coins, Games & Miners


View Profile WWW
August 20, 2015, 11:02:28 AM
 #21076

It could be that if enough miners connect to port 3301 they alter the version number (without using XT) on the block itself that gets relayed, expressing support for the BIP but not using the flawed XT implementation?

Just shooting an arrow on the dark here....

TheRealSteve
Hero Member
*****
Offline Offline

Activity: 686
Merit: 500

FUN > ROI


View Profile
August 20, 2015, 12:38:09 PM
 #21077

It could be that if enough miners connect to port 3301 they alter the version number (without using XT) on the block itself that gets relayed, expressing support for the BIP but not using the flawed XT implementation?
And with that, it's obvious that the pool operators should indeed be more specific in what exactly is on the back-end of the 3301 port.  There's at least 3 readily accessible possibilities;
1. Bitcoin-XT, which has the block vote but also already contains the additional other changes.
2. Big-block only, which has the block vote and all code to handle big blocks, but does not contain the additional other changes.
3. Not-XT, which only pretends to be XT and sets the version number (thus voting), but does not actually have the code to handle big blocks (or any of the parts that take votes into account)

While all 3 constitute a 'vote for' big blocks, the devil is in the details.  I highly doubt it's the third option as that would basically be double-crossing those who explicitly chose to mine at that port expecting either the first or second option, but that still leaves those two.  Can't hurt to clarify the particulars Smiley

pekatete
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile WWW
August 20, 2015, 12:46:55 PM
 #21078

Its a means to an end and not the end itself (and we're not at the end either). If and when we get to THAT end, then I agree, it would be nice (just nice) to know what means a pool deploys. As it stands, it is neither here nor there (akin to dilligently applying a razor to a hair-strand!).

It is a simple vote (by hash) of whether we'd like to get to a certain end-point (not a vote on the means to get to that endpoint).

TheRealSteve
Hero Member
*****
Offline Offline

Activity: 686
Merit: 500

FUN > ROI


View Profile
August 20, 2015, 01:07:30 PM
 #21079

I think it's great that they offer the choice at all, let people decide.  The thing some people are pointing out is that there are changes in the XT client that are completely separate from the block size voting and apply immediately.  Presenting the choice as being purely about the block size and something that only applies to the future and only if certain thresholds are met is painting an incomplete picture.  That's not a matter of splitting hairs, but one of informed choice.  It's also only a single comment/post to clarify Smiley

pekatete
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile WWW
August 20, 2015, 01:53:13 PM
 #21080

The razor and hair-strand comment was not directed towards your comment, was just included in a response to your comment.
Saying that, I think you hit it on the head there, aka there are changes in the XT client that are completely separate from the block size, which (no surprise here) is exactly my thinking. The hash vote is for block size not the XT client (or the other means to achieving a larger block size). That there are implications to that should be the subject of another thread, of which I am sure there are plenty .... but thanks for clarifying anyway.

Pages: « 1 ... 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 [1054] 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 ... 1142 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!