Avatar
Tim Bouma
06b7819d7f1c7f5472118266ed7bca8785dceae09e36ea3a4af665c6d1d8327c
| Independent Self | Pug Lover | Published Author | #SovEng Alum | #Cashu OG | #OpenSats Grantee x 2| #Nosfabrica Prize Winner

The mechanical engineer in me loves these types of reductive ratios: Au/sat nostr:note13vpf9nq762g8uxgag6ulpdg94kuqs5ju2drec26esj6cc0nx8z7s69qrl8

I think the only way to guarantee a “personhood credential” is to demand a urine sample before issuance.

Kidding aside, I read these papers, and despite their good intentions, I see red flags everywhere. The next step is to convince a policymaker this is the way to go, and boom, you’ll need a license to access the internet.

Bottom line, I am trying to figure out what they are missing, and what we are seeing differently, if that is indeed the case.

It’s a subtle shift in understanding, but once you realize this, you can’t go back. nostr:note1qr20jk0wnh6ulmzy83rcz3r2mmzcdreuefkc38dlzu7afkzxkhcqzaq27q

The latest academic paper on “personhood credentials” - a purported solution to solve the problem of deep fakes, AI bots, authenticity, etc., on the internet.

My questions are: who gets to issue the personhood credentials? Why can you only have one? Who enforces this.

My take is that there is still not an appreciation of the root of the problem. Enabling self-generated npubs and signed events to begin with. Without that starting point, an eventual authoritarian intervention is unavoidable.

Curious if anyone else has takes on this paper?

https://arxiv.org/pdf/2408.07892

KFC is preferable to KYC+NFC

Be your own backup plan. Use #nostr

Yup. Still in development, but I issue the command 'safebox new' and a wallet can exist on a relay of choosing.

Yeah, it's better but it's the underlying problem. They are too similar models that go to centralization.

npub-to-relay(s) goes one step better to solve that.

A 'wallet' is not an 'app' to be regulated, it's an abstract concept.

Psst! Keep this a secret while the EU regulates to death every app that looks like a wallet.

Let's just keep theses 'wallets' in the #nostr network and we'll win in the end.

#safeboxisnotawallet

First, it's intended to be a replacement component for custodial wallets in my lightning payment service. It will eliminate the requirement for me to store any personal data (including tokens) - only the #nsec of the component. The data gets stored on (redundant) relays. If my database gets attacker, the attacker would have to go through each #nsec. The user will have access to that #nsec - they can sweep out the wallet to a new one, or I can do the sweep on their behalf.

Second, the functionality - it acts as a cashu wallet, with interfaces to lightning and lightning addresses. The cli I am building for testing has commands to send from the wallet to lightning.

In the end, it's just experimenting with the new architectural patterns that are only possible on #nostr

Nice. Have you ever heard of Wilfred Campbell? I consider him to be the poet laureate of Lake Huron.

Coming soon!

#nostr Safebox

A Python implementation of #nsac (or nutsack) a concept invented by nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft (NIP-60+61).

A #nsac is a ‘wallet’ that exists as encrypted events across relays, only accessible by the corresponding #nsec. It uses redundant providers, relays,mints and blossom servers in a way that only the #nsac holder can access the info.

I would love to have this mentioned at #nostriga unconference nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg

Nostr Safebox. Early days, but it works. Key idea is that the ‘wallet’ exists is in the network as a bunch of events. Similar to the idea of a ‘utxo’ which is really just a sum of transaction outputs.

https://github.com/trbouma/safebox