Topic: [ANN] pynode: Simple bitcoin P2P node (Read 7439 times)
Is pynode still being updated? Or is there a follow up?
Nice. This is a fun project to play around with.
Merged "addnodes" support, so that additional nodes may be added via configuration file.
This received several bug fixes, by way of its use of python-bitcoinlib.
Thanks for the quick reply. As soon as I figure stuff out I shall contribute anything useful I do back.
Hello I am a bit new to programming but I would love to experiment around with pynode and python-bitcoinlib are there any guides or source code examples available or would I need to figure that stuff out myself? (I promise not to store anyone's life savings using it until I know the node and libs inside and out inside and out)
pynode and assorted utilities dbck.py and mkbootstrap.py are essentially source code examples for python-bitcoinlib. Unfortunately that's it.
Contributed examples are welcome in both projects, however.
Hello I am a bit new to programming but I would love to experiment around with pynode and python-bitcoinlib are there any guides or source code examples available or would I need to figure that stuff out myself? (I promise not to store anyone's life savings using it until I know the node and libs inside and out inside and out)
Library forked, and moved to a new home and forum thread:
https://github.com/jgarzik/python-bitcoinlib
Pull requests and donations welcome, as always.
https://github.com/jgarzik/python-bitcoinlib
Pull requests and donations welcome, as always.
pynode is very much alive and well. It is becoming popular enough that we can branch off the internal "bitcoin" sub-directory into a proper python library, python-bitcoinlib.
Stay tuned for details.
Stay tuned for details.
The on-disk block file format was just updated to match the network's "block" message format.
This is an incompatible change. You will need to delete, and re-download, your block databases.
Thanks (again) to socrates1024, pynode has switched to using the leveldb database, plus a flat file format for raw blockchain data.
This database upgrade is wholly incompatible with the previous GDBM-based database.
When signature checking is disabled, the entire blockchain may be downloaded in 34 minutes.
When signature checking is enabled, the blockchain download process takes many hours (6-12), due to slowness of python.
This database upgrade is wholly incompatible with the previous GDBM-based database.
When signature checking is disabled, the entire blockchain may be downloaded in 34 minutes.
When signature checking is enabled, the blockchain download process takes many hours (6-12), due to slowness of python.
Wondering if an Electrum client might be able to modified to talk to a pynode ... or vice versa?
What does Electrum use to talk to bitcoind? pynode provides a JSON-RPC HTTP server interface, just like bitcoind...
It uses the Stratum protocol ... but I don't have detailed knowledge of that, yet.
there are 2 electrum applications: the electrum client and the electrum server. The electrum server talks to bitcoind using the JSON-RPC interface but stores it's own blockchain. The electrum client talks to the electrum server using the stratum protocol.
Wondering if an Electrum client might be able to modified to talk to a pynode ... or vice versa?
What does Electrum use to talk to bitcoind? pynode provides a JSON-RPC HTTP server interface, just like bitcoind...
It uses the Stratum protocol ... but I don't have detailed knowledge of that, yet.
Very nice tool. Am I correct that this could be the basis of a tool to monitor large numbers of addresses for activity?
Sure. It could monitor whatever metrics you need, on the bitcoin network.
Wondering if an Electrum client might be able to modified to talk to a pynode ... or vice versa?
What does Electrum use to talk to bitcoind? pynode provides a JSON-RPC HTTP server interface, just like bitcoind...
preserved
Very nice tool. Am I correct that this could be the basis of a tool to monitor large numbers of addresses for activity?
Not sure how this one slipped under my radar ...
Wondering if an Electrum client might be able to modified to talk to a pynode ... or vice versa?
Wondering if an Electrum client might be able to modified to talk to a pynode ... or vice versa?
Thanks to socrates1024, pynode got a much needed upgrade from python's asyncore to the more modern gevent.
This opens the door to easy multi-peer operation, so expect full node status very soon.
In addition to the fully validating node and python-bitcoin module, pynode also maintains a branch that contains a non-validating node calling a "mini-node", naturally found in the "mini-node" branch of pynode.git:
https://github.com/jgarzik/pynode/tree/mini-node
This is essentially ArtForz' half-a-node, with the minimum needed to work on mainnet.
Forks have already started appearing. blkmond inside pushpoold existed for a long time. And bitcoin network sniffer fork also just appeared.
https://github.com/jgarzik/pynode/tree/mini-node
This is essentially ArtForz' half-a-node, with the minimum needed to work on mainnet.
Forks have already started appearing. blkmond inside pushpoold existed for a long time. And bitcoin network sniffer fork also just appeared.
Thanks jgarzik for pointing this out, I haven't seen this before, so I went and create my own...
Jump to: