<unnamed>

Public Key

npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy

Profile Code

nprofile1qqsrx4k7vxeev3unrn5ty9qt9w4cxlsgzrqw752mh6fduqjgqs9chhgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg5waehxw309aex2mrp0yhxgctdw4eju6t0qy8hwumn8ghj7mn0wd68ytnddakszrthwden5te0dehhxtnvdakqz8thwden5te0dehhxarj94c82c3wwajkcmr0wfjx2u3wdejhgqgjwaehxw309ahkvenrdpskjm3wwp6kyjfdmnn

Publishing to

nostr-pub.wellorder.net

offchain.pub

Last Notes

2025-09-29 07:59:33 UTC

- reply

fixed

2025-09-11 08:02:27 UTC

- reply

Hi, this sounds great but you're probably 1 of 10 users of this relay and that's just not worth the effort. Besides, I'd say relay-browsing apps should just implement these filters on the client - with wot/reactions/etc as filters, that's much more versatile then me trying to cater to every possible filtering/UX need at the relay level.

2025-09-09 17:05:41 UTC

- reply

I mean if keys can't be extracted and operator just kills the enclave then keys are gone and LN node's channels are force closed and node's sats are gone with the keys and operator gets no benefit from the shutdown. Or am I missing something?

2025-09-09 16:47:56 UTC

- reply

My point is the motivation for taking your funds for myself is obvious, while taking them to no-one's benefit - not so obvious.

2025-09-09 16:28:14 UTC

- reply

It's not a rug, funds aren't stolen, but destroyed - enclave is terminated and keys are lost, a very different set of incentives to do this.

2025-09-09 16:12:45 UTC

- reply

I think the difference btw "we are 100% sure this mint runs this code" vs "we don't really know what it's doing but some checks make it look fine" is significant.

2025-09-09 15:43:44 UTC

- reply

I would separate rug pull risk from service failure risk. Cashu is custodial without unilateral exit so with or without enclave, if mint goes down, funds are inaccessible. To me it looks like rug pull risks are minimized with enclaves - we could get a lot of independent mints all running verified code, which sounds quite awesome. The rest are reliability questions: backup might be sync real time, coordinator can live in another enclave, dns record can be controlled by the current master, updates don't require a blockchain - just a set of signatures by pre-declared maintainers (that's my current approach). Not that it's a proven set of solutions, or that I am against the blockchain, but I think more experiments are needed to figure out the actual problems and solutions.

2025-09-09 14:08:24 UTC

- reply

Tell me more on why blockchain is needed? To set policies for how to get the keys out? Why would you want the keys out?

2025-09-08 08:38:08 UTC

- reply

Not to be rude, but how do you know it's bad? And bad compared to what? Is there a source that is not bad? I maintained stats for myself to see the real picture, and some people think the real picture is different, but they never cite the source. I 100% support passing the torch to someone, but don't hope the new maintainer will give you much "better" data.

2025-09-08 08:25:35 UTC

- reply

So do you want to work on stats, or the whole package - the relay, the nostr.band site with search, profile stats, trending etc?

2025-09-04 12:34:10 UTC

- reply

I'm ok, priorities are changing. And yes, nostr.band and stats haven't been worked on for a very long time, keeping them up until good alternatives emerge.

2025-08-07 13:05:04 UTC

Clone yourself https://github.com/nostrband/askexperts

2025-07-08 09:22:24 UTC

- reply

On Amber cc @nprofile…lmth

2025-07-08 09:18:47 UTC

- reply

Is it working now? I was restarting it and making some changes today.

2025-07-02 08:24:51 UTC

- reply

There's L402 by Lightning Labs, there's l402.org by fewsats, there's x402 by coinbase, there's cashu nut-24. Cashu seems like the simplest indeed.

2025-06-30 14:57:18 UTC

- reply

On my side too

2025-06-30 14:53:22 UTC

- reply

Apologies, relay.nsec.app was down for a while, should be up now.

2025-06-23 10:43:16 UTC

- reply

Try reloading the page, etc. We changed nothing there, something might have changed with your extension/browser setup.

2025-06-10 08:57:47 UTC

@nprofile…wvxz check PR please https://github.com/dezh-tech/ddsr/pull/16

2025-06-05 16:50:24 UTC

- reply

You will soon be able to launch docker images in enclaved app server at a fraction of the cost

2025-06-04 10:01:17 UTC

- reply

> In most cases there is no real way for Nostr account to be a practical thing to use without a the possibility of a human being laying eyes on the nsec.
If nsec is generated inside an enclave and bunker url is returned then no human has seen it.
If some "policy" was provided when nsec was generated, like "require m-of-n multisig to change perms, rotate the bunker url, change this policy, etc", then a board of directors can control the nsec without seeing it, and if one of humans leaves they can change the policy and the bunker url.
Does this make any sense, or is there still a fundamental flaw here and we're just kicking the can?

2025-05-30 10:04:34 UTC

- reply

50k
which wallet are you integrating?

2025-05-29 16:00:52 UTC

- reply

After you go through hell of getting your android and ios dev accounts

2025-05-29 15:59:52 UTC

- reply

Found it, says Connecting and then Request timeout.

2025-05-29 15:54:02 UTC

- reply

How can I connect the nwc wallet?

2025-05-28 06:48:18 UTC

- reply

Can't login with bunker bcs it throws on auth_url challenge.

2025-05-26 08:34:56 UTC

- reply

Fixed, could you please open use.nsec.app then wait a bit, click Reload button at the header when it appears to update it, then retry. Thanks you very much for this feedback!

2025-05-24 05:26:18 UTC

- reply

Just use

2025-05-23 21:16:04 UTC

- reply

VS plugin https://github.com/RooCodeInc/Roo-Code

2025-05-23 19:24:16 UTC

- reply

I've been vibing a side thing in the background for a week. I break it into small tasks, think through the architecture and major important pieces. Then roocode and Claude do next task in several minutes. Sometimes it goes crazy and I had to rollback. Sometimes it's stuck and I have to figure things out. But if you treat it like a super productive junior, it's fascinating. It would take me at least 3 weeks full-time to get where we are now. Just don't think it can do big things alone.

2025-05-23 19:19:10 UTC

- reply

Where are the other 86?

2025-05-23 07:36:31 UTC

- reply

My apologies. Could you please try again now?

2025-05-22 06:53:54 UTC

- reply

What's the problem with nsec.app ?

2025-05-20 14:47:24 UTC

- reply

I need to look at how to parse them properly. Does any of big clients show nutzaps under notes?

2025-05-20 13:32:29 UTC

- reply

Well while we were talking RooCode looked through one third-party golang codebase, figured out how to do what I need, and wrote me a ts function to solve my problem. I tried doing that by hand before and just gave up. Sometimes it's super helpful.

2025-05-20 11:36:44 UTC

- reply

I'm only playing with it atm, no good number yet.

2025-05-20 06:57:21 UTC

- reply

Sorry I don't see any other way to pass ln address with NWC - lud16 is included now, maybe that's something on your side? Are you setting the NWC string into an existing profile that already had ln address? Maybe Freerse uses address from NWC only if profile didn't have one already?
Yes it's using relay.zap.land

2025-05-19 16:29:41 UTC

- reply

Does the NWC string that you're getting now include &lud16=<address> ?
Yes works great w/ @nprofile…q7y6 !

2025-05-19 14:26:15 UTC

- reply

Ah ok I found it, added lud16 to NWC now - could you please try again checking if LN address will be taken from NWC?
I recommend managing the wallet using Alby Go or similar app for now, I don't have immediate plans to add transfers etc to zap.land

2025-05-19 13:36:16 UTC

- reply

Hi, this isn't really a wallet app, it's just here for you to generate NWC string and start using it elsewhere.
Zap.land gave you the ln address which you could put into your profile, is that what happened? NWC isn't really related to ln address, these are separate things

2025-05-17 07:42:21 UTC

- reply

Ok see it below now.

2025-05-15 14:31:52 UTC

@nprofile…7c2c @nprofile…n07m please take a look? thanks https://github.com/getAlby/js-sdk/issues/384

2025-05-15 09:59:14 UTC

- reply

This was basically my first shot, I just used cursor with claude 3.5 sonnet. What do you use?

2025-05-15 08:50:37 UTC

- reply

Kevin says they'll allow invoice creation with offline receiver too, that's promising.

2025-05-15 05:12:10 UTC

- reply

Although I am looking at the diagram, the LN payment itself is offline, but looks like invoice generation still needs receiver to be online, which means something like zaps isn't possible offline.

2025-05-15 04:54:37 UTC

- reply

Awesome, thanks! Offline receive is a great capability.

2025-05-14 14:17:50 UTC

- reply

Automatic wallet creation by apps for new users is one of the goals of the nwc-enclaved, and it supports zaps.
The tradeoffs with Spark are that it's a new tech and quite complex and not many people can understand it. And Spark operators have to be trusted, although I'd say they should run in enclaves too. And no fees for now but they will come and hopefully will be competitive. And 'unilateral exist' is 'coming soon' at the moment. And your wallet still has to be online 24/7 to receive payments if I understand it correctly. So - pick your poison. I think it's very promising, but wouldn't bet 100% on it right now.

2025-05-14 13:46:47 UTC

- reply

We will create spank-based on too, it's a different set of tradeoffs.

2025-05-14 13:45:32 UTC

- reply

The wallet service has it's own nostr profile here: @npub1ldl…0rpx

2025-05-14 13:43:10 UTC

- reply

Ah and btw you can add wallet creation to your app using this lib: https://github.com/nostrband/nwc-enclaved-utils
It discovers a valid service instance and creates a wallet in a couple lines of code.

2025-05-14 13:34:13 UTC

Lightning wallet in 1 click!
I vibe-coded a trivial wallet-creation app today: https://zap.land
One click and you get NWC string that you can put into Alby Go to topup the wallet and send payments, or put into Damus/Amethyst to send zaps. You also get LN address that you can paste into your Nostr profile and receive zaps to this wallet.
https://image.nostr.build/9ec71b3e9425129120863d812f9ece3f671838757b4a20ef34e2a840ce64b471.jpg
The backend of this is a development instance of a new custodial lightning wallet deployed in a trusted execution environment. That means you get better security and privacy guarantees, along with great usability. It's open source, you will be able to launch an instance of it yourself and clients could discover your instance along with ours and let users choose. The source code is here: https://github.com/nostrband/nwc-enclaved
This is an invitation for public testing and for your feedback. The wallets created have the max balance limit of 1000 sats and will likely be turned off at some point when testing is over and dev instance needs to be shut down. This is not the real thing, it's a toy to get a taste of it!
The service is based on "phoenixd" wallet with fully automatic liquidity management, which means - fees. Phoenix charges 4 sats + 0.4% per payment - we charge extra 1 sat, phoenix charges 1% plus mining fees for liquidity - we add nothing here, we also charge 1 sat per day to avoid getting spammed. When I say "we" I mean "the code inside the enclave" - it will only use revenue to pay for itself inside the enclave, not to make a profit.
Anyways, send some feedback!

2025-05-12 07:21:15 UTC

- reply

Hello, no nsec.app doesn't interfere with your nip05 set in your profile - we assign you our own nip05 but you'd need to enter it into your profile manually for other people to see it.

2025-05-09 12:25:30 UTC

- reply

afaik Alby generates new key for every nwc-connection so they'd have to have a separate auth/conn per user, doesn't seem like a good fit.

2025-05-09 08:26:05 UTC

- reply

Yes it's the first thing I wrote for nostr, closed source mess

2025-05-08 09:41:24 UTC

- reply

I sent a PR with some fixes to bunklay, and there's also an issue: https://github.com/dezh-tech/ddsr/issues/14

2025-05-07 12:56:51 UTC

- reply

It should be non-strfry (try https://github.com/dezh-tech/ddsr/tree/main/bunklay) it should retain kind 24133 events for 10+ sec and ignore other kinds and that's about it.

2025-05-05 07:29:29 UTC

- reply

1500 ping is probably due to you being in Asia, typical ping is 600 (300 of which are strfry).
Key not found sounds like service worker was off when you clicked Upload. Could you please reload the page and try again? Need to figure out how to wake the SW up if it starts sleeping with an open tab.

2025-05-02 17:47:51 UTC

- reply

Btw could you also create the same kind of relay for nip47 (NWC), please? Will use both soon.

2025-05-02 11:59:22 UTC

- reply

One particular thing is that ephemeral events should be kept for a while (i,e. 10 sec) to allow consumers to restart/reconnect. Not sure it's specified anywhere but quite important in practice.

2025-05-02 10:36:22 UTC

- reply

I could give it but I recommend trying something else, strfry has high internal latency for delivering new events to active reqs (>300ms). I plan to switch from strfry myself, here is a nip46-specific khatru-based relay by @npub1h49…9kay https://github.com/dezh-tech/ddsr/tree/main/bunklay - haven't tried yet, but looks promising.

2025-05-01 14:16:49 UTC

- reply

This rocks!

2025-05-01 11:40:52 UTC

- reply

nsec.app is running over relay.nsec.app which is a normal strfry. It's actually quote slow for ephemeral events processing - it has internal latency of at least 300ms for delivery of new events to active SUBs, plan to switching to something more specialized. Aside from that, again, try the secure enclave thing in settings.

2025-05-01 10:26:56 UTC

- reply

Thanks makes sense.

2025-05-01 10:01:23 UTC

- reply

idk about Amber, @nprofile…tcvv

2025-05-01 10:00:31 UTC

- reply

Will give, I need to try it first to see if something feels bad, but definitely can add some food for thought related to my recent research with TEE - i.e. running trusted builds in trusted third-party environments.
Also question - why focus on ecash for payments?

2025-05-01 09:47:27 UTC

- reply

That's what Amber should be able to do, web apps can talk to it - though not sure how good it works in practice.

2025-05-01 09:46:24 UTC

- reply

Thanks for the huge work you and others have done on GitViaNostr! I've got a lot to digest now.

2025-05-01 09:23:24 UTC

- reply

Which bunkers are you mostly using/tried?

2025-05-01 09:21:41 UTC

- reply

Thanks! Added nip34 to indexing in wss://relay.nostr.band - should be nip-50-searchable now. Also added kind:1111 to indexing - long overdue, missed them somehow.

2025-05-01 08:12:14 UTC

- reply

Is there a chat somewhere about GitViaNostr? @nprofile…633s

2025-05-01 05:39:41 UTC

- reply

It fetches from everywhere

2025-04-30 09:02:50 UTC

- reply

Pardon, it's {"kinds":[39089],"search":"bitcoin"}

2025-04-30 09:02:25 UTC

- reply

And to search through follow packs send nip50 requests (https://github.com/nostr-protocol/nips/blob/master/50.md) to wss://relay.nostr.band like {"kinds":39089,"search":"bitcoin"}

2025-04-30 07:29:42 UTC

- reply

relay.nostr.band now let's you search through these events

2025-04-27 14:43:21 UTC

- reply

In our case app in tee generates a key to be used for encrypted comms and that pubkey is included in the attestation

2025-04-27 14:42:22 UTC

- reply

Comms with enclave are e2ee that's critical. Attestation of nitro can have pubkey, nonce or small piece of data

2025-04-25 20:52:30 UTC

- reply

Many people seem to have worked on this, why don't you mention any actual project?

2025-04-24 12:49:11 UTC

- reply

kinostr

2025-04-24 08:02:55 UTC

- reply

I see, sending you a signal DM please check

2025-04-24 08:02:10 UTC

- reply

I see zap receipts don't work because zap request 9734 event doesn't have "relays" tag (https://github.com/nostr-protocol/nips/blob/master/57.md#appendix-a-zap-request-event) - zap receiver doesn't know where to publish the receipt.

2025-04-24 07:59:04 UTC

- reply

Ah yes! Didn't notice the Zap symbol on kinostr. Did you try to figure out how to add some wallet integration? For one-click zaps or for creating wallets for signing-up users?

2025-04-24 07:52:45 UTC

- reply

Cool! Which of your apps have zaps? Zap receipts are published by receiving wallet, so I don't think your app is responsible for that.

2025-04-24 07:13:50 UTC

- reply

Did it work?
Btw did you try integrating LN/zaps to your vibed apps?

2025-04-23 09:25:32 UTC

- reply

Yes we use Ghost themes but not Ghost itself. It can be self-hosted but there are currently some drawbacks when doing that (no server-side rendering), instructions here https://blog.npub.pro/post/how-to-self-host-on-github/

2025-04-12 08:10:58 UTC

- reply

Thanks for the link, good read!

2025-04-11 19:41:21 UTC

- reply

Nothing to prove here, if you trust AWS virtualization infrastructure, then use it, otherwise ignore. There is always some root of trust.

2025-04-11 19:22:02 UTC

- reply

Why?

2025-04-11 18:57:13 UTC

- reply

Ah got it, you pass the bunker url to creator, and they try to export and that only succeeds once. Sounds good!

2025-04-11 13:20:05 UTC

- reply

So you create an nsec for Taylor Swift and start reposting her insta pics on nostr, those get zapped, eventually you tell her about those sats and invite to take over the nsec. Is that the set up? Wouldn't you want to prove to enclave, somehow, that it's her? Otherwise someone could front-run her?

2025-04-11 12:53:43 UTC

Store your nsec in a secure enclave!
We've spent a big part of 2024 trying to make a reliable non-custodial signer with nsec.app. It hasn't worked out perfectly - remote access to keys stored on a mobile device is still unreliable, especially on iOS.
That's why we got very interested in AWS Nitro Enclaves - h/t @nprofile…j64l and MapleAI team for inspiration!
The idea is to have an open-source custodial signer and deploy it in an isolated environment that provides attestation for the deployed code. Anyone would be able to reproduce the code build and verify that the signer is running the correct code in a safe environment.
So here it is: https://github.com/nostrband/noauth-enclaved
Each instance of a signer deployed in an enclave announces itself on Nostr. We added some Nostr to attestation provided by AWS - the report is linked to pubkeys of a person building the code image, and a person running it. This way you can choose a signer based on your own preferences.
It's already integrated into nsec.app, go to Settings => Secure enclave and try to upload your keys to the server. The signer API is described in README.
https://image.nostr.build/c94c04248420e49a0c9c3c13727943d47b629ec63c9a5078fd9302f675e7032f.png
DO NOT deploy your real keys just yet - it's running in a production environment, but the code hasn't been well audited yet. First we need some community members to review the code and reproduce the code image.
The signer can also be used to generate throwaway keys for automated testing of nip46 implementations, check out "generate_test_key" method.
Looking forward to your feedback!
(Signed by my nsec from the enclave)

2025-04-09 19:18:05 UTC

- reply

Even Protocol Enhancements section doesn't mention payments, they probably hope to get everyone on their closed platform eventually. Same with discovery.

2025-04-09 19:11:44 UTC

- reply

That's what I was trying to say

2025-04-09 19:03:57 UTC

- reply

Exactly, don't see payments mentioned which makes no sense

2025-04-01 11:18:37 UTC

- reply

No, you can only change contributors. Admin can change settings, contributors post content.