seriously, i can't find ONE mining service that won't kill my computer  You might want to provide a bit more information than this. If you're trying to mine BTC using the CPU or GPU of your computer, save yourself the headache and stop. You're about 3 years too late to the party. You'll need to purchase dedicated mining hardware, running on ASICs. |
|
|
|
|
Sorry for the few day delay on the updates, but before I get to the numbers, I'd like to take a moment to thank you, kano, for the analysis. You've certainly addressed one of the issues of the decentralized nature of p2pool: reliance upon who-knows-what kind of hardware and connections and bandwidth across the network. Because there are no real minimum requirements to setup a p2pool node, pretty much anybody who wants to do so, can.
This week I switched over to TheAnalogKid's node, located right up the road from me. The switchover was completely seamless as the work I'd done on the NastyPoP was tracked and kept right on going. From my perspective, the only way a miner would even know if he'd moved from the US to EU or back is that on the nastyfans miner status page, a new graph appears.
Speaking of those graphs, it sure would be nice to see the share lines colored differently for dead and orphaned shares. Currently a miner cannot tell if a submitted share-chain share was accepted. For example, the first 3 or 4 share-chain shares I submitted on the US node were likely either dead or orphaned. Of course, it could have been that previous shares were dropping off the chain right as the new ones were being found. I couldn't tell, and that's why I'd like to see a visual representation... say red for orphans and purple for dead.
Alright, onto the numbers... my NastyP2P miner suffered some dead/orphaned shares (I think) at the beginning of the week, and the payouts reflect it.
3/20 - 3/27
NastyPoP - 0.02843568BTC
NastyP2P - 0.01970915BTC
Expected - 0.033BTC
Luck - 90.54%
OP updated
|
|
|
|
Someone please help me understand the concept of the "difficulty" setting.
So far, I get that I have 3 - s3's on antpool with a recommend difficulty setting of 512K.
Next week, when my S4 comes in, I set the difficulty for that 2THS/S machine at something bigger because it is more powerful. I forget where this is set right now, but I know it is a setting.
Would a S5's be set somewhere in between an S3 and S4?
Does this mean that the S4 is more efficient because it can take on bigger chunks of work?
Is work or shares dolled out according to the level of difficulty?
Does the higher dificulty level of a faster machine like the 2TH/s S4 mean that the machine will remain profitable to operate further in the future?
So far, I've read two "beginners" level books but they do not explain this. This is keeping me awake at 3:45 AM local time so please help put my mind to rest so I can go to bed!
Thanks,
Tom
If your mining on Antpool, then just go to sleep because the difficulty is set by the pool software with what's called a dynamic diff. You have absolutely NO CONTROL over what it TELLS your hardware is the minimum acceptable share difficulty. I understand but is a S4 better than 4-S3's (if S3' ran at 500MH/S)? Is the S4 going to produce more/faster/better hashing at the end of the day because of the level of difficulty it can take on? I am also assuming that power is the same. 2TH/s is 2TH/s no matter how it is achieved. Doesn't matter if you've got 1 S4 or a room full of block eruptors. The "level of difficulty" is only a falsified setting introduced by pools to help reduce the amount of traffic they need to accept and process. |
|
|
|
Eclipse Mining Consortium (aka Eclipse or EMC) at 5% PPS pays best for me and that's where I mine.
Many won't mine here because of the association with Butterfly Labs. Me, I don't care.
Always paid within an hour of request. No question in my mind that payouts are bigger here than anywhere else.
Care to explain how a PPS pool charging 5% has bigger payouts than anywhere else? Let me answer that for you, so as you're not confused: it doesn't. |
|
|
|
Gotcha. Shifts are supposed to be ~50 minutes long. Kano did a really nice detailed writeup on the payouts/shifts a few pages back. I've typically seen the same thing you're reporting 40-48 minutes or so. Honestly, I have no idea why kano chose to display 99 shifts on the page as that number really isn't relevant to the your shares' validity except on the rare occasion where 99 would equal 5N  |
|
|
|
5x current difficulty is N, which at 2.5PH/s is 111.47 hours. I'm a bit confused by your question, though, so maybe that's not what you're looking for |
|
|
|
|
You might have some luck with localbitcoins.com. I'm not sure if you'd have any luck trying to sell the prepaid cards here in the marketplace, but you could try that as well.
|
|
|
|
im using C#.NET or ASP.NET doesnt matter. But i need to generate a few addresses in same time.
For example i ll generate 10 addresses in one script. And then i ll use them later. One by one in another scripts.
Is there any doc you know? or any algorithm?
WTF? Did you just copy and paste the OP? I mean, word for word... lol. Try reading the replies... they provide the answers. |
|
|
|
For a long time now, I've wanted to run a full bitcoin node on my Windows computer and NOT run the wallet part of Bitcoin Core (formerly -QT). I wanted to contribute a full node to the network, but not use the Core wallet, nor have the wallet software load up and sit there taking up system resources for no reason except to contribute the node. I read and asked a lot, before I finally figured it out. Here's how: Dowload and install Bitcoin Core from the official download page -- https://bitcoin.org/en/download -- but DO NOT START THE PROGRAM in the usual way. Instead, open the Windows Command Prompt program and enter cd\program files\bitcoin\daemon [return] .. then bitcoind [return] That starts the program, even though you see no indication of that in the window. You can't close the Command Prompt window or the program stops; but you can minimize it to the tray and it continues to run fine. After it's downloaded the blockchain and begun doing its regular function, you can check that it's running well this way: Open a second Command Prompt window and enter cd\program files\bitcoin\daemon [return] .. then bitcoin-cli getinfo If you've opened Port 8333, you should see more than 8 connections, and all is well with the world. To stop running the node, you can just close the Command Prompt window it's running in. This does not disable the wallet functionality in any way, shape or form. All it does is run the core daemon without the pretty GUI. You are quite able to still perform sends, create new wallet addresses, etc. You have two choices if you want to actually disable the wallet: 1) Compile and build the client yourself without compiling in the wallet. Easy enough to do in *nix OS. 2) Start the service by passing the -disablewallet parameter. |
|
|
|
My new S5s got caught up in customs so I rented 10TH to point at the pool for the next 10 days or so.
Take THAT customs.
Well done! I hope your rentals work out for you |
|
|
|
|
Wow... your laptop craps out just from the CPU spooling up? Have you tried other processor intensive tasks to see if it behaves the same way? I mean, I know that Bitcoin Core can run up the CPU usage when it's synching up the blockchain... but the issue is definitely in your hardware.
|
|
|
|
Sorry its a B+ I have followed various of guides, but a friend of mine told me the problem is on Githubs site. It's definitely not github. Something's going on with your side. Don't try to clone a branch, clone the repo. Then, switch to the branch you want. I have downloaded the files now, but I am not able to use the command qmake to start creating the qt Did you install all the prerequisite libraries and packages to be able to build? Honestly, I'm not sure that B+ will have access to enough available RAM to actually build the core to begin with, unless you're doing some fancy virtual RAM swapping with an attached external drive. There are a number of tutorials on how to build Bitcoin Core on a Pi; however, if you've never used Linux before, I'd suggest you do a bit of reading on the OS and how to get around in it prior to attempting. |
|
|
|
just have look on the "Confirmations" field of your transaction in blockchain.info...
It's possible that the coins never made it to the recipient, yet still show confirmed because of the "mixer" aspect of using the shared transaction. That's why you need to recover the intermediate addresses to see if the coins are stuck there. |
|
|
|
|
Ok...
1) Did you send more than the minimum of 0.01BTC and less than the maximum of 50BTC?
2) Did you try to recover the intermediate addresses?
3) Did you look at the recipient's address on the blockchain to see if they received a transaction in the amount you sent?
|
|
|
|
|
From a mining perspective, you'll need to have about 1TH/s to earn 0.01BTC daily at current difficulty levels. So, good luck finding any kind of faucet which provides that kind of coin. Signature campaigns, depending on your rank here, have the potential to pay that out. For example, at my level with the signature campaign I use, I would have to post about 10 constructive posts a day to make 0.01BTC.
|
|
|
|
Sorry its a B+ I have followed various of guides, but a friend of mine told me the problem is on Githubs site. It's definitely not github. Something's going on with your side. Don't try to clone a branch, clone the repo. Then, switch to the branch you want. |
|
|
|
Not too bad... Nice way to earn 3 and change percent. Hope you get paid |
|
|
|
Hahahaha... Too funny |
|
|
|
Not sure but when the pool first started it paid every hour and we asked for it to be extended as a lot were getting very small payments.
The amount due to me is larger than what was paid a couple days ago from the older difficulty.
Well, you would get ridiculously small payments. One would expect to find a difficulty 1 share after 2^32 attempts. That means a 1TH/s miner would expect to find 232.83 a second. Let's say for the sake of argument that I set my difficulty to be 232.83, so I'm expecting to submit 1 share per second to the pool. That's 3600 shares in an hour. 3600 * 232.83 * 0.00000000053513 = 0.000448534 BTC. So, 24 of those tiny payments a day. How about the guy with an S3? 0.00019736 BTC an hour. An S1? 0.00008074 BTC an hour. Basically, if you've got anything less than an S3, you're likely going to end up spending more in fees trying to send your coin somewhere than you're getting from mining in the first place. Obviously, the longer you set your payout threshold, the more BTC you're going to get per payout. That's why I don't understand why any typical miner would bother to setup payouts at anything less than 24 hours. Sure, if you're pushing hundreds of TH/s, you might accept more payouts per day, but pushing that kind of hash rate is not a "typical" miner |
|
|
|
|
Show Posts
