From: Davidson Souza <davidson.lucas.souza@outlook•com>
To: Bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Announcing Libforesta
Date: Mon, 31 Jul 2023 17:47:26 +0000 [thread overview]
Message-ID: <IA1P223MB04501EFD534B3A53708740E1CA05A@IA1P223MB0450.NAMP223.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1: Type: text/plain, Size: 2056 bytes --]
Hi, list. My name is Davidson, and I’m thrilled to share `libfloresta` with the Bitcoin devs mailing list!
This is a derivate of a project I’ve been developing for a few months, called `Floresta` (Portuguese for forest). An Utreexo powered, Fully-Validating Bitcoin Full node with integrated watch-only wallet and Electrum Server, meant to be a compact, simple, and ready to use full node for end users.
After some feedbacks and thoughts, I’ve decided to turn it into a series of reusable libs that can be used in other applications in a straightforward way. The main goal here is low-power devices, like SBC and smartphones, but can be used in any environment. To achieve that, I’m writing the main logic in Rust and will generate bindings to the original code and compiling to WASM, allowing it to run virtually anywhere.
The project is in an early stage, but I’m using it on signet for a while now with no problems. Mainnet support is almost ready, but we need to solve some performance issues with bridge nodes and set some up, so you can have utreexo peers.
The project is available on [my GitHub](https://github.com/Davidson-Souza/Floresta) and I wrote an initial [blogpost](https://blog.dlsouza.lol/2023/07/07/libfloresta.html) explaining how to use it (in Rust). I’ll write more as the project matures, and I get it running on other platforms. Any feedback is welcome!
## Consensus
I know that alternative implementations is a spicy subject in Bitcoin land, but this project **does not** reimplement the Bitcoin Consensus machine from scratch. I’m using `libbitcoinconsenus` and plan to use the full `libbitcoinkernel` in the future. While this doesn’t guarantee consistency, it minimizes misimplementations leading to splits.
I’m also making an extra effort into cross-test against Bitcoin Core to find any inconsistencies before it causes any trouble.
## Acknowledges
A special thanks to [Vinteum](https://vinteum.org/) for supporting my work with utreexo and Floresta.
Best regards,
Davidson Souza.
[-- Attachment #2: Type: text/html, Size: 6639 bytes --]
next reply other threads:[~2023-07-31 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 17:47 Davidson Souza [this message]
2023-08-01 8:02 ` Bastiaan van den Berg
2023-08-02 21:32 ` Davidson Souza
2023-08-03 14:03 ` leohaf
2023-08-03 20:34 ` Davidson Souza
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=IA1P223MB04501EFD534B3A53708740E1CA05A@IA1P223MB0450.NAMP223.PROD.OUTLOOK.COM \
--to=davidson.lucas.souza@outlook$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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