pull down to refresh
they end up being a static label attached to the maker. Be it size based or coin age based.
please review my original ramble, again...
I'm completely opposed to fidelity bonds. I rarely pull out such scathing criticism, although I consider them worse than spinning rims on the training wheels of a bicycle at the Tour de France.
coin-age labelling is only used for prioritizing which strands of the UTXO history are selected for the next weaving of the resultant graph. there is no attempt for takers to counterspy makers, because that is the naive futility which opens the door to all this epicyclic overcomplicating of what could have been an incredibly simple protocol.
So it goes!
Do you want to write a bit more about it now? maybe a standalone SN post. For future references also :-)
Why were FBs a mistake? What problem are they trying to solve? What do they do well? What do they do badly? What are the alternatives? Which one is the better one?
thank you for the ping+reminder
unfortunately I'm currently struggling through infrastructure purgatory, and the kind of questions you suggested are the welcome distraction, rather than my main focus, these days.
if you want a realistic projection... it'll take at least a week, and if I force myself to publish so quickly, then my rant will mostly be about general ideas, rather than thoroughly grounded in research about each of the systems that have been deployed in the past decade.
Let me know if I can help you with your node setup somehow.
do you know of any guide for minimal-footprint node setup?
I'm less worried about long compilation times; I'm simply literally unable to compile Alby Hub on my current "daily driver", although I suspect I could run a binary...
I have other options, they just all take a while. My least preferred options are buying new hardware, or just renting a server that I don't physically administer.
Thanks for the reference. I think you will like nothingmuch's fungi protocol. TLDR a multiparty coinjoin protocol without coordinator, where Sybil protection comes from a provenance term and users have their own cost function for choosing what inputs they mix with and how to arrange their outputs. Here are some links: https://fungi-protocol.github.io/docs/ and https://gist.github.com/nothingmuch/f5b9a559958c6116606d9da0d4d884f2
Anyway, that being said, I think the biggest issue FBs have is about privacy, since they end up being a static label attached to the maker. Be it size based or coin age based. So the renting market is a way to address this, independent on the kind of FB actually.
The good part of the size based ones is that the sacrifice is pretty clear/measurable. I personally wouldn't oppose to trying the coin age based ones as well. But then it's not that FBs are a mistake (that was what I understood when reading your comment). It would be more of FBs being a necessary but annoying thing and choosing over different tradeoffs.
The provenance alternative from nothingmuch is very promising. Let's see how it goes "in real life".