gospel

README

Gospel: GO SPEcial Library

(c) 2010-2021 Bernd Fix brf@hoi-polloi.org >Y<

Gospel is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

Gospel is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.

You should have received a copy of the GNU Affero General Public License along with this program. If not, see http://www.gnu.org/licenses/.

SPDX-License-Identifier: AGPL3.0-or-later

Packages

• gospel/parser: Read/access/write nested data structures
• gospel/network: Network-related functionality
  • services
  • packet handling
  • SOCKS5 connection handler
  • SMTP/POP3 mail handling
• gospel/network/p2p:
  • P2P core library
• gospel/network/tor:
  • Tor controller
  • hidden services (onion handling)
  • Tor utilities
• gospel/bitcoin:
  • Elliptic curve crypto (Secp256k1)
  • Bitcoin addresses
  • key exchange
  • raw transactions
  • hash functions (Hash160, Hash256)
  • base58 encoding
• gospel/bitcoin/wallet:
  • HD key space
  • BIP39 seed words
• gospel/bitcoin/rpc: JSON-RPC to Bitcoin server
• gospel/bitcoin/script: Bitcoin script parser/interpreter
• gospel/bitcoin/tools:
  • passphrase2seed
  • vanityaddress
• gospel/math: Mathematical helpers
  • Fast Fourier Transformation
  • Arbitrary precision integers with chainable methods
• gospel/crypto: cryptographic helpers
  • secret sharing
  • prime fields
  • PRNG
  • Paillier crypto scheme
  • cryptographic counters
• gospel/crypto/ed25519:
  • general purpose Ed25519 crypto
• gospel/logger: logging facilities
• gospel/data: useful data structures like
  • stacks
  • vectors
  • Marshal/Unmarshal Golang objects
  • Bloom filter

Install

This version is designed for the Go1.11+ release.

Make sure that your Go environment - especially ${GOPATH} - is set up and enter the following command:

$ go get github.com/bfix/gospel/...

Test notes

Network-related tests

1. Tor-related tests

To run the Tor-related tests you need to set some environment variables to access the Tor control port:

export TOR_CONTROL_PROTO="tcp"
export TOR_CONTROL_ENDPOINT="127.0.0.1:9051"
export TOR_CONTROL_PASSWORD="my_torcontrol_secret"
export TOR_TEST_HOST="127.0.0.1"

Only TOR_CONTROL_PASSWORD is mandatory; TOR_CONTROL_PROTO, TOR_CONTROL_ENDPOINT and TOR_TEST_HSHOST default to the above values.

If Tor is not running on localhost (127.0.0.1), but remotely (either on a separate machine or in a Docker container), the environment variables for Tor tests above need to be adjusted. Let 1.2.3.4 be the IP address of the Tor instance and 5.6.7.8 the IP address of the system running the tests. Both systems must be interconnected, so they can talk to each other. The settings in this case would look like:

export TOR_CONTROL_PROTO="tcp"
export TOR_CONTROL_ENDPOINT="1.2.3.4:9051"
export TOR_CONTROL_PASSWORD="my_torcontrol_secret"
export TOR_TEST_HOST="5.6.7.8"

N.B.: You have to make sure that host 5.6.7.8 can access the Tor control port and Tor socks proxy ports (see torrc settings on the Tor instance).

Bitcoin-related tests

To successfully run the Bitcoin-JSON-RPC tests, follow these steps:

1. Edit the 'bitcoin.conf' configuration file

Use an ASCII editor to set the RPC variables to appropriate values:

server=1
rpcuser=<username>
rpcpassword=<password>
rpctimeout=30
rpcport=8332

2. Prepare an encrypted test wallet

Make sure that the encrypted test wallet has some transactions for the default account in it, if you want to run all implemented test paths.

3. Start the Bitcoin daemon for the test wallet

The RPC calls implemented in the library are compliant with Bitcoin Core v.0.14.0 and probably result in errors if used with previous (or later) versions; tests only work in 'testnet' (enforced).

bitcoind -testnet

4. Export environment variables for the RPC tests

If none of these variables are defined, the RPC tests will be silently skipped:

export BTC_HOST="http://127.0.0.1:8332"
export BTC_USER="<username>"
export BTC_PASSWORD="<password>"
export BTC_WALLET_PP="<your test wallet passphrase>"
export BTC_WALLET_COPY="/tmp/testwallet.dat"

The following environment variables are optional and listed with their default value; you can replace them with other valid data:

export BTC_PRIVKEY=""
export BTC_BLOCK_HASH="000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943"

N.B.: The variable BTC_PRIVKEY is a string representing a private Bitcoin key (like "93DaDjT5M5cBE6ApLhniKL1ct6N55tboJ8BdZYjfu5ZkWENS8VK"). If defined, it will be imported into the wallet and triggers a rescanning to evaluate its balance -- this could take a long time (see next step).

5. Run the tests

go test github.com/bfix/gospel/bitcoin/rpc

If you import a private key the rescanning will timeout the test run and result in a failure. Please run the test command with a 'timeout' setting in this case:

go test -timeout 3600s github.com/bfix/gospel/bitcoin/rpc