Just published a new blog post with @thunderB on how to use the @bitcoindevkit to create and spend from a descriptor based #Bitcoin wallet using two different spending policies. Check it out! https://bitcoindevkit.org/blog/2021/02/spending-policy-demo/
BDK v0.4.0 has been published! 🎉
It comes with a new API to build transactions, upgraded dependencies and more!
See @afilini's blog post for details
@rcasatta just published a super interesting article "Fee estimation for light-clients", I'm really looking forward to see where he goes with it! #Bitcoin #MachineLearning
i'm not too familiar with those stuff, but i read the tor manpage and it had a few interesting options to limit bandwidth burts to prevent dos attacks.
plus, there's a way to kill circuits that spams too much, and considering that building a circuit is fairly expensive, this would limit the capacity of an attacker to take down an hidden service
@btcede yeah, but i guess the complexity can be reduced quite a bit if there's a trusted coordinator.
the goal here is not really to have an instance with no admins, more like to make a single instance more resistant to censorship from ISPs and cloud providers
@rusticbison i'm not a huge fan of ipfs myself because it doesn't really replicate data unless many people download a specific file. i guess it would work, but I'd try with something else first if possible
really what I'm trying to achieve is a way to distribute people who don't run their own instance across multiple smaller instances run by volunteers, making sure that none of them grows to the point where it can't be easily hosted "at home" anymore.
even better if those smaller instances can "look like one" (for the network effect), plus the benefits from replicated data
@livestradamus yeah i guess people ideally should try to host their own instance if they can and/or care about privacy.
thinking about it, i guess what i'd like to achieve can be summarized to "a way to distribute people that are not running an instance to a set of small instances".
even better if this "set of small instances" is actually one big instance distributed on multiple devices.
@hanakookie i still think it's very important to point out potential attack vectors and try to, at least, theorize better alternatives.
i don't want to replace and/or compete with this instance, i'm just trying to think about how we could do better in the future if censorship from isps or cloud providers gets worse
@Seccour that could help for some stuff, but it would mainly distribute just the http part, not all the other components of a mastodon instance (storage, background processing, etc)
still very interesting, i'll take it into account as well
@jakub that's awesome, but it still doesn't solve the problem that hosting a large instance at home might not be that easy. i was thinking about *somehow* splitting up the instance mainly for that reason, to stop relying on cloud providers
@ikmertz it looks like tor has some nice dos protections built in, especially for v3 hidden services. ideally i'd try to use those instead of relying on external providers
@hanakookie it's not political in any way. i'm just saying that hosting a large instance at home is not practical, while instead if you manage to split it up it can become feasible and increase the censorship resistance quite a lot
if the traffic is sufficiently spread around, then it could potentially become feasible to host the entire instance outside of the cloud, avoiding any kind of "deplatforming"
Bitcoin Maston Instance