KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2438 blocks

[kano]

Kano- do you think you'd make the stratum changes on this pool to support the new overt ASICBOOST?

Not before getting access to one.
I'm not stupid enough to assume any code is just going to work when created by a certain person who loses blocks on his pools and calls that 'misfortune'
Testing properly is a way to avoid that
But hackers usually have no idea about such things.
Experience tells you otherwise.

So if they don't actually exist ... then no they wont be supported

I ordered one - so if I get it, I'd be open to sending it to you to test / integrate (and trust you'd send it back )

No need to send it to me - just to point it somewhere and let me test it properly and see what happens.

So ... I'm setting up a new node in South Africa and I thought ... well it won't hurt to see what happens if I run the latest git code for that ...
LOL core dumped, crashed before it even connected to anything ...
... how unexpected ... NOT
No problem of course, switched back to my earlier version ... runs ok.

Looks like that AsicBoost testing will also be fixing already known bad code.

I'll mention about the new node for anyone close to it, after I've let it run for a while and see how it performs in that remote part of the planet ...

[gaud]

[snip]
Anyway, how exactly does everyone who's in a similar situation here transfer (sweep or import?) their mining payouts from cold storage to warm/hot wallets where they can spend the Bitcoins they've earned?

I have looked back through some conversations here and there; however, I'd like to know how you guys recommend doing this in a secure, repeatable manner. Thanks in advance.

I used to go the same route you go, but I've switched to using a hardware wallet. Makes these things much easier. I highly recommend one.

Same here, I use a non-USA based wallet to collect my payouts and consolidate to my hardware wallet around once a month.

So, just to understand a little more about the process before I go out and buy a hardware wallet, could I keep mining to my original paper wallet and import(?) it into the hardware wallet; use the hardware wallet to consolidate the payouts into another address on the hardware wallet; spend a portion of the BTC from the consolidated address; and finally repeat the process later--after more BTC accumulation--by re-consolidating everything into the change-containing address?  

Is that how that all would work, or should I go do a bunch more research?  

Thanks for everyone's patience reading (and hopefully replying to) this painful-to-understand post.

personaly i got cell phone wallet for mining and spending i guess and hardware wallet for saveing what i dont use in the market.

[wavelengthsf]

No need to send it to me - just to point it somewhere and let me test it properly and see what happens.

Sure - fingers crossed it comes in close to the date they promise

[BSGMiner]

[snip]
BTC 50 TH/s giveaway !!!! BTC
[snip]

Ok... Last try. Put your thinking cap on Padrinogtr!  
[snip]
Analogy:
Here's the very best and easiest way I can explain it using something that we should all be familiar with: Employment

*** Does anyone remember when employers used to hold your first week's paycheck?!

Due to this payout method, you were always technically a paycheck behind, but you never lost any money in the deal since they were just delaying it slightly, and even after you left the job, you still could count on having another paycheck that you were owed from when they held your first week's pay.

Now, imagine that they didn't hold your entire first check; just 4/5 of it. Then, each payday that rolls around afterward, they withhold less (3/5) and less (2/5) of each new paycheck until after five (5) paydays, you are now receiving your entire paycheck. In the back of your mind, though, you know that even if you left, you'd still have all that back-pay coming to you.
[snip]
It's up to you now Padrinogtr. Good luck!
[snip]

this one is looking really good
ill put my thinking cap on it asap

thanks for the effort

Padrinogtr, how'd it go? Could you understand that good enough to teach someone else, or are you still stumped?

Maybe, over the weekend you could try posting your explanation... Best of luck!

[robinsoz]

It has been fun mining with you guys. I'll unfortunately probably be pointing my few TH back at Slush sometime in the next few days (until next winter or Kano finishes the accounting code).

Reason has nothing to do with being unhappy with the pool but is rather because I run obsolete bitcoin miners in the winter for heat and in the summer to soak up excess solar power off a solar array. With the weather warming up I'll soon be below dust level.

Good luck to all.

[BSGMiner]

Kano- do you think you'd make the stratum changes on this pool to support the new overt ASICBOOST?

Not before getting access to one.
I'm not stupid enough to assume any code is just going to work when created by a certain person who loses blocks on his pools and calls that 'misfortune'
Testing properly is a way to avoid that
But hackers usually have no idea about such things.
Experience tells you otherwise.

So if they don't actually exist ... then no they wont be supported

This and a few other comments recently lead me to believe there's an interesting back-story here...

Too bad someone doesn't write an autobiography on Kano. I'm sure it'd be pretty enthralling.

[rifleman74]

The miner exists, that's not the problem here.  It's how well it performs on a pool with asicboost enabled vs not.   

[wavelengthsf]

The miner exists, that's not the problem here.  It's how well it performs on a pool with asicboost enabled vs not.  

It will not run without ASICBOOST on the pool. It is hardcoded into the miner driver. You can only run the Dragon miner on pools that support the stratum changes that ASICBOOST needs. You can read the speculation thread - they hacked the driver to force it to hash at a non-AB pool, and it did something like 4 TH.

[gaud]

The miner exists, that's not the problem here.  It's how well it performs on a pool with asicboost enabled vs not.  

It will not run without ASICBOOST on the pool. It is hardcoded into the miner driver. You can only run the Dragon miner on pools that support the stratum changes that ASICBOOST needs. You can read the speculation thread - they hacked the driver to force it to hash at a non-AB pool, and it did something like 4 TH.

well if they starat building them that way i guess all the pools will need asic boost

[Shazam!!!]

C'mon BTCLOCK!!! It's close, I can feel it with my extraordinary telekinetic energy!!! Ha!!!

[clgrissom3]

Time for a good old fashioned BLOCK FRIDAY!

[kano]

The miner exists, that's not the problem here.  It's how well it performs on a pool with asicboost enabled vs not.  

It will not run without ASICBOOST on the pool. It is hardcoded into the miner driver. You can only run the Dragon miner on pools that support the stratum changes that ASICBOOST needs. You can read the speculation thread - they hacked the driver to force it to hash at a non-AB pool, and it did something like 4 TH.

well if they starat building them that way i guess all the pools will need asic boost

Well - there clearly aren't that many in existence at the moment ... most likely none ...

Since the beginning of the year there are only 12 blocks (out of 10809) that have a version that isn't 0x20000000

All of those 12 have a version of 0x20000012 and they were all empty blocks mined by BTC.TOP (eleven) and Canoe (one)
All being empty probably means they are Covert AsicBoost, or just the usual crap empty blocks by most pools - most pools still do mine empty blocks - even slush does.

FYI the 12 blocks this year are:

Code:

2018-01-01 13:48:00.356487 UpdateTip: new best=0000000000000000003bdcf6918edfcd97a9059263fd395825ed4d9893875523 height=502051 version=0x20000012 log2_work=87.776815 tx=287971508 date='2018-01-01 13:48:08' progress=1.000000 cache=3.0MiB(583tx) warning='1 of last 100 blocks have unexpected version'
2018-01-02 01:17:44.789560 UpdateTip: new best=00000000000000000057bcaaacb218fbd38c347dc73a950f61716e65160ed05c height=502126 version=0x20000012 log2_work=87.780196 tx=288101441 date='2018-01-02 01:17:50' progress=1.000000 cache=65.5MiB(61582tx) warning='2 of last 100 blocks have unexpected version'
2018-01-06 06:46:54.058780 UpdateTip: new best=00000000000000000021d2d4b838670a1a970e69d7330827e10a704225a3cde2 height=502803 version=0x20000012 log2_work=87.810363 tx=289686857 date='2018-01-06 06:46:58' progress=1.000000 cache=174.1MiB(133700tx) warning='1 of last 100 blocks have unexpected version'
2018-01-08 16:53:38.192066 UpdateTip: new best=00000000000000000011b4db68e2f052572fdfd93c8293257b7727429f5418b9 height=503198 version=0x20000012 log2_work=87.827676 tx=290543710 date='2018-01-08 16:53:45' progress=1.000000 cache=134.1MiB(122466tx) warning='1 of last 100 blocks have unexpected version'
2018-01-13 11:23:36.181593 UpdateTip: new best=000000000000000000169ae5a9eed6972a2ed1322d57c818f977f05f16a08c2a height=504027 version=0x20000012 log2_work=87.863534 tx=292134843 date='2018-01-13 11:13:50' progress=0.999994 cache=175.6MiB(137947tx) warning='1 of last 100 blocks have unexpected version'
2018-01-19 22:29:39.877408 UpdateTip: new best=0000000000000000001213ccd3c8bb82048b3836ba146eb1e7f36fa30c65fa34 height=505058 version=0x20000012 log2_work=87.913219 tx=293939811 date='2018-01-19 22:29:56' progress=1.000000 cache=76.6MiB(31554tx) warning='1 of last 100 blocks have unexpected version'
2018-01-30 00:30:21.372304 UpdateTip: new best=000000000000000000292ecd5467e96309d28c7dedcda3480d658182d64cb204 height=506736 version=0x20000012 log2_work=87.996037 tx=296280252 date='2018-01-30 00:30:25' progress=1.000000 cache=135.2MiB(51183tx) warning='1 of last 100 blocks have unexpected version'
2018-02-07 23:51:20.353495 UpdateTip: new best=0000000000000000001084f4ca958301230dd738362455ecabb0d17f6daed056 height=508175 version=0x20000012 log2_work=88.070093 tx=298253147 date='2018-02-07 23:51:26' progress=1.000000 cache=148.2MiB(34809tx) warning='1 of last 100 blocks have unexpected version'
2018-02-21 12:54:18.724562 UpdateTip: new best=00000000000000000046850487510041a397a9e30934eab85864bd2fb2aa3179 height=510240 version=0x20000012 log2_work=88.179539 tx=300706266 date='2018-02-21 12:54:23' progress=1.000000 cache=182.5MiB(41535tx) warning='1 of last 100 blocks have unexpected version'
2018-02-28 01:19:53.290623 UpdateTip: new best=00000000000000000048a93ce52112aa8608f21f2f30961b75c413bf5d939e0c height=511243 version=0x20000012 log2_work=88.231904 tx=301894656 date='2018-02-28 01:19:59' progress=1.000000 cache=116.0MiB(23757tx) warning='1 of last 100 blocks have unexpected version'
2018-02-28 02:31:52.265986 UpdateTip: new best=00000000000000000042a0ea923a2104b82283ff5df4a1cacd323a39d043c2b7 height=511255 version=0x20000012 log2_work=88.232519 tx=301904432 date='2018-02-28 02:31:59' progress=1.000000 cache=104.4MiB(23438tx) warning='2 of last 100 blocks have unexpected version'
2018-03-03 15:06:20.072255 UpdateTip: new best=00000000000000000029678c12cbff2e550159b758714ef1ccbe2b0eca7d5eda height=511824 version=0x20000012 log2_work=88.26139 tx=302608191 date='2018-03-03 15:06:25' progress=1.000000 cache=119.0MiB(19782tx) warning='1 of last 100 blocks have unexpected version'

[kano]

It has been fun mining with you guys. I'll unfortunately probably be pointing my few TH back at Slush sometime in the next few days (until next winter or Kano finishes the accounting code).

Reason has nothing to do with being unhappy with the pool but is rather because I run obsolete bitcoin miners in the winter for heat and in the summer to soak up excess solar power off a solar array. With the weather warming up I'll soon be below dust level.

Good luck to all.

Good luck helping them mine empty blocks

slush's last empty block was a week ago:
https://btc.com/0000000000000000000d637d922588b7d30c85fd35d87b42ef86a8ce9609764e

[Rabinovitch]

Good luck helping them mine empty blocks

The majority of people don't care about empty blocks, about bitcoin's network "health" and the future of the cryptocurrencies in general. All they need from mining are regular payouts. That's why they prefer Antpool and other Chinese crap. That's why every little miner is important here at your pool. Not only those who was lucky enough in this embodiment to deploy 5 or more Phs of hashing power... That's why I was talking about at least little additional reward for blockfinder even with 20-30 Th, as soon as you decided to attract more hashing power here.

Argh...  And I wrote a complex php script using curl to "log in" to my S9 / D3 miners to monitor and reboot them.  An api would have been much easier!  Are there reference docs that are easy to find on the web?  Bitmain's site does not have a lot of help documents that I could find.

Is your script for sale or you can share it with the community without charge?

[kano]

To restart a Bitmain miner using linux wget

Code:

wget --timeout=10 --tries=1 --user=root --password=$pass -O - http://$ip/cgi-bin/reboot.cgi

$pass is the miner password
$ip is the IP address of the miner

[Jeremiah1610]

Added a 4th S9, (sorry I too hate shitmain), any future improvements will be Canaan. Mine on. Thank you Kano for all your hard work.

[robinsoz]

It has been fun mining with you guys. I'll unfortunately probably be pointing my few TH back at Slush sometime in the next few days (until next winter or Kano finishes the accounting code).

Reason has nothing to do with being unhappy with the pool but is rather because I run obsolete bitcoin miners in the winter for heat and in the summer to soak up excess solar power off a solar array. With the weather warming up I'll soon be below dust level.

Good luck to all.

Good luck helping them mine empty blocks

slush's last empty block was a week ago:
https://btc.com/0000000000000000000d637d922588b7d30c85fd35d87b42ef86a8ce9609764e

Give me a rational reason to stick around once my average hashrate drops below half a Terrahash and I’ll stay - like I said I’ll be back at some point. I prefer to mine on whichever pool I feel contributes the most to the network - but do like to get paid occasionally. Even at my highest hashrate when all my miners were running, I have wondered at times if I was leaching more from this pool than I was contributing - given the transaction fee cost of sending a few dollars worth of bitcoin after every block.

[WBF1]

Kano-

On one of my pools or miners i used to track highest difficulty share mined per second or something and chart it on a graph.

I know itd be pointless, but maybe a fun way to "pass the time" to show a graph like that. Plus then we could all get angry about how close we get to solving a block.

Just an idea I had anyway.

If the data was available thru an api I could throw something together.

[kano]

Kano-

On one of my pools or miners i used to track highest difficulty share mined per second or something and chart it on a graph.

I know itd be pointless, but maybe a fun way to "pass the time" to show a graph like that. Plus then we could all get angry about how close we get to solving a block.

Just an idea I had anyway.

If the data was available thru an api I could throw something together.

I don't track or store the 'current' 'best share' on purpose
If you submit 1000 valid shares, and your work difficulty is X, every one of those shares is worth X, no matter how high the difficulty is.
As long as they are X or more, they are worth X.
This is how all reasonable and fair payout systems work.

Any other valuation of shares adds yet more variance to your rewards and allows people to take advantage of that.

Many people look at the "best share" value and assume it means something, when in fact it means nothing at all ... unless it's a block.

You miner knows it's "best share" if you are curious to see what it is.

However, I do store every share above a limit for my regular statistical analysis, but no I wont be showing graphs of that.

[gaud]

Kano-

On one of my pools or miners i used to track highest difficulty share mined per second or something and chart it on a graph.

I know itd be pointless, but maybe a fun way to "pass the time" to show a graph like that. Plus then we could all get angry about how close we get to solving a block.

Just an idea I had anyway.

If the data was available thru an api I could throw something together.

I don't track or store the 'current' 'best share' on purpose
If you submit 1000 valid shares, and your work difficulty is X, every one of those shares is worth X, no matter how high the difficulty is.
As long as they are X or more, they are worth X.
This is how all reasonable and fair payout systems work.

Any other valuation of shares adds yet more variance to your rewards and allows people to take advantage of that.

Many people look at the "best share" value and assume it means something, when in fact it means nothing at all ... unless it's a block.

You miner knows it's "best share" if you are curious to see what it is.

However, I do store every share above a limit for my regular statistical analysis, but no I wont be showing graphs of that.

to simplify "close only counts in horseshoes and hand grenades "