VzxPLnHqr

Public Key

npub10ynmcm393ynjn2wq9gfn93qf56djshs58wwcghz5lkwpl6pfuf0qw5495k

NIP-05 Address

Profile Code

nprofile1qqs8jfaudcjcjfef48qz5yejcsy6dxegtc2rh8vyt320m8qlaq57yhspz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsd7rk2x

Publishing to

yabu.me

relay.damus.io

nos.lol

Author Public Key

npub10ynmcm393ynjn2wq9gfn93qf56djshs58wwcghz5lkwpl6pfuf0qw5495k

Show more details

Last Notes

2025-10-28 18:41:17 UTC

- reply

I sometimes use it with Roo Code / VSCode.

2025-07-30 23:00:42 UTC

- reply

Is there intention to add the reverse feature too? (for nostr people who already know each other's npubs but want to use bitchat for messaging going forward)

2025-07-09 20:08:13 UTC

@nprofile…ku2x have you considered adding some markets pertaining to activation of various bitcoin soft-fork/upgrade proposals? Something like "will bitcoin activate ctv+csfs (or equivalent) by jan 1, 2027?"

2025-04-24 18:33:50 UTC

maybe we should bitcoin+nostr+mcp this hashcash thing https://github.com/TecharoHQ/anubis but make it so that the challenge string (provided by a spam-deterring site operator) is actually the components of a prospective bitcoin block header.
If the operator is too lazy to run their own bitcoin node to construct the block template, then they can grab one from a service like mempool.space
From the visitor's perspective it is the same (they must complete the pow challenge), but at least this way every website operator can also be a solo miner.

2025-03-20 18:04:06 UTC

- reply

@nprofile…sxlf will you please do a hard refresh of your browser? This may be related to the browser caching an older version of the underlying javascript.

2024-10-25 02:36:19 UTC

- reply

Unfortunately there is not an easy way to implement this idea in a backward compatible fashion since nostr event signatures do not currently have a notion of sighash flags. But maybe we should consider adding such a thing?

2024-10-24 20:37:18 UTC

what if every nostr identity is, or easily, and optionally, could be, its own root certificate authority (CA)?
Say your master nostr identity is `nsec_master` with pubkey `npub_master`. For an event signature to be considered valid the event either:
1. must be directly signed by `nsec_master` (as is done currently)
2. or it has a small chain of signature/message pairs (certificates) terminating with a valid signature produced by `nsec_master`.
Since everyone runs their own CA, the length of the signature chain should be quite short, but even so it still would make the total event size larger (only for events that use this). But the usability improvements and features might be worth it.
Certificates need not be long-lived. For example, your CA could issue a 30 day cert to a fresh npub generated by your phone. If you lose your phone a lot, maybe a 1 day or 1 hour cert would be better for you. Now your phone can happily post and sign nostr events on behalf of your root nostr identity. Then, when you lose your phone, at least the cert will expire and you have not compromised your `nsec_master`. In the interim you could publish a revocation event.
As with everything in nostr, it would be up to clients to verify events.

2024-10-17 22:20:06 UTC

- reply

Duly noted regarding the links. Apparently I need nostr training wheels :-P
I rule out cjdns for the same reason you do. Regarding yggdrasil, supposedly they are doing some sort of routing magic per https://yggdrasil-network.github.io/implementation.html#what-does-yggdrasil-do-differently the most succinct description I could find was:
"... A spanning tree is used to provide synchronisation and to allow nodes to allocate themselves a set of tree coordinates, which are used to exchange and establish bootstrap and path setup messages. Nodes then exchange bloom filters which contain information about which keyspace neighbours are reachable through each node. Intermediate nodes then populate their routing tables with these paths, enabling nodes to forward packets closer to their destination public key."
It feels somewhat similar to your design, but yours seems simpler.

2024-10-17 18:34:26 UTC

- reply

happy to see that you are also thinking about these sorts of things! Did you look into things like [cjdns](https://github.com/cjdelisle/cjdns/) or [this](https://github.com/yggdrasil-network/yggdrasil-go) ?

2024-08-29 19:01:31 UTC

`op_ctv` or `op_cat`?

2024-07-28 02:09:00 UTC

has leaving an iris.to tab open sucked up 3.4GB of ram for anyone else or is this a memory leak?

2024-07-22 22:27:27 UTC

- reply

running statechainjs

2024-01-24 18:53:58 UTC

why is p2pool mining no longer a thing on bitcoin mainnet? coinbase outputs taking up too much of the block space?

2023-12-27 23:08:32 UTC

- reply

answering my own question: https://stats.nostr.band/

2023-12-25 00:04:48 UTC

anyone have a current estimate of the total number of unique nostr events happening per second on average across the network?

2023-12-22 22:58:19 UTC

- reply

This is really interesting and exciting to see. What about embedding the nostr event id in a fresh bitcoin block template and then grinding on the actual blockheader instead of the nostr event? It is solo mining, and the block template could put various relays, charities, or whoever as recipients in the coinbase output.

2023-12-06 22:53:07 UTC

- reply

actually, clicking "unfollow" on a few of them seemed to get rid of all except 1 of them.

2023-12-06 22:32:09 UTC

@npub1g53…drvk Is it a bug that when I go to my profile in iris.to and click "follows," it shows me that I am following myself 20 times?

2023-11-30 20:40:58 UTC

running nostr (again), this time via snort.social and using @fiatjaf nos2x browser extension for signing!

2022-07-19 16:28:47 UTC

- reply

I have been meaning to look into Fedimint, but have not yet had a chance. Would be very curious to know your take if you look into it.

2022-05-12 19:10:24 UTC

- reply

fwiw, you may want to check out raspiblitz too. As for wallets on your node, since your node is hosting it, you could use something web-based like LNBits too.

2022-05-05 02:22:01 UTC

- reply

nevermind, I mis-read. I see who he follows and (obviously) I know who I currently follow (it's on the right pane of my branle client). Please ignore this. Sorry for the unnecessary mentions! #[0] !

2022-05-05 02:19:54 UTC

why is it that when I (using branle) click on somebody's profile like #[0] I can see who #[0] follows, but when I click on my own profile I cannot?

2022-05-03 20:22:27 UTC

- reply

Regardless, great to see experiments like this happening.

2022-05-03 20:18:59 UTC

- reply

Thanks! I will sign up and stack some sats then!

2022-05-03 17:17:23 UTC

- reply

do you have a link? I cannot seem to find the post on there about UBI

2022-04-28 19:32:02 UTC

Is anybody working on a pay-via-lightning nostr relay with inbound email address mapped to nostr pubkey (delivered via direct message on nostr)? Outbound email could be charged at higher rates to avoid spammers. Might not even need outbound service at all though.

2022-04-18 23:11:16 UTC

- reply

yes, it is fixed now. Thanks!

2022-04-15 22:51:12 UTC

- reply

Got it. Now it makes sense why your bot posted something about a recent bitcoin block having 78 bits of nostr difficulty. I thought for some reason you were actually mining on the bitcoin block header, but you were just re-interpreting its hash in this way. Thanks for clarifying.

2022-04-15 22:40:03 UTC

- reply

#[3] did something happen to our blue checkmarks? On the branle.netflify.app client yours gone too, so it is probably not isolated to just me I presume?

2022-04-15 22:37:26 UTC

- reply

#[1] This is an interesting idea. Is there somewhere I can read about how you define "nostr difficulty?"

2022-04-15 19:43:12 UTC

Is there some sort of daily summary/news bot on nostr yet which I can follow?

2022-04-11 20:51:43 UTC

- reply

fantastic! I have a blue checkmark now like all the cool kids. Thanks #[5]

2022-04-11 19:27:34 UTC

- reply

Sorry for my delay in reply. I will DM you to set my blue checkmark up too!

2022-04-11 19:24:06 UTC

- reply

I think this is a pretty solid prediction. Great work getting i PoW relay setup!

2022-03-11 20:34:31 UTC

- reply

#[1] how can I get one of these blue checkmarks on branle without owning a domain name? Is there a relay which offers (expiring) NIP-05 codes in exchange for lightning payment?

2022-03-11 20:32:41 UTC

how can I get one of these blue checkmarks on branle without owning a domain name? Is there a relay which offers (expiring) NIP-05 codes in exchange for lightning payment?

2022-02-18 23:04:48 UTC

- reply

Not that I know of. In general a video/audio conferencing solution that (client-side) blurs faces and disguises voices to allow for pseudonymous yet real-time collaboration is interesting. I wonder if such things exist?

2022-01-24 17:49:15 UTC

- reply

For the address reuse problem, it seems to me like the main solution would be for participants in nostr who want to do payments to adopt (by convention) something like paynym or similar. Alternatively, if nostr has a simple way to switch out a pubkey for a new one...

2022-01-24 17:35:11 UTC

- reply

Sorry if you are getting multiple replies @0xtr Branle seems to be lagging for me. But yes, Bolt12 and paynyms is interesting. Hopefully custodial-relay wallets are not really necessary.

2022-01-22 00:56:52 UTC

- reply

for implementing payments, two questions:
1. for lightning, are you mostly thinking trusted/custodial (offered by the user's relay?) or something else?
2. since each nostr key can be used to create a valid bitcoin address, what do we do to prevent/discourage address re-use?