Topic: Devcoin - page 89. (Read 412952 times)

Thanks for running it.

I suggest a 1/5 of a share maintenance bounty as long as Termhn posts the daily runs on a web site. There won't be a bounty for a second site, because running devtome.py downloads most of the site, costing bandwidth.

By the way, Termhn if possible please run devtome.py at GMT 7 AM or so, when English traffic on the internet is low. By running it at low traffic time, you don't increase the peak load on the server, also you're less likely to get blank pages that might appear when the server is at high load. If you get a blank page, devtome will print a warning, and can not add that article to the total.

I can confirm that twobits Windows build works on my machine (running Windows XP). I've been running it for 15 minutes and have downloaded 50000 blocks (so much faster than downloading the bitcoin blockchain!) and it looks like the receiver files are all downloading smoothly as well. As someone who had trouble getting the previous builds to work, this is pretty awesome.

(Also, thank you Unthinkingbit for the coins. Just doing whatever I can to get involved.)

Edit:

I successfully downloaded all the blocks, and was able to transfer coins from my devda wallet to the new wallet. Oddly enough, I got a PHP error when I made the transaction on devda, and now it says my balance is -1 coins, but the transaction still went through.

Edit2:

Unthinkingbit, I changed my DVC address on devtome (now that I got my wallet working I'd rather not rely on a web wallet), will the system update my address automatically?

Well that might get political.

Basically it would be adding code into mainline bitcoin that it does not use, and its own usability will rely on that code sucessfully not being run when the code is running as actual bitcoin.

(Because the support for merged mining is a forking change: the blocks are different, so it requires the majority of the clients or miners or somesuch to all be using that new type of block some some day when it actually turns on.)

Basically you'd need to have an "#if BITCOIN" clause preventing actual use of merged mining if running actual bitcoin, in the same place where you would normally have "#if MERGED_MINING_NOW_ACTIVE" clauses in coins that actually do have merged mining activated as of some block-number.

Easier changes to get them to accept would be all the cosmetic stuff like putting all the names and icons and magic numbers used for handshaking and default port numbers and so on that distinguish one coin from another all into one place so it is easy to change the name and port and so on from one coin to another.

This is why I keep suggesting there should be a "bitcoin with ONLY the merged mining patches applied" repo maintained; all merged mined coins, even if they switch the hashing algo to scrypt, would benefit from such a repo.

-MarkM-

I don't think he did all the update to the newest bitcoin tree, may be some fix against the current devcoin tree.

I download it and found the version is 0.3.24-beta, though.

and, could we just push the merged ming patches into mainline bitcoin tree, that resolve this problem ultimately ?

So give us the source code link! Your github repo for it or whatever!

Maybe even consider prepararing a pull request for it so it can be merged into the mainline.

Though ouch, it sounds like you may have wasted a lot of potential work-savings, because the very first thing one should do when working from newer bitcoin code is prepare a "bitcoin with ONLY the merged mining patches applied" repo, which can then be used by ANY/ALL merged mined coins as the basis from which to then make their coin-specific changes to go from "bitcoin if bitcoin had merged mining" to whatever specific merged-mined coin they are working on.

(Maybe though you didn't so much alter a new bitcoin to make it a devcoin but simply copy-pasted the wallet encryption code from bitcoin over to the currently in use devcoin?)

-MarkM-

ok.. everything has just been updated...   mostly to fix an issue discovered that would effect those silly people that run a program by double clicking instead of from the command line.


So


devcoin-win32.7a  https://www.box.com/s/mbpf9os0fhhg1tzuce1u

devcoin_osx.zip https://www.box.com/s/h26atelim2ylqjrmorbf

and for those feeling brave.

devcoin-win32-exp.7z https://www.box.com/s/tyyqloma3tf8xldfvcog

More of an experimental version based on a bit newer version of the bitcoin code, that has encrypted wallet support as someone on irc was complaining about lacking this last night. Exp,  Experimental,  back up your unencrypted wallets first if you turn on encryption.

Hmmm.. I think I am going to try and get on the list as a floater also... I may not always do 10 hours a week, but when I do work on something it is  far more then that so it should average out easily.

I do not recall any specific bounty.

Basically so far I have tended to get around to doing some work on DeVCoin code now and again because I am on the list of recipients of "is a developer of free open source software" DeVCoins so I have to work on free open source software at least ten hours a week or some such figure to stay on that list, so the DeVCoin code has been one of the items of free open source software I have put some of my time into.

Basically when I am not busy working on some other item of free open source software I turn to doing some work on the DeVCoin code.

I also tend to batch things up, since once I update the merged mining patches to apply to newer bitcoin code all the merged mined coins all can then start being updated since all of them can start off from the same "bitcoin with only the merged mining patches applied" code. So I tend to go through all the merged mined coins, or a bunch of them anyway, once I have a new "bitcoin with only the merged mining patches applied" version to work from.

I started this some time back, it is why my devcoind and devcoin-qt repos on github are named old-devcoind and old-devcoin-qt, I took a new copy of bitcoin, applied the merged mined patches, and started to make a generic new coin that would basically give me the absolute minimal patch needed to change one coin into another if nothing other than the name was to change. But then something happened I guess, maybe big new changes to bitcoin or something so that I figured lets wait for that to settle before proceeding.

So I think so far it had kind of been assumed that among all the people who have devcoin itself as one of the items of free open source software that they work on, someone would eventually get around to working on it.

I do not know how many people have vague/floating definitions of what exact free open source project they work on though. Most people who work on Open Transactions, for example, likely are on the recipients list specifically because of that.

So I might currently be the only person on the list who doesn't necessarily have one specific project that justifies them being on the list. I do work on Open Transactions to an extent, but also on a bunch of altcoins from time to time and on Galactic Milieu stuff and so on. I like it that way because it means I don't have to keep dropping off the list and going back on the list from month to month depending on whether some one particular project actually comes up with enough work for me in any given month.

Others' mileage may vary.

-MarkM-

EDIT: Ten hours a week working on free open source code might seem like a heck of a lot of work just to earn the same share that writing just 1000 words in devtome gets but bear in mind it was intended more as a freebie given to people who already anyway do that much work - lifestyle free open source coders basically - than as any kind of real actual pay intended to motivate people to do the work.

I spend too much time on such things, I keep on not taking time away from it to earn far more lucrative pay putting my writings into the devtome!

Hello, could anyone confirm that, or is there already a plan doing that?

I just don't want to waste time digging into all the holy huge bitcoind code there...

As of block 89000 we 'lock in' our shares right?

Nice. Somehow I have 3 less shares on the more current run, but also 1,000,000 extra DVC. So, works out

Ran it just a couple minutes ago

If this is 4-26, then shares have gone up in value to somewhere around 600,000 DVC since the 24th.

First daily 4-26-13 run:

What do you mean?

Just fyi for the guys who joined kinda recently. You should probably combine all your posts into a single post rather than multiple replies, you will probably tick some people off or have a mod deleting your posts.

Will this be the lowest payout ever???

The less people get paid, the more valuable they will be

And traffic is going to get CRAZIER soon

Good idea.

If anyone is wondering how many Devcoins they will earn (as of April 24th), go to the link in the quote above. Find the LAST number in the row next to your name, and multiply it by 180,000,000...

EX:

if someone has 1 share, that is not close to 2,000 words (so very close to 1000 words) the last number will be 0.00277814672157
If you multiply 0.00277814672157 X 180,000,000 you get = 500,065.2

So as of April 24th, 1000ish words is worth 500,065.2 DVC

I'm going to make it a daily thing to run the script and post results here for everyone