Bitcoin Development Mailinglist
 help / color / mirror / Atom feed
From: Antoine Riard <antoine.riard@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Cc: btc@ariard.me
Subject: [bitcoindev] New bitcoin backbone code release: addr / tx relay mngt + multiproces support layout
Date: Tue, 7 Apr 2026 04:13:12 +0100	[thread overview]
Message-ID: <CALZpt+GMFjL5on=2pFfOLJ4neJHgXmHv+g1iQ-SRnRNuB1y+Kg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]

Hello devs,

Shared new code for bitcoin backbone, with a lot of new stuff at the tx and
addr management level. The most notable change has been to start to isolate
all the interfaces code in its own daemons, and start the groundwork to
re-implement the multiprocess interface in bitcoin backbone. That way in the
future being able to have the bitcoin-wallet calling the code, the
bitcoin-gui
or any future application that likes the interface [0]. It's not for nothing
that *NIX has the POSIX which lets you write a shell (which is a not trivial
piece of software...) and lets you run it everywhere on all *NIX.

There is also a dedicated mailing list on framagroupes.org, for the ones who
are more interested to follow updates (
https://framagroupes.org/sympa/info/bitcoin-backbone-dev).
This also avoid me to have to spam the mailing list [0] with each update of
the project, and only keep it to share back what is interesting. Next
updates
are going to be focused on pouring more love on the test framework. I know,
I know, so far testing has been only manual.

Do the work and keep building.

Cheers,
Antoine
OTS hash: 208bd991dc7a04b9ccb7023ae2a4de12c76484361c766ff3986cc107eecb5cf9

[0] See this old gist on some ways to improve perfs for wallet in
bitcoind's thanks
to bitcoind: https://gist.github.com/ariard/89f9bcc3a7ab9576fc6d15d251032cfa

[1] Better to be careful in this ecosystem with spam. No one expects the
Spanish
inquisition but you never know...

-- 
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%2BGMFjL5on%3D2pFfOLJ4neJHgXmHv%2Bg1iQ-SRnRNuB1y%2BKg%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 2447 bytes --]

                 reply	other threads:[~2026-04-07  8:52 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+GMFjL5on=2pFfOLJ4neJHgXmHv+g1iQ-SRnRNuB1y+Kg@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