fedimint VS sled

Maybe Fediment could be a promising way to store your Bitcoin. I've been keeping an eye on how this is progressing.

You might be interested in what is going on with Fedimint

Something like planetary fedimints or similar https://fedimint.org/

I hate to say it, but I believe most people aren't responsible. I think new options to on-board people which bring more comfort will be needed for mass adoption. Maybe a community custody platform such as Fediment or whatever the folks over at Ego Death Capital are up to that seems to have Jeff Booth and others just ecstatic. However I fear massive on-boarding comes with a lot of people still trusting an investment firm.

You might find https://fedimint.org/ interesting if you're not familiar - i could see bitcoin custody becoming a community centric thing but time will tell :D

when i start the scripts this error keeps popping up . I am running the scripts referring to this github repo https://github.com/fedimint/fedimint/blob/master/docs/dev-running.md

Fedminit: https://fedimint.org

In Cashu, a mint is a single custodian, while Fedimint is designed around a multiple federated mints in a multisig. Both issue e-tokens signed with blind signatures. Both of them also integrate with the Lightning network, so users of the minted cash can make use of the rest of Bitcoin ecosystem for payments.

The Bitcoin base chain can handle about 7 transactions per second, lighting theoretical upper limit is up to 1,000,000 transactions per second. You can use lighting without managing a node yourself. There are even projects[0] in development that allows for community custody, so it stays trustless even when using a custodian.

0: https://fedimint.org/

a few times, seems interesting. The author's also built a lot of other cool concurrency primitives for Rust as well.

[0] https://github.com/spacejam/sled

- Dropbox [3] uses a similar approach but they talk about it a bit more abstractly.

Sans-IO is more documented in Python [4], but str0m [5] and quinn-proto [6] are the best examples in Rust I’m aware of. Note that sans-IO is orthogonal to deterministic test frameworks, but it composes well with them.

With the disclaimer that my opinions are mine and mine alone, and don’t reflect the company I work at —— I do work at a rust shop that has utilized these techniques on some projects.

TigerBeetle is an amazing example and I’ve looked at it before! They are really the best example of this approach outside of FoundationDB I think.

[0]: https://risingwave.com/blog/deterministic-simulation-a-new-e...

[1]: https://risingwave.com/blog/applying-deterministic-simulatio...

[2]: https://dropbox.tech/infrastructure/-testing-our-new-sync-en...

[3]: https://github.com/spacejam/sled

[4]: https://fractalideas.com/blog/sans-io-when-rubber-meets-road...

[5]: https://github.com/algesten/str0m

[6]: https://docs.rs/quinn-proto/0.10.6/quinn_proto/struct.Connec...

Sled uses bw-tree actually https://github.com/spacejam/sled/wiki/sled-architectural-outlook

There is a valid argument to be made for threads over async in a large percentage of use cases where async is considered the default. If this is what you are referring to however, I don't think they ever referred to async as completely useless: https://github.com/spacejam/sled/issues/1123.

Have you looked into other pure-Rust databases as well, such as sled or GlueSQL which has an SQL interface on top of sled? I wonder how those would compare to Persy.

I'm not sure what you need. Are these of any use? https://github.com/meilisearch/heed https://github.com/spacejam/sled

There is also Sled but as I understand it that is being reworked to use the author's new DB core Marble

There are some databases like sled/FlashDB designed to be embedded to other applications even bare metal microcontrollers. But I do doubt the potential bussiness value of a pure embedded database.

https://github.com/spacejam/sled

To add transaction support, you probably need a good understanding of how the memtable works in Log Structured Merge trees: