Topic: [50 BTC total bounty] for Groupcoin development and help - page 2. (Read 26269 times)

I checked that, I have 1 connections, it was even 2 when I posted my first message

I'll take a look at Abe, and I'll mine a bit if I can

You might not have any connections yet. I could give you my IP but I am going to bed soon and have to shutdown my mining rig.


Not that I know of as yet but Abe could easily handle it.

http://abe.john-edwin-tobey.org/

https://github.com/jtobey/bitcoin-abe


We need more people to mine for one.

Hi everybody
I find this project quite interesting!

Moreover, all went fine:
I downloaded devcoin-qt-*, installed dependencies, compiled with qmake and make, and the qt client was ok and started downloading blocks immediately
I just downloaded devcoin-* too for bitcoind, I compiled it and it works ok
My miners can't connect to bitcoind though

I have two questions:
Is there a block explorer?
What help is needed?

Hi Unthinkingbit,

Devcoin needs a community forum and knowledge portal. As a suggestion we could use simple machines with a mediawiki bridge.

Actually, now that all the receiver_2.csv files have been updated, receiver_1.csv has been updated so please upload the latest version from:
https://raw.github.com/Unthinkingbit/charity/master/receiver_1.csv

done and http://www.perth-exchange.org/receiver_1.csv

I'd also like to check that this is working as its supposed to e.g. 90% going to developers as my balance seems to be getting pretty high.

At the moment its 2175000.00000000

It sure does.

Now upload the file at:
https://raw.github.com/Unthinkingbit/charity/master/receiver_2.csv

to:
http://www.perth-exchange.org/receiver_2.csv

Unthinking bit:

I have a nearly free speech account. I have uploaded it to that for now.

http://www.perth-exchange.org/receiver_3.csv

Also I can probably upload to a site  khal (dot-bit forum site admin) has given me but I haven't used yet.

Does that look ok?

Now that we have three administrators we can assemble the devcoin majority download receiver tree, which is explained in the Technical section of:
https://github.com/Unthinkingbit/charity/wiki/Devcoin-Description

Because the algorithm in receiver.h is forward looking, we have to assemble the tree backwards so that no devcoin program ever sees an inconsistency.

So please upload the receiver_3.csv file:
https://raw.github.com/Unthinkingbit/charity/master/receiver_3.csv

to, ideally, an http site which lets you call it *receiver_3.csv, rather than forcing you to call it *

The uploaded file must be in raw form, if the upload site adds any tags or whatever, the majority download receiver.h algorithm will not work because it expects identical files.

If you can't find an http site that lets you upload a raw file, then you can use an https site like github.  Https means the additional dependency of python for devcoin, but it's not a big problem because almost everyone who would use devcoin would have python.  Once you've uploaded the file, post the link to it.

Once there are three copies of receiver_3.csv, I'll create a receiver_2.csv file to upload, then a receiver_1.csv file to upload.

Assembling the tree is awkward, but once done devcoin will be able to keep working even if one receiver website is down and in future rounds administrators will just have to upload a single file.

Hi Caston,

I sent you the million devcoins for your induction bounty.  You are now a devcoin receiving active developer.  In the next round of generation, which starts at block 8,000, you will begin receiving your share of the 90% of the generation that goes to developers.  You can see your devcoin address:
19piwg8kyW5unDpLjYjbvE6GGvtAfghT8c

at index 20 in the receiver_2.csv file at:
http://pastebin.com/raw.php?i=u51edxd0

Now that you are inducted, you can become an administrator, as described in:
https://github.com/Unthinkingbit/charity/wiki/Devcoin-Description

Please accept the invitation.  If you accept, devcoin would have three administrators so we could test the democratic download of the receiver file.  If that test succeeds, devcoin would be ready for the next set of bounties.

Below is your contributor file.  Please check it and update it if necessary.

Contributor: Caston
Devcoin Address: 19piwg8kyW5unDpLjYjbvE6GGvtAfghT8c
Description: Founder of Rejuvepedia, the Wiki that aims to do for health what bitcoin does for wealth.
Project Homepage: Rejuvepedia">http://www.rejuvepedia.org/index.php?title=Main_Page'>Rejuvepedia
Project License: Creative Commons Attribution ShareAlike 3.0 Unported
Project Type: Wiki


The recommeded method to handle funds for collaborations is pasted below and described in:
https://github.com/Unthinkingbit/charity/wiki/Devcoin-Description

"Collaborative Developer

People who develop a collaborative project, like a wiki, get shares for their work according to how much they work.  An active developer who creates ten hours a week of good accomplishments gets a share.  A part time developer who contributes every month, but does not create ten hours a week of accomplishments gets half a share.  A contributor who occasionally writes articles gets 0.2 shares in the funding round that the article is submitted.  A contributor who occasionally edits the wiki gets 0.1 shares in the funding round of the edits.

The shares are added up and rounded, totals ending in .5 are rounded to the nearest even number. The result is the number of collaborative editors who get on the active developer list, and therefore get a direct share of the generation. They in turn send the collaborators who are not on the developer list their share of the devcoins at least every funding round (every 4,000 blocks, roughly once a month). If they do not give the collaborators their share they will be removed from the active developer list."

You're welcome.  Devcoin is made to make developers happy 

You've just made me very happy. Thank you!

Thanks for the great post, two hundred thousand devcoins are on their way.


Thanks for leaving it on, the more nodes we have the better.

By the way, your work on Rejuvepedia qualifies you to be an active developer in the writer category.  Furthermore, from the beta devcoin bounty article:
https://github.com/Unthinkingbit/charity/wiki/Devcoin-Bounty

since you're one of the first five writers, you also get the one million devcoin inductee bounty.

It will be more complicated because you have a collaborative wiki and so your active developer share will have to be shared in turn with your collaborators.  It will take time to work that out so we can talk about it when you return from work.

I seem to remember it downloading the .csv file soon after it connected to irc or got its first connection. Do you think I missed anything else? I am running it from it's directory and haven't yet made a /usr/sbin symbolic link or something like that.

Heh so it works without reading the INSTALL file and, as it instructs, putting the receiver_*.csv files into the directory that is the "current directory" (Present Working Directory) you are in when running devcoind? Cool.

-MarkM-

thank you I am now mining at 227 mhash.

I'll try to recap what I did:

I'm using Linux coin 0.2b that I have installed to my HD.

I previously installed multicoin and then group coin with help from knotworking on the irc channel #groupcoin

I went to http://sourceforge.net/projects/galacticmilieu/files/ in the Cromium web browser.
and downloaded devcoin-02-Aug-2011.tgz

I then open up a terminal and typed cd Downloads
I then typed gunzip devcoin-02-Aug-2011.tgz
after that I typed: tar -xf devcoin-02-Aug-2011.tar (using tab completion of course)

I then typed cd devcoin then cd doc
I then read the build build-unix.txt file and installed all the dependencies.

Some of these I could find using apt-cache search and some I had to find and download using google and then compile.

I then changed to /Downloads/devcoin/src and ran:
make -f makefile.unix bitcoind
to build it headless

You can cat the INSTALL for more information. You should also follow the other instructions "The files that must be in the current directory at runtime
are https.py and the receiver_*.csv files."

After that finished I changed to cd /home/user/.devcoin/ and created a devcoin.conf file with a username and password for rpc in the same format as a bitcoin.conf file

If you don't find this folder it will probably be created the first time you run the devcoin bitcoind daemon.

I then logged to the web interface for my router and set a virtual server and a IP address reservation for my mining rig to forward tcp port 52333 to it.

after that I started the client in /home/user/Downloads/devcoin/src/ using ./bitcoind
from a different terminal I checked the status in the same directory as above using ./bitcoind getinfo

It took a while to get my first connection but opening the #groupcoin channel seemed to help me get my first connection
I used sudo netstat -p | grep bitcoind to see if bitcoind was connected to irc server and if it was using the outgoing ports to make connections. I finally got my first connection and started mining using the username and password I specified in my devcoin.conf file.

./bitcoind getinfo (now says)
{
    "version" : 32400,
    "balance" : 200000.00000000,
    "blocks" : 4921,
    "connections" : 2,
    "proxy" : "",
    "generate" : false,
    "genproclimit" : -1,
    "difficulty" : 16.00000000,
    "hashespersec" : 0,
    "testnet" : false,
    "keypoololdest" : 1312339094,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

I went to the toilet and when I came back I saw I had already mined 6 blocks!

Please let me know if you have anymore questions. I'm about to go to work but will leave devcoin mining while I am at work.

Good news, thanks for not giving up

I'm hoping and assuming you'll write a post tying together all that you went through.  When you do I'll send two hundred thousand devcoins to what I am assuming is the devcoin address you posted.  What you've written so far is good but since it's distributed over a few posts it doesn't qualify for the informative post bounty.

If you don't want to write anything else, then just state that and I'll send one hundred thousand.

Thank you. I thought I had downloaded the headless version but I am trying that make option now.

OK I have it compiled now and I am getting:


./bitcoind getinfo
{
    "version" : 32400,
    "balance" : 0.00000000,
    "blocks" : 0,
    "connections" : 0,
    "proxy" : "",
    "generate" : false,
    "genproclimit" : -1,
    "difficulty" : 1.00000000,
    "hashespersec" : 0,
    "testnet" : false,
    "keypoololdest" : 1312339093,
    "paytxfee" : 0.00000000,
    "errors" : ""
}


I assume the port I should open is 52333 ?

I have opened that port as tcp but still no connections.

How can I get my first connection?

I finally have a connection now:



./bitcoind getinfo
{
    "version" : 32400,
    "balance" : 0.00000000,
    "blocks" : 4912,
    "connections" : 1,
    "proxy" : "",
    "generate" : false,
    "genproclimit" : -1,
    "difficulty" : 16.00000000,
    "hashespersec" : 0,
    "testnet" : false,
    "keypoololdest" : 1312339093,
    "paytxfee" : 0.00000000,
    "errors" : ""
}
user@linuxcoin:~/Downloads/devcoin/src$ ./bitcoind getnewaddress
19piwg8kyW5unDpLjYjbvE6GGvtAfghT8c

The makefile defaults to making the wxwidgets GUI version.

To make the daemon try make -f makefile.unix bitcoind

Or to not use upnp, try make -f makefile.unix USE_UPNP= bitcoind

Or to not only include upnp but default it to being active, try

make -f makefile.unix USE_UPNP=1 bitcoind

-MarkM-