The round 29 bonanza

I did not expect to do very well in round 29.  I certainly did not expect to just rake it in.  I was actually without a computer for half of that round, and the rest of it my life was really too busy.  I only wrote 12,000 words.  Between that and shares I get for signing up new writers and keeping a copy of the receiver files on my website, plus some writer reviews I filled out I wound up with somewhere between 22 and 23 shares for round 29.

Unthinkingbit posted the total word counts for all Devtome writers and I noticed that there were not too many writers earning shares.  A few days later when he sent me the link to the receiver file I opened it up to find that there were only 325 receiver lines.  That is the fewest number of receiver lines I have ever seen in all my time writing for the Devtome.

My crude calculations indicate that I will be easily bringing in twelve million Devcoins while round 29 is paying out, the highest amount I’ve earned yet.  Of course, it now takes close to six million Devcoins to buy one Bitcoin (if I were to simply dump them), and if I were to sell the Bitcoins at the current market rate, I would wind up with between $600 and $800 in earnings.  Not bad for a little bit of writing.

Now imagine that I stockpile all those Devcoins on the exchange in high sell orders and a few weeks later Devcoin gets pumped to reach a high averaging 80 sat and I was able to sell all twelve million DVCs for that amount.  That would yield 9.576 BTC on mcxNOW.  If the price of Bitcoin only dropped back down to $200 (I figure it would have to drop substantially in order for Devcoins to get pumped), I’d earn over $1800 for that round assuming I sold off my Bitcoins.

As unlikely as the second scenario is to happen, I bring it up to make the point that you really never know what will happen between the time a round closes and the time it pays out.  Devtome writers consistently make the mistake of choosing to not write in a given round based on the current prices of Devcoins.  And yet they really don’t know what the price will be six weeks later when the Devcoins they earned are finally paying out.  But the writers who contribute content to the Devtome no matter what else is going on will greatly benefit from the lapse, as I will in a few weeks.

I mention this whole story because predictably a few days ago there was another round of complaining about how big a bite the Devtome writers took out of the monthly share generation pool, all at the expense of coders getting paid bounties for truly useful work such as developing 3-D printers or fixing whatever is wrong with the Devcoin source code at the moment–the bug which nearly got Devcoin taken off mcxNOW.  Had any of these coders gotten paid a bounty for their work, they would have collected far more Devcoins per share than expected, just as I did, and for the same reason.

I’ve gone on record saying again and again that I truly am OK with any sort of modification to the pay structure that the people in charge of Devcoin believe is necessary, even if the writers are given a much smaller piece of the pie.  If the coders need a bigger piece to be properly incentivized then so be it.  However, the coders have the same opportunities that the writers do, and when they decide to contribute something during a round in which few others have, then it’s a bonanza for them.  Also, there’s no rule that says coders can’t be writers too.

If you are a writer, then the moral of this story is to simply continue writing.  Write and publish your content no matter what the price of Devcoins is, no matter what you think it will be in six weeks, no matter how many other people you think are also writing, and no matter what else may be going on in your life or the crypto world in general.  Just write.  Most rounds will probably be average in terms of payout; some may even be thin, especially if a ton of new writers come on board and they publish everything they’ve ever written in one round, and some rounds will turn out to be true bonanzas.

This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *