LBRYCommunity/lbcwallet
1
0
Fork 0
Code Issues 5 Pull requests Projects Releases 14 Packages Wiki Activity
A secure lbry wallet daemon written in Go
74 commits 1 branch 18 tags 9.6 MiB
Go 99.7%
Makefile 0.2%
Find a file
Josh Rickmar eff1407afe go fmt
2013-10-13 19:27:30 -04:00
tx Save correct addresses for new utxos 2013-10-10 18:44:44 -04:00
wallet Save correct addresses for new utxos 2013-10-10 18:44:44 -04:00
.gitignore Initial commit. 2013-08-21 10:37:30 -04:00
cmd.go go fmt 2013-10-13 19:27:30 -04:00
cmdmgr.go Begin sending notifications based on all accounts. 2013-10-10 16:20:23 -04:00
config.go Default to testnet. 2013-10-07 13:25:05 -04:00
createtx.go small cleanup 2013-10-11 10:53:55 -04:00
createtx_test.go fix tests 2013-10-13 19:25:47 -04:00
README.md Remove finished items from TODO list 2013-10-01 14:45:06 -04:00
sample-btcwallet.conf Add simple sample configuration file. 2013-10-04 09:01:04 -04:00
sockets.go Begin sending notifications based on all accounts. 2013-10-10 16:20:23 -04:00
version.go Add missing licenses to files 2013-08-22 12:30:38 -04:00

README.md

btcwallet

btcwallet is a daemon handling bitcoin wallet functions. It relies on a running btcd instance for asynchronous blockchain queries and notifications over websockets.

In addition to the HTTP server run by btcd to provide RPC and websocket connections, btcwallet requires an HTTP server of its own to provide websocket connections to wallet frontends. Websockets allow for asynchronous queries, replies, and notifications.

This project is currently under active development is not production ready yet.

Usage

Frontends wishing to use btcwallet must connect to the websocket /wallet. Messages sent to btcwallet over this websocket are expected to follow the standard Bitcoin JSON API and replies follow the same API. The btcd package btcjson provides types and functions for creating messages that this API. However, due to taking a synchronous protocol like RPC and using it asynchronously, it is recommend for frontends to use the JSON id field as a sequence number so replies can be mapped back to the messages they originated from.

Installation

btcwallet can be installed with the go get command:

go get github.com/conformal/btcwallet

Running

To run btcwallet, you must have btcd installed and running. By default btcd will run its HTTP server for RPC and websocket connections on port 8332. However, bitcoind frontends expecting wallet functionality may require to poll on port 8332, requiring the btcd component in a btcwallet+btcd replacement stack to run on an alternate port. For this reason, btcwallet by default connects to btcd on port 8334 and runs its own HTTP server on 8332. When using both btcd and btcwallet, it is recommend to run btcd on the non-standard port 8334 using the -r command line flag.

Assumming btcd is running on port 8334, btcwallet can be started by running:

btcwallet -f /path/to/wallet

GPG Verification Key

All official release tags are signed by Conformal so users can ensure the code has not been tampered with and is coming from Conformal. To verify the signature perform the following:

  • Download the public key from the Conformal website at https://opensource.conformal.com/GIT-GPG-KEY-conformal.txt

  • Import the public key into your GPG keyring:

    gpg --import GIT-GPG-KEY-conformal.txt

  • Verify the release tag with the following command where TAG_NAME is a placeholder for the specific tag:

    git tag -v TAG_NAME

What works

  • New addresses can be queried if they are in the wallet file address pool
  • Unknown commands are sent to btcd
  • Unhandled btcd notifications (i.e. new blockchain height) are sent to each connected frontend
  • btcd replies are routed back to the correct frontend who initiated the request

TODO

  • Require authentication before wallet functionality can be accessed
  • Serve websocket connections over TLS
  • Documentation
  • Code cleanup
  • Optimize
  • Much much more. Stay tuned.

License

btcwallet is licensed under the liberal ISC License.