Avatar
Leo Wandersleb
46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d
https://walletscrutiny.com https://nostr.info Working on Bitcoin, Nostr and being a good dad.
Replying to Avatar Leo Wandersleb

I want to **run a relay** financed by a tiny percentage of its users and strongly believe

in the following being a way to align incentives for all clients and relay operators:

For this bounty, the minimum requirement for the resulting relay is:

* relay is as efficient or better than [strfry](https://github.com/hoytech/strfry) at supported nips, synchronization between instances and handling concurrent connections

* nip42 support

* all read and write operations are metered per connected pubkey: milliseconds spent on queries, query count, events sent, event kBs sent, etc. (If Alice pushes Bob's events, it gets tallied to her pubkey - the one authenticated via nip42)

* allow managing group of primary (TIER 0 or T0) users via API

* secondary users are those followed by T0 users etc.

* define limits depending on follows distance to primary users, using five tiers: 0 = primary users, 1 = follows, 2 = follows of follows, 3 = follows of follows of follows, inf = all the other pubkeys

* allow configuring hourly, daily and monthly limits per tier and metered aspect.

**This bounty was created with the goal of actually running a relay with this feature and will not be awarded for a proof of concept that is not a fully functional and performant relay. Strfry is "good enough". If you want to implement the proposed feature in a different relay, please reach out to discuss first.**

This bounty was offered in other places before:

* [github.com/hoytech/strfry](https://github.com/hoytech/strfry/issues/17)

* [bountsr.org](https://bountsr.org/relay-with-wot-based-limits/)

testing something ...

Curious but ... I can't find anything about the alleged law suite.

Fedimint sounds awesome:

https://www.youtube.com/watch?v=BtbUGFHZTW8

but ... are there any tools already or is it still only for developers?

Where can I custody my kids' pocket money so they can seamlessly use lightning without having to run their own nodes and without me knowing who of them sent to that Silk Road wallet?

If you use the same APK, they are free to update from either, so ... no big problem.

I think I would use beta testers on PlayStore though, too, so users have the right expectations and then you can coincide pushing to production with the F-Droid release.

That's not a bad thing though. So it would be behind by up to two weeks? That's a good reason to split into more branches, ultimately committing to a more stable release that gets new features only after some wild-west hot-plug testing.

I'm afraid that self-custody isn't even the solution as self-custody currently requires to control at least one UTXO and growing the UTXO set to 8 billion would be unfeasible in a short time frame.

I think we need some "Uncle Jim" approach, where it is easy for some to provide custody for others in a much more distributed way than 3 big wallets holding all the funds.

The best solution I could think of right now are chaumian mints with both the UTXO set and the minting requiring m-of-n signatures, combined with tools that allow users to join or form federations dynamically.

Until that is ready, joining your Uncle Jim's Single Sig BtcPayServer is better than using WoS for sure.

Congrats! Most people don't know what an achievement that is. It means at the very least you did not cut corners in the creation of your product as the standards to openness are quite high on F-Droid.

And now to get a routine of keeping it updated there, too. That should be the easier part.

I hear this sentiment a lot but you are a maker and probably an influencer and net-receiver of zaps. Most plebs will never have their own nodes and those will get hurt if WoS "gets hacked".

I worked for a self-custodial mobile wallet and we had users with more then $100k in our product and my estimate always was that the average was $100. For WoS it might be closer to $10 but with more than 100k installs on Android alone that's still at least a million USD.

For me it's not only about personal loss and blaming the other guy who held all his sats in WoS. For me it's about us collectively creating these incentives for crooks to provide these honey pots that plebs fall into.

If your business plan is to take off with all the users' funds, you have much more resources to create a great product than if your plan is to provide an honest and forever free product.

Psychopaths exist and I've seen plenty in Bitcoin, too.

At the risk of getting blocked by all the zap-o-maniacs ...

LN is great but to celebrate zaps as circular economy that just works is pathetic. 99% are custodial with some 3 providers. 100% of zaps are easy to fake as there is no proof of payment between actually distinct entities in the zap and the "recipient" can emit receipts absent payment anyway. Still most prefer to celebrate WoS instead of taking self-custody. And when WoS "gets hacked", they will keep saying it was fun while it lasted.

It **is** fun and we might get better but at its current level it's a toy and not the pinnacle of the decentralized economy allowing us to dunk on shitcoiners with their respective pretend solutions.

And yeah, if you try to zap me, my LN node won't emit a zap event and some clients don't even give you the option to tip my lightning address. Zaps are not about "value for value" but about showing off the value you give aka "value for value for value". Maybe that's why I'm not tuning in to your Kumbaya praise of zaps, trying to harvest some for myself.

nip05 is an identifier and nothing more. It does not verify anything beyond the fact that the administrator of the domain was willing to lend you an ID.

The only nip-05 identities that I consider as verification right now are _@domain (you are the administrator of that domain) or when I check the nostr.json and I see it's only very few, hand picked keys. And I would not apply this heuristic if the domain was without any value.

That is not "verification" and to call it this is misleading.

Unless you have your very own domain that only you control, nip05 gives little to now assurance what so ever.

There might emerge some nip-05 services that do KYC but without that - without knowing well the nip-05 service, it means nothing. There is plenty of free such services out there that don't even require resolving a captcha.

Buenos Días Nostrlandia!

There **is** such a feature. At least on Snort you can "toggle preview".

Granted, that preview doesn't tell you how it would look on [other clients](https://nostrgram.co).

https://void.cat/d/MWE9C5f4LqKR6Q9wEQhy46.webp

So apparently some people are freaking out over #Bitcoin #Stamps, an attack on Bitcoin that somehow justifies not growing the chain size but the UTXO set which wouldn't be easy to prune but worse - would be kept in RAM, not only on disk.

In the past there were suggestions to take UTXO size into account for fee calculation - if your TX spends 20 UTXOs into two new UTXOs, your TX gets priority even without a fee but of course with good will alone, big miners don't forego the higher fee for themselves to reduce RAM demand for all. Classic tragedy of the commons.

As of now there is no sudden spike in UTXO size and I wonder why people are talking about this just now. Did attackers find a way to trick others into paying for this attack because art or something?

https://void.cat/d/NR9mRntfwDtQ49m6uixiqS.webp

If you do that as a file hoster and get some popular client to use it by default to get this style of links broadly used in nostr, pulling the plug on the original url would quickly drive other devs to add these few lines of code to their clients.

So that looks like bittorrent-first. I think in order to introduce this in nostr-land, we would have to do dns-first: Unaware clients just use "https....printer.gif?bittorrent=magnetLink" while aware clients treat the url as fallback.

Given Localbitcoins and probably Paxful, too, will retain all account information for five years after account deletion anyway, it would probably be a good idea to copy users' reputation over into nostr events to more easily bootstrap trust in a decentralized protocol.

Users could set their homepage to something containing their npub on these platforms and multiple non-colluding accounts could run a script to attest to these accounts having that reputation and being this npub on nostr.

https://void.cat/d/MDk7t4mauA863v19aCVWZK.webp