Braydon Fuller

Software Engineer • Bitcoin & Nostr • Economics • Security

"Do not give in to evil, but proceed ever more boldly against it." —Motto of Ludwig von Mises

Lightning self-custody with https://github.com/braydonf/satdress

Public Key

npub1r0ulywwu593kzjdu9uluxdq80t54n65kql9vl9z7lrutkgnachssk7zzyc

NIP-05 Address

_@braydon.com

NIP-57 Address

zap@lightning.braydon.com

Profile Code

nprofile1qqsph70j88w2zcmpfx7z707rxsrh462ea2tq0jk0j300379myf7utcgpzpmhxue69uhkummnw3ezuamfdejsz9thwden5te0v4jx2m3wdehhxarj9ekxzmny9exfq2

Publishing to

nostr.wine

eden.nostr.land

relay.braydon.com

Author Public Key

npub1r0ulywwu593kzjdu9uluxdq80t54n65kql9vl9z7lrutkgnachssk7zzyc

Show more details

Last Notes

2024-10-17 03:55:32

- reply

Perhaps with "transfer keys" that could be associated with a profile (and attested to by peers) and later used to send a multisig transfer event should that pubkey become revoked.

2024-10-15 22:42:53

- reply

This is awesome.

2024-10-14 23:32:10

- reply

Yeah, 69% are not very much to none at all.

2024-10-14 17:22:12

- reply

With multiple clients for different use cases (notes, git collaboration, video channels and podcasts), I do think it is more efficient for relays to do more of the work that a client might do, such as streaming and syncing all the events that one will need. A global view wouldn't be so much global as it is relative to a relay's configuration, perhaps another term could be used. Each client need not implement the full complexity of coordinating with thousands of different relays, when that can be done once with a private relay and many clients can benefit.

2024-10-13 19:12:12

- reply

Cool. I also added that regexp to Version String Extraction and $2 as the match group. Gives a version number instead of the hash.

2024-10-13 17:25:13

- reply

What App Source URL do you use?

2024-10-11 16:39:12

- reply

I've noticed that Gossip has made it an option the merge, pull down or push up the local version. None of that would be needed if each was its own event because it would continuously be merged without a conflict.

2024-10-11 01:01:44

- reply

I need to run strfry with a config option to increase the timeout for the router. This should be in the next release; however, I have code for it now here:
https://github.com/braydonf/strfry/tree/router-timeout
Some related issues:
https://github.com/hoytech/strfry/issues/45
https://github.com/hoytech/strfry/issues/127

2024-10-11 00:39:02

Okay, this is awesome. I have the "outbox model" working in #amethyst today.
It's using a topic relay that pulls down events for everyone that I follow.
It's using `strfry relay`, `strfry router` and `strfry sync` with negentropy. I have a set of tools to create the necessary config files.
It's very much a work-in-progress; however, I'm currently using it now for my relay and already I see notes coming in via it, so great to see.
The early code is here:
https://github.com/braydonf/strfry-tools
cc: @nprofile…vzaw

2024-10-10 21:24:52

- reply

I concur. I also accept sats instead of time.

2024-10-10 17:44:28

- reply

NaN?

2024-10-10 17:06:01

- reply

AOSP software distribution did many things well, dev signing APKs was a good move. Having an app with a dependency of another on the other hand, is something every GNU/Linux distro has done so much better. In my opinion, some of the Nostr functionality should be much closer to the OS, and a Nostr distribution of AOSP (like a fork of GrapheneOS) will be an inevitable solution.

2024-10-10 16:31:01

- reply

Indeed, just finished reading it, and recommend it. Will have to listen too sometime.

2024-10-08 20:36:23

- reply

The hamburger patty "hack" is funny, but works.

2024-10-08 18:37:08

- reply

Could be, could not be. Reminds me of monolithic vs microkernel architecture arguments of kernels. Today both are used as well as hybrids. The monolithic Linux kernel has its advantages. Space for all approaches.

2024-10-08 17:17:30

From "The Allegory of the Swamp" Appendix A of "A Lodging of Wayfaring Men":
"No, to get out of this, we will have to fly in defiance of our feelings, and think. The truth is that most people will do almost anything rather than this."

2024-10-08 16:49:15

Engineers working on what they think, or their customers think, is important while others disagree with them, who are not their customers or manager, is what makes Nostr great. Value is ordinal and not cardinal and determined at the margin. Carry on!

2024-10-07 15:39:28

- reply

Cool, are you using negentropy at all yet? Code for this available any place?

2024-10-07 14:34:30

Key revocation and rotation is a solvable problem and is ultimately about authentication, regardless if a key is ever compromised!
How do you know who is who? Do you remember their npub? Where do you save the name you have for their npub? Right now it is all just a list of pubkeys in a follow list (mostly).
#nevent1q…xsmw

2024-10-07 14:21:12

- reply

I disagree! Key revocation and migration is a solvable problem!
https://github.com/nostr-protocol/nips/pull/1452
https://github.com/nostr-protocol/nips/pull/1499

2024-10-07 13:53:48

- reply

Awesome! What type of course work, books and study guides are you using? The Mi Primer Bitcoin workbooks?

2024-10-06 16:33:06

- reply

I've been thinking about integrating with my homepage with a profile view similar to njump.me and npub.pro for this purpose (among others).

2024-10-05 19:07:24

- reply

Yeah, weight fluctuates, a huge percentage of body mass is water. When I first started carnivore +/-, I didn't weigh myself for the first 90 days or think about portion control, just ate until I was full, and stuck with it for that commited time period. About a month or two in there were some days I hardly felt hungry and ate about once a day, not trying for fasting or anything. First thing I noticed was my pants not fitting that well and older shirts fitting again. I found it felt freeing to not think about it.

2024-10-05 17:30:15

- reply

Yeah, not much more than could be found via `kind 3` (follow list) and `kind 10002` (relay meta), that are known anyways.
Private lists may help also in that regard.
And yup, VPN, Tor, reverse proxies can all help with IP address tracking for the private relay and clients.

2024-10-05 16:00:46

- reply

Not really, that relay could be yours and could take care of that censorship resistance for you by connecting to other relays owned by your contacts (two way syncing and streaming). Ultimately, you only need to connect to it (redundancy would also help still though).

2024-10-05 12:04:18

- reply

Yeah I agree, too early. Also, there's negentropy syncing and other optimizations / simplifications that can be done with relays.

2024-10-04 23:49:44

- reply

A few things, however, it solves a problem I have now in Amethyst, which is that many notes are only "seen" by one or two relays (and without connecting to many more relays listed via NIP-65 for contacts).
Once complete, Amethyst connects to that private relay (and a few others) and it will stream and sync from many hundreds to thousands of relays. Much more than just a few as it is currently.

2024-10-03 22:59:10

- reply

Another benefit of an "outbox model" is that it's asking only their relays about their notes (without auth) so still somewhat private.
Not entirely sure yet how to have a private relay fetch these without access to decrypt the list. Will have to think about this one, perhaps lists could be shared with other pubkeys.

2024-10-03 22:01:52

TIL that Gossip supports private lists and Amethyst supports viewing public lists (not private nor their creation).

2024-10-03 19:29:13

- reply

Yeah or send to a Nostr npub via DM (not NIP-04), email or PDF receipt to save (or similar).
Something that I've noticed some folks ( e.g. @nprofile…yfa4 ) will do for films purchased with sats, is to use a URL (Vimeo) and a password. So perhaps the encrypted URL can also include some additional meta data? And perhaps a clickable link and/or redirect!?
More integration with Nostr could also be interesting, a sort of receipts or paid stuff catalog kind. Could eventually integrate with Kodi, NewPipe, @nprofile…ntld devices for books and etc. And could also work with subscription services for relays, vpns and such.

2024-10-03 10:11:21

- reply

Worked w/ open wallet, cool.
One thing I'd suggest is that the URL that is unlocked could be more above "the fold" on mobile, as it's just on the edge and could be easy to not see it change after payment.

2024-10-03 03:55:08

- reply

That's awesome.

2024-10-03 03:54:50

- reply

Great to see :)

2024-10-03 03:39:09

- reply

What about kind 3 (follow/contact list), kind 10002 (relay list meta) and kind 0 (profile meta) or is that assumed?

2024-10-03 00:21:30

- reply

Interesting exploration.
Pay-per-kb could be another and expand to blossom.

2024-10-02 23:49:54

- reply

Okay, got my curiosity, how does it work with complete technical details, is there documentation?

2024-10-02 23:44:33

- reply

I've thought about this also. I don't think digital goods must always go immediately to available for everyone at zero cost. There is a gradient of scarcity even with digital goods. Yes, the next marginal unit is at near zero cost to produce, however that first non-identical unit is not at zero cost and is still scarce. Each person that makes a copy contributes to it becoming less and less scarce until there are hundreds of thousands of copies and it is so available that it's no longer an economic good. Skipping over that transition period, I think misses out on a market opportunity and for value comparisons to be made that can help guide the direction of digital goods and what customers value the most.

2024-10-01 23:13:36

- reply

I believe strfry uses lmdb, which is faster.
I use a strfry relay and want to stream and sync notes for follows/contacts so that clients do not need to support NIP-65 "outbox model" directly themselves.
For example, mobile clients like Amethyst can indirectly support NIP-65 through these relays. Such clients can also save bandwidth by using negentropy syncing with that relay as it will have almost everything already.
For an npub with 200 follows and an average of 4 relays listed for each, this could be 800+ connections to relays. It could be a lot from a mobile device and limited metered data.

2024-10-01 22:44:47

- reply

I've needed to increase the timeout in `strfry router` to connect to all the relays, otherwise it enters a retry cycle. This should have an update in the next release. Need to test this more and possibly make some other performance improvements.

2024-10-01 22:05:00

A right to free speech and censorship resistance are inextricably linked with private property.

2024-10-01 18:52:33

Now running Gossip with the number of follows that follow count on the profile image.
I think it could be more clear what the number means (I just learned about it from a nostr note). It could be displayed with more details on a user profile page (including who specifically).
Next better, user metadata attestations (with a duplicate of the metadata).

2024-10-01 18:31:27

- reply

Displaying this type of info, I think is a good move.

2024-09-30 23:21:19

Okay, I have an early working example of a strfry relay that will sync (with negentropy) and stream all notes for your contacts and network.
https://raw.githubusercontent.com/braydonf/strfry-tools/5ed4cbbb22df248edd4c65580d06dae370029935/graphics/strfry-tools.png
A configured pubkey (or more) can have their kind 3 (NIP-02) contact/follow lists and their contacts' kind 10002 (NIP-65) relay list metadata ("outbox model") retrieved for syncing and streaming events for them and their contacts through their relays.
The code is available at:
https://github.com/braydonf/strfry-tools
This is still quite early, and this is aimed currently at early testers and developers, I am waiting on a few things:
1. Configuration updates (in the next release) to `strfry router` to handle this quantity of streams.
2. More relays to support negentropy syncing, there are already several, but given a few more months this will improve a lot.
3. More clients to list NIP-65 relays (not full support).

2024-09-30 20:45:08

- reply

I've read all of these.
1. It is not needed to opentimestamp the revocation (migration) event.
2. It isn't even necessary to indicate what key is being migrated to with the revocation event.
Profile attesations (like PGP key signing) can tag both the new and old key, and this can help people follow their new key. The revocation event informs people the key can not be trusted and to seek alternatives (and for those attestation events).
3. There also isn't a need to whitelist keys. Confirmation of the profile can happen in any number of ways "out-of-band".

2024-09-30 16:48:41

It is possible, there just isn't a "global" agreed upon consensus — and that is fine. It is not as complicated as it has been made to sound.
PGP has key signing and revocation, that's pretty much all that is needed.
The use case is valid. If someone's PGP key is compromised, I've seen it happen, they need to revoke the key, create a new one and then have coworkers, friends and etc. sign the new one, done.
#nevent1q…39sk

2024-09-28 00:39:55

A few relays that are currently supporting negentropy syncing with the latest strfry 1.0.1 release:
wss://relay.snort.social
wss://strfry.iris.to
wss://relay.westernbtc.com
And there are several others.

2024-09-26 23:24:11

- reply

Was testing earlier today with strfry 1.0.1, it works.

2024-09-26 23:14:44

- reply

Yes, I think it is a protocol version mismatch. I have received the same error with strfry v1.0.1 and I don't think relay.damus.io has upgraded yet.
I've had success with relay.westernbtc.com and several others.

2024-09-26 20:36:34

- reply

This is an excellent comprehensive start, learned a few new things too.

2024-09-26 20:34:38

- reply

What is mentioned in "Section Seventeen: Private Payments"?

2024-09-26 20:32:17

- reply

Yeah, I think "your network" is better, also more recognizable. "Web of trust" is more technical and relates more to PGP key signing (and etc.) instead of trusting Certificate Authorities. I think it would be great to have the equivalent of that for Nostr npubs.

2024-09-26 20:20:46

I think it would be a great idea for a client to have an invite url that could bootstrap a network (no global) with discovery relays, suggested people to follow (and their relays) and a few prepaid (redeemable ecash) relays for storing their notes and a way to know when they join to auto follow them.
#nevent1q…dxfu

2024-09-26 18:21:50

- reply

I've run the sync command between different strfry versions and this does seem to be the notice for likely incompatible versions 0.9.7 to 1.0.1.
Are you using a timeout for relays that don't support negentropy yet? The connection and sync process seems to stay open indefinitely and the NOTICE messages range a lot to machine parse.

2024-09-26 17:37:16

Getting close to having my private strfry relay stream down and sync (with negentropy) all events for my contacts/follows listed on kind 3 (NIP-02) using their relays listed in kind 10002 (NIP-65) with the "outbox" model.

2024-09-25 03:11:06

- reply

Yup, was the case in Czechoslovakia before the Velvet Revolution, I believe.

2024-09-23 21:55:33

- reply

Okay cool, I am wondering if there are any more similar to purplepag.es that only handle kind 0 and 10002. Haven't heard of any yet.
Also, NIP-65 mentions in point 5 of the Final Considerations: "If a relay signals support for this NIP in their NIP-11 document that means they're willing to accept kind 10002 events from a broad range of users, not only their paying customers or whitelisted group."
This could open a relay up to a DoS where the hardrive fills up with noise generated as quickly as npubs can be generated and bandwidth is able to transmit. There is a case, I think, when signalling NIP-65 support only for paying customers (and perhaps also their network) is desired. However, I am not certain how NIP-11 documents are currently utilized.

2024-09-23 21:32:03

- reply

In some ways it helps and in others it doesn't. In Amethyst, I think it means you're following them and not necessarily verified.
Here are a few scenarios:
A) If the profile (maliciously or otherwise) changes their name, pfp, bio and etc. (kind 0), it'll be difficult to know which one of your follows/contacts it was when you initially followed them. This could be used to imposter someone.
B) If the private key of a profile is compromised (similar to A) all metadata can change. If notes appear from this account that the key has been compromised and to migrate to a new key; it will be very difficult to recover and determine honesty. The NIP05 nostr address will also not be useful, as that too could have changed.
C) If you're not following someone, yet still want to be able to verify them, the mark won't help in this case.
There may be others scenarios as well, and plan to go through and document these in more detail. I have a few NIPs drafted to introduce a profile metadata attestation event kind that could be used to verify profiles and mitigate and help the above scenarios.

2024-09-22 15:14:20

- reply

In a course I took with @nprofile…29qg I've heard that economics education in college is similar with nonsense to support the banking cartel.
In my college education for design, software taught was entirely non-free and monopolized. With the help of community, I taught myself free/libre software shortly after graduating, one of the best things I have done.

2024-09-22 00:57:03

- reply

Is there a list of such relays documented someplace?

2024-09-21 12:32:52

- reply

I am not sure when this is useful, but it seems it will be for something.

2024-09-20 12:58:47

- reply

Sure!
Perhaps as well, private attestations could be made with a follow for just the name and profile image, as a starting point.

2024-09-20 12:39:46

- reply

Here is the mentioned animated wireframe of how what I described could work:
https://raw.githubusercontent.com/braydonf/nostr-key-migration-and-revocation/89a9437e958f44bf748f145b85e603d83cf7ef2f/graphics/ux-storyboard-animation.webp
And NIP text:
https://github.com/braydonf/nips/blob/secure-profiles/xx.md

2024-09-20 12:25:38

- reply

IDK, I often look at the Nostr Address/NIP05 checks in comments, some folks' are easy to remember (yours for example). Amethyst does well here, atleast.

2024-09-20 12:20:11

- reply

Yup, it needs to be remembered and known. That is why I think it is a good idea to be able to verify an account user metadata, name, nip05, website and etc. Verified values can be recorded via an attestation event/note that could be private or public. I've drafted up a wireframe of this and NIP on how it could work.

2024-09-20 00:31:24

- reply

More importantly, is for local entrepreneurs, businesses and communities to stack BTC (sats). It can include accepting it, but it can also be done through trading (sometimes more simple).
From my experience accepting bitcoin payments as a small local business, it is pretty challenging (not from a technical point of view, that is pretty simple now). I now think it needs to be a community effort to draw the necessary attention. This helps to reduce the necessary marketing expenses, per business, through a shared effort. In larger cities, it may be easier, as the likelyhood of bitcoiners being around increases.
Some more rural communities have had success by getting a community together and creating a circular economy and attracting tourism. I went to @nprofile…qkn2 (Uvita, Costa Rica) and they've done a pretty great job getting it all started there. Bitcoin Beach (El Zonte, El Salvador) is another. There is probably a lot to learn from them and others.

2024-09-19 20:25:19

- reply

Looks like v1 may be better with `since` and `until` filters as there is a new command `strfry negentropy` for configuring trees...

2024-09-19 20:07:29

- reply

I've also added a few paid relays like relay.westernbtc.com and nostr.wine and eden.nostr.land and haven't had issues.
It'll also be good to have a private relay (could be provided as a no hassle paid service or on your own hardware) that will use negentropy sync and streaming for your follows. I'm looking into this now with strfry.

2024-09-19 17:52:41

- reply

Let's hope with 1.x.x it remains backwards compatible. Perhaps @nprofile…a7qk knows more on this and the plan for future releases and the protocol extension stability.

2024-09-19 17:42:14

- reply

Nice! Yeah, those work too! 0.9.7 appears to be the version most are running currently.

2024-09-19 17:37:06

@nprofile…vjzk Just got negentropy syncing working with relay.westernbtc.com with version strfry 0.9.7 (doesn't work with 0.9.0 or 1.0.1)
I used this command:
```
./stryfry sync wss://relay.westernbtc.com --filter='{"authors": ["<hex-pubkey>"]}' --dir=down
```
I've been unsuccessful with other relays like nostr.wine and nostr.land
Perhaps I am using the wrong version or command?
cc: @nprofile…sgtg @nprofile…w3kv

2024-09-19 14:54:45

A bitcoin security vulnerability I wrote about in 2019 has been resolved (2022) and now published on the Bitcoin Core website.
https://bitcoincore.org/en/2024/09/18/disclose-headers-oom/
Great job! Much thanks to Suhas Daftuar, Pieter Wuille and Niklas Gögge for getting it patched and to all code reviewers, maintainers and everyone involved.

2024-09-18 21:28:48

- reply

Haha... pretty good. 😅
So many notes seem to only be coming through only via nostr.wine on Amethyst now for me.
Negentropy sync would be great for a mobile client. It connects to only a few relays and those relays sync with other relays, etc, etc.
Lots of great stuff to do.

2024-09-18 19:15:32

I've upgraded my private relay to strfry 1.0.1 and negentropy syncing works from it. Other relays and clients can pull down events from it very efficiently. Very cool.

2024-09-18 18:49:26

- reply

I'll take a look, thanks.

2024-09-18 18:35:35

- reply

I think it would be great to be able to verify npubs (private or public) of names and etc, a bit like GPG key signing, or having custom names in Signal (not from their profile but from an individual address book).

2024-09-18 17:58:08

- reply

The relay at relay.primal.net is also getting a lot of spam, removed them from my relay list and I don't think there is a paid replacement. 🤷‍♂️

2024-09-17 22:25:14

- reply

Was looking for this the other day but couldn't find it via search, strange. 🤷‍♂️

2024-09-17 21:19:02

- reply

Topical relays could be interesting to browse that way. Could be possible to use LLM based filters for a relay and WoT for client side ordering and filtering. Hashtags can get so easily spammed with unrelated stuff and an LLM is pretty decent and finding patterns and relevancy.

2024-09-17 20:49:33

I think we need this one:
https://github.com/nostr-protocol/nips/pull/1494
Haven't looked at the details yet.
Might implement a sync based on a follow list on a private relay with strfry.

2024-09-17 19:09:44

Math Art: Diffusion Illusion Puzzle
https://youtube.com/watch?v=b5nElEbbnfU

2024-09-17 18:22:49

- reply

This is pretty good quick overview.
It's probably been said here on Nostr a few times, but worth repeating, Fiat Food by Matthew Lysiak goes more into depth on this topic for those interested.
Has helped my health a lot. 🤘🚀
And follow @nprofile…zhgl

2024-09-17 17:40:01

- reply

Yeah exactly, that's more how I would say it. Your keys, your relay, your freedom. 🤘🚀

2024-09-17 17:18:13

Nostr is available for everyone to own.
Your keys, your relay, your freedom.
#nevent1q…vndd

2024-09-17 16:53:19

I've realized in Amethyst, in the general relays settings, you don't need to completely remove a relay from the list to stop incoming spam from it, you can just turn off all of the Home, DM, Global and Search icons.

2024-09-17 16:40:42

Something that could be useful for paid relays to provide is negentropy syncing between relays for the follow list of subscribers, with configurable depths. Also, calculating how much storage space and bandwidth are being used on behalf of a subscriber and having having rates per GB or similar (the could also extend into media storage, images, video and audio).

2024-09-17 15:49:04

- reply

The argument against supporting other devices always seems to be because of the Google Titan secure chip. Kinda surprised GrapheneOS hasn't been forked to support more hardware and an app like Obtainium as the "App Store".

2024-09-17 15:20:03

Something I've noticed with my current relay setup is that some notes that are replied to will not be found. Is "rebroadcasting" the note that has been replied to not common? Or provide a relay that it can be found? 🤔

2024-09-17 14:07:06

- reply

Relays that don't add some cost to write notes and other stuff are likely going to fail.

2024-09-17 00:42:49

- reply

Still? I haven't seen much of any since about two days ago.

2024-09-16 19:04:42

- reply

Removed all client side filters as well, still doing well. The solution to spam is simple.

2024-09-16 18:46:32

- reply

Added eden.nostr.land as another paid relay.

2024-09-16 17:49:05

- reply

It's a vector, download the svg file.

2024-09-16 13:41:53

- reply

https://commons.wikimedia.org/wiki/File:Bitcoin_logo.svg

2024-09-16 10:24:22

Besides these two relays, what are some other paid relays to join?
nostr.wine
westernbtc.com

2024-09-16 09:57:06

Having only paid, private and wot relays is doing well; no spam or impersonators. 🤘🌞😃🚀

2024-09-16 09:48:16

- reply

Yup, removed relay.primal.net I don't think they have a paid alternative either (with less spam), unfortunately.

2024-09-16 01:17:54

This video had me wondering if there is or could be a generative AI that could find many different M.C. Escher type advanced tessellations.
https://image.nostr.build/d6dc90cc063faa049afb90c84800bf61c5e10cef7619c1a255f6c8455fd4bb52.jpg
https://www.youtube.com/watch?v=FMRi6pNAoag

2024-09-15 23:08:07

- reply

LLMs could be useful to determine relevancy, as another method to filter and organize.

2024-09-15 22:09:47

LLMs can be useful to determine comment relevancy for filtering too! Here is a basic demo:
https://image.nostr.build/0e255116359cf11a42042629ad94559e1bd27eb6fad6565118a03ec254052c34.jpg

2024-09-15 19:19:43

- reply

Yeah, one of your posts had a lot earlier. I've moved to WoT, paid and private relays and have been doing well.