Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 8. (Read 4382714 times)

GBT already exists, and no pool or miner has used GBT to allow people to choose their own transactions.
It either leads to a massive bloat in the data sent to the miner, or each miner requires access to their own bitcoin node, which will lead to lost blocks due to the fact that the pool should be configured to handle work changes way better than a miner could.

There is no reason to choose transactions, since it will always be based on ignorance, bias, prejudice, intolerance or corporate interests.
The best example of that being LukeJr putting such prejudice into the ubuntu release of bitcoin years ago.

If your pool's transactions are not already taken, unbiased, from the mempool of the best paying transactions at the time you generate the work, but instead include bias in that choice, then there is a problem with the pool and miners should mine somewhere else.

The original flaw in stratum was the fact that the work did not include the work difficulty.
Slush wouldn't change that coz he said it was too much work for him to fix his pool, thus stratum was released with that flaw.
See the original stratum discussion thread for that argument.
https://bitcointalksearch.org/topic/ann-stratum-mining-protocol-asic-ready-108533

The miner already supplies stats about itself via the API I designed and wrote, that there are many tools available to see those stats.
The pool already can determine the hash rate of the miner and when it submitted the last share.
The miner providing these API statistics to the pool is, to be blunt, completely unnecessary and thus will only lead to nefarious use of this data by the pool.

Your current firmware also includes a major well known security risk - xnsub.

With that shit on Java, JSFile, Cloudflare I will never look after it.
When will you trash this tracking shit?

If you realy wan't to inform people, paste it here in your thread.

New mining stack on the way! Secure, transparent and flexible

We are designing a new mining protocol, Stratum v2, with the aim of addressing all the major issues of the current one. To provide a complete mining stack — open-source and compatible throughout — we have also taken a big step and started designing the new mining software in Rust language.

Now, we’re almost done with the design and would like to invite you all to participate in our effort to create this open standard. We’d be delighted to listen to your needs to find out what features you’d like to see in the new mining package.


Visit the website and get in touch: braiins.com/upgrade

^^^^^this times 100%

and Kano does not make payouts just once a month SMH - he makes payouts at every block that is found and he never has empty blocks.  It can go long spells between blocks but the payout is higher as well. 

@john139 -- using what you posted of  1T * 24H = 0.00003958 BTC - If I apply that to my miners (I have 80 TH on Kano) I would make .0981584 before 2% fees and .09619523 after fees. with Kano pool, if the block is only 12.5 in rewards (no tx fees) which there are always tx fees but as they vary I will simply use 12.5, and the same TH I will get .033 per block found before his .9% fee and .032703 per block after fee. So if we find 3 blocks in a month I am thus even with slush/antpool etc that you got the 1T * 24H = 0.00003958 BTC from.

And if we find more than 3 blocks, I am ahead. Now this can vary by pool size - the calculations are based on current pool hash rate. however as it usually does, when the hash rate increases and my payouts decrease, the blocks are then also found more frequently and it tends to break even.

the only hard part is waiting for it to ramp up while the pool hashrate is so small.

Both slush and Antpool and most of the large pools create unnecessary empty blocks.

Luck finding blocks is not affected by the size of the block, but they choose to make empty blocks anyway.

Each time they do this, that's rewards lost for PPLNS miners, and extra transactions not confirmed until later.

This has been discussed a lot in the past, there's even a thread about it, but most people seem to think it's ok to ignore for some unknown reason.
If you go back to Jan 2018, txn fees were around 30% extra, so that's a lot of BTC to throw away on a single empty block.

well I think kano makes pay outs every month , due to some reasons i cant wait one month ,

I check at btc.com that it is written ( Mining Earning  -----   1T * 24H = 0.00003958 BTC )

I checked slushpool ( currently using) and  antpool (which i used to mine before ) their payment is same as above
1)I thnik most of people are against Antpool bcz its policy is against the health of btc network and if there is something else please  let me know ?
2)I think they take 2% fee, imagine if I am supposed to earn 1BTC per month ( take it equal to 5300$) so they will get 126$ monthly is my calculations correct  ? If I am ok with this amount of fee is there another reason that i shouldn't mine there 

I would say to stay away from both antpool and slushpool - i have used both in the past and slush is my failover currently for a set of 5 miners. but I would not use them for primary.

I have 20 miners - 5 point to kano.is, 10 are pointing to viabtc and the other 5 at various pools mining non btc sha256 coins.

yes my lack of patience  ,
i had another questions ?
1)in other pools like antpool you can see  how many of u r shares has been accepted and how many rejected ( stale or ...) , i did want to know how can i see my stale shares on slushpool
2) i didnt change my miners min difficulty and it is 128 from the first day isn't it less?  I have 30 ,M3 miners my scoring hash rate is about 358 some how it is ok in comparison to my miners capacity , so can this mean difficulty is correct and no need to be changed whether automatically or manually ?
tnx if any one can help me

their current luck (last 10 blocks or so) is low but overall their luck is where it should be. you can see that by looking at the long game - the 50 and the 250

hey guys
what is wrong with slushpool , is it really bad luck ?  or there is some problem going on ? 

65.54 %
10 Blocks
-----
98.83 %
50 Blocks
------------
102.71 %
250 Blocks

I solved, imported with excel. if someone needs help with that i can make a post on how to push slush data into it.

i think i did mine with miners and also with rented hashing power on kano..but that was in the good ol' days. i would surely want to see more blocks from kano and from the pool operator point of view more hashing power more blocks more fees colected..and your 5X block system of reward was good in keeping the mining hoppers away. slush has also a good system against this.
now, back to my issue.... ))

Nope, not the only pool.

Mine is also, I block rentals and stop them whenever I find them - rentals are a financial risk to mining, due to the fact they make a financial gain from withholding blocks if they are not detected.

i also have an issue with the difficulty setting..they say they use vardiff but they do not have that option for me to check it. i need to manually put in a value for minimum difficulty. how the fuck can i choose vardiff? also this is the only one pool that is not nicehash compatible because of this shit. if anyone knows what setting should i use for minimum diff please advise.

it's on a roll now!  lol

sure - better late then never right? only 15 months and NMC has only dropped by like 1000% in value.

Hi,

we are working on that. We believe the NMC payouts are going to be processed until the end of April/at the beginning of May.

We are once again sorry about the delay.

Any update on the merged mining payout? Also, on the new site I can't even seem to get to the Namecoin rewards to see the infinite number of blocks that are stuck in a processing state. Am I missing something here....other than the merged mining payouts. HAHA

any update on the merged mining payouts that have been held up for over a year? that you stated a month ago would handled within a few weeks?

Thanks a lot Smiley I have set the min. Diff. to "auto" and the pool changed it to "16384". Hope that I get the best result now.

https://imgur.com/wkxlc7t