#WasabiWallet is going to remove its dependency on a central server. There will be two independent components: * Wallet API, the one that provides compact filters for wallet synchronization, and * WabiSabi API for coordinating coinjoins. Privacy warriors can run one or both. On the client side, In the settings page, users will be able to select the Wallet service provider and the Coinjoin service provider. Other services such as transaction fee rate provider and exchange rate providers are configurable too.

I will make a few enemies with this but I really hate all the 'Pura Vida' thing. I imagine that non-native Spanish speakers could find it cool, but imagime you visit an English-speaking country and every time you say hello, the response is 'Pure Life'. You say goodbye and the response is 'Pure Life'. Thank you is also responded with 'Pure Life'... Welcome.. 'Pure life'... ummm, how are you? 'Pure life'.... It feels like entering in an alternative universe where people want to say normal things like 'I am tired of this hot weather' but the matrix replaces all negative thoughts with 'Pura Vida'.

It would be great to have a filter to display only zapped notes/articles/whatever because zapped notes are generally speaking much higher quality than GMs notes. Does any #nostr client have something like that?

#WalletWasabi is implemented on top of an #ecash system. The coordinator mints credentials (tokens), which are then redeemed in the form of Coinjoin transaction outputs. This means that the tokens have a very short lifespan; however nothing forces us to do that and they can be used for many many things if we create long-live ones. Right now, I'm thinking we could use them to prevent DoS attacks against the coordinator by charging per request. That would be much better than the current mechanism, which bans coins depending on their size and how many times they were used to disrupt rounds, etc.

To have a chance of surviving in an increasingly hostile environment, #WasabiWallet must evolve. And to do that, it must leave behind comfort and embrace stress and uncertainty. It must focus on the development of the wallet under conditions of resource scarcity, far from the warmth of a sponsoring company's arms. The #WalletWasabi git repository has been transferred from the zkSNACKs organization to a new organization called WalletWasabi.

GitHub

GitHub - WalletWasabi/WalletWasabi: Open-source, non-custodial, privacy preserving Bitcoin wallet for Windows, Linux, and Mac.

Open-source, non-custodial, privacy preserving Bitcoin wallet for Windows, Linux, and Mac. - WalletWasabi/WalletWasabi

How we deploy the Wasabi coordinator: nix build github:zksnacks/walletwasabi/

I'm going to continue developing #Wasabi. I'm not talking about maintainance only but actual development. Of course that without coinjoins there won't be any significant income, if any, to pay my salary, or at least no in the middle/long term, however that sets a clear goal for the short term: downsize it all. It doesn't sound great, but it is. Wasabi was born as a light bitcoin wallet but with the time it became bigger and bigger. But now, zkSNACKs won't run the coinjoin coordinator anymore, all what is corporate-ish, such as Terms and Conditions, Web site, chainanalysis integration, affiliation integration, etc, etc, can finally be removed. All what made the code complex and that was great for marketing like "plebs don't pay", "friends don't pay" can finally be removed. Wasabi needs to be also downsized to be maintainable for a couple of guys and that means we can remove things that are still there for reasons that I don't agree with, like the "password finder" among many others. I started doing that a few years ago in what I called Wasabito (little Wasabi) but then I went back to contribute to Wasabi, anyway, here you can have a better idea of what I had, and still have, in mind:

GitHub

Commits · lontivero/Wasabito

FOSS, privacy focused Bitcoin wallet for the free people of this universe - Commits · lontivero/Wasabito

------------- These opinions are my own and I don't know whether zkSNACks decision making team agrees with me or not. Anyway, it is what I think should be done.

Even without coinjoins, Wasabi is the best wallet for privacy. It's not just because of Tor or because it doesn't share your information (scripts, addresses) with random servers on internet. The way it handles choosing coins is better than any other method I've seen, infinitely better than manual coin selection. It lets you control who knows about your transactions without accidentally revealing more than what is strictly necessary. It won't let you make mistakes that harm your privacy. By the way, manual coins selection is supported but is is hidden because it opens the door to make terrible mistakes, but you can use it if you want. The privacy alerts tell you how private your transaction will be and how to make it even better. It suggests ways to remove change when you can and does all sorts of amazing things. Payjoins are supported too even before bip78 were a proposal. #wasabiwallet

If after arresting a writer all his books are ordered to be removed from the shelves of bookstores, then he has not been arrested for something he has done but for what he has said. Why are github repositories being removed?

Sadly, now all those xpubs have leaked. #samouraiwallet

I'm sure that I am missing something here but IMO the concept of replaceable events in #nostr is at least unnecessary. The same applies for event deletion. These are detrimental to the integrity of the web of references.

GitHub

Nostra/Nostra.Client at master · lontivero/Nostra

A F# library for Nostr. Contribute to lontivero/Nostra development by creating an account on GitHub.

is a #nostr cli tool written in #fsharp strongly inspired by nostr-commander-rs. It is still WIP but available anyway.

Cashabi - nostr-native eCash system based on WabiSabi Keyed-Verification Anonymous Credentials. Repo:

GitHub

GitHub - lontivero/Cashabi: An experimental eChash system based on WabiSabi and Nostr

An experimental eChash system based on WabiSabi and Nostr - lontivero/Cashabi

Why?:

Cashabi

Nip44 Encrypted Payloads are supported by Nostra

GitHub

Nip 44 (Encrypted payloads) by lontivero · Pull Request #17 · lontivero/Nostra

#[0] https://photos.app.goo.gl/ojdmPV2zVvxyheAK6

I have a new pet project: Berlino, a simple #bitcoin wallet in #fsharp.

GitHub

GitHub - lontivero/Berlino: The simplest bitcoin wallet

The simplest bitcoin wallet . Contribute to lontivero/Berlino development by creating an account on GitHub.

My keyboard is so hard, flashy and noisy that I don't feel comfortable using it in a table full gays with Apple products. It is like eating pork in a vegans party.

I've just finished the very first version of NostraRelay a simple nostr relay written in F#.

GitHub

Nostra/Nostra.Relay at master · lontivero/Nostra

A F# library for Nostr. Contribute to lontivero/Nostra development by creating an account on GitHub.

First instance running here: http://gkzvzh23a3iffm6jbihhcvktjlm2gppld2ww6qc54ixwsdfobwavpgyd.onion

My article about npub1duedmhed2nevtejwz4c2hjuu0gz7spqm4s8wnaprta55ln9k3dwssvgp4 and npub1h72rkut9ljnpdfyrcmw8q9jx52tgn2m8zyg0ehd6z236tz2vmg2sr5k5rt idea to improve the nostr encrypted direct messages' privacy:

Private Nostr direct messages proposal

Your Extended Public Master Key is not supposed to be public, you should keep it secret. Don't let the word Public fools you.