Author

Topic: Devcoin - page 155. (Read 412998 times)

hero member
Activity: 935
Merit: 1015
December 31, 2011, 06:50:53 PM
I see. It seems to cycle through addresses from the receiver.csv file each block.

Indeed, it cycles through the addresses. I added an explanation to the devcoin article:
http://devtome.org/wiki/index.php?title=Devcoin#Disbursing_the_Share

and pasted it below.



The generation share is 90% of the block, which is 90% * 50,000 devcoins = 45,000 devcoins. It is disbursed to the devcoin addresses in the receiver file, in round robin order. In each generation round, for a given block height, the index of the line of addresses is the block height above the start of the round, modulo the number of addresses. The code snippet for that follows below.

vector getCoinAddressStrings(const string& dataDirectory, const string& fileName, int height, int step)
{
..
   int remainder = height - step * (height / step);
   int modulo = remainder % (int)coinLists.size();

   vector originalList = coinLists[modulo];

   for (vector::iterator tokenIterator = originalList.begin(); tokenIterator != originalList.end(); tokenIterator++)
   {
      if (*tokenIterator != string("="))
         oldToken = tokenIterator->substr();

      coinList.push_back(oldToken);
   }

   return coinList;
}

Then in CreateBlock, the share per address is calculated by dividing the generation share by the number of coin addresses in the line of addresses.  A subtransaction to create share per address coin value is then added for each coin address to the generation transaction. The transactions from generation can be seen by looking at a devcoin block explorer:

http://devcoinblockexplorer.info:2750/chain/Devcoin

or

http://explorer.devcoin.org
legendary
Activity: 2940
Merit: 1090
December 31, 2011, 09:43:30 AM
Yes, curl goes and gets the receiver file, and the first few transactions in the block, or maybe somehow extra outputs in the coinbase transaction, send the 45000 out to addresses found in the receivers file. I think it maybe even allows multiple addresses on a line in the receivers file and divvies the 45000 between them maybe. Can't really recall now its been a while since we got that part done.

-MarkM-
legendary
Activity: 1078
Merit: 1005
December 31, 2011, 08:50:25 AM
check http://explorer.devcoin.org - for an example of how the transactions are made, 45000 go to a set address
I see. It seems to cycle through addresses from the receiver.csv file each block.
hero member
Activity: 896
Merit: 1000
Buy this account on March-2019. New Owner here!!
December 31, 2011, 08:27:06 AM
check http://explorer.devcoin.org - for an example of how the transactions are made, 45000 go to a set address
legendary
Activity: 1078
Merit: 1005
December 31, 2011, 06:34:16 AM
When a miner solves a  block, 50,000 devcoins are created. Of these, 5,000 goes to the miner. Where do the other 45,000 go? My understanding is they go to 'developers' as a donation. How is this distributed? Do miners create the transactions to send the coins to them as part of minting the block? Or do the coins go to an address and an administrator periodically sends them out?
legendary
Activity: 1078
Merit: 1005
December 31, 2011, 01:51:53 AM
How do you caclulate the hashrate of the network? Is it "only" a matter of checking the timestamps of the most recent blocks and together with the current difficult rate calculate the hasrate?
I believe that's how it's done, yes.
hero member
Activity: 525
Merit: 500
December 31, 2011, 01:24:43 AM
What is the current hashrate of the entire devcoin network?

How do you caclulate the hashrate of the network? Is it "only" a matter of checking the timestamps of the most recent blocks and together with the current difficult rate calculate the hasrate?

If that's all there is to it, I could possibly add some infos into the exchange, as I have all the daemons running, I have access to all the info provided by getinfo.
legendary
Activity: 1078
Merit: 1005
December 31, 2011, 01:17:33 AM
...I think you missed a couple of your Bitcoin to Devcoin replacements as I still see Your Bitcoin Address: in the GUI and Bitcoin at the top in the app the name displays properly in the top of the screen in the unified menus that OSX uses and in the dock when hovering over it.
Yes, I probably have - I erred on the side of caution in the renaming. I'll do a GUI build and fix it up at some point.
legendary
Activity: 1078
Merit: 1005
December 30, 2011, 11:48:03 PM
Indeed don't need more BS on the system than is already there now it just gave me 32 bit app on its run through on the 64bit it gave me this below for some stupid reason both builds use the --disable-ldap --disable-ldaps for the configure options so don't know why it would error on 64bit usually once I have the 32 it is good to go all the way to a universal app at the end.
Isn't cURL fun! You need to either build libidn for 64 bit, or configure curl using "--without-libidn".
legendary
Activity: 1078
Merit: 1005
December 30, 2011, 11:11:39 PM
Ok thanks any clue on the error(s) above?
Build libcurl without ldap support. There's a configure option for it. Otherwise it's a pain - you have to build ldap libraries and link to them.
legendary
Activity: 1078
Merit: 1005
December 30, 2011, 10:03:34 PM
Interesting so all you would need to do is import your BTC private key into your devcoin wallet and you would be good to go. Sounds like an idea actually how hard is that to do anyways, import the key that is?
The latest bitcoin source includes a patch to import and export private keys. I'll cherry-pick that patch into my devcoin repository to make it easier. So it shouldn't be too difficult. I'll do some testing.
hero member
Activity: 896
Merit: 1000
Buy this account on March-2019. New Owner here!!
December 30, 2011, 09:38:50 PM
Devcoin Download Links
Download

Devcoin Source:
https://github.com/knotwork/old-devcoind

Devcoind 32 Bit Linux Binary (i686)
http://pool.devcoin.org/files/daemons/devcoind

Devcoind 64 Bit Linux Binary (x86_64)
http://btcnetwork.com/files/daemons/devcoind

This information can also be found by clicking the 'Download' tab at
http://www.devcoin.org

and just so everyone knows pool.devcoin.org is ready for merged mining switch and will be collecting the pool portion of the bounty

woo-hah!
legendary
Activity: 1078
Merit: 1005
December 30, 2011, 08:52:42 PM
Ok it did fail on OSX with the undefined symbols like it did on the i0 so I think you know that fix already and it built the daemon fine on my Ubuntu 11.04 64bit box.
These link errors are due to devcoind requiring libcurl - something none of the other alt chains use. You'll need to build libcurl (http://curl.haxx.se/libcurl/) and and change the 'LIBS' line in the makefile.osx to:

Code:
LIBS= -dead_strip \
 $(DEPSDIR)/lib/libdb_cxx-4.8.a \
 $(DEPSDIR)/lib/libboost_system.a \
 $(DEPSDIR)/lib/libboost_filesystem.a \
 $(DEPSDIR)/lib/libboost_program_options.a \
 $(DEPSDIR)/lib/libboost_thread.a \
 $(DEPSDIR)/lib/libssl.a \
 $(DEPSDIR)/lib/libcrypto.a \
 $(DEPSDIR)/lib/libcurl.a

Note that libcurl.a addition at the end. Let me know if this works ok and I'll push a fix to the repository with this.
legendary
Activity: 1078
Merit: 1005
December 30, 2011, 08:46:28 PM
Thanks SAC, looking at it now. I've added the ability to register with a devcoin address to the mmpool now. See here for details. I'm thinking of automatically setting existing users devcoin address to their bitcoin address since they are compatible. Then users can mine devcoins without re-registering and import their private key if they want to claim them.
legendary
Activity: 1078
Merit: 1005
December 30, 2011, 06:59:59 PM
Don't think I really have to ask but I will. I take it you fixed the makefiles so it actually builds on the supported OS's and the binaries it produces are named properly?
Makefiles are changed to produce the correct binary name and use of 'bitcoin' in the app itself has changed to 'devcoin'. I modified the other OS makefiles but haven't been able to test them. Let me know if OS X fails and I'll fix. I'll test Windows later today.
legendary
Activity: 1078
Merit: 1005
December 30, 2011, 06:46:19 PM
I take it this means another coin added to the mmpool so if wanting it then a new user has to be created again to include the devcoin address you want the coins sent too right?
At some point, yes. I'll announce when it's available to register with a devcoin address.  There's a way to avoid this need to re-register using the message signing capability in recent clients but it requires a decent amount of programming changes to the pool. I'll look into doing that though to avoid the pain of re-registering.

For those keen on trying it, I'm using my own devcoin daemon, built from https://github.com/doublec/devcoin, which is based on the original bitcoin release that devcoin was applied too, devcoin patch applied, and a bunch of cherry-picked bugfixes (the same as I applied to i0coin).
hero member
Activity: 896
Merit: 1000
Buy this account on March-2019. New Owner here!!
December 30, 2011, 12:50:17 PM
ok thanks for letting me know mark, I will remove it from the download list

(excited for block 25000! ) Smiley
legendary
Activity: 2940
Merit: 1090
December 30, 2011, 12:23:32 PM
We don't actually have a -qt that will still work when block 25000 comes around, and I already removed the old one from souceforge since it would break at that block anyway. For now people who want a GUI are going to have to deal with wxWidgets it seems; the old-devcoind actually has the old wxWidgets code in it, we just never used that back when the -qt worked.

-MarkM-
hero member
Activity: 896
Merit: 1000
Buy this account on March-2019. New Owner here!!
December 30, 2011, 09:30:06 AM
Devcoin Download Links
Download

Devcoin Source:
https://github.com/knotwork/old-devcoind

Devcoind 32 Bit Linux Binary (i686)
http://pool.devcoin.org/files/daemons/devcoind

Devcoind 64 Bit Linux Binary (x86_64)
http://btcnetwork.com/files/daemons/devcoind

This information can also be found by clicking the 'Download' tab at
http://www.devcoin.org
hero member
Activity: 896
Merit: 1000
Buy this account on March-2019. New Owner here!!
December 30, 2011, 09:08:18 AM
i686 = 32 bit

if it were 64 it would say x86_64

Jump to: