|
namecoin just checks the result from bitcoin mining and if it is good, applies it to the namecoin block tree. BTCguild does namecoin along with bitcoin on pplns. namecoins are worth about 6% of a bitcoin. I send the namecoins i make to BTC-e to convert them to bitcoins. then i have to wait until i meet the minimum transfer amount to send them to my wallet. I wouldn't care if i stopped getting namecoins.
|
|
|
|
|
You guys complaining about payout are watching the confirmed amount and not the total amount, right? also, in my opinion, expecting a payout more often than once every 24 hours is being greedy. I've set my payout to be once every 7-10 days and have had no problem what-so-ever.
|
|
|
|
does anyone know what the specific usb connector that plugs into the ASICminer 49 port hub is called? none of the cables i have around the house seem to be the correct one. I need to know what to buy.
It's a USB A-to-B cable. THANKS!!! |
|
|
|
|
does anyone know what the specific usb connector that plugs into the ASICminer 49 port hub is called? none of the cables i have around the house seem to be the correct one. I need to know what to buy.
|
|
|
|
Ok, i have a 49 port ASICminer Hub. My issue is that none of the USB cables i have laying around from dead hubs will plug into it. the hub side connector is too big on the cable. does anyone know what usb cable i need to get?  |
|
|
|
|
You could stop mining and wait for all your share to pay out. once there is no more coming in a manual payout would zero your account, I think. Of course that would be expensive in unmined shares.
|
|
|
|
|
Another thought, try with one Blade first. I seem to remember reading that the blades restart if they are under powered.
|
|
|
|
because i am a linux guy..   I think he was being sarcatic. |
|
|
|
|
as far as i know, there aren't any cpu mining programs any more. There may be some old ones out there somewhere.
|
|
|
|
So I've gotten the two blades to receive work from bitcoind and I can see it in their webgui that they are receiving work. After about two minutes, however, they stop receiving work and their timers reset and bitcoind on the server becomes unresponsive and have to reboot to get bitcoind to start up correctly again.
Even running one blade directed at bitcoind hangs up and bitcoind becomes unresponsive. Anyone have any ideas for solutions?
Hmmm, It might be that bitcoind isn't fast enough for the blade. you might try putting a stratum proxy in between the blade and bitcoind. something to act as a buffer of sorts. This is just a thought on my part. |
|
|
|
|
the price on the Neptune is about $10,000.00 for previous customers.
|
|
|
|
Nothing from Dave about hardware availability.  I guess he made all the money he needs.  or, he's waiting until stuff is in hand so he won't get yelled at. |
|
|
|
|
what about the BlackArrow stuff?
|
|
|
|
The thing is that there is more than one right solution for any given block. All the pools and solo people use different inputs than every one else in hopes that their input will find the desired output. Say your hashrate is 5 Gh/s, that means you are checking 5 million different inputs every second looking for the one output that will complete the block.
5 billion :-) oops, i just knew i was gonna mess that up. I even went over it in my head a few times and still typed it wrong. When ever i answer questions here i feel like i'm back in college taking a test. |
|
|
|
I thought of a way to reduce orphans: more full nodes on the network. Unfortunately, non-mining full nodes are not rewarded directly by the protocol. Also, most "miners" are not full nodes: they simply rely on pools. More nodes reduce orphans by speeding up block propagation: - By having more aggregate CPU power verifying transactions. Slow CPUs probably don't help too much for preventing orphans.
- By having more aggregate bandwidth for relaying transactions and blocks.
- More nodes make any successful DDOS more expensive to run.
My personal Bitcoin node has been in the planning stages for months. When up, it will have an average bandwidth of ~463kbps (burstable to 5Mbps). Calculation: (300GB/month(cap))/(30days/month)/(24hours/day)/(3600seconds/hour)*(8bits/byte)/2(symmetric bandwidth usage) If I get a second (or better paying) job, I will consider renting a dedicated server with ~7.7Mbps (burstable to 100Mbps) (5TB cap) Edit: read page 4: sending only block headers sounds like it just might work (assuming the node has seen all the transactions) Isn't every Wallet a node, providing that they are using bitcoin-QT? |
|
|
|
It doesn't work that way. It didn't take that long to find a specific block, it took that long to find any block. Every time someone else finds a block, we start looking for a new block based on what they found. That's why we call that 12 hours a round, not a block.
So every time you see "stratum detected a new block" in the miner log would indicate that the hashing power is being spent on solving a block rather than looking for a new one? Unless someone solves that block first. But if you don't see a new block detected for a long while, the hashing power is being spent finding a new one? How is hashing power divided between looking for new blocks vs solving, is there a ratio set by the pool operator depending on how many active blocks have been found? -noob. When you see "stratum detected a new block" it means that someone somewhere in the world found a solution for the current block and that a new block is now being worked on. Solving is looking for new blocks. Different names for the same thing. The thing is that there is more than one right solution for any given block. All the pools and solo people use different inputs than every one else in hopes that their input will find the desired output. Say your hashrate is 5 Gh/s, that means you are checking 5 million different inputs every second looking for the one output that will complete the block. Ah, so there is only one active (known) block at a time that all miners are working to solve. Once that is solved, the answer leads to the next block? Also I was a bit thrown on the block vs round. I checked the wiki but will do some more looking. Sorry if my questions are elementary, I am fairly new and I must say it is quite a lot to grasp. Thank you for taking the time out of your day. Yes, you have got the blocks down. A round is how long it takes for the pool to find a block. If it took 10 hours for the pool to find a block, that is a 10 hour round. A lot of people will call that a 10 hour block, but that is confusing to new people. |
|
|
|
It doesn't work that way. It didn't take that long to find a specific block, it took that long to find any block. Every time someone else finds a block, we start looking for a new block based on what they found. That's why we call that 12 hours a round, not a block.
So every time you see "stratum detected a new block" in the miner log would indicate that the hashing power is being spent on solving a block rather than looking for a new one? Unless someone solves that block first. But if you don't see a new block detected for a long while, the hashing power is being spent finding a new one? How is hashing power divided between looking for new blocks vs solving, is there a ratio set by the pool operator depending on how many active blocks have been found? -noob. When you see "stratum detected a new block" it means that someone somewhere in the world found a solution for the current block and that a new block is now being worked on. Solving is looking for new blocks. Different names for the same thing. The thing is that there is more than one right solution for any given block. All the pools and solo people use different inputs than every one else in hopes that their input will find the desired output. Say your hashrate is 5 Gh/s, that means you are checking 5 million different inputs every second looking for the one output that will complete the block. |
|
|
|
Hey guys, i have a problem, i get nothing at mining.
I mine 10-30 minutes and nothing happened, i will get LW (i dont know what it means) and some NB(i dont know what it means) but i have all time 0khash/s.
I don t know what is wrong, in the past i had mined bitcoins whit 200mhash (gpu) and now 0khash??? There must be something wrong. I mean this is with cpu i think but there muste be some khash.... What is wrong?
You don't have any hardware for cgminer to mine with. It is no longer a cpu or gpu miner. What was the last version with GPU support and would that one work with Blue Furys? |
|
|
|
|
So, am i reading this right? the OP is offering to reimburse the pools for orphanned blocks that may be the result of increasing the size of the blocks? And, they have some way to speed up the creation of new wallets?
|
|
|
|
Finally broke that block... 12:40, ugh.
Now imagine you'd had mined that Block solo o.0 (personally, with my performance I wouldn't even live to see the day that block got solved :p ) It doesn't work that way. It didn't take that long to find a specific block, it took that long to find any block. Every time someone else finds a block, we start looking for a new block based on what they found. That's why we call that 12 hours a round, not a block. |
|
|
|
|
Show Posts
