Topic: BTCD is no more - page 232. (Read 1328507 times)

Note to self:  When building a new trading bot, do not let it loose with all of your coins until it is fully tested!!

I now have even more BTCD.  not a terrible thing.

If you are only on a command line, then you cannot run a BitcoinDark-qt. Run BitcoinDarkd, it runs just as well.

cd src/
make -f makefile.unix

Only on command line but i cannot see that file, I think i may just install a GUI on this server but security wise not very good

Are you on a server with gui support?

If you are on a command line only, use BitcoinDarkd

No centralized organization can provide this level of support. 

Man this is harder than i thought lol.

root@Server:~/bitcoindark# ./BitcoinDark-qt &
[1] 13045
root@Server:~/bitcoindark# QXcbConnection: Could not connect to display

I will take you up on your offer in irc Paul

#dumbass123

The easy bit!  from your shell you can run
./BitcoinDark-qt &
(the & means that it runs in a new process so you dont need to leave the shell open afterwards)

Some good progress. Along the way we made a few bugs, but now all is testing well with the existing blockchain.

There are 4 changes I have asked for that will complete the core work needed from BTCDdev and now the builds should be much easier with Mac and even Windows, so the BTCD daemon is looking very close.

I drastically simplified the internal complexity by gutting the TCP totally and switching to a UDP only statemachine approach. Each node will have a separate state machine relative to every other node. So all the complexity will be the specific state differences. As long as each state machine is solid, then the entire peer to peer set of states will be solid.

The removal of TCP removes a Dos attack vector of tying up the sockets on a node. With UDP you will need to saturate its entire connection with junk traffic. Due to the strong nested onion encryption, this is really the only practical attack vector that I can think of. [Other than swat teams confiscating all the nodes!]

I also realized that since it is not possible to know when the final layer of the onion has been peeled, the fact that you are even talking to a specific privacyServer is actually the bigger info leak than anything the privacyServer can determine about you! So, I am switching to routing via randomly selected privacyServer for all traffic.

Over the months I had scrubbed all the info that can be gleaned from the privacyServer, so this actually simplifies things even more as there are no special privacyServers for each node.

James

P.S. If anybody is on a Mac, can you try to build following the instructions on https://github.com/jl777/btcd
It is still a dev version and can be any state of bugginess, but the build process can be verified and this will help save time. So, the question is if it builds and links. you can run it too, but please dont keep it live as I am trying to keep a controlled test going

Thank you Paul.

I have BitcoinDark-qt now but how do i run it? 

That sure is brutal. I try not to think about what COULD'VE been either. I'm sure we all have had a similar experience. Just glad I've been on board for awhile.

I had 15 TH/s mining on that first day (10-15% of the network for many hours).  I left it on a pool and went to bed.  When I woke up I had zero coins as the pool had fucked up and wasn't submitting found blocks properly.  By the time I had realised the problem and switched pools I estimate I had lost 15-20k coins at least.  I then mined for the next couple of days and gained a bag of well over 20k+ coins, only to delete my wallet.dat with them in whilst encrypting my wallet after moving them all off the exchanges (true story, you can read back through the threads here).  I try not to think about losing $250k worth of coins.  Thankfully I has the sense to sell my LTC and bought a couple of k whilst it was still in the 100k-300k price range, so it isn't a total loss. 

It's understandable that the price will retract a bit now until teleport and the new wallet is released.  At which point it will absolutely fly through 0.02 and beyond very quickly.  So yeah, stock up now at this price range if you want to double up within a few weeks!!

Not sure who you are referring to, but I'm warning others of my mistake and what i have witnessed (I've been following since day 1) and learned in the meantime. Even though I sold for a nice profit at the time, I still think about that bloody Sunday.  

For those wanting to build the QT wallet on linux, please make sure to read down to the part about build configuration options....
https://github.com/laowais/bitcoindark/blob/master/doc/readme-qt.rst

If you don't have miniupnp installed then you will have to build without UPNP support or it wont compile..
qmake USE_UPNP=-

Alternatively you can install miniupnp before building.  On Ubuntu this can be done by installing the libminiupnpc-dev package...
sudo apt-get install libminiupnpc-dev

Please stop your scammer crews from going to our thread. Thanks

Sorry, but the hype-train is all out of steam right now.

Next price increases will become after the hyped features are published and working as intended.

IMO most of the people currently selling are those that bought above 0.013 and are selling at a loss for fear of a further drop, this is when those who know what's going on accumulate cheap BTCD and the price rebounds eventually. Take it from the guy who sold 11,000 BTCD at 0.0005.

So that post will make the price rise again. Especially who understands it will buy more. Thank you.

https://github.com/jl777/libjl777
jl777
711 commits / 674,967 ++ / 402,946 --

There are definitely a lot of stuff going on in the background.  I suppose if you can read code, you can check github and see that it's being updated and worked on all the time by jl777.   Everything has been open source since the beginning, which you don't see with many (if any) coins out there.  If I'm correct, I think he's aiming to start releasing features by the end of this month.

The latest shift for the BitcoinDark Multipool paid out over 91 BTCD.

Cheers!