<unnamed>

Public Key

npub1gy87t05c3k0eaxk04zh4m46enkezqmxjdngr0373h0qlsnjxwseszvsa6f

Profile Code

nprofile1qqsyzrl9h6vgm8u7nt863t6a6avemv3qdnfxe5phclgmhs0cfer8gvcprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv5gmnzt

Publishing to

relay.snort.social

Last Notes

2023-08-01 23:16:05 UTC

- reply

📅 Original date posted:2023-08-01
🗒️ Summary of this message: Libfloresta is a compact, low-power Bitcoin full node for end users, written in Rust and compatible with low-power devices. It uses libbitcoinconsensus for consensus and is available on GitHub.
📝 Original message:
Am i correct in the following interpretations?
- the utreexo bridge peers are the only real bitcoin nodes
- you cant use -only- libfloresta to be a node , you cant mine with it, you
cant do normal tx with it
- you are targetting webbrowsers (???? , i'm really confused about the why
of this)
On Mon, Jul 31, 2023 at 9:11 PM Davidson Souza via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> 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.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230801/d3e4d737/attachment-0001.html>

2023-06-07 15:42:20 UTC

- reply

📅 Original date posted:2015-07-15
📝 Original message:On Wed, Jul 15, 2015 at 5:49 PM, Me via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
>
> > Blockcypher's "confidence factor" model(1)
> > under the hood - yet another one of those sybil attacking network
> > monitoring things
>
>
> Peter, I noticed on your twitter you have a lot of bad things to say about
> Blockcypher and their business model (which I might not full agree, but
> totally respect), can you share any evidence they perform any form of Sybil
> attack on the network, please.
? He says it -monitors- for such a attack, usually monitoring does not
include causing it ;)
--
buZz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150715/2a85d431/attachment.html>