Devcoin

[markm]

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-

[1714002902]

1714002902

[12gaFacelift]

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

[emfox]

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):

sudo apt-get install g++ make libcurl4-openssl-dev  libdb++-dev libboost-all-dev libglib2.0-dev

then compile it:

cd /home/emfox/devcoind/src
make -f makefile.unix USE_UPNP= bitcoind

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:

mv /home/emfox/devcoind/src/bitcoind /home/emfox/bin/devcoind

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

rpcpassword=your_random_password_blabla

at last, run!

/home/emfox/bin/devcoind -daemon

devcoind should have started, and listening on port 52333.

That's all.

[FinShaggy]

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, here is the command:

sudo apt-get install g++ make libcurl4-openssl-dev  libdb++-dev libboost-all-dev libglib2.0-dev

then compile it:

cd /home/emfox/devcoind/src

make -f makefile.unix USE_UPNP= bitcoind

so now there's a file 'bitcoind' laying in /home/emfox/devcoind/src

we do not like the name and won't let it stay in a source tree, so we just:

mv /home/emfox/devcoind/src/bitcoind /home/emfox/bin/devcoind

before running it, we should edit ~/.devcoin/devcoin.conf, add a line:

rpcpassword=your_random_password_blabla

at last, run!

/home/emfox/bin/devcoind -daemon

devcoind should have started, and listening on port 52333.

That's all.

This confused the hell out of me.

[Balthozar]

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, here is the command:

sudo apt-get install g++ make libcurl4-openssl-dev  libdb++-dev libboost-all-dev libglib2.0-dev

then compile it:

cd /home/emfox/devcoind/src

make -f makefile.unix USE_UPNP= bitcoind

so now there's a file 'bitcoind' laying in /home/emfox/devcoind/src

we do not like the name and won't let it stay in a source tree, so we just:

mv /home/emfox/devcoind/src/bitcoind /home/emfox/bin/devcoind

before running it, we should edit ~/.devcoin/devcoin.conf, add a line:

rpcpassword=your_random_password_blabla

at last, run!

/home/emfox/bin/devcoind -daemon

devcoind should have started, and listening on port 52333.

That's all.

This confused the hell out of me.

Lol Fin. It's all linux.

[FinShaggy]

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, here is the command:

sudo apt-get install g++ make libcurl4-openssl-dev  libdb++-dev libboost-all-dev libglib2.0-dev

then compile it:

cd /home/emfox/devcoind/src

make -f makefile.unix USE_UPNP= bitcoind

so now there's a file 'bitcoind' laying in /home/emfox/devcoind/src

we do not like the name and won't let it stay in a source tree, so we just:

mv /home/emfox/devcoind/src/bitcoind /home/emfox/bin/devcoind

before running it, we should edit ~/.devcoin/devcoin.conf, add a line:

rpcpassword=your_random_password_blabla

at last, run!

/home/emfox/bin/devcoind -daemon

devcoind should have started, and listening on port 52333.

That's all.

This confused the hell out of me.

Lol Fin. It's all linux.

Lol, I don't know anything about Linux except for that's where they usually make the viruses and that usually Linux cant get viruses.

[emfox]

Now, I have set up a seed node for devcoin. It's running on a linode server.

The host is dvc.rpwt.org:52333 or devcoin.rpwt.org:52333, both domain name works.

Edit: I reg a new domain for the purpose, please use d.veco.in:52333 instead.

[FinShaggy]

Block: 86887/89000
It's getting close

[Unthinkingbit]

Now, I have set up a seed node for devcoin. It's running on a linode server.

The host is dvc.rpwt.org:52333 or devcoin.rpwt.org:52333, both domain name works.

Thanks, you get 1/5 as long as it keeps going:
https://raw.github.com/Unthinkingbit/charity/master/bounty_23.csv

[Balthozar]

Block: 86887/89000
It's getting close

Yessir! 

[emfox]

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):

sudo apt-get install g++ make libcurl4-openssl-dev  libdb++-dev libboost-all-dev libglib2.0-dev

then compile it:

cd /home/emfox/devcoind/src
make -f makefile.unix USE_UPNP= bitcoind

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:

mv /home/emfox/devcoind/src/bitcoind /home/emfox/bin/devcoind

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

rpcpassword=your_random_password_blabla

at last, run!

/home/emfox/bin/devcoind -daemon

devcoind should have started, and listening on port 52333.

That's all.

Edited, adjust word and add quotes.

I'll maintain it if anything changes.

[markm]

You didn't mention the receiver files. Maybe you simply happened to be in the same directory those files were in when you ran the devcoind? As one place they can be to work is wherever you are when you run the program. They then copy them over from there to their actual destination in a subdirectory of the data directrory. The other option is to specifically put them in that subdirectory yourself, which would usually mean you'd create the diata directrory create its subdirectory and put the receiver files there.

Obviously simplest, it is weren't for the difficulty of conveying to Windows users the concept of "current working directory" and how to put yourself in a particular directrory before running something, would be to make sure you are sitting where those files are when you first run the program.

-MarkM-

[emfox]

You didn't mention the receiver files. Maybe you simply happened to be in the same directory those files were in when you ran the devcoind? As one place they can be to work is wherever you are when you run the program. They then copy them over from there to their actual destination in a subdirectory of the data directrory. The other option is to specifically put them in that subdirectory yourself, which would usually mean you'd create the diata directrory create its subdirectory and put the receiver files there.

Obviously simplest, it is weren't for the difficulty of conveying to Windows users the concept of "current working directory" and how to put yourself in a particular directrory before running something, would be to make sure you are sitting where those files are when you first run the program.

-MarkM-

When I start to run devcoind, it reports that download from raw.github.com error, so I just copy receiver_0.csv (only this file) to ~/.devcoind/, remove the blk_* and __db* files from ~/.devcoind, restart devcoind and everything works. So I think it's just a temporily  network problem of my own. you see, devcoind download all the other receiver_*.csv files, isn't it?

So I didn't even mention that ...

[Balthozar]

Anyone pay attention to the small climb that DVC made against the USD today? 

Also, what happened on May 21 of last year that caused DVC to be worth $10 for the day?

[jackjack]

Proposition

• Hardcode current receiver files
• Hardcode an Unthinkingbit's signing address
• Create a new message type 'getrecfile', which only contains the height of the receiver file
• Create a new message type 'recfile'
  
  
  • Height of receiver file -> var_int
  • Pubkey that signs the receiver file -> var_str (because of compressed/uncompressed keys)
  • Signature of the recever file by pubkey (signed message is Height+Receiver_file) -> var_str
  • Receiver file -> var_str
  
  

How it works
Everybody:

• The client needs receiver_N.csv
• It sends a 'getrecfile' message with height=N to its peers
• If one of them has it, it sends back a 'recfile' message with the data
• The client checks that the signing pubkey is ok
• The client checks the signature is ok
• The client can process the received receiver file

Unthinkingbit signs a new receiver file:

• Put height in a var_int
• Put receiver file in a var_str
• Concatenate those two -> msg
• Sign msg with hardcoded pubkey
• Stores the 'recfile' message
• Broadcast it to peers or wait until someone asks for it (I have a preference for the latter, it avoids spamming the network)

In case of Unthinkingbit leaves/disappears/is kidnapped

• Devcoin community choses a new signing guy, whose pubkey is Pubkey2
• Fork the client and puts: Pubkey1 if Height<50, else Pubkey2

And if the new signing guy dies:

• Fork the client and puts: Pubkey1 if Height<50, else if Height<123 then Pubkey2, else Pubkey3

[markm]

Too centralised. Hardforking on signing key would be a bitch.

Better to just get a bunch more places where the files are available.

-MarkM-

[FuzzyBear]

Too centralised. Hardforking on signing key would be a bitch.

Better to just get a bunch more places where the files are available.

-MarkM-

I can post the files so people can download them from a server

[jackjack]

Devcoin itself is totally centralised

[FuzzyBear]

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, here is the command:

sudo apt-get install g++ make libcurl4-openssl-dev  libdb++-dev libboost-all-dev libglib2.0-dev

then compile it:

cd /home/emfox/devcoind/src

make -f makefile.unix USE_UPNP= bitcoind

so now there's a file 'bitcoind' laying in /home/emfox/devcoind/src

we do not like the name and won't let it stay in a source tree, so we just:

mv /home/emfox/devcoind/src/bitcoind /home/emfox/bin/devcoind

before running it, we should edit ~/.devcoin/devcoin.conf, add a line:

rpcpassword=your_random_password_blabla

at last, run!

/home/emfox/bin/devcoind -daemon

devcoind should have started, and listening on port 52333.

That's all.

This confused the hell out of me.

Lol Fin. It's all linux.

Lol, I don't know anything about Linux except for that's where they usually make the viruses and that usually Linux cant get viruses.

No don't believe the lies!! lunix may look confusing at first, but it truely is superior to windows in soooo many ways.... and for the record it is the anti-virus software manufacturers who mostly write the viruses so u have to buy their product... or have i just donned my tin-foil hat??

[jackjack]

Lol, I don't know anything about Linux except for that's where they usually make the viruses and that usually Linux cant get viruses.

No don't believe the lies!! lunix may look confusing at first, but it truely is superior to windows in soooo many ways.... and for the record it is the anti-virus software manufacturers who mostly write the viruses so u have to buy their product... or have i just donned my tin-foil hat??

Also, compiling windows apps/virus/etc is much much much much easier on windows, so there's no chance viruses are coded on Linux