https://blockchain.info/tx/df60741e004f63c13d07eb422f89b3fbc1a2b270cccd35c05d0daeb35af5f20fnow 10 blocks have skipped the .0013 fee transaction due to it having 52 small parts of coin and 3 big parts. thus 55 parts of coin which takes up space so it gets skipped. even though the fee is .0013 I got skipped here for this block. These funds were sent to me and there are 3 big parts in the send about 7.5 and 52 small parts around 0.05 This is tough as small payments take up space and the large fee of .0013 is not big enough. 55 pennies is large fee to send $4,400 ? Last week I spent $46.00 to wire $1,700 at the bank. Sticking to .0001 per kb should still assure relatively fast acceptance. First off I understand the fee mechanism, but many don't.. Many people think 0.0001 or 0.0002 just works. From your post I am inclined to think you realize BTC size means nothing kb size means everything.So a 1 btc send consisting of 75 x 0.02 is expensive to send. 0.0013 is too small While a 25.2 btc send consisting of a confirmed virgin block is cheap to send. 0.0004 will do the trick almost everytime The problem is a lot of people don't understand this. Most people do not understand that btc amount means nothing. Here is one of my kano.is payment addresses: it has .20453225 in it https://blockchain.info/address/16yLHLoeyuCLPMXkVpC3gyrRYvwRGwjKJrthat is from 1 avalon6 and is the last 20 rewards from kano.is pool to empty this and send to someone will cost 0.0004 to 0.0006 due to the fact it is 20 payments or so. .204 is under 90 bucks and this is why I would like 1 payment a day since it would be 6 payments not 20 plus and sending the coins out would be 0.0002 or 0.0003 tops. I think the rec I have seen was to check how many bits are in your transaction, then multiply by 20 sat. So, for 700bits, 700X20=14000 sat or 0.00014 btc So far it worked for me. If need comes, i will bump it to 30sat/bit, but I haven't done any transactions in a week or two. At this risk of continuing this off topic discussion, doesn't your wallet software automatically compute a reasonable fee for size of the transaction? I remember the first time I bought something with mined coins and was shocked by the fee. Then I realized how huge the transaction was due to tons of tiny inputs, after which it made sense. I've only used Bitcoin-Qt and a Trezor for receiving mined income. Both of them seem to do a decent job of computing reasonable fees when spending. Never seen a stuck transaction. Maybe other wallets don't automatically do as good a job, or maybe people think they know what they're doing and they override the wallet and low ball the fee? Note that in the Trezor's case I periodically transfer from my mining account to my main one so that I can consolidate my bazillion tiny inputs. One drawback of the Trezor is that its signing is slow, so big transactions can take a long time to sign (many minutes sometimes). By consolidating I can pick when I want to spend that time.
|
|
|
Would you consider adding more control over the notification sounds?
It would be great to be able to have a different, user selectable sound for blocks found verses payout events.
It would also be nice to be able to control which notifications have sound and which do not. Currently all you can to is disable all notification sounds.
Yes. Actively working on it. Shooting to get that into this next version and ideally out way before the pool hits 10 blocks a daily with 10 payouts as it will quickly become a bit tiresome instead of useful for some (esp those not interested). edit: I've already demoted the payout notification to not have sound - 2/13. Will make it configurable though with defaults. Cool! Thanks for your hard work!
|
|
|
Would you consider adding more control over the notification sounds?
It would be great to be able to have a different, user selectable sound for blocks found verses payout events.
It would also be nice to be able to control which notifications have sound and which do not. Currently all you can to is disable all notification sounds.
|
|
|
Finally got one of the cats out from under the couch.
+20.2 = edonkey
|
|
|
I just noticed one of my S7s has a best share of 66,576,783,617. That's the biggest I've ever seen from one of my rigs. It would have been a block back in November, which is a mere three months ago Yes, I know that best share is a useless statistic. But it does give me an artificial, meaningless, and admittedly silly sense of accomplishment.
|
|
|
I can't even ask the cats for their guess. When I try, they both hide under the couch. With this brutal difficulty trend, I feel like joining them
|
|
|
Thanks so much for setting up the club! Raising awareness of the Compac stick was important for the community. It was a lot of fun, regardless of whether we hit a block or not. Although there's still a little time for that block to happen I'll leave the email notification running for one more day, then I'll turn it off.
|
|
|
What PDU's would you recommend for 220V running the S7's?
These are good switched PDUs. Either only order factory reset PDU or 1 that comes with the serial cables so you can do a reset and set up IP and everything you want manually. APC AP7911 Switched Rack PDU 16-Outlet 200-240 VAC You can't go wrong with APC PDUs. Never had a single failure. They have tons of models so be careful to pick the form factor that you want with the power capacity that you need. This may just be my personal experience, but you should avoid Tripp Lite. They're probably cheaper, but not worth it. I had a pair of them die in exactly the same way just a few months apart. Bad design resulted in a blown diode.
|
|
|
Block!
Damn. I thought for sure I'd beat you to the punch this time. You must sit in front of your computer clutching your iPhone waiting for the notification
|
|
|
One of my S7s did not come back after the last disconnect. I had to power cycle it remotely via PDU. Weird...
Yet another reason to have a PDU if your miners are remote (mine are at a data center).
|
|
|
Today is down and we are finished at +23.6% for the day!
I cashed ½ my coins today. I will buy back when we drop under 250. Looking forward to this crash. Phil do you use Coinbase to sell your coins? If so, do you use their exchange or just your account (and whatever rate they provide at that moment)? I'm just curious because so far I've never sold any coin. But I'm thinking about it now... I sell them on coinbase directly to my bank. you will need to give a real id to sell like that. and keep sales under 10k Thanks Phil. That's pretty straightforward. I'm already cleared with Coinbase's ID requirements. Note that I was thinking about selling anyway, but not in anticipation of some sort of crash. My issue is that I bought into batch 1 S7s. They were so expensive in BTC terms that the only ROI that I can see is in fiat. At this stage my S7s have earned about 75% of ROI in fiat terms in 129 days. That's largely due to the price increase since I bought these. Whereas I'm only 47% ROI in pure BTC terms. At the current difficulty, I'm still 205 days from a BTC ROI. With the insane difficulty increases this effectively equates to 'never'. These early S7s were always a long shot due to the halving, but now it's basically impossible. The only way to get a return is a combination of selling BTC and selling the S7s, at an opportune time. Man, life was much simpler in the good ole S3 and SP20E days. Those ROI'd in pure BTC terms in no more than 120 days. By the time I sold them, I more than doubled my BTC investment. I can see a not-too-distant future where all I'll have is a pair of Sidehack Compac sticks, just to keep my hand in...
|
|
|
Today is down and we are finished at +23.6% for the day!
I cashed ½ my coins today. I will buy back when we drop under 250. Looking forward to this crash. Phil do you use Coinbase to sell your coins? If so, do you use their exchange or just your account (and whatever rate they provide at that moment)? I'm just curious because so far I've never sold any coin. But I'm thinking about it now...
|
|
|
I have 3 coupons for sale. PM me an offer.
|
|
|
+13.3 = edonkey
Neither cat likes to count this high. They yearn for single digit changes.
|
|
|
When you look at the block statistics page it's a full column of fluorescent green! It's like the seventies all over again, except with bitcoin
|
|
|
adjusted to go down the hierarchy but not up. this is useful feedback. appreciated since i don't see all the common use cases yet. if it's not relevant i'll chime in accordingly and punt the request.
I re-added the worker address for my stick in the Sidehack Compac Stick pool and all I see is that stick instead of all the other members. This is a welcome improvement. Thanks very much!
|
|
|
It's very cool to wake up in the morning and see the pool notifications on my phone's home screen from the previous night.
Just sent a small donation.
thanks. also. you should be able to see solo worker data at this point. there is still an anomaly floating about that i'm trying to trap but it should be healthy enough to access. right now, solo worker address can be any syntax as long as the btc address is there address, address_worker, address.worker. the logic will move up to the top level address and grab all related worker under the user. as far as i can tell, there appears to be no workers without a corresponding solo users stat, and there's no immediate benefit to just see / track a single worker under the user umbrella. Cool! It works! It's kind of magic that this works without an app update. I guess you aggregate the data on your own backend, or something like that. As per your description, when I put in my worker address for the Sidehack Compac Stick pool I see all the pool members. The way that "pool" is structured is that we all use an address provided by philipma1957, with individual workers to track shares. It's a lot to look at, but it does work. No need to limit the view to individual workers on my account.
|
|
|
It's very cool to wake up in the morning and see the pool notifications on my phone's home screen from the previous night.
Just sent a small donation.
|
|
|
you said it right there solo pool. second time today. i'm half reading posts for some reason. it's on its way.
No problem. I missed the fact that solo addresses were not supported in the first post. I guess I'm also having problems reading today. Anyway, no worries. Thanks for your continued efforts.
|
|
|
The worker stats works great for normal hash rate miners. But I have a pair of Compac stick miners pointing at ck's solo pool and they only show as "idle" with a hash rate of 0. Sure the stick miners only produce about 16 GHs each, which is admittedly pathetic. But that's as fast as they go. In fact, they're overclocked I expect that lots of us (including everyone in the Compac Solo Club) are pointing low hash rate miners at the solo pool. It would be nice if that was supported in your app. it should be displayed. put your worker name at the end of this url string, browse it and see if there's data. https://www.kano.is/worker.php?a=fix it first to get data and pm me the worker address if there's a mismatch. The addresses in question are on ck's solo pool, not kano's. Here's an example URL, including the address: http://solo.ckpool.org/workers/1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.Jan11edonkeystickMaybe you can't monitor addresses on the solo pool? I tried to see if there was a different config if I selected the solo pool on the main page of the app, but it seems like there's a single configuration for the app for both pools.
|
|
|
|