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

Hello. I installed devcoind from source on a debian squeeze machine, so here is the step by step guide:

Download source from http://sourceforge.net/projects/galacticmilieu/files/DeVCoin/ and unpack it anywhere, e.g. /home/emfox/devcoind .

Of course you should have g++ and make to build it, and devcoin use curl and db, we need them, at last, boost and glib2.0 is needed (I don't like bother to find which boost lib, so installed all of them):
then compile it:

Now there's a file 'bitcoind' laying in /home/emfox/devcoind/src, but we do not like the name and won't let it stay in a source tree, so we just:

before running it, we should edit and add this line to ~/.devcoin/devcoin.conf:

at last, run!

devcoind should have started, and listening on port 52333.

That's all.

well i dont need to wait until morning if everything work good. and now what i have to do?

It has to have incoming port open so people who cannot program their routers to allow incoming ports can reach out to connect to it.

One gig of RAM should work for now I think, maybe. So far it is mostly I0coin and GeistGeld that like to eat up four gigs each.

Hmm maybe its not enough though, "ps ux" shows VSZ 1010568 and RSS 225228  for devcoind right now. I think that is virtual size and resident size. Oops misread that, its only one meg not one gig VSZ! Yeah should fit for now. IF that is measured in bytes. If it is measured in kilobytes then it IS over a gig for VSZ. Hmm need to check "ps" man page I guess... Hmm it is 1.3% of the 16 gis of RAM so yeah I guess it must be bytes. So hey, devcoind is tiny currently, should work even in a half gig virtual machine, though I have heard a full bitcoind no longer works in a quarter gig virtual machine.

-MarkM-

Hello, I have a linode 1024 vps, is it qualified for running a node? if ok, I could set one node. please tell me how to do it, just running a devcoind or anything more? a link explain it is helpful.

Thanks, please post or message me your devcoin address and I'll add you to the bounty list.


That varies according to how many shares are sent out. A share is expected to be probably more than 150$ for the next few months, so 1/5 of a share is expected to be more than 30$:
http://www.devtome.com/doku.php?id=earn_devcoins_by_writing#generation_share

I have a 24/7 node running at 198.154.60.183 with incoming port open. I am in fact running merged mining there, it has my p2pool and all the merge-able chains all running.

We distributed the old receiver files with the program, that is why we never did get around to going back and correcting the old files where they make mention of a site that long ago went offline - an administrator who faded away or quit or something.

We discussed going back over all the files replacing mention of that no longer existing site with some other site, but figured since packaging all current receiver files with the client makes it never need to go get those old files it wasn't necessary, plus as we only had three admins we'd just have to do it all again if one quit again.

Now we have five (or more) admins maybe we should go back and remove references to the dead site.

It certainly sounds from this talk of bootstrapping that you are talking about depending on github if there are no receiver files present at all thus it has to guess where it might find some?

GitHub has indeed started being unreliable, we should replace it with some server that does not do that "too busy" stuff all the time.

I have two dedicated servers now, I only run devcoind on one of them because both are on the same class C (sub)net so people would not connect to both even if both were listed as seed nodes. These are over and above the purely web-hosting site where I currently host my copies of the receiver files. (They are also at the same provider so not maybe very indepdendently down or up, if one is down maybe both will be, depending why/how it gets to be down.) I do not even run webservers on them yet but I on at least one of them if it were necessary. So far I have not because I already have a purely-webhost hosting I use for web stuff.

We should also find out how DNS seeds work and set some up. We have various devcoin and devtome domains plus I have knotwork.com domain.

-MarkM-

im testing a fresh install then in morning(20:30 here at the moment) i will see how that thing turn from here

¤¿¤

If someone is going to do this as a fresh install of devcoins, please pm me for my changes to help test it.   It already has Mark's node coded in as a seed now, so it can run without irc on, which can be useful as a lot of places ban the use of IRC in their AUP.

I have set up one at 174.34.170.240

It may be a bit flakey for the next few days as I am also using it for testing so stopping and restarting it often.  It will however
get hardcoded into the client as part of my changes and run 24/7 at that point.

How much is 1/5 of a share anyway in terms of coins right now?


Not sure off hand.  Just having working seed nodes will at least stop that from being a showstopper.  Long term,  either
add some more peer discovery methods and/or find another irc to use.


Ok..

A full dvc node?

Please make one, you'll get devcoins for it for as long as you maintain it. If you have any questions about what is required, ask Mark.

if you need a "node" always online then pm me, i can setup one node to stay 24/24 online

We used to have a bounty for seed nodes, but it was closed because we thought there were enough seed nodes. Since there aren't I suggest a bounty of 1/5 of a share ongoing, for the next ten seed nodes (it used to be five, but was boosted to ten to protect against a ddos or some other problem).


What could be done to fix that?


Github has been flaky lately, so we'll switch away from github for at least receiver_0.


Edit; four seed node bounties have been awarded, six remain:
https://bitcointalksearch.org/topic/m.1936384
https://bitcointalksearch.org/topic/m.1937955
https://bitcointalksearch.org/topic/m.2128556 (Jasin and Mark)

Oh, I was not saying some people may not want an installer.  It however looked like it was being pushed as the solution to the bootstrapping issues though.  I was saying it was the wrong place to fix that.

Even after downloading the receiver files is improved, it would still be useful to make a windows installer that installs devcoin-qt, and devcoind with one click.

Ok...  as a work around for the github server too busy message getting stored sometimes as receiver_0.csv which then borks
that installation until it is deleted I propose that I make the following two changes to the logic:


1: Only write out a fetched file that starts with the line 'Format,pluribusunum'.

2:  Add some logic to not keep retrying the same url more often them some time period so we don't then try to DDoS github when
everyones client hits this type of result.

I am not sure this will be enough for it to recover yet, but it at least gives it a chance to do so on the next restart.

The bounty for the windows installer?

You know I really need to write up a bounties considered harmful.  I already commented that the bounty is even hunting the wrong target, not to mention the other problems with this type of bounty even if it was going after the right target.

Thanks for all the work.

To All,

I suggest a 6 share bounty for this work, this is besides the windows bounty, which is still active. Any objections, or should any changes be made.


I suggest once the error recovery and robustness is improved, another 6 share bounty be awarded.

It would probably take a forking change to get them into the blockchain at this point?  Even if you did so,  I think the program
needs the files to validate the existing blockchain and there is no way to go back and insert it.  So, since I don't think we would want to do a relaunch, we are stuck with needing the information to bootstrap.   I do think the way it is being done is way too fragile.   Everything is dependant on github to bootstrap and that is failing right now.  Also the irc that is used has ben failing alot lately.  After not running the client for some months, it has been a real pain to be able to get it working again. I think the folks that have been running it all along, do not realize how fragile the current bootstrapping is right now.  All the seed nodes are gone,  the IRC is flakely, and the fetching of the receiver_0 will not work in the existing code at all. Fixing that you still often get failure due to that error from github I was showing.   This process needs more recovery and robustness.  I would even say we should use DNS txt records to not be stuck on only a hardcoded github url for bootstrapping.

So, either way, this code needs to be improved, and once it is, I am not sure there is enough to gain from them putting it in the blockchain?
 

There is a bounty to correct this a couple pages back it was discussed.