|
Bump. Send a reasonable offer.
|
|
|
|
Up for sale is a lightly used GTX 1080 Aero Video card. Used for a slight time for mining, but has been unplugged for quite some time. Always under-powered to 80% TDP. Would like to sell within the US. Willing to use escrow, at your cost. I'll use philipma1957, unless you have your own preference. https://photos.google.com/photo/AF1QipMMD_NDDI528a-zfQFqDHJZsUOnTlrS6AcbqYTT$390 in BTC if shipped to the US, else PM me. Free shipping in the US. |
|
|
|
|
I have my tokens in Exodus and hit the ‘register ‘ button a few weeks back. Am I good to go from within exodus or will I need a new wallet?
|
|
|
|
What is the mining pool sentiment of replacing stratum with this 'BetterHash' proposal by Matt Corallo?
If I understand it correctly, it will decouple pool selection and block construction.
I haven't chimed in on this publicly because I think people would be disappointed by my response and criticise me for being negative. It's a great idea, but will be a complete failure in the real world I'm afraid. Even if I write the reference client and server software to use the protocol, no mining hardware out there and virtually no pool will be using it, thanks to Bitmain's hardware and pool dominance. I've had this discussion with Matt but he's more hopeful than me; otherwise he wouldn't have gone to the effort of formalising his proposal. I'd be happy to be proven wrong on this... All the news stories I've read are glowingly positive that this is a good idea, which I agree it is. However, nobody bothered to ask a miner/ pool operator. |
|
|
|
|
What is the mining pool sentiment of replacing stratum with this 'BetterHash' proposal by Matt Corallo?
If I understand it correctly, it will decouple pool selection and block construction.
|
|
|
|
So I read your post, and came across this video on Youtube: https://www.youtube.com/watch?v=59I1KvEpMco. He concentrates on a 3-season approach, however I'm envisioning a modified box that still vents out the top, but vents to a 3" PVC pipe, inlined coupled to a 4" fan. This way I could run the box inside the house. I have a pipe available to me in my utility room that is vented to the outside. A fan can be put inline. How many CFMs does one need for a 6-card rig of 1080Tis or for multiple rigs of Tis? |
|
|
|
Are there instructions to claim BTCH if held BTC in Trezor?
Trezor would need to be petitioned to split them on your behalf. They would have to do an update, since I don't think they'll export your key. Not sure if there has been a concerted effort to do this. |
|
|
|
wallet isnt sync since tommorow
Mine wasn't syncing either but a reindex fixed it for me, i just typed reindex=1 into the hush.conf located in appdata/roaming/hush What is the rpc user/pass info in there used for? |
|
|
|
I've switched a couple of my rigs over to Nicehash. Similarly configured machines have wildly different daily estimates of earnings.
Can anyone point me to setting, configuration strategies, etc. to normalize and maximize revenue using their service?
If privacy is not an issue. go the nicehash email full account mine method which gives cheap withdrawal to coinbase. this will all be tracked and taxable but you save on fees. I am like Phil I have 3 btc addresses and left coins build up. I check 4 times a day manually but most often mine Zec due to ease of mining it. I am referring to maximzing hashrate/revenue on the rig, not take home revenue. One machine forecasts 60 to 70% more revenue than the one next to it. |
|
|
|
|
I've switched a couple of my rigs over to Nicehash. Similarly configured machines have wildly different daily estimates of earnings.
Can anyone point me to setting, configuration strategies, etc. to normalize and maximize revenue using their service?
|
|
|
|
|
If you wanted to venture into further alt-coin earnings, you could post your write-ups on steemit.com
|
|
|
|
How do I get BTCH corresponding to BTC? Same way? Private key into agama?
With the way this is currently going, I would proceed down this path with extreme caution. If you are this risk adverse, absolutely make sure the underlying BTC corresponding to that private key is already moved before exposing the key to the Agama wallet. |
|
|
|
|
Not every chip is created equally. When you're mass producing anything, there will be a natural distribution of quality. It's been called the ASIC lottery or chip lottery. That one chip on that card can run slightly faster than the rest at the same power envelop. Said another way, given a fixed clock rate, it will consume less power.
This is how Intel is able to sell "low power" versions of their chips that are drop-in replacements as other chips (ie Intel i5 6500t vs 6500). They're able to cherry pick a few chips that run very well and create a market for them.
|
|
|
|
how are you doing export private keys from hush wallet 0.70.0?
thank you..
Go to the addresses tab, right click on an address, and select obtain private key |
|
|
|
Looking to buy around 10 hush, DM if interested and you have it in your wallet.
Not willing to go first, so escrow is acceptable.
Thanks,
I tried to PM you, but it would not send since you're a newbie. |
|
|
|
So you cannot spend a bech32 to a 'standard' address? If so, I was not aware. Maybe that's not what you said....
I get that '3' addresses are segwit-compatible-multi-sig addresses.
Anyways.. would you not be spending to a bech32 adddress upon a block found/payout? Is the finding address not a '1' or a '3' address?
Yes a bech32 is neither a 1 nor a 3 address; it's a new format that starts with bc. You can spend from any address to any other address. The bech32 addresses are not nested P2SH addresses, they are native segwit addresses and thus 10% smaller than 3x segwit addresses. Each wallet that has a bech32 address will have the private key to a corresponding 1x address or 3x address but I don't have code in ckpool to read a bech32 address and then decode it to the underlying address, and we can't actually assume that wallets will know to look for the 1x and 3x counterparts of their bech32 addresses should you send coin to them instead of the actual bech32 address. Sending directly to bech32 is something I have not investigated so I don't even know if you can generate directly to them. This pool does all payments through generation transactions which by nature are not segwit transactions. You've been much helpful. Thanks. |
|
|
|
please be aware that bech32 addresses (starting with bc) which have started appearing in some wallets are not currently supported by this pool
Why is this? Just not popular enough to add support? The 'standard' has been around for a while now. I've found a few places reject this format, even though electrum has offered the format for some time now. No code in the pool to support it? I'm also not sure on whether you can generate directly to a bech32 address since it's meant to be segwit to segwit only. So we've not successfully mined a block to a native SewWit address? I'm a bit fascinated by the (lack of) SegWit adoption. Segwit address yes we have, plenty. Bech32 is a unique segwit to segwit only address format. Virtually all segwit in use today is using the 3x address format though. So you cannot spend a bech32 to a 'standard' address? If so, I was not aware. Maybe that's not what you said.... I get that '3' addresses are segwit-compatible-multi-sig addresses. Anyways.. would you not be spending to a bech32 adddress upon a block found/payout? Is the finding address not a '1' or a '3' address? Honestly... I'm not trying to be a troll. I just would like to know the reason for the slow rollout of such 'upgrades'. Is it technical? Political? Trying to understand the landscape... |
|
|
|
please be aware that bech32 addresses (starting with bc) which have started appearing in some wallets are not currently supported by this pool
Why is this? Just not popular enough to add support? The 'standard' has been around for a while now. I've found a few places reject this format, even though electrum has offered the format for some time now. No code in the pool to support it? I'm also not sure on whether you can generate directly to a bech32 address since it's meant to be segwit to segwit only. So we've not successfully mined a block to a native SewWit address? I'm a bit fascinated by the (lack of) SegWit adoption. |
|
|
|
please be aware that bech32 addresses (starting with bc) which have started appearing in some wallets are not currently supported by this pool
Why is this? Just not popular enough to add support? The 'standard' has been around for a while now. I've found a few places reject this format, even though electrum has offered the format for some time now. |
|
|
|
|
Show Posts
