This release is a pre-release and may not be stable for production use.
sPRUNED
A Bitcoin lightweight pseudonode with RPC that can fetch any block or transaction
What’s this?
sPRUNED is a bitcoin client for light systems. 256mb ram & 500mb hdd should be fairly enough to keep it up & running.
Supports both Bitcoin Mainnet and Testnet It’s a replacement for bitcoind on lightweight systems (It’s proven to work on a Raspberry Zero, along with CLightning), it provides an interface for bitcoin-cli.
How it works?
spruned downloads and store the bitcoin blocks on demand, when you need them, directly from the Peer2Peer Bitcoin Network. there’s a “bootstrap” functionality, to keep the last ~50 (default settings) blocks on the local storage, because fetch blocks may require also up to 10 seconds with slow connections, and this “bootstrap mode” reduces latencies on usage.
You can use bitcoin-cli, or any other RPC client, as if you had bitcoind up & running. For the transactions related APIs and utxo tracking, spruned uses the electrum network.
Documentation
Dependencies
spruned works with Python >= 3.5.2. Right now it should work only on Linux systems. It make intensive usage of connectrum, pybitcointools and pycoinnet libraries. Thanks to mantainers & contributors! Especially at this stage of development (but it would be better always), it is recommended to use virtualenv to run spruned.
Usage
Developers: I hope code is self explaining enough, if you’re familiar with asyncio.
Everyone else: You can get inspiration on how to install spruned taking a look at setup.sh but, if you’re lucky enough, setup.sh itself will create a virtual environment and install spruned into it.
Well, try this:
$ cd ~/src
$ sudo apt-get install libleveldb-dev python3-dev git virtualenv
$ git clone https://github.com/gdassori/spruned.git
$ cd spruned
$ ./setup.sh
$ venv/bin/python spruned.py --help
usage: spruned.py [-h] [--rpcuser RPCUSER] [--rpcpassword RPCPASSWORD]
[--rpcport RPCPORT] [--rpcbind RPCBIND] [--datadir DATADIR]
[--daemon] [--keep-blocks KEEP_BLOCKS]
[--network {bitcoin.mainnet,bitcoin.testnet}] [--debug]
[--cache-size CACHE_SIZE]
A Bitcoin Lightweight Pseudonode
optional arguments:
-h, --help show this help message and exit
--rpcuser RPCUSER Username for JSON-RPC connections (default: rpcuser)
--rpcpassword RPCPASSWORD
Password for JSON-RPC connections (default:
rpcpassword)
--rpcport RPCPORT Listen for JSON-RPC connections on <port> (default:
8332 or testnet: 18332) (default: 8332)
--rpcbind RPCBIND Bind to given address to listen for JSON-RPC
connections. (default: 127.0.0.1)
--datadir DATADIR Specify data directory (default: /home/guido/.spruned)
--daemon Run in the background as a daemon and accept commands
(default: False)
--keep-blocks KEEP_BLOCKS
--network {bitcoin.mainnet,bitcoin.testnet}
--debug Enable debug mode (default: False)
--cache-size CACHE_SIZE
Cache size (in megabytes) (default: 50)
And, once you run spruned:
$ tail -f ~/.spruned/spruned.log # to see what's going on!
or check the status*:
$ bitcoin-cli getblockchaininfo
{
"mediantime": 1523387051,
"blocks": 517579,
"headers": 517579,
"verificationprogress": 100,
"chain": "main",
"chainwork": null,
"difficulty": null,
"bestblockhash": "00000000000000000018e502dec1f93d32521674019a45d7d095cbd390279dff",
"warning": "spruned v0.0.1. emulating bitcoind v0.16",
"pruned": false
}
Download a block:
$ bitcoin-cli getblock `bitcoin-cli getblockhash 1`
{
"bits": 486604799,
"mediantime": 1231469665,
"nextblockhash": "000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd",
"tx": [
"0e3e2357e806b6cdb1f70b54c3a3a17b6714ee1f0e68bebb44a74b1efd512098"
],
"previousblockhash": "000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f",
"version": 1,
"chainwork": "Not Implemented Yet",
"nonce": 2573394689,
"time": 1231469665,
"height": 1,
"hash": "00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048",
"versionHex": "Not Implemented Yet",
"merkleroot": "0e3e2357e806b6cdb1f70b54c3a3a17b6714ee1f0e68bebb44a74b1efd512098",
"difficulty": "Not Implemented Yet"
}
Or a transaction:
$ bitcoin-cli getrawtransaction 0e3e2357e806b6cdb1f70b54c3a3a17b6714ee1f0e68bebb44a74b1efd512098 01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff0704ffff 001d0104ffffffff0100f2052a0100000043410496b538e853519c726a2c91e61ec11600ae1390813a627c66fb 8be7947be63c52da7589379515d4e0a604f8141781e62294721166bf621e73a82cbf2342c858eeac00000000
* bitcoin-cli is not included
Emulated APIs as in bitcoind 0.16:
- estimatefee - estimatesmartfee - getbestblockhash - getblock [mode 0 and mode 1] - getblockchaininfo - getblockcount - getblockhash - getblockheader [ verbose \ non verbose ] - getrawtransaction [ non verbose only ] - gettxout
Work in progress:
- sendrawtransaction - getrawtransaction [ verbose ] - getmempoolinfo - getrawmempool
Requirements
An internet connection
less than 500mb of disk space :-)
Python >= 3.5.2
Limitations
May reduce privacy: if you have the entire blockchain on your own, you have to tell no one what you’re looking for.
Not fast as a full node: internet download is slower than a read from disk.
Doesn’t relay and partecipate to the network (this may change).
Very unstable!
Future development
Full Tor support
Mempool emulation
Zeromq emulation
Maintenance UI
Metadata
Release files for spruned 0.0.1a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| spruned-0.0.1a1.tar.gz | 52.8 kB | Without provenance | Details for spruned-0.0.1a1.tar.gz |
Release files / spruned-0.0.1a1.tar.gz
| Download URL | spruned-0.0.1a1.tar.gz |
|---|---|
| Size | 52.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d38f89b4909c4ef23796f40f7c6f18c8dd4d481a2899f183861ee70e0eaeca0
|
|
BLAKE2b-256 checksum How to use checksums |
54f57d1ab17358d99963001be219882b3bcf21a93c9b4f01bf7aced14fb566fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for spruned 0.0.1a1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.