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

This is actually one of the reasons I don't want to see an upgrade right now.  Ever since I installed 0.8.1 I wind up having to wait for my block to get reindexed every few days.

I started a list...  did not get many.....   will post it to the wiki.


http://www.devtome.com/doku.php?id=devcoin_seeds

I'd be nice if it was re-forked from the 0.8.1 codebase so we can use leveldb.

Devcoin is pretty much the same client as bitcoin, at the time it was created.  What is the issue with the client you want to see addressed?

I was skeptical too, but looking through his userpage(http://devtome.com/doku.php?id=wiki:user:FinShaggy), every article I've checked looks original.

Brilliant man, just brilliant.   You suggest a bounty to make the client capable of doing what is already is capable of doing.    You really like low effort bounties don't you.    Since this was told in discussions in the very thread that you quoted you either did not do your research or just felt like posting nonsense?


You really do take that 'Blah Blah Blah' under your avatar seriously don't you?



This is being addressed already, do you read the posts?

I propose that we limit the number of proposals one person may make in some time span without paying a fee to propose more things.    This may make it so people actually think about, and research their proposal before doing something as silly as proposing a bounty for something that already is in the code.

He wrote 61,000 words of original material?

Or adequately re-worked in his own words three times that much of other people's material?

Even Stephen King doesn't write that much that fast does he?

-MarkM-

A few updates to my DVC Ticker app (should I post a separate thread for this?). You can now specify an amount of coins to convert, and the API requests are cached to reduce load on Vircurex (more exchanges are next on the list).

Here's an example of how this could be used:

There are 180000000 DVC generated every 4000 blocks (one "round"). Based on http://www.devtome.com/doku.php?id=daily_script_results, there are 107 shares (for devtome writing) and based on https://github.com/Unthinkingbit/charity/master/bounty_23.csv, there are 71.6 other shares, for a total of 178.6 shares. 180000000 / 178.6 ~= 1007839 DVC.

A round's worth of DVC =
A single share =
Note that a bitcoin is worth

Also FinShaggy currently has 61 shares from word count alone! Worth

Alright well those 2 ips should work they are the ones we put up the other day. Let me know if they work out.

I guess not since my devstart.sh script has


I expect most of those are the ancient ones that have long gone away.

So, I have commented that whole block out and now instead have


-MarkM-

What the heck, I might as well run devcoind on my second dedicated machine too, so there will be no later worries about changing the IP address to move from one machine to the other. Both are on the same class C subnet so any one user's one client will not connect to both, as there is code that makes them try to pick from different class C subnets if possible.

Thus, my second "stable" server is the 24 gigs of RAM machine at 198.154.60.61

The list put into the code though should include at least five distinct class C nets, even if that means more than five actual machines.

-MarkM-

108.61.57.117 and 5.9.233.104 are the seed nodes you were after before, did you ever test it ?

Can we please try to make a list of all STABLE nodes so I can plug them into the code so when someone builds a windows client it will be able to find connections?

I have a node intended to be stable at 198.154.60.183

Are there any others out there?

Once upon a time we were paying to have five stable nodes, I guess maybe as soon as we stopped paying they all shut down?

(Maybe part of the reason for choosing five was so each could get 1/5 of a generation share and it would add up to a whole number of shares?)

Note that coin daemons apparently take more memory as they get more connections, so we want these to be big nodes, not little virtual machines with half a gig or a gig of RAM. I am running mine on my 16 gigs of RAM dedicated server but my second dedicated server has 24 gigs of RAM so if the 16 gig ever isn't enough I could switch to using the 24 gig box. (Though that has a different IP address (on the same class C subnet) so I guess maybe putting a name in a DNS could be useful if DNS lookups work well, so that I could switch to the other box without needing to change an IP address hardcoded into the code.)

(I guess we should think up some standard names we will use for at least five stable servers, maybe the same names on different domains, like dvcstable1.knotwork.com, dvcstable1.decoin.org, dvcstable1.devcoin.com, dvcstable1.devtome,org and so on, maybe all of a given number pointing to the same stable node, and put into the code five or so different domains on which those hostnames can be found?)

-MarkM-

Guys - can someone please make a Devcoin client for windows that is professional and easy to use and claim the bounty for that

I think the windows exe files already exist so it shouldn't be too hard for someone with the skills.

This will help in more people using Devcoin!

Once bitcoin settles down into a stable version it will be time to start a repo that has just bitcoin with merged mining patches applied.

Then from that each merged mined coin can start making its own mods to turn that into each specific merged mined coin. Devcoin is only one of several coins waiting for that.

-MarkM-

I don't remember making a bounty for a multi currency wallet. I don't plan on making one until at least after the problems with the devcoin client are fixed.


Once devcoin is ported to 0.8.1+, then there will be a one share bounty for an electrum wallet.

Pushing updates should probably be left to the distros, e.g. apt-get or yum or Windows Update or whatever a particular platform uses to automatically update its users' machine to latest versions of software.

-MarkM-

This seems pretty reasonable to me. How difficult would it be to have the (official) client automatically push updates?

Adding our stable nodes to the client is, I am pretty sure, trivial, it is mostly waiting for an actual list of actually stable nodes. It is silly to need a bounty for that, it just needs me to input some IP addresses into the code in the same place where long ago I removed the IP addresses of bitcoin nodes. A minute or two's work, with the puublishing of the new version being motivated mostly by the desire to get another checkpoint out there to further secure the cold-wallet devcoins the DigiDeVCoin tokens on the Digitalis Open Transactions Server represent.

Doing things using hostnames instead of IP addresses I am less eager about because as I mentioned before i0coin dies on boost's failure to look up an IP address from a hostname. It is possible that the reason I0coin is the only coin I see doing that could be because it is trying to look up a network-time server by hostname, it might not, or might not *always*, be trying to look up a seed node by name or do some lookup related to clients it is connected to or trying to connect to. But it indicates that using boost to look up hostnames might not be a great idea.

Also, we are supposed to be plugging in STABLE nodes. If they are STABLE we should reasonably be able to expect at least some of them to still be at the same IP address for at least a few years. That is part of being STABLE.

The bASIC guy hijacked our entire devtome even though that was based on domain name not on IP address, so really if you cannot rely on someone to keep a server at a STABLE IP address I do not really think there is a whole lot more chance, really, that they will maintain a STABLE hostname either. A fuckup is a fuckup, I tried to warn the people ordering bASICs that the guy could not even administer the complicated task of renewing a domain when it expires (or was deliberately stealing our domain and content) so expecting him to actually produce an ASIC was massively stupid. They shrugged it off as if oh well who cares, so he cannot do the simplest frikking thing, so what, he will do this amazingly complex thing just fine...

So basically if people cannot even just frikking keep paying for the same damn IP address for a few years expecting them to maintain a DNS is like are you frakking crazy that actually takes maybe some knowledge not just throwing money at a hoster saying "I demand a fixed IP address".

If it IS safe to do DNS lookups in the code though, I don't mind putting in some hostnames on a domain whose DNS I control, and plugging our list (where is that list, by the way, I do not see it ha ha please lets come up with one) of STABLE nodes' IP address into DNS as hostnames. I can even spread the DNS providers / domain name providers out, as I have domains with Network Solutions and with Godaddy and with NameCheap, so even if two out of three of those providers goes down there will still be one provider left doing DNS for a host record that is (supposedly) the IP address of a STABLE node.

But, again, if the IP addresses are good its almost easier to put them into the code than into all three DNS/domain providers' DNS systems. And that allows us not to use boost's seemingly not all that great to use DNS-lookup code.

Maybe we should consider putting a "time to die" trigger in the code too, so people HAVE TO update their development-coin code regularly, it is after all all about development...

-MarkM-

I have tried to make electrum work with dvc, but faild. It is not that we should update electrum to work with dvc, but should update dvc to work with electrum. because electrum need several api calls and features from those *coind. Once meet the requirement, electrum could easily be ported to any altcoin.