BTCD is no more

[junsha]

Hi my bitcoindark wallet couldn't sync. it's a known problem?

[cloudboy]

Hi my bitcoindark wallet couldn't sync. it's a known problem?

Did you set up your BitcoinDark.conf file?

[jl777]

a lot of stuff happening in https://forum.thesupernet.org/index.php?board=14.0 and ##supernet IRC:

[16:02] <jl777> on one server I see {"requestType":"publishPservers","NXT":"10694781281555936856","Pservers":["209.126.70.170", "185.21.192.9", "23.97.66.164", "104.41.129.107", "74.143.21.66", "89.212.19.49", "209.126.70.156"],"firstPserver":0,"Numpservers":7,"xorsum":2198144725}
[16:03] <jl777> and {"requestType":"publishPservers","NXT":"13434315136155299987","Pservers":["209.126.70.159", "209.126.70.170", "89.212.19.49", "185.21.192.9", "199.193.252.103", "74.143.21.66", "23.97.66.164", "137.116.193.215", "209.126.70.156"],"firstPserver":0,"Numpservers":9,"xorsum":3355436066}
[16:03] <jl777> so this is very good! I have some MGW code to do and tonight I hope to make progress on making the propagation work reliably
[16:51] <jl777> OK, MGW code is being tested. back to the routing issues.
[16:51] <jl777> the third server only sees {"requestType":"publishPservers","NXT":"8894667849638377372","Pservers":["209.126.70.156", "74.143.21.66", "89.212.19.49", "185.21.192.9"],"firstPserver":0,"Numpservers":4,"xorsum":3867160699}
[16:51] <jl777> and I see the dreaded error: got ("error":"no np or global udp for sendmessage || destnp->mypeerinfo.srvnxtbits == 0"})
[16:52] <jl777> yesterday, I had some infinite loops where one server responded to another server, which caused another command sent, etc.
[16:52] <jl777> sort of like infinite recursion
[16:53] <jl777> I was just hardcoding an implicit statemachine by the code for each API
[16:54] <jl777> but clearly this is not workable for any complicated logic, so I need to generalize some simple ACK and ACK ACK protocol in a generic statemachine so the majority of API calls can just use a default statemachine
[16:54] <jl777> does anybody see a flaw with this approach?

[junsha]

Hi my bitcoindark wallet couldn't sync. it's a known problem?

Did you set up your BitcoinDark.conf file?

No I didn't, how to setup this file?
Thank you!

[omahapoker]

found this thread on page 3 again. interest dying out?




BTCD really needs a good dice site to make BTCD more known

[jl777]

mgwBTCD should be caught up now
let me know if any missing tx

James

[salsacz]

During my speech in Shanghai Bitcoin expo I also introduced the Teleport as one of the technologies which will be used or anon transactions and also as a member of the Supernet. I printed all whitepapers and handed them to the audience, but didn't talk much about boring technology, more about the history behind the BTCD. The second tech was CryptoNote technology, since it is already existing one. So BTCD was presented in a big way, I guess it would be useful to share this info with ya

[crackfoo]

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

Cheers!

[cloudboy]

During my speech in Shanghai Bitcoin expo I also introduced the Teleport as one of the technologies which will be used or anon transactions and also as a member of the Supernet. I printed all whitepapers and handed them to the audience, but didn't talk much about boring technology, more about the history behind the BTCD. The second tech was CryptoNote technology, since it is already existing one. So BTCD was presented in a big way, I guess it would be useful to share this info with ya

Video?

[jl777]

just pushed a version that fixes sync issues so all the peers should auto discover each other, but need to see it in action to be sure that the bandwidth usage drops off as the nodes get in sync

James

[paulthetafy]

@devs, any thoughts on how long before any of the new features are released?

[jl777]

@devs, any thoughts on how long before any of the new features are released?

The network of about 10 servers is being tested
The onion routing has been seen to work, though there are still some bugs
I did a bunch of new code to make the onion routing reliable and also the propagation of the routing info, so another day or so and I think we should have a pretty stable SuperNET networking. Still dont have any test programmers to create some really intense test scenarios, maybe I have to do this myself...

Some small changes are needed to go from a loopback mode (where I had Teleport working) to SuperNET capable, but not so much. give me a couple days after the network stabilized to get teleport into testing. The GUI I have no idea how long this will take, also Windows and Mac builds. Without test programmers, I am nervous to scale things up much beyond the current network size. So hopefully we can find some

Since nobody has ever made a SuperNET before and nobody has ever implemented Teleport before, to make an exact estimate is not going to be reliable. Now I am finally able to code for most of the day and I have made it clear I am done maintaining the MGW servers and also I dont bother with the SuperNET thread, these are all things that maximizes the time I have for coding.

Keep in mind that once the SuperNET networking is working, all the other features are at the application level and will go much faster. And there are degrees of working. As soon as we have a dynamic library version of a build process, then we can make a hardfork update once. Then to update to a new SuperNET will just require adding a new dynamic library file to your system. So, this is what I want to have, but I am not doing this build process so I dont know how long it will take.

As soon as we have that, then we could make a new release candidate and then make incremental SuperNET API releases. This I think is the practical path.

James

The design review of Teleport/SuperNET is not finding any critical issues and I did have to make improvements made, I dont think I posted much about these types of things and I know last weeks I have not been posting much here, but there has been a lot of progress toward the finish line. Validating the design via independent reviews is a critical part of all this

[cloudboy]

What's with all the orders of 0.0005 BTC worth of BTCD on both the Buy and Sell sides?

Obvious market manipulation, someone trying to drive down volume?

[SHossain]

http://explorebtcd.info now shows total BTCD supply on the header if anyone is interested.

[Aptidude]

http://explorebtcd.info now shows total BTCD supply on the header if anyone is interested.

When I go to explorebtcd.info, I get this screen:

[cloudboy]

http://explorebtcd.info now shows total BTCD supply on the header if anyone is interested.

When I go to explorebtcd.info, I get this screen:

It works for me. I'm on Ubuntu 14.04.

[SHossain]

http://explorebtcd.info now shows total BTCD supply on the header if anyone is interested.

When I go to explorebtcd.info, I get this screen:

Aptitude, sorry for the poblem. I'm not sure why you are seeing this. I can view it from my Windows and Ubuntu desktop. Please try using this link instead http://explorebtcd.info:3000

[BTCDDev]

I was able to compile libjl777 as a shared library and link it into BitcoinDarkd.

Here is how:

1. copy randombytes.o from the nacl build directory (nacl-20090405/build/<username>/<processortype>/lib) to btcd/src
2. change the LIBS line in makefile.unix to this:
   

Code:

LIBS += $(CURDIR)/leveldb/libleveldb.a $(CURDIR)/leveldb/libmemenv.a -ljl777 libuv.a libnacl.a randombytes.o -lcurl -lm -ldl

3. create a new file in btcd/libjl777 called make_shared and paste this into it:
   

Code:

rm libjl777.so
rm /usr/lib/libjl777.so
gcc -shared -Wl,-soname,libjl777.so \
-o libjl777.so libjl777.o libtom/*.o \
picoc/*.o picoc/cstdlib/*.o picoc/platform/*.o \
libgfshare.o -lstdc++ -lc
mv libjl777.so /usr/lib

4. edit btcd/m_unix to this:
   

Code:

git pull
./BitcoinDarkd stop
cd libjl777
./clean
./m
cp libjl777.a libs
cd libuv
make
cp .libs/libuv.a ../libs
cd ..
cp libs/*.a ../src
./make_shared
cd ../src
rm BitcoinDarkd
make -f makefile.unix
rm ~/.BitcoinDark/debug.log
cp BitcoinDarkd ..
cd ..
./BitcoinDarkd

Let me know if it works for you. My CPU usage seems to be pretty high, not sure if this is causing that. If we can get this perfected, then future SuperNET upgrades can be made by simply replacing libj777.so in /usr/lib with the updated one instead of rebuilding BitcoinDarkd 

[flexnuts]

Very unique place to use  your BitcoinDark.    https://bitcointalk.org/index.php?topic=802212.0

[BTCDDev]

We can always use more volunteers to help us test SuperNET!

If you know your way around a command line and some makefiles, grab a vps and head over to
https://forum.thesupernet.org/index.php?topic=66.0 to help!

It will speed things up and you get to be on the cutting edge of the hottest new tech. in cryptocurrencies! 

Matthew