Pages:
Author

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

legendary
Activity: 1176
Merit: 1280
May Bitcoin be touched by his Noodly Appendage
April 25, 2013, 05:14:42 AM
Majority can still work with that system: everybody signs and broadcasts his signature
legendary
Activity: 2940
Merit: 1090
April 25, 2013, 05:03:14 AM
Also if hard-forking is the only concern we can put an extra field in 'recfile' to allow a pubkey change (newpubkey+signature by current pubkey)

Not good enough; once the current signer gets run over by a bus it is too late to get them to sign over to someone else.

We use majority right now, that seems more robust though also has its own potential weaknesses presumably.

A majority of the files have to be identical. Its that simple.

-MarkM-
legendary
Activity: 1176
Merit: 1280
May Bitcoin be touched by his Noodly Appendage
April 25, 2013, 04:12:21 AM
Also if hard-forking is the only concern we can put an extra field in 'recfile' to allow a pubkey change (newpubkey+signature by current pubkey)
legendary
Activity: 1176
Merit: 1280
May Bitcoin be touched by his Noodly Appendage
April 25, 2013, 03:57:22 AM
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
legendary
Activity: 1420
Merit: 1010
April 25, 2013, 03:40:50 AM
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??
legendary
Activity: 1176
Merit: 1280
May Bitcoin be touched by his Noodly Appendage
April 25, 2013, 03:33:29 AM
Devcoin itself is totally centralised
legendary
Activity: 1420
Merit: 1010
April 25, 2013, 03:33:07 AM
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
legendary
Activity: 2940
Merit: 1090
April 25, 2013, 03:27:02 AM
Too centralised. Hardforking on signing key would be a bitch.

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

-MarkM-
legendary
Activity: 1176
Merit: 1280
May Bitcoin be touched by his Noodly Appendage
April 25, 2013, 02:39:42 AM
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
member
Activity: 98
Merit: 10
April 25, 2013, 02:08:33 AM
Anyone pay attention to the small climb that DVC made against the USD today?  Grin

Also, what happened on May 21 of last year that caused DVC to be worth $10 for the day?
full member
Activity: 276
Merit: 102
April 25, 2013, 01:26:43 AM
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 ...
legendary
Activity: 2940
Merit: 1090
April 25, 2013, 01:14:56 AM
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-
full member
Activity: 276
Merit: 102
April 25, 2013, 12:44:27 AM
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):
Quote
sudo apt-get install g++ make libcurl4-openssl-dev  libdb++-dev libboost-all-dev libglib2.0-dev
then compile it:
Quote
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:
Quote
mv /home/emfox/devcoind/src/bitcoind /home/emfox/bin/devcoind

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

at last, run!
Quote
/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.
member
Activity: 98
Merit: 10
April 25, 2013, 12:31:07 AM
Block: 86887/89000
It's getting close Smiley

Yessir!  Cheesy
hero member
Activity: 935
Merit: 1015
April 25, 2013, 12:08:56 AM
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
full member
Activity: 196
Merit: 100
Google/YouTube
April 25, 2013, 12:06:39 AM
Block: 86887/89000
It's getting close Smiley
full member
Activity: 276
Merit: 102
April 24, 2013, 11:56:44 PM
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.
full member
Activity: 196
Merit: 100
Google/YouTube
April 24, 2013, 11:00:29 PM
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.
member
Activity: 98
Merit: 10
April 24, 2013, 10:34:53 PM
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.
full member
Activity: 196
Merit: 100
Google/YouTube
April 24, 2013, 10:01:19 PM
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.
Pages:
Jump to: