Topic: BTCD is no more - page 395. (Read 1328490 times)

This logo reminds me of the Debian Logo (one of the famost Linux distributions):
https://www.google.com/search?q=debian+logo&tbm=isch

Apart from that: Nice work!

awsome work, only a week? let the panic buying begin.

That's why the main image represents a portal..."teleport".  A lot of time and effort was put into this by the non-core dev team, and I'm pretty happy with the final logo we've developed.  We've moved away from the "coin" image that everyone else seems to be stuck on.  Our logo represents a portal in abstract form and will be easily recognizeable, and is perfectly scaleable, so it is very to make out even at small sizes.  Another aspect is that the gold logo will be the main logo, however we can use different colors for different features, e.g. blue for teleport, green for privatebet, black for anon card, etc.

I still have the local file encrypt/decrypt to link up, but I can test the teleporting without that, so I will probably procrastinate on it until a bit later. So, I am sure I have some small parts not quite right, but at long last I feel I can call it "code almost complete"

Before you get excited, this doesnt have much error handling and it hasnt been ported into BTCD core, but it does have multisig support, ready for user defined cipher sequences for local files, randomized cloning times, and I made it so that it should be pretty much an install it and run it design. As long as your BitcoinDark.conf file has "server=1" and rpcusername/password defined, Teleport should be enabled. No need for hours long reindexing of blockchain and other horribly inconvenient install issues. Turns out 80% of MGW code was needed to achieve this!

With all the new features, especially multisig added after I started, it feels like I need three days to get this debugged, so if I can achieve that timeframe, then on Wed some people will be able to do some command line teleports. After that I need to partition the code to make it easy to implant into BTCD core. I plan to make a libjl777.a that can be linked to the BTCD core and with a few small hooks, we can have just a single wallet executable that has everything needed for Teleport. until the QT has been updated, it would still be command line, but from the QT debug window console

Let's say two days to get it into libjl777.a form and the weekend to get it into BTCD core. This is getting more speculative, but if all goes well, a week from Monday, we could have a BTCD-qt with teleport built into it.

Now this first pass will not have full privacyServer + onion routing. That is a totally independent transport mechanism and I wanted to get a teleport enabled released into testing sooner rather than later. While the basic teleport is being tested, I will make the privacyServer that is embedded in the BTCD-qt do all the things it needs to do.

Even if I meet this schedule it is Aug 18th for the teleport enabled release, so I am three days late...
Blame multisig!

James

###
I totally forgot!
The other reason for libjl777 is to allow other coin's to link up to BTCD network, most importantly InstantDEX and Teleport. This will allow creation of a super network composed of all the participating coin's networks. It wont require a hardfork and would be a matter of linking the library and make some few interface functions. After they do that they will be able to utilize the encryption network and more importantly have access to InstantDEX orderbooks. The more people (and tradebots) trading on InstantDEX, the better liquidity, lower spreads, and more commissions. Also, if they can connect directly to the encryption network that increases Teleport traffic (and fees) which increases anon levels (and dividends)

All part of my master plan for liberation from fiat govts

I like the way it conveys "bitcoin" in dark
Not sure about upper lower case, but the important thing is to convey that BTCD makes bitcoin itself dark
people will assume (correctly) that BTCD itself is dark, but most will be surprised that BTCD makes Bitcoin Dark

James

design is better, perhaps change the case from BITCOINDARK to BitcoinDARK.

the buys vs sells in the order book are amazing, almost no one is selling.

Nobody cares what you think  about buying bitcoindark, its a decent coin

Hope everyone enjoys the new look!

I remember when the EFF made Deep Crack in '99, but I haven't kept up with the state of cryptography since then.  I'm no expert.  

With that said, my naive recommendation is to use AES.

Thanks!
I will delete it from the possible list of ciphers, any others that have been cracked?

Don't use plain old DES.  It is not safe.

Any idea when http://btcd.xpool.ca/ will be back up?  Im currently still able to mine, but cant access the page.

OK, got the JSON parsing of the "ciphers" field added to jl777.conf and while I was at it, I got all the encryption/decryption functions added to the codebase, along with initializing them and getting all the functions needed to process them in realtime. turns out I also needed sha256, but I will need that for other things too, so it is good it is integrated into the new codebase. I also added rmd160 as that is used for bitcoin encryption

I still have the actual encryption/decryption loop to do, but with all the parsing done and all the ciphers accessible, I will save that task for when I am too tired to do anything too difficult.

Add another 1000 lines to the code size and that's just the code I had to push through the automated context customizer. The actual cipher codes and data tables are probably around 20,000 more lines! I am not calling any system libraries, so all the code that is needed is right there in case there is ever an issue to be investigated, I can always start debugging from the source.

I didnt plan to get all this fancy user configurable cipher sequences in, but it had to be done before production release so just shuffling the order of getting stuff done. My guess is no other crypto allows the user to customize how their files are encrypted this way. Also noteworthy is that the way things are setup, even though all public addresses go to the same "post office box", each one will end up with a customizable "ciphers" field. This just makes me realize I need a field in the telepod filename to tell what coin's public address it received from, otherwise I would have to try all the various possibilities and that seems pretty inefficient

James

having multiple ciphers sequences complicated things a bit, I think for initial release only 1 ciphers sequence will be supported, but there should be no reason (other than debug time) that we cant have multiple cipher sequences

it was nearly at 600k yesterday

Can this thing reach 500,000 Satoshi?  Wow!!!

Poll is up!

I think only the OP can do it.

does somebody know how to make a poll?
maybe we can vote on which of the 19 ciphers to use for the default method
community determined encryption method. I think that could be a first

James

Speaking of encrypting the telepods, we have a rather large choice of methods to use:

aes
blowfish
xtea
rc5
rc6
saferp
twofish
safer_k64
safer_sk64
safer_k128
safer_sk128
rc2
des
des3
cast5
noekeon
skipjack
khazad
anubis

That's 19 possible ways to encrypt and that's only if we use one level of encryption. I dont know the details of all these encryptions to figure out which one is best to use for telepods. If anybody has insight into this, I'd appreciate any feedback

I could allow the exact encryption method and sequence to be encoded in the .conf file, this way it is totally flexible so we can always test it with various .conf files to see which ones have the best results, or maybe they will all be pretty much the same?

Offhand, I think JSON like this:

"ciphers":[{"skipjack":"RMhMMyuJcJFw2kdxuqTyZnkZ8ZYxvKTtAp"},{"aes":"RFN1LKmcmC2kywNK5MHt4eqzg4QEGoapTy"},{"blowfish":"REiBxsAkDJodK4L4NaDfMZQntkC3difwfA"}]

You can add more that three, or just have one. I just picked three telepod addresses I already generated as the second part of each JSON field. Each address -> privatekey and that will be used to seed the cipher. For accounts without a "ciphers" field would just default to one level using the default public address for seed and one of the above 19 I pick at random.

Now, using this method means that in addition to your BTCD wallet password the exact sequence of the ciphers/addresses is REQUIRED to decrypt your telepods. That means if you ever lose this sequence, the telepods are lost!
I cannot stress this enough. Nobody will be able to decrypt the telepods if the cipher sequence is not known. So if you do use this, I highly recommend that you come up with some sort of mneumonic that is easy to remember so you can recreate the cipher sequence and then also label the addresses used in a way that you can recognize the sequence, but somehow other people wont.

I realize, arbitrarily nested encryption sequences might be a bit of overkill, but I am designing Teleport system to keep it safe from attackers and to be generational. If you do put significant wealth into telepods, then I would suggest to:

dumpprivkey

This will spit out a bunch of letters and numbers. This is the privatekey!! Be VERY careful as this like like the key that opens the telepods. So, make a file (do not save it) with the cipher, address and the privkey, one to each line. and then take a picture of it. Make a printout in a secure place, eg. your own printer and store both the removable media the pic was saved and the printout in a safe deposit box or some physical location that you are comfortable having the keys to all those telepods in.

Dont save this file, so it never goes on your HDD. Also make sure you have no key loggers or spyware, etc. Maybe doing this on some old laptop you buy just for doing this. reformat HDD, install fresh OS and get a copy of the BTCD wallet.dat. Dont ever need to go online with this offline laptop. Better to use some sort of Ubuntu desktop instead of Windows, but with care, even Windows should be OK if you are installing a trusted copy and never go online.

James

P.S. I am writing in such detail so that someone can go through these posts to make user manual

and if anyone wants to join the BitcoinDark Promo Trello, or choose any of the displayed category... https://trello.com/b/BPl2YkZV/bitcoindark-promo