Floresta icon indicating copy to clipboard operation
Floresta copied to clipboard

A fully-validating Bitcoin node powered by Utreexo, with an integrated Electrum Server

Results 29 Floresta issues
Sort by recently updated
recently updated
newest added

We currently use multiple error handling crates like `anyhow`, `thiserror`, and also custom macros. It'd be good to standardize this and pick one option.

good first issue
chore
code quality

See https://github.com/Davidson-Souza/Floresta/issues/86 Since floresta has a variety of strategies to handle errors, the chosen for this PR was to delegate all LibFloresta errors to a separate module, so it can...

We're expecting testnet4 to launch in the coming months and be a part of the next Bitcoin Core release. PR is here: https://github.com/bitcoin/bitcoin/pull/29775

enhancement

`closes` #86 This PR aims to standardize the error handling across all the crates mentioned in the comment https://github.com/Davidson-Souza/Floresta/issues/86#issuecomment-1822268886 (and more, if found). - [ ] BlockchainError - [ ]...

Fixes #86 This PR aims to solve the mentioned issue using `thiserror`. Any suggestion/ feedback is appreciated!

Getting things rolling on BIP324 just to start a discussion. It will take some significant time for signet nodes to adopt this so it can actually be tested more thoroughly....

- Aims to resolve https://github.com/Davidson-Souza/Floresta/issues/106 - initialized ssl in electrum

# Summer of Bitcoin 2024 Floresta Proposal ### Description Since Floresta is heavily based on async features to work properly and at the moment is using async-std, moving to [Tokio](https://tokio.rs/)...

Some tests need to be executed outside the code, like the integration of `florestad` and `electrum` or unit tests for our `json-rpc`.

enhancement
code quality

`async-std` is not well maintained anymore, and `tokio` seems to be the de-facto choice for an async runtime in Rust: https://corrode.dev/blog/async/

enhancement