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

Unable to get explorers working (for address balance). Anyone suggest which to use?

Thanks to BTCDDev!

I am now able to build and test libjl777.so without having to rebuild BitcoinDarkd
what this means is that we can start to think about release candidate testing for BitcoinDarkd!

The first version can just have a disabled libjl777 so all it tests is the new multisig, PoS v2, API pass through support and various other improvements BTCDDev has added over the months.

this will allow us to upgrade the installed base that is ready for a dropin libjl777.so into the /usr/lib and the Windows and Mac equivalents.

Then as new SuperNET features are qualified for release, we can make releases for libjl777 independently of a new BitcoinDarkd

James

but I only make a few hundred builds per week. is that too many?

Great, now we don't have to rebuild BitcoinDarkd when you update libjl777  

We recently began the process of open testing.  Teleport will be one of many new features available to BitcoinDark through the SuperNET integration.

I invite you to visit https://forum.thesupernet.org/index.php?topic=66.0 to view our testing progress.

BitcoinDark Block Explorer http://explorebtcd.info gone Dark. Now with more juice.
Showing Stake Reward for each block.

Various API available to get your info.

Test with some value from below:


use any of the API method after the domain name & enjoy.

Is it running stable?
I was getting random malloc/free errors using a .so
works great!
I pushed a merged btcd repo

BTCD with supernet will make a sensation on the cryptocurrency world and of course market.

just can't wait.

Any news on Teleport?

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

Very unique place to use  your BitcoinDark.    https://bitcointalksearch.org/topic/ann-crypto-collider-the-worlds-first-bitcoin-gaming-trading-hybrid-802212

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///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 

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

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

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

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

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?

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

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

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