https://github.com/demining/bitcoin-seeder-google-colab
bitcoin seeder Google Colab
https://github.com/demining/bitcoin-seeder-google-colab
bitcoin bitcoin-api bitcoin-core bitcoin-payment bitcoin-transaction bitcoin-wallet colab colab-notebook colab-notebooks colab-tutorial colaboratory google-colab google-colab-notebook google-colab-tutorial google-colaboratory google-colaboratory-notebooks
Last synced: about 1 month ago
JSON representation
bitcoin seeder Google Colab
- Host: GitHub
- URL: https://github.com/demining/bitcoin-seeder-google-colab
- Owner: demining
- Created: 2022-02-17T20:20:17.000Z (about 3 years ago)
- Default Branch: master
- Last Pushed: 2022-07-02T01:12:30.000Z (almost 3 years ago)
- Last Synced: 2025-03-26T07:36:10.027Z (about 2 months ago)
- Topics: bitcoin, bitcoin-api, bitcoin-core, bitcoin-payment, bitcoin-transaction, bitcoin-wallet, colab, colab-notebook, colab-notebooks, colab-tutorial, colaboratory, google-colab, google-colab-notebook, google-colab-tutorial, google-colaboratory, google-colaboratory-notebooks
- Language: C++
- Homepage:
- Size: 6.32 MB
- Stars: 1
- Watchers: 2
- Forks: 10
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
-------------------------
### Run bitcoin-seeder-Google-Colab
https://colab.research.google.com/drive/1OShIMVcFZ_khsUIBOIV1lzrqAGo1gfm_?usp=sharing
-------------------------
Bitcoin-seeder is a crawler for the Bitcoin network, which exposes a list
of reliable nodes via a built-in DNS server.
Features:
* regularly revisits known nodes to check their availability
* bans nodes after enough failures, or bad behaviour
* accepts nodes down to v0.3.19 to request new IP addresses from,
but only reports good post-v0.3.24 nodes.
* keeps statistics over (exponential) windows of 2 hours, 8 hours,
1 day and 1 week, to base decisions on.
* very low memory (a few tens of megabytes) and cpu requirements.
* crawlers run in parallel (by default 24 threads simultaneously).
REQUIREMENTS
------------
$ sudo apt-get install build-essential libboost-all-dev libssl-dev
USAGE
-----
Assuming you want to run a dns seed on dnsseed.example.com, you will
need an authorative NS record in example.com's domain record, pointing
to for example vps.example.com:
$ dig -t NS dnsseed.example.com
;; ANSWER SECTION
dnsseed.example.com. 86400 IN NS vps.example.com.
On the system vps.example.com, you can now run dnsseed:
./dnsseed -h dnsseed.example.com -n vps.example.com
If you want the DNS server to report SOA records, please provide an
e-mail address (with the @ part replaced by .) using -m.
COMPILING
---------
Compiling will require boost and ssl. On debian systems, these are provided
by `libboost-dev` and `libssl-dev` respectively.
$ make
This will produce the `dnsseed` binary.
TESTING
-------
It's sometimes useful to test `dnsseed` locally to ensure it's giving good
output (either as part of development or sanity checking). You can inspect
`dnsseed.dump` to inspect all nodes being tracked for crawling, or you can
issue DNS requests directly. Example:
$ dig @:: -p 15353 dnsseed.example.com
^ ^ ^
| | |__ Should match the host (-h) argument supplied to dnsseed
| |
| |_______ Port number (example uses the user space port; see below)
|
|_______________ Explicitly call the DNS server on localhost
RUNNING AS NON-ROOT
-------------------
Typically, you'll need root privileges to listen to port 53 (name service).
One solution is using an iptables rule (Linux only) to redirect it to
a non-privileged port:
$ iptables -t nat -A PREROUTING -p udp --dport 53 -j REDIRECT --to-port 15353
If properly configured, this will allow you to run dnsseed in userspace, using
the -p 15353 option.
Another solution is allowing a binary to bind to ports < 1024 with setcap (IPv6 access-safe)
$ setcap 'cap_net_bind_service=+ep' /path/to/dnsseed
----
| | Donation Address |
| --- | --- |
| ♥ __BTC__ | 1Lw2kh9WzCActXSGHxyypGLkqQZfxDpw8v |
| ♥ __ETH__ | 0xaBd66CF90898517573f19184b3297d651f7b90bf |