I read this project has been moved to bitcore. When I look at both sources they look very different.

How has the architecture/setup changed from one project to another? Any benefits for using this one over the newer one?

A few additional steps are needed to compile the bindings.

• Copying ./libbitcoind/src/leveldb/helpers/memenv/memenv.h to /usr/local/include/
• Compiling and installing ./libbitcoind/src/secp256k1/

cd libbitcoind/src/secp256k1
./configure
make
install

• Adding additional libraries (though not ideal)

'libraries': [
  ...
  '/usr/lib/libdb_cxx-4.8.so',
  '/usr/local/lib/libsecp256k1.a',
  '/usr/lib/x86_64-linux-gnu/libboost_program_options.so',
  '/usr/lib/x86_64-linux-gnu/libanl.so'
]

Hi,

Is [email protected]:bitpay/libbitcoind.git a private repository atm?

Right now, I don't believe we need the wallet functionality (although I could be very wrong about this long term). We may want to patch bitcoind to compile and run without pwalletMain.

Please show how much of a performance increase you can get if you provide node bindings to bitcoind versus calling the json rpc methods.

The primary methods needed are:

• getInfo
• getRawTransaction
• sendRawTransaction
• getTransaction

Wallet functionality isn't needed, and libbitcoind.so could be compiled with the --disable-wallet flag.

And only recompile if necessary, similar to running locally.

Hey guys,

Right now, bitcoindjs.cc has 3-4 different methods of starting the blockchain download (as if you were to run bitcoind straight away). Most of them have problems (the first which simply starts the boost threads in net.cpp cannot connect to peers). The AppInit2 methods start downloading the blockchain but have exception issues. The AppInit method gets run on the node thread pool. It works well, but the callback never gets executed because AppInit blocks, adding -daemon to the argv isn't what we want because it will just fork it.

Would love people to mess around with this and bitpay/libbitcoind. Checkout src/bitcoindjs.cc

Look into the possibility of using:

• https://www.npmjs.com/package/node-pre-gyp
• https://gitian.org/

If an earlier patch was installed...we need to check out the tag listed in PATCH_VERSION and re-patch and build.

i tried setting it up on my Mac but had some issues, and I don't want to make this a forum for debugging my build. Could you provide a Dockerfile? Thanks!

Modify patch to work against the latest bitcoind tags (and maybe bitcoin xt)?

Related code https://github.com/bitpay/bitcoind.js/blob/master/lib/modules/address.js#L32

• reduce the number of calls to isPublicKeyOut
• call toAddress as this will run the isPublicKeyHashOut and isScripthashOut checks, if there isn't an address check that it's a publickey out (or add this functionality to the toAddress method)
• outputs.length memoized as var length = outputs.length;
• script should be stored as hex, and parsing it as opcodes can be avoided by using _scriptBuffer
• use benchmarks to compare the performance of using join(':') and buffer writing (passing a buffer directly to the value for the key). Ultimately it's converted to a buffer, so there may likely be some improvements.
• we may or may not need to store the script, though it may help with performance.