Devcoin

[Unthinkingbit]

Please let me know what you need me to send to where. What do you mean private purser key?

Thank you for replying.

I mean the key for the address:
19piwg8kyW5unDpLjYjbvE6GGvtAfghT8c

You can extract that key from the devcoin wallet by using the modified version of bitcoin tools which incorporates Matt Giuca's privkeyimport:
https://github.com/Unthinkingbit/bitcointools

or you could also use Jackjack's pywallet:
https://github.com/jackjack-jj/pywallet

the instructions for which are in the Pywallet section at the bottom of the post:
https://bitcointalk.org/index.php?topic=34586.msg432697#msg432697

The easiest way would be to send the wallet which has that key to:
unthinkingbit@gmail.com

I'll extract the key then delete the wallet. 

You can have back all the devcoins if you like. I'm not even going to do any sums.

I'm going to extract the 22,500,000 extra devcoins from this generation round, the rest are yours.

To confirm some more details though I was mining first on a machine with 2 6870's which is the one that generated the address I gave you which the bounties and everything else went to.

The wallet from that machine would be the one.  You can send me the wallet or try to extract the key.

The other machine was my main machine which I later started mining on with a 6950. I believe it has about 2 million devcoins but I will need to double check when I get home. Do you want these as well or just all the devcoins from the first machine?

Those are your devcoins, I do not want those.  I only want the wallet or key from the first machine.

I may be able to send coins to you when I get home but I usually get home from work about 1am. I work a long way from home and don't own a car so get home via train and bus.

Thanks for telling me roughly when you can send them.

[caston]

OK I am back home now. I have e-mailed the wallet.dat file to you.

For what its worth I had shown the seeds of expressing interest in starting some new bounties. One for a devcoin logo the other for a devcoin linux based live CD:

http://www.devcointalk.org/index.php?board=5.0

[markm]

OK I am back home now. I have e-mailed the wallet.dat file to you.

For what its worth I had shown the seeds of expressing interest in starting some new bounties. One for a devcoin logo the other for a devcoin linux based live CD:

http://www.devcointalk.org/index.php?board=5.0

Yeah but I guess the conflict basically is were/are you actually interested in devcoin, which it seems is quite a well defined project roadmap Unthinkingbit already has laid out, or in some hypothetically or even superficially similar project that might or might not interest those of us who are working on devcoin?

-MarkM-

[Unthinkingbit]

OK I am back home now. I have e-mailed the wallet.dat file to you.

Thank you very much.

I have extracted the key for the address:
19piwg8kyW5unDpLjYjbvE6GGvtAfghT8c

I am going to be periodically draining that key, usually one million devcoins at a time, until the extra 22,500,000  purser coins are drained.  I will leave a balance of one million, but please don't use that account until all the purser coins have been extracted because that might lead to invalid transactions.

Until then, if you want to send people devcoins, please use the wallet on your other machine.

[Unthinkingbit]

Because purser accounts lead to problems, the receiver_2 round is the last round with pursers.  In future, bounties will be paid directly from the generation share of the next round.  The conversion rate for already posted bounties will be 5,000,000 DVC per developer month share.  For example, a bounty of 1,000,000 DVC would be 1/5 of a developer month share, and a bounty of 100,000 DVC would be 1/50 of a developer month share.

The current remaining bounties of 100,000 DVC for a minimal post and another 100,000 DVC for an informative post remain, those are the last defined bounties.

[Shattienator]

Because purser accounts lead to problems, the receiver_2 round is the last round with pursers.  In future, bounties will be paid directly from the generation share of the next round.  The conversion rate for already posted bounties will be 5,000,000 DVC per developer month share.  For example, a bounty of 1,000,000 DVC would be 1/5 of a developer month share, and a bounty of 100,000 DVC would be 1/50 of a developer month share.

The current remaining bounties of 100,000 DVC for a minimal post and another 100,000 DVC for an informative post remain, those are the last defined bounties.

Is my post #24 can be classified as minimal one?

P.S. Devcoin node at 50.19.210.139:52333 was offline for some time but now it is running and have active 6 connections. Block number is 8286 right now.

[markm]

Shattienator, maybe I simply missed where you posted the address to send your bounty/bounties to?

I think I am basically watching/waiting for actual addresses to sent to for a number of posts that have happened without indication of what their receive-account is?

-MarkM-

[Shattienator]

Shattienator, maybe I simply missed where you posted the address to send your bounty/bounties to?

I think I am basically watching/waiting for actual addresses to sent to for a number of posts that have happened without indication of what their receive-account is?

-MarkM-

I was not sure if this post is informative enough

Here is the address: 1Fhex5BvBGaChJqK75Z6MPxtK9muSsScKC

P.S. I can set up two more seeding nodes (in addition to existing one) - do we need them?

[markm]

Shattienator, maybe I simply missed where you posted the address to send your bounty/bounties to?

I think I am basically watching/waiting for actual addresses to sent to for a number of posts that have happened without indication of what their receive-account is?

-MarkM-

I was not sure if this post is informative enough

Here is the address: 1Fhex5BvBGaChJqK75Z6MPxtK9muSsScKC

P.S. I can set up two more seeding nodes (in addition to existing one) - do we need them?

Of course we need them. I have four nodes running behind my NAT router but the stupid router does not work with the UPNP lib so no incoming ports. We especially need nodes with incoming ports.

The post didn't have to be particularly informative, the bounty doubles for "informative".

[markm@desktop bitcoin]$ ./devcoind.sh sendtoaddress 1Fhex5BvBGaChJqK75Z6MPxtK9muSsScKC 100000.00
d11420d97c3b9570841d07df8bd33cede50becce79191e10d5f9cd86e4df191b

-MarkM-

[Shattienator]

Of course we need them. I have four nodes running behind my NAT router but the stupid router does not work with the UPNP lib so no incoming ports. We especially need nodes with incoming ports.

Tomorrow I will set up two more permanent seeding nodes. Necessary ports will be opened.
These servers (instances at the amazon EC2) are pretty fast and have permanent IPs - so three nodes will be able to provide seeding fast enough to feed requests for blocks from hundred of connecting clients.

[markm@desktop bitcoin]$ ./devcoind.sh sendtoaddress 1Fhex5BvBGaChJqK75Z6MPxtK9muSsScKC 100000.00
d11420d97c3b9570841d07df8bd33cede50becce79191e10d5f9cd86e4df191b

Received.

[caston]

OK I am back home now. I have e-mailed the wallet.dat file to you.

Thank you very much.

I have extracted the key for the address:
19piwg8kyW5unDpLjYjbvE6GGvtAfghT8c

I am going to be periodically draining that key, usually one million devcoins at a time, until the extra 22,500,000  purser coins are drained.  I will leave a balance of one million, but please don't use that account until all the purser coins have been extracted because that might lead to invalid transactions.

Until then, if you want to send people devcoins, please use the wallet on your other machine.

OK I have started hashing again


user@linuxcoin:~/Downloads/devcoin/src$ ./bitcoind getinfo
{
    "version" : 32400,
    "balance" : 0.00000000,
    "blocks" : 8298,
    "connections" : 1,
    "proxy" : "",
    "generate" : false,
    "genproclimit" : -1,
    "difficulty" : 92.94920663,
    "hashespersec" : 0,
    "testnet" : false,
    "keypoololdest" : 1313039523,
    "paytxfee" : 0.00000000,
    "errors" : ""
}
user@linuxcoin:~/Downloads/devcoin/src$ ./bitcoind getnewaddress
12Byy43HThNYsqWLH6fzY2Bxa2JP7Z5wYk


I'll do my best to help you guys reach block 9000 .. seems silly not to finish what I started

[caston]

In the meantime is anyone interested in blogging on Rejuvepedia for Devcoins?

Oh damn I only just noticed IXcoin ...

[Shattienator]

Another two seeding devcoin nodes up:

107.20.209.11:52333

107.20.228.112:52333

in addition to existing 50.19.210.139:52333.

[markm]

Another two seeding devcoin nodes up:

107.20.209.11:52333

107.20.228.112:52333

in addition to existing 50.19.210.139:52333.

Do any of them have any DNS, even a no-ip.org type DNS, so we can use them in the DNSseed part?

Also, the IP address array has them coded somehow, I am not sure exactly how, what byte order it uses for instance...

-MarkM-

[Shattienator]

Another two seeding devcoin nodes up:

107.20.209.11:52333

107.20.228.112:52333

in addition to existing 50.19.210.139:52333.

Do any of them have any DNS, even a no-ip.org type DNS, so we can use them in the DNSseed part?

Also, the IP address array has them coded somehow, I am not sure exactly how, what byte order it uses for instance...

-MarkM-

As DNS you mean mnemonic name such as www.domain.org?

[jackjack]

Another two seeding devcoin nodes up:

107.20.209.11:52333

107.20.228.112:52333

in addition to existing 50.19.210.139:52333.

Do any of them have any DNS, even a no-ip.org type DNS, so we can use them in the DNSseed part?

Also, the IP address array has them coded somehow, I am not sure exactly how, what byte order it uses for instance...

-MarkM-

As DNS you mean mnemonic name such as www.domain.org?

Yes
Go to dyndns.org or no-ip.org, create an account and link devcoinnode1.dyndns.org or something to one of your ip

[Shattienator]

Here are the names:

107.20.209.11:52333 - ec2-107-20-209-11.compute-1.amazonaws.com

107.20.228.112:52333 - ec2-107-20-228-112.compute-1.amazonaws.com

50.19.210.139:52333 - ec2-50-19-210-139.compute-1.amazonaws.com

[Unthinkingbit]

The purser payouts for generation rounds 0 and 1 are done.  There are two sets of payouts, because when I first did the accounting I accidentally multiplied 0.9 * 45,000 instead of the correct 0.9 * 50,000.  The accounting notes follow:

share = 4,000 / 25 * 2 * 45,000 = 14,400,000
share * 3 = 38,880,000 43,200,000
43,200,000 - 200,000 (informative post) - 1,000,000 (induction bounty) - 5,000,000 (explorer bounty) = 37,000,000
(25 * 0.05 - 1) = .25 extra per administrator who is already getting a share
.25 * share = 3,240,000 extra per administrator 3,600,000 - 360,000
32,680,000 - 3,240,000 - 3,240,000 = 26,200,000 29,800,000
26,200,000 / 20 developers = 1,310,000 per developer 1,490,000 - 180,000

The transaction is at block 8319 or block 8322 or somewhere around there.  I can't check where they are because I haven't been able to get a page from:
http://devcoinblockexplorer.tk/
or
http://devcoinblockexplorer.dyndns.org/.

Before the end of round 2, Mark and I will make the final purser payouts.  After that, all bounties and administration shares will be direct from generation.

[jackjack]

devcoinblockexplorer.* is currently down because Abe is reading the bitcoin blockchain and it takes LOOOONG time.... It began about a day ago and it is only reading block 112185....

[Unthinkingbit]

Because the devcoin difficulty is lower than the bitcoin difficulty, miners can switch in and out of the chain, which means the block generation rate varies wildly.  To fix this problem, the difficulty can be determined with a continous average rather a step function, and it can calculated over one day instead of two weeks.  This will lead to greater daily variation than bitcoin because it is being averaged over a small time; but it would be a much smaller variation than the current factor of more than two as a miner switches in and out.  The original code follows:

Code:

    const int64 nTargetTimespan = 14 * 24 * 60 * 60; // two weeks
    const int64 nTargetSpacing = 10 * 60;
    const int64 nInterval = nTargetTimespan / nTargetSpacing;

    // Genesis block
    if (pindexLast == NULL)
        return bnProofOfWorkLimit.GetCompact();

    // Only change once per interval
    if ((pindexLast->nHeight+1) % nInterval != 0)
        return pindexLast->nBits;

The new smooth average code, with a switch over at block 10,700 to give people time to download the new devcoin, follows:

Code:

    // Genesis block
    if (pindexLast == NULL)
        return bnProofOfWorkLimit.GetCompact();

    int64 nTargetTimespan = 24 * 60 * 60; // one day
    const int nSmoothBlock = 10700;
    if (pindexLast->nHeight < nSmoothBlock)
        nTargetTimespan *= 14; // two weeks
    const int64 nTargetSpacing = 10 * 60;
    const int64 nInterval = nTargetTimespan / nTargetSpacing;

    // Only change once per interval
    if (((pindexLast->nHeight+1) % nInterval != 0) && (pindexLast->nHeight < nSmoothBlock))
        return pindexLast->nBits;

While this would fix the step change difficulty problem, would this create another other problem in turn?