Bitcoin Forum
May 10, 2024, 09:53:43 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 [6] 7 8 9 10 11 12 13 14 15 »
101  Bitcoin / Mining / Re: US Mining Hardware Deduction/Depreciation on: April 27, 2014, 09:52:44 AM
a story problem


mine 1 BTC at $400   - logged as income
Cost to mine that same 1 BTC - $490 logged as expense

net loss - $90

sold same 1 BTC at $500


do you pay capital gains on $100 or $10?
Not a lawyer or accountant, but here's how I'd figure it.

You mined the bitcoin for a value of $400, it's the same as if your boss (for a typical job) paid you $400 that day.  So you add the $400 to your regular income.

You can then deduct the $490 (as a business expense expense if you're running your bitcoin mining as a business, or as a hobby expense if you're not a business but itemize your deductions).  Either way, you'd net out with zero income, so no extra tax there.  That said, consult with an accountant on whether you can deduct the extra $90 loss from your other income. Also, you can't deduct at all if you mine as a hobby, and you take the standard (non-itemized) deduction.

Next, you sold your bitcoin for $500. This means a capital gain of $500 - $400 = $100. So you pay capital gains on $100.
102  Bitcoin / Pools / Re: [185 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: April 25, 2014, 09:30:40 AM
Don't complain. Be thankful  Wink
Oh, I'm very thankful, and I want more! Lemme go buy up some more hardware so I can cash in on this mania! ... *evil grin*
103  Bitcoin / Pools / Re: [185 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: April 25, 2014, 09:06:22 AM
It seems our pool hash rate has shot up by over 100TH in the last few hours, and it's still rising.  Yay us! Anyone know what happened? Did some smaller pool switch to using p2pool as their back end?
104  Bitcoin / Legal / Re: OK, Denmark, time to step up. on: April 24, 2014, 10:29:47 AM
No country will ever give Bitcoin the status of a legal tender because this is utterly impossible. Only the notes printed in state's own mill can be legal tender by law. But this does not mean Bitcoin is illegal, just because it is not legal tender...
Congratulations, you just declared that all coins are not legal tender.

You might want to review what "legal tender" actually means...
105  Bitcoin / Legal / Re: How I plan to do my taxes (USA) on: April 23, 2014, 07:57:44 AM
A good read, thanks for the tip! Seems the guy did roughly what I did, but with the benefit of less transactions and an accountant to talk to. Smiley
106  Bitcoin / Hardware / Re: U2 Antminer USB Hubs on: April 21, 2014, 07:04:24 AM
Check here for some ideas: https://bitcointalk.org/index.php?topic=253749.0
107  Bitcoin / Legal / Re: How I plan to do my taxes (USA) on: April 20, 2014, 12:48:24 PM
Great info.

I still think it's ridiculous that you have report mining as ordinary income and keep track of the current US price at the time. But great job following the law.
Thanks.  I'm honestly not thrilled about it either, but I still live out in the real world. Pipe dreams about paying no taxes are just that, dreams. Last thing I need is for them to turn into real-life nightmares. Mind you, I'll still petition the IRS to create a new category (or at least an alternate ruling) for cryptocurrencies, but until then, I'm kinda stuck.
108  Bitcoin / Legal / Re: US Taxes - Form 8949, Turbo Tax and Importing Transaction data on: April 19, 2014, 11:26:44 AM
Thanks for taking the time to share how you went about doing your taxes in detail here.  This could be very useful for many people in the future.  Smiley

No problem. Surprises me I didn't find any other thread about this. Of course I didn't look that hard. I got myself another 5 months to figure this out.
I posted something pretty similar (though much more long-winded) here: https://bitcointalk.org/index.php?topic=572763.0
109  Bitcoin / Legal / Re: How I plan to do my taxes (USA) on: April 17, 2014, 05:07:41 PM
And the promised gawk script.  Save the script below into a new file named run.gawk. (Yes, I can be simplistic. Smiley )  If you use another name, adjust the run command you use accordingly.

Code:
BEGIN {
# Typical run command:
# gawk -f run.gawk bitstampUSD.csv > bitstamp_daily.csv


# Input format:
# Date/Time, $/BTC, #BTC

# Constants for reading the date/time split values
# Sample date: Tue Apr 04 21:48:17 2006
DAY = 3;
MONTH = 2;
YEAR = 5;

FS = ",";
OFS = ",";

# Variables in the script
TotalBTC = 0;
TotalDollar = 0;

} # BEGIN

function MonthToNum(val)
{
# Forgot there's no switch/case in awk...
if ("Jan" == val) return 1;
if ("Feb" == val) return 2;
if ("Mar" == val) return 3;
if ("Apr" == val) return 4;
if ("May" == val) return 5;
if ("Jun" == val) return 6;
if ("Jul" == val) return 7;
if ("Aug" == val) return 8;
if ("Sep" == val) return 9;
if ("Oct" == val) return 10;
if ("Nov" == val) return 11;
if ("Dec" == val) return 12;
return 0;
} # MonthToNum()


# Main program
{
# Store the rate and amount
Time = strftime("%c",$1);
Rate = $2;
Amount = $3;

#Get the date components
split(Time, Components, " ");
CurrentDay = Components[DAY];
CurrentMonth = Components[MONTH];
CurrentYear = Components[YEAR];

# Check for a new day. Ignore the first line.
if ( NR != 1 && ( CurrentDay != PreviousDay || CurrentMonth != PreviousMonth || CurrentYear != PreviousYear ) )
{
# New day.  Print out summary of last day and reset.
print PreviousYear "-" MonthToNum(PreviousMonth) "-"  PreviousDay, TotalDollar / TotalBTC;
TotalBTC = 0;
TotalDollar = 0;
}

# Store the values for the current day
TotalBTC += Amount;
TotalDollar += Amount * Rate;

# Store the date for comparison with the next line
PreviousDay = CurrentDay;
PreviousMonth = CurrentMonth;
PreviousYear = CurrentYear;
} # Main program


END {
# Print the final day results
print PreviousYear "-" MonthToNum(PreviousMonth) "-"  PreviousDay, TotalDollar / TotalBTC;
}
110  Bitcoin / Legal / How I plan to do my taxes (USA) on: April 16, 2014, 06:33:26 AM
-- Background --

I thought it might be interesting to document the process I'm following to figure out how to pay my bitcoin-related taxes as I finalize my taxes for the previous year.  I want to point out the obvious before I start: I'm neither a lawyer nor accountant, so bear in mind that I'm certainly not qualified to give tax advice! I'm just documenting how I myself plan to figure out my taxes. I strongly urge you to consult with a real accountant before trusting anything I say in here.

I do want feedback on this process, so please feel free to pitch in with any thoughts! I'm keeping this thread unmoderated, but I do have a request. If you believe that the IRS is evil, that taxes are evil, that we shouldn't pay the IRS, or anything along those lines, more power to you - but please don't post those comments in this thread.  This thread is specifically about how to comply with IRS regulations. There are lots of other threads for complaining; please use one of those to voice your opinion, or start your own thread.

Some background about me.  I first became involved in bitcoins around 2011, and I mined a couple of coins back then (worth all of twenty bucks at the time!) before more or less forgetting about the idea.  I started back up in 2013, and I've been a strong proponent ever since.  I'm a US citizen, and yes, I do pay my taxes scrupulously.  I have some programming experience, enough that I can code up a basic application without shooting myself in the foot, but I'm certainly not a professional programmer.  I also have extensive experience with Excel, which came in handy.

I don't have access to an accountant who is familiar with both IRS rules and bitcoins, so I decided to go it alone.  I'm using Turbotax to handle most of my taxes, and entering the bitcoin-related tax info manually into it. That said, I'm not sure I can trust Turbotax - I found, documented, and reported a bug in one module that would have had me pay a whopping five times my taxes to the IRS! I also have an extension for filing, so the April 15 deadline doesn't apply to me.


-- Preparation --

I started out by exporting all transactions from my primary wallet into a spreadsheet. Then, I went to each Web-based wallet or exchange site I used, got a data dump of all my transactions there, and added it to the spreadsheet.  As a side note, I'm glad I didn't use blockchain.info as a wallet in 2013.  Their exports are horrible! They contain almost none of the info I needed to categorize or even identify my transactions, and the export had full bitcoin transaction info (such as multiple source addresses, multiple outputs, no labels for addresses, etc.) -- almost all of which is irrelevant for tax purposes, or worse, misleading. I played around with my 2014 data a bit, just to see how it would work, and if they don't improve their export interface by next year, I'll have to resort to screen-scraping and copy/pasting the info into a spreadsheet.

Then I started perusing the transactions for patterns.  I would look for common ways in which I earned coins, or different transactions where I would spend coins for something.  The idea at this stage was just to get an overall feel for how I've been using bitcoins.  I started labeling the transactions and grouping them into several broad categories.

Next, I categorized each transaction as follows: buy coins, spend coins, mine coins, or other.  Buying coins is any transaction which resulted in me getting coins I didn't have before, except for mined coins.  Spending coins is any transaction which resulted in me getting something of value in exchange for coins. It doesn't matter what the "something" is for tax purposes - could be mining hardware, could be a book or a song, could be a pizza!  Mining includes both generated coins (solo mining and p2pool or similar) and pool mining (where the mined coins go into a common pool account, then get distributed to miners).  All other transactions, such as giving coins away as tips or transferring coins between wallets, are irrelevant for tax purposes.

After that, I gathered up my documentation. In particular, I got any receipts I could for cash-to-coin and coin-to-cash transactions, since that establishes my cost basis for those coins.

Then, I had to find a reliable price source for valuing my mined coins.  After mulling my options, I eventually decided to go with MtGox pricing up until the end of 2013, and Bitstamp for 2014 onwards.  Conveniently, bitcoincharts.com has historical records of pricing, and even actual transaction volumes, posted at http://api.bitcoincharts.com/v1/csv/ .  I downloaded the files for MtGox to USD and Bitstamp to USD, then tried to import them into Excel - and it failed miserably. The files had over 1M lines, which is the max Excel can handle. In addition, the date/time is in UNIX epoch format, which takes some effort to convert to usable form in Excel. (It's not hard, just another irritating step to handle.) So, I wrote a little gawk script to parse the files, calculate the daily weighted average, format it in human-readable form, and put that into a text file.  This got me a daily price for the coins. I'll post the gawk script in a follow-up post in this thread, if anyone would like to use it.  A little Excel vlookup() magic later, I had the exchange price for each non-cash transaction in my log.


-- Tax Puzzlers --

One of the first questions was whether to treat my bitcoin exploits as a hobby or a business. While I do have a desire to profit, the IRS requires a lot more than that before accepting it as a business.  For example, it requires an actual profit every once in a while ... And while classifying bitcoin stuff as a business would allow me to deduct my mining losses, it would also impose massive paperwork overhead on me. In the end, I decided that based on how I use bitcoin and how little it matters to me in terms of income (compared to my day job), I couldn't justify calling it a business. So, hobby it is!

I struggled a bit with trying to figure out when I should be looking at transactions for capital gains, when for income, and when it's irrelevant for both. Eventually, I hit upon a revelation (that may be obvious to others, but was news to me). Income tax should be considered only when a coin is received. Capital gains tax should be considered only when a coin is spent. However, in both cases, it only counts if the coin was spent or received in exchange for something of value.  (As per the IRS instructions, mining is considered something of value.) If I transfer coins between wallets, no tax of either type is due - just like no tax is due if I move money between two accounts at different banks, or move my stock holdings from broker A to broker B.  Similarly, if I give coins to someone as a gift or tip (and receive nothing in exchange for the tip), then no capital gains applies. From the very name, capital gains only matter if you gain something.

That said, to calculate capital gains, you have to know your cost basis. So, to get an accurate valuation of all my coins, I figured out that I have to include *every single coin-received transaction* in my capital gains calculations, even if they're not counted as taxable income. This information matters not just for this year, but for figuring out the cost basis for next year's taxes too. However, as noted, cap gains taxes are only due when something of value is received, so only coin-spend transactions that resulted in a taxable gain are included.

At some point in 2013, I gambled a few milliBTC at SatoshiDice. I was a bit puzzled by how to account for these, but ultimately decided to treat them roughly the same as RL gambling. Any wins would be totaled up, cost of gambling (the value of the bets) deducted, and any profits declared as income. As it turned out, I didn't win one single bet, so the issue was moot for me.  As the gambling total was a loss, I ignored it for tax purposes.  (Just like you generally can't deduct fiat gambling losses from your non-gambling income, I doubt you could deduct bitcoin gambling losses from bitcoin non-gambling income. An interesting question would be whether you could deduct your bitcoin gambling losses from fiat gambling wins.)

Another oddity I had to deal with was group buys and investments.  For example, I bought a few shares in a miner that was hosted by the group buy organizer. Periodically, I would receive my share of the coins that the miner earned.  So, what was the right way to account for this? Do I treat it identically to a hardware miner purchase, and the income I got as mined coins? Or do I treat it more like an annuity? Is it also a gamble, like the SatoshiDice games? Or is it more akin to a stock or mutual fund purchase that pays dividends? In the end, I settled on treating it the same as a hardware miner purchase. I figured that I effectively own a part of the miner, and the coins I receive are not substantially different (for tax purposes) from coins I'd mined myself.

The last puzzler is one that will hit me in 2014. I (perhaps foolishly) bought and traded some mining power on Cex.io, and that very quickly turned into a painful loss. How will I account for the coins "mined" by Cex.io? Can I deduct the trading losses from my income? Luckily, I don't have to decide these questions now, as they are for next year's taxes, but I'm willing to hear some discussion on the topic of how to account for cloud mining and btc investment losses!


-- Tax on Income --

So, now that I had the info sorted out, I had to figure out my taxes.  There are two parts for this: income tax for mined coins, and capital gains for spent coins. As of now, I'm not aware of any tool that calculates taxes on mining directly. So for the mining part, I took a straightforward approach: I treated each mined coin as income at that day's BTC-to-USD rate (this is as per the IRS instructions), and counted that as general income.

However, you can't mine bitcoins with just air! Mining gear costs money, and as I understand IRS rules, you can deduct the cost of mining expenses up to the value of the mining income generated, if you're itemizing your deductions.  In my case, I have to itemize anyway, so this is perfect for me. (Side note: if you treat your bitcoin mining as a bona fide business, then things get complicated and you should talk to your accountant - but you can probably deduct the cost of mining expenses even if it's more than your mining income.)  When I purchased mining hardware with bitcoins, I again calculated the USD value of each transaction using that day's exchange rate.

I didn't deduct any hardware I used for general purposes because the IRS rules on how much you can deduct in such cases are arcane at best -- so for example, even though I bought an AMD video card over an nVidia one for my desktop PC just because I could mine a little with it, I didn't even attempt to figure out what portion of its cost is deductible.  I did deduct the cost of the dedicated mining hardware I'd purchased and the hubs, power supplies, etc. that are used exclusively to support mining.  Again, the rules get very complex for gear with an expected usable life of over one year, but in general, mining gear is considered obsolete after a year. So, I didn't have to worry about depreciating the cost of the hardware over multiple years.

It's also legit to deduct the cost of electricity and cooling required to run the mining hardware, but in my case, electricity is cheap. The value of my time in figuring out the deductible cost would actually be more than the deduction itself! So to keep my life simple, I treated that as zero.

So, all that said, it turns out that I paid way more for mining equipment than I earned by actually mining ... big surprise there, right? The upshot is that my hobby income was canceled out by my hobby expenses.


-- Capital Gains --

Next, I headed over to bitcointaxes.info to look at my capital gains.  There are three sets of information I needed.  First, I needed my old source-of-coins history - I only had mined coins (not purchased) before 2013, but even if I had bought coins, I needed the date, amount, and valuation of the coins at time of acquisition.  Second, I needed my 2013 coin acquisitions.  This consists of any transaction that consisted of my coin total increasing, so it includes mined coins, purchased coins, and received coins (from any other source).  Last, I needed my taxable 2013 coin spends.

I gathered my old mining history (pre-2013), arranged it into the requisite format (arranged as follows: "Date,Source,Symbol,Volume,Price,Fee,Currency,Total"), saved it as a comma-delimited file, and uploaded it into their Opening Position section using the file import tool.

Next, I pulled together my 2013 acquisitions and spends into a new sheet, and arranged them as follows: "Date,Source,Action,Symbol,Volume,Price,Fee,Currency".  Any coin spending transactions were listed as a SELL, any coin acquisitions were a BUY.  If I traded the coins for actual cash, I used that as the value; otherwise, I used the day's coin price as the rate to figure out the value. I included the mined coins as a coin BUY at that day's rate.  This allows me to value them properly for capital gains purposes.  Again, I saved this as a comma delimited file and uploaded it into the Trades tab.

Finally, I let the site do the calculations by clicking on the Calculate Gains tab.  Just like magic, all the capital tax info was there! The default method of calculating taxes is FIFO, which makes sense for most cases. However, judging by how I used my bitcoins, it was almost always a case of "buy coins so I could spend them right away to get X item" -- that sounds a lot more like LIFO. In addition, LIFO also resulted in lower overall taxes, as there was a closer match to the value of the coins bought to the coins sold. One of the other methods actually resulted in somewhat lower taxes, but over the long term, I think LIFO is the closest to how I actually use coins.

On the final tab, there's even an option to export the capital gains info in a number of formats, including a TXF file that I could import directly into Turbotax (which alone made it worth the premium subscription cost), as well as coins-remaining info that will become the basis of next year's source-of-coins history.


-- Importing into Turbotax --

So, the hard work of calculating is done.  My next step was to figure out how to get these number properly loaded into Turbotax!  Turns out it's a lot easier than I thought.  (Sorry, I don't have Turbotax open in front of me, so the screen labels are approximate.)

Under the income section, near the bottom, there's a section for Miscellaneous Income; one of the screens in that section lets you enter Hobby Income and Hobby Expenses.  That's where I loaded my mining income and my cost of mining hardware, respectively.

After that, under the Stocks section, I added a new "account", then chose the option to import a TXF file.  I pointed it at the file generated by bitcointaxes.info, followed the prompts, and that was that.

I figure it's still an easier chore than explaining bitcoin to an accountant ... but nevertheless, I do plan to review all this with an accountant at some point before I file.


-- Wrapping Up --

A few observations that helped me preserve my sanity as I worked through this process.  First, not every transaction has to be accounted for! For example, I had numerous transactions where I was shuffling money between wallets or addresses I controlled.  These were neither buys nor sells, so they can be ignored. Similarly, transactions where I gave coins away for no appreciable benefit (e.g., tips to strangers or gambling losses) likewise don't impact my taxes.  That said, random tips *received* from strangers do count as income.  Transaction fees paid to send coins somewhere are also not relevant for tax purposes (although, if you pay a substantial transaction fee on a coin spend transaction, I suppose you could legitimately deduct the fee from the value of the item you're buying, lowering your capital gains).

On the whole, the process was stressful, just because I was pretty much on my own. Once I'd figured out my strategy, though, it was fairly simple to actually run the numbers and come up with the rates.

I hope you found this entertaining, but I want to stress again what I said at the start -- I'm neither a lawyer nor an accountant, and this is NOT tax advice! What works for me may very well not work for you; or worse, my ideas above could be just plain wrong! So by all means, feel free to use this info as a starting point for discussion with your accountant or for your own research, but please don't rely on it for your tax decisions.
111  Bitcoin / Legal / Re: US Taxes - Form 8949, Turbo Tax and Importing Transaction data on: April 16, 2014, 05:53:19 AM
Is there a bitcoin tax website that automatically sorts out all my Mtgox transactions into easy to print Excel sheets?

Check out bitcointaxes.info. It makes it trivial to do these calculations and export to Excel or Turbotax TXF files.
112  Bitcoin / Pools / Re: [185 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: April 15, 2014, 04:57:51 PM
1) Have all miners payout to a single address by starting each with -u MYPAYOUTADDRESS, where MYPAYOUTADDRESS is the same as the address the p2pool node pays.
2) Have all miners payout to a single address as in option 1; however, that address is not the same as the p2poool node payout address
3) Have each miner payout to a different address, independent of the node's payout address.
4) Something I haven't thought of?

If my understanding is correct, the only time the p2pool node would payout to it's default address is if I'm collecting fees.  If I want to see payouts on the "Payout if a block were found now", I would have to set my miners to pay to the node's payout address as well.
I actually had to make a very similar decision recently. What I learned is that if you don't set an address (and instead use a generic label like "Antminer") for each miner, then all the shares earned will default to the payout address you've set for your pool.  That way, you can track each device individually in your local p2pool node's stats, but still get the benefit of a combined payout.  If you use the -a option on the command line, you can specify any payout address, even one that isn't part of the local bitcoin node's wallet.

If you prefer, you can set a specific payout address for each device, and track the earnings that way, but with your RPi, you won't get shares very often.  That will lead to long stretches of no shares.  Also your payouts will be more fragmented, which means when it comes time to spend them, you'll have to pay slightly higher transaction fees.

As to your options, you could do #1, but I personally went with the "labels" option I mentioned. #2 is more or less identical to #1; it's just up to you where you define the address (on each miner, or on p2pool's command line). #3 is also permissible, but has the downsides I mentioned.
113  Bitcoin / Pools / Re: [185 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: April 15, 2014, 04:22:27 PM
Which would you pick?

The point you are seemingly missing or ignoring is that the odds of either great luck or terrible luck happening are the same, and you don't know which will happen ahead of time. You don't get to pick.

Yes, larger pools provide smaller variance. Everyone knows that.

Given that your BTC payout per block is constant (as per our assumptions), I'd much rather have the first option.

What the heck, I'll play along. How do I choose the pool which is about to have 3 months of finding blocks at twice the normal rate? Yes I'll choose that option too. Will you share which pool it is going to be?
I'm not missing it at all; in fact, that's the point I was trying to make. I even highlighted it with my example of the gambler's fallacy! What I was saying is that while you can't predict when a good streak will come, you have to judge for yourself whether you can ride out the cold streaks. For a machine with a useful life of months, an extended cold streak like what we're seeing now means a significant loss. Many users will decide they'd rather have smaller but more consistent payouts from a traditional pool, rather than larger but inconsistent payouts from p2pool. If we want p2pool to thrive, we have to find a way to counter that.
114  Bitcoin / Pools / Re: [185 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: April 15, 2014, 12:59:39 PM
The thing is, while variance may average out over the long term, that only matters if difficulty remains the same.  If you think that I'm wrong, let me offer you a scenario. Hypothetically, let's say that based on current pool hashrate and network difficulty, we can expect one block per day. I'll offer you a choice. You can get three months of double the expected block success (two blocks per day initially), followed by three months of zero payouts. OR, you can get three months of zero payouts, followed by three months of double the expected success rate.  

The naive answer is that both will average out to the same thing - and that answer is correct so long as the pool maintains the same hashrate and block difficulty throughout the six months. In reality, even if we hold the pool hashrate constant over six months, your total payouts with the two options will be radically different due to the increasing difficulty rate. The double payouts followed by a dry spell will earn much more than a dry spell followed by double payouts, simply because you're getting paid when difficulty is lower - thus more blocks are found during a given time period.

Sigh. I'm getting so tired of arguing with math fallacies. So I won't.

My statement is that while things may average out over the long term, I don't live or mine in the long term - only in the short term. If in the short term I get better results on another pool then I'm more inclined to stay with the other pool.  It's exactly the same logic as saying that if I go to Las Vegas casino A and lose, then go to casino B, play the same games, and win, I'm more inclined to play at casino B the next day. Long term, on average, most players will lose at both casinos, which is why the casino business can be so profitable - but individuals can and do win big in the short term. It's pure gambler's fallacy, but it's the way many people think - both in terms of casinos and in terms of pools.

Here's the math basis I used to come to this conclusion I stated in the quote above. For simplicity, I made the following assumptions:

  • Difficulty adjusts every 10 days exactly, and each increase is exactly 5%.
  • All months have 30 days.
  • A starting difficulty of six billion (expressed in millions below, so 6000 = 6000MM).
  • Both overall pool hash rate and your share of that hash rate remain constant (which means your p2pool shares per period of time is also assumed to be constant).
  • The pool always find blocks at the expected rate.

Here's the part I'm not 100% on. I'm assuming that if the difficulty exactly doubles, then your chance of finding a block is exactly halved.  I suspect this isn't correct, but regardless, it's certain that as difficulty increases, the chance of finding a block decreases. So while the block probability numbers below may be slightly off, the overall trend would be the same.

Here's what the block-finding probabilities would look like (note that the table lists number of blocks found per 10-day period, not amount of BTC earned).

Period #Starting monthStarting dayStarting difficultyChance of block/dayBlocks found
1116,0001.00010.000
21116,3000.9529.524
31216,6150.9079.070
4216,9460.8648.638
52117,2930.8238.227
62217,6580.7847.835
7318,0410.7467.462
83118,4430.7117.107
93218,8650.6776.768
10419,3080.6456.446
114119,7730.6146.139
1242110,2620.5855.847
135110,7750.5575.568
1451111,3140.5305.303
1552111,8800.5055.051
166112,4740.4814.810
1761113,0970.4584.581
1862113,7520.4364.363

So, how does that look like in terms of blocks?

Option 1: double blocks for first three months, zero for next three months. Total blocks found: about 150 (with rounding).
Option 2: zero blocks for first three months, double for next three months. Total blocks found: about 96 (with rounding).

Option 0: no scenario, just straight mining for six months: Total blocks found: about 123.

Which would you pick? Given that your BTC payout per block is constant (as per our assumptions), I'd much rather have the first option.  If I buy mining gear with a useful lifespan of a few months to a year, it very much matters to me which option I pick.
115  Bitcoin / Pools / Re: [185 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: April 15, 2014, 07:16:40 AM
Then they do pseudo experiments ignoring all the things I said above and show a better payout at some random other pool for that day and they're lost for good.
While you're technically correct, I would contend that to the average user, his "pseudo experiment" is a pretty good indicator of his profitability, delta his very short term luck.  I understand the math behind this, and why this is wrong in the greater scheme of things. I know about variance, and about short term spikes (or dips!) in luck, and all the good stuff about p2pool and why it's better for a decentralized network than other alternatives.

But here's the thing - all of that is irrelevant to Joe Blow Miner. I have X GH/s of mining power.  If I point them at p2pool, or at GHash.io, or at Slush's, or at any other pool, I'm still "supporting the network", so long as I'm cautious about fraudulent pools or ones approaching 40% or more of the network.  The differentiating factors then become ease of use and profitability.

I'm pretty sure we can all agree that running your own p2pool node is a lot more complex than just typing in a URL into your miner. Using someone else's node is the same as any other pool.

So let's look at profitability. The common refrain when users complain about uneven payouts from p2pool is that it will all average out over the long term. This is not a useful answer to a user who's burning electricity for (what seems like) no gain. An answer of "wait a few months" is not going to sway the user. We need a better answer.

The thing is, while variance may average out over the long term, that only matters if difficulty remains the same.  If you think that I'm wrong, let me offer you a scenario. Hypothetically, let's say that based on current pool hashrate and network difficulty, we can expect one block per day. I'll offer you a choice. You can get three months of double the expected block success (two blocks per day initially), followed by three months of zero payouts. OR, you can get three months of zero payouts, followed by three months of double the expected success rate.  

The naive answer is that both will average out to the same thing - and that answer is correct so long as the pool maintains the same hashrate and block difficulty throughout the six months. In reality, even if we hold the pool hashrate constant over six months, your total payouts with the two options will be radically different due to the increasing difficulty rate. The double payouts followed by a dry spell will earn much more than a dry spell followed by double payouts, simply because you're getting paid when difficulty is lower - thus more blocks are found during a given time period.

And that doesn't even take into account the reduced pool hashrate that will result from a three-month dry spell.

So the short answer is the same it's always been: we need to find a way to make p2pool more attractive to users. That in turn will increase our chance of finding a block in a reasonable time, reduce the variance, and increase profitability for everyone. And yes, I realize the catch-22 inherent in what I just wrote.
116  Bitcoin / Legal / Re: Bitcoin being classified as property is far, far, far better than having it be c on: April 13, 2014, 05:12:30 AM
<snip>
Bitcoin Taxed as Property
<snip>

Bitcoin Taxed as Property
<snip>
Did you mean to have both headers as property?
117  Bitcoin / Mining software (miners) / Re: Linux mining distro for the Raspberry PI - MinePeon on: April 08, 2014, 06:07:37 AM
Hi guys, i dont know what to do... Sad

I have raspberry pi with minepeon (MinePeon-0.2.4.6-RaspberryPi.img).

Installed it into a sd card, and i use browser of my desktop to access minepeon on raspberry pi.

I have to antminers U2 connected in an usb hub to the raspberry pi. I setup the pool in minepeon, but it says all the time that no devices running. I dont know what to do.  Huh Huh
What kind of hub are you using? If it's a USB3 hub, that won't work with a Raspberry Pi.  Some folks have had success by plugging the USB3 hub into a USB2 hub, then plugging the USB2 into the Pi, but that doesn't always work either.
118  Bitcoin / Mining software (miners) / Re: Linux mining distro for the Raspberry PI - MinePeon on: April 07, 2014, 11:59:35 AM
.... snip ....

Thats odd, it seems that there are some changes to a few files that it does not like.  It can easly be fixed though, do this;-

cd /opt/minepeon
git checkout bin/scripts/FactoryReset.sh
git bin/bitstreams/README
git pull

I will try to work out what I did wrong!

Neil

I think Neil missed the word "checkout" in the second command:

Quote
cd /opt/minepeon
git checkout bin/scripts/FactoryReset.sh
git checkout bin/bitstreams/README
git pull

The idea being, your git pull command is being blocked because it doesn't like something about those two files. If you check out both those files, you should be able to do a git pull successfully, until Neil can figure out and fix the real root cause.
119  Bitcoin / Legal / Re: mining rig capital or current expense? on: April 07, 2014, 09:16:10 AM
The IRS did NOT rule that coins are "capital assets"; they ruled that they're property.  If I buy a car today for $10,000, and then sell it in a year or two for $15,000, then I technically owe taxes on the $5k profit.  Same way, if I buy $10k of bitcoins, then sell them for $15k, I owe taxes on the $5k profit.

As to the question of depreciating mining equipment, I understand that IRS rules on depreciation require that equipment have a useful life longer than one year. Since mining equipment generally has a useful life of under a year, that means it's OK to expense the cost right away.  As always, check with your accountant if you have any doubts.
120  Bitcoin / Mining software (miners) / Re: CGMINER ASIC miner monitoring RPC linux/win/osx/mips/arm/r-pi 4.2.2 on: April 04, 2014, 10:25:40 PM
could anybody be so kind and give step by step instruction on how to get 4.2.2 working on linux (ubuntu)?
From reading the first post in this thread, you learn you have to do this:

Go here: http://ck.kolivas.org/apps/cgminer/

If you have 32-bit Ubuntu, download the file cgminer-4.2.2.tar.bz2.
If you have 64-bit Ubuntu, download the file cgminer-4.2.2-x86_64-built.tar.bz2

Either way, unzip the file you downloaded.  Then run the executable you just unzipped, follow the prompts to set up your first pool, plug in your devices, and poof, you're mining.  (I also suggest, after you configure your pool and other settings, that you save a config file using the in-program menus and prompts.)

For anything more specific than that, you'll have to ask a clearer question.

ok iĺl be more specific...

last time i had cgminer running it was 3.7 i think through the console/terminal so i dont know wich executionable you are talking about.. if you could be so kind and tell me i would apreciate it.
i need to get cgminer running now, as i have just received a package.
I thought it was clear - "run the executable you just unzipped". The executable is cgminer - it's just zipped up for faster download. Once you unzip it, you just run it, like any other Linux program.  Either type in the name from the command line, or double click the file if you're using a GUI.  If you want to control how it runs, check the readme file and set the command line parameters the way you want them, or configure them in the program and write the config file using the built in function.

I'm sorry, but I'm honestly not sure how to be any clearer. If you don't know how to run a program in your preferred operating system, then you need to spend some time learning how to do that along with other basic tasks, like how to safely boot and shut down the PC, or how to log on and log off, or how to save your documents for later use.
Pages: « 1 2 3 4 5 [6] 7 8 9 10 11 12 13 14 15 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!