From: Jeff Garzik <jgarzik@exmulti.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] [ANN] pynode: Simple bitcoin P2P node
Date: Sun, 22 Jul 2012 15:16:59 -0400 [thread overview]
Message-ID: <CA+8xBpcxHUqQCjwnS5C0Or--mjo8jaNrbR5rjT=BBAT2r9Vs4g@mail.gmail.com> (raw)
Github URL: https://github.com/jgarzik/pynode
pynode is a simple bitcoin P2P client, based on ArtForz' half-a-node,
which maintains a blockchain database and TX memory pool.
It is intended to be a useful base for another projects, such as
network monitoring nodes.
At present, it is mainly for developers and not end users. Here is
what pynode does NOT do:
* RPC
* key management (wallet)
* script verification
* chain re-org
Here are the limited things that pynode can do at present:
* Outgoing TCP connection to a single remote P2P node
* Initial blockchain download
* Maintain a transaction memory pool, with TX's removed as they are
confirmed in blocks
* Maintain an indexed blockchain database
Over time it will become more capable, but this is an alpha quality
release for developers at present.
Contributions welcome! It is intended to become a full, wallet-less
node over time (though if somebody wanted to contribute a wallet
module, that is OK too)
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
reply other threads:[~2012-07-22 19:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+8xBpcxHUqQCjwnS5C0Or--mjo8jaNrbR5rjT=BBAT2r9Vs4g@mail.gmail.com' \
--to=jgarzik@exmulti.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox