From: Antoine Riard <antoine.riard@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Cc: btc@ariard.me
Subject: [bitcoindev] new backbone code release with bitcoind python test framework integration
Date: Fri, 24 Jul 2026 02:45:00 +0100 [thread overview]
Message-ID: <CALZpt+Ec=cmFmEesnQ4DKvux-aK80ZiMw30+N8ZGyxDU2tWvxg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2405 bytes --]
Hi devs,
For the curious, I released a new version of backbone code, the
6th public release, mostly focus on starting the heavy work of
quality assurance and testing. After testing a lot of tweaks,
succeeded to overhaul and adapt bitcoind's python test functional
test despite the difference in runtime architecture with the multi
daemon native process. Branch is available on bitcoinbackbone.org
I have to change a bit the backbone-cli to be able to drive the main
backbone daemon from test and I'm still testing few different approach
on how to dispatch cli commands internally for the different daemons
(blocks, addr, etc), though the overall init, send cmds from the python
framework and shutdown, works smoothlier than I did expect. So the huge
benefit is to be able to reuse directly bitcoinds really furnished python
testing framework and the python test vectors for the networking p2p
coverage,
even if there is a lot of work ahead to fine-tune them for backbone.
Sharing it if the approach it can be useful for other folks leverating
the libbitcoinkernel and building cool stuff around it. One can build
backbone and test a demo integration with
`./functional-test/p2p_addrelay_connection.py`
(have only tested on a linux box so far).
I'm also cleaning up and improving the backbone-servers, working on some
experiments integrating some of the cryptographic protocols stuff and
experiment from my old civkit project [0]. The ideas were interesting
to serve as a foundational structure for growing a real p2p bitcoin economy.
Hope to have some cool experiments on that ready soon, and it let me
"dog food" my own backbone interfaces, if they are ergonomic enough.
One year in. Keep building. Keep a growth mindset.
Cheers,
Antoine
OTS hash: 26c6a523bc54799e06c17a6973252647516ade539fab933623eea4b3f21f78a7
[0] "Civ Kit: A Peer-To-Peer Electronic Market System":
https://gnusha.org/pi/bitcoindev/CALZpt+G_wqAqXkenDwdojT4EhpweYwe2DiCYZRFfCbMLL8DbVA@mail.gmail.com/
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CALZpt%2BEc%3DcmFmEesnQ4DKvux-aK80ZiMw30%2BN8ZGyxDU2tWvxg%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 15523 bytes --]
reply other threads:[~2026-07-24 1:55 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='CALZpt+Ec=cmFmEesnQ4DKvux-aK80ZiMw30+N8ZGyxDU2tWvxg@mail.gmail.com' \
--to=antoine.riard@gmail.com \
--cc=bitcoindev@googlegroups.com \
--cc=btc@ariard.me \
/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