Bitcoin Forum
June 22, 2024, 03:37:11 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bcoin vs Bitcoin core integration/staging tree  (Read 410 times)
dragons_are_secure (OP)
Jr. Member
*
Offline Offline

Activity: 42
Merit: 2


View Profile
October 15, 2017, 05:12:43 PM
 #1

 We're doing our initial development work in Bcoin (node.js), since that is faster for us.  But, I'm curious the Bitcoin Forum's take on alternatives to the main bitcoin network reference stack. 

 As I read it, purse.io is the main user of Bcoin, are there others?
 If we continue development past the starting stages and eventually into production, is it better to switch to another stack (e.g. back to C++?)

https://github.com/bitcoin/bitcoin
https://github.com/bcoin-org/bcoin

 Are there other node.js alternatives that we should be considering or other languages that the Forum feels should be considered?
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3430
Merit: 6720


Just writing some code


View Profile WWW
October 15, 2017, 11:20:37 PM
 #2

Bitcoin Core is not a library, so if you are looking for something to use as a library in a software, then you should not use Bitcoin Core. If your application can work without directly calling things as in a library but rather just use Bitcoin Core's RPC commands, then Bitcoin Core may be better for you. With the RPC commands, you can write your software in whatever language you want.

IIRC Bitcoin Core is far faster and less resource intensive (i.e. less memory usage) than BCoin because of the difference in programming languages (JS, vs C++).

dragons_are_secure (OP)
Jr. Member
*
Offline Offline

Activity: 42
Merit: 2


View Profile
October 17, 2017, 01:56:14 AM
 #3

Thank-you for your comment and suggestion.  We are planning on changes that would be larger than met by using RPC calls.  But, I am concerned that we may have to develop first in the node.js and then redo for production in C++.

At this stage of development its more important, I think, for us to be able to try out ideas fairly quickly, and so issues with memory management and even possible resource drain is less important.  But, I very much appreciate the thought, since looking ahead to possible production, those could be very important issues.
dragons_are_secure (OP)
Jr. Member
*
Offline Offline

Activity: 42
Merit: 2


View Profile
October 17, 2017, 01:36:04 PM
 #4

also, just to make sure that we aren't missing codebases, these are coming up as the main connections for RPC calls -- others that should be added?

https://github.com/bitpay/bitcoind-rpc
https://github.com/ruimarinho/bitcoin-core
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3430
Merit: 6720


Just writing some code


View Profile WWW
October 17, 2017, 02:54:29 PM
 #5

also, just to make sure that we aren't missing codebases, these are coming up as the main connections for RPC calls -- others that should be added?

https://github.com/bitpay/bitcoind-rpc
https://github.com/ruimarinho/bitcoin-core
You don't really need a library for RPC calls; the RPCs follow the JSON-RPC 1.0 specification (and maybe 2.0 too). It's just an HTTP server which you send JSON formatted text to and get JSON formatted text back.

dragons_are_secure (OP)
Jr. Member
*
Offline Offline

Activity: 42
Merit: 2


View Profile
October 19, 2017, 12:07:46 PM
 #6

Do you (or others on the list) know the status of particular JSON-RPC extensions?  We're thinking of tapping into that, somewhat similar to this proposal:
 
  https://wiki.opendaylight.org/images/9/9d/JSON-RPC.pdf

It sounds like we'd need formal approval for an extension to be used.  Or, is this simply an internal network optional that we can modify as we'd like?

achow101
Moderator
Legendary
*
Offline Offline

Activity: 3430
Merit: 6720


Just writing some code


View Profile WWW
October 19, 2017, 05:18:14 PM
 #7

Do you (or others on the list) know the status of particular JSON-RPC extensions?  We're thinking of tapping into that, somewhat similar to this proposal:
 
  https://wiki.opendaylight.org/images/9/9d/JSON-RPC.pdf

It sounds like we'd need formal approval for an extension to be used.  Or, is this simply an internal network optional that we can modify as we'd like?
If it is not part of the JSON-RPC 2.0 specification, then Bitcoin Core probably does not support it.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!