2026-07-30T09:46:09Z https://nostr.now floscodes https://nostr.now/npub10jlrnq8wgqem3w0s6qhswwqagfzh00z3up7a43xd5qt8tglukkkqxsxlwj https://image.nostr.build/9c87178ab46f8d8aff138570f911d3eeb0a1b1d6a5786cbac57de3230e4e43b2.jpg https://image.nostr.build/9c87178ab46f8d8aff138570f911d3eeb0a1b1d6a5786cbac57de3230e4e43b2.jpg https://nostr.now/nevent1qqswpk8qjh8t09slptjyfvjququg4nc0q84ptpmlft5atcwx4pwpzvszyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66c2ra5qk In reply to <a href='/nevent1qqsykre94ht38efpvvlngfyaz0xwupwy98usfzkts4d074u8536n2gcqv8fx0'>nevent1q…8fx0</a><br/>_________________________<br/><br/>Thanks, I really appreciate that! It felt like the right time to let it Go 🙂 2026-10-02T08:11:37Z https://nostr.now/nevent1qqsv90qq5lvcdnh56p3dqhueww0ruqjrvus6xwuxugkptz07cdlpnzszyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66c0yme2e Hi guys, I’ve stopped developing Xmes. Maintaining a messaging app and handling legal responsibilities takes a team and funding beyond what I can provide alone. Thanks for trying it!<br/><br/><a href="https://github.com/floscodes/xmes">https://github.com/floscodes/xmes</a> 2026-10-01T15:37:29Z https://nostr.now/nevent1qqsyltxt0wzq95xtwlrxa0nw6wxfgzzpcfl33mmvzh9xpzjs38yshagzyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66ckljgq7 In reply to <a href='/nevent1qqsp2r4syx73lslfj30sekrdw0uzwk7mwa9und9wu5r9ztvrnyx8w2g7gdhd6'>nevent1q…dhd6</a><br/>_________________________<br/><br/>Exactly. Thanks. 2026-08-11T20:24:56Z https://nostr.now/nevent1qqsdt9tqp845tasngxhalufm7hw06u8nsqrv220vk46pyvjgc5vr9xgzyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66cg2g6t0 In reply to <a href='/nevent1qqsxc6xl3tz3yv0xltxtgwvaa4v7n6v4cvl0m8m2tqd8lsx76esvp0smapy2y'>nevent1q…py2y</a><br/>_________________________<br/><br/>… another interface. 2026-08-01T14:38:55Z https://nostr.now/nevent1qqsxc6xl3tz3yv0xltxtgwvaa4v7n6v4cvl0m8m2tqd8lsx76esvp0szyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66cnu6lz2 In reply to <a href='/nevent1qqsrqk2nvucvsfcfg8g0697v8jnjmf4famexfr6p3utmnc60ysx27xck0fj55'>nevent1q…fj55</a><br/>_________________________<br/><br/>It’s also important to clarify that this is not a bridge to Meshtastic or an integration with the Meshtastic application layer. It simply uses the Meshtastic protocol as a transport medium. RNS packets are encapsulated into Meshtastic frames, so from Reticulum’s perspective it’s just another interface. 2026-08-01T14:38:14Z https://nostr.now/nevent1qqsyp4g4pt2kke4q68ucgxtm9wgvgxkzrgjkmqxt2wwclxl9xw37p6qzyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66cg7s40l In reply to <a href='/nevent1qqsrqk2nvucvsfcfg8g0697v8jnjmf4famexfr6p3utmnc60ysx27xck0fj55'>nevent1q…fj55</a><br/>_________________________<br/><br/>From my perspective, that dramatically lowers the barrier to entry. There are already thousands of Meshtastic devices in the wild. If those radios can be used as Reticulum interfaces without any firmware changes, Reticulum suddenly becomes much more accessible. 2026-08-01T14:37:26Z https://nostr.now/nevent1qqswp0ty4a0u66wjjy6gx6g0nlnslg4n7q3ymar7tn6dtw6tdy2vkqszyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66cwn67dv In reply to <a href='/nevent1qqsww8r9jpw4tc7slxd7xj8gxdq3megx36nlwcq2s47c65333a0py4slysv8p'>nevent1q…sv8p</a><br/>_________________________<br/><br/>…just another interface. 2026-07-31T03:15:59Z https://nostr.now/nevent1qqs856ucaha9gwwyys06xvncpvjry4l43q9eve38e2k3egt7ehjaqnqzyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66c52rj59 In reply to <a href='/nevent1qqsyym62854h30m3f06fajqqq57srgkwm2kqnge0zxvhrjr0nsk9gwsxa38ja'>nevent1q…38ja</a><br/>_________________________<br/><br/>Happy if you Check it out 😉 2026-07-31T03:08:40Z https://nostr.now/nevent1qqsww8r9jpw4tc7slxd7xj8gxdq3megx36nlwcq2s47c65333a0py4szyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66chjt64v In reply to <a href='/nevent1qqswjjwdqhlph6mnue83xtfgy02s0sj7ywhxzaxcc6tykq4qxy8kt2g96uqru'>nevent1q…uqru</a><br/>_________________________<br/><br/>It’s also important to clarify that this is not a bridge to Meshtastic or an integration with the Meshtastic application layer. It simply uses the Meshtastic protocol as a transport medium. RNS packets are encapsulated into Meshtastic frames, so from Reticulum’s perspective it’s just another interface. 2026-07-30T18:00:10Z https://nostr.now/nevent1qqsr5zulx4pzhavkwrtngq5aznnlkkwtrfqhqv4angylqctc6gch82qzyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66cjtpngv In reply to <a href='/nevent1qqswjjwdqhlph6mnue83xtfgy02s0sj7ywhxzaxcc6tykq4qxy8kt2g96uqru'>nevent1q…uqru</a><br/>_________________________<br/><br/>Of course, there are practical performance limitations. Meshtastic offers relatively low bandwidth, so large transfers will be slow. In my implementation I’ve also deliberately limited forwarding to a single Meshtastic rebroadcast (1 hop) to avoid overwhelming the Meshtastic mesh with high-volume Reticulum traffic. The goal is to make Reticulum available over existing Meshtastic infrastructure while still being a good citizen on the network. 2026-07-30T17:58:20Z https://nostr.now/nevent1qqsddjkcsrz5hdh22eru7dgw88wevtvpezh6l4u2xrwm7ml39x9wanqzyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66cehluj9 In reply to <a href='/nevent1qqswjjwdqhlph6mnue83xtfgy02s0sj7ywhxzaxcc6tykq4qxy8kt2g96uqru'>nevent1q…uqru</a><br/>_________________________<br/><br/>That’s one of the nice things about Reticulum: it’s transport-medium agnostic. The Meshtastic link is simply another transport. RNS packets are encapsulated into the Meshtastic protocol, so from Reticulum’s perspective it’s just another interface.<br/><br/>That means all Reticulum applications (NomadNet, RNode utilities, LXMF, RSH, RBBS, etc.) work without modification. 2026-07-30T17:57:54Z https://nostr.now/nevent1qqsd9xdwtntpdv5k89wnfx896z2cg44l3ptwu4jun5rphwqzju4d36czyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66ce7khrq In reply to <a href='/nevent1qqs932dk2e825n428d5at9y40ejdjruh4rvzkezzwjuyaf5pcqnctjc0x8s75'>nevent1q…8s75</a><br/>_________________________<br/><br/>more accessible to a much larger community. 2026-07-30T17:08:28Z https://nostr.now/nevent1qqs932dk2e825n428d5at9y40ejdjruh4rvzkezzwjuyaf5pcqnctjczyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66csk04uv In reply to <a href='/nevent1qqsgy4ehv7jusgdepa82ghndt45rtwh5rknqu9e0357ae4z9resdlmgmaygde'>nevent1q…ygde</a><br/>_________________________<br/><br/>One of the biggest advantages is that it could instantly give Reticulum access to the existing Meshtastic ecosystem and community.<br/><br/>The idea isn’t to replace Meshtastic or require people to flash different firmware. You simply leave the standard Meshtastic firmware on the radio and use it as a native Reticulum interface.<br/><br/>From my perspective, that dramatically lowers the barrier to entry. There are already thousands of Meshtastic devices in the wild. If those radios can be used as Reticulum interfaces without any firmware changes, Reticulum suddenly becomes much more accessible to a much larger community. 2026-07-30T17:07:26Z https://nostr.now/nevent1qqs0suxl7lk84l0myml0wrmyxm2u7n57xup5q03c354l5ff7u4xfcegzyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66cuanssw In reply to <a href='/nevent1qqst55r6dffmvyp08ks0szu6ufqjhmdmtu92m9drv582cusdmdj5mzgppemhxue69uhkummn9ekx7mp0m0h5ms'>nevent1q…h5ms</a><br/>_________________________<br/><br/>The MeshtasticInterface is now available as a standalone Python file. If Reticulum is already installed, simply copy it into ~/.reticulum/interfaces and add the configuration.<br/>👉 <a href="https://github.com/floscodes/RNS_MeshtasticInterface">https://github.com/floscodes/RNS_MeshtasticInterface</a><br/>#Reticulum #Meshtastic #LoRa #MeshNetworking #OpenSource 2026-07-30T14:32:31Z https://nostr.now/nevent1qqst55r6dffmvyp08ks0szu6ufqjhmdmtu92m9drv582cusdmdj5mzgzyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66c9g7yus I’ve added a Meshtastic Interface to a Reticulum fork. If anyone with a Meshtastic setup would be willing to test it and share feedback, I’d really appreciate it:<br/><a href="https://github.com/floscodes/Reticulum">https://github.com/floscodes/Reticulum</a><br/>Thank you!<br/><br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1ej5lyf444vqkatj9gvdmzvgukmndhcpke86mnvle0pauxpd88s7sq2f6k2" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Meshtastic</span> (<span class="italic">npub1ej5…f6k2</span>)</a></span> <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub142t785ujh97zzvnss8xm8jm8fhage8rxxjfaksmenfq8j4266xcs7ds6ue" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Meshtastic</span> (<span class="italic">npub142t…s6ue</span>)</a></span> #meshtastic #reticulum #rns 2026-07-30T09:27:19Z https://nostr.now/nevent1qqstjshlt43eca85zrwnn9tegum8sz3c0pngwq2pvp0yl58mv93xf4czyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66cr65hw3 In reply to <a href='/nevent1qqsgsaq7n8xce2agv2a7we59kt5e7gd35872hw8rwe7aw7uwevr3kjgprpmhxue69uhkummnw3ezuurpwfjhgmeww3hhwm30kj68qa'>nevent1q…68qa</a><br/>_________________________<br/><br/>Hi guys - I was thinking about zaps in general and I would like to propose this - maybe this would be an interesting approach:<br/><br/>🔥 Spark — a proposed Nostr extension for triggering native on-chain wallets directly from a profile.<br/><br/>No Lightning, no receipt event: just a `wallets` array in Kind 0 metadata and a Kind 9736 request that hands off to your wallet extension or app via deep link. Chain-agnostic by design (BTC/XTM/SUI/ETH so far).<br/><br/>PoC: <br/>Nostr Spark / Native Asset Payment PoC<br/>Nostr Spark / Native Asset Payment PoC<br/>Nostr Spark / Native Asset Payment PoC<br/><a href="https://floscodes.github.io/spark-poc/">https://floscodes.github.io/spark-poc/</a><br/><br/><br/><br/>Discussion: <a href="https://github.com/nostr-protocol/nips/issues/2387">https://github.com/nostr-protocol/nips/issues/2387</a><br/><br/>#nostrdev #tari #xtm #spark #zaps 2026-07-24T08:57:43Z https://nostr.now/nevent1qqs2upqxphmg4jz0arl5tpjtrhyr7sfaunsa27ze8fnskedpeqazz7czyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66ck5lwx5 In reply to <a href='/nevent1qqsqqqpjqx5268spm064gtw8w29d2fuevp5f2jewuvykd0dwx0v0p8spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsfwmkkd'>nevent1q…mkkd</a><br/>_________________________<br/><br/>Hi guys - I was thinking about zaps in general and I would like to propose this - maybe this would be an interesting approach:<br/><br/>🔥 Spark — a proposed Nostr extension for triggering native on-chain wallets directly from a profile.<br/><br/>No Lightning, no receipt event: just a `wallets` array in Kind 0 metadata and a Kind 9736 request that hands off to your wallet extension or app via deep link. Chain-agnostic by design (BTC/XTM/SUI/ETH so far).<br/><br/>PoC: <br/>Nostr Spark / Native Asset Payment PoC<br/>Nostr Spark / Native Asset Payment PoC<br/>Nostr Spark / Native Asset Payment PoC<br/><a href="https://floscodes.github.io/spark-poc/">https://floscodes.github.io/spark-poc/</a><br/><br/><br/><br/>Discussion: <a href="https://github.com/nostr-protocol/nips/issues/2387">https://github.com/nostr-protocol/nips/issues/2387</a><br/><br/>#nostrdev #tari #xtm #spark #zaps 2026-07-24T08:50:41Z https://nostr.now/nevent1qqsqxhguy3te0dtkml67dhrmy023rt2qkqns8und8w9nk25jrcxmt0gzyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66c760w2d In reply to <a href='/nevent1qqsvg4x7wdjgv7g5tafh5f33d5lp8076nunxdewdz6aupp294x4m0ggpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs04h6a3'>nevent1q…h6a3</a><br/>_________________________<br/><br/>Hi guys - I was thinking about zaps in general and I would like to propose this - maybe this would be an interesting approach:<br/><br/>🔥 Spark — a proposed Nostr extension for triggering native on-chain wallets directly from a profile.<br/><br/>No Lightning, no receipt event: just a `wallets` array in Kind 0 metadata and a Kind 9736 request that hands off to your wallet extension or app via deep link. Chain-agnostic by design (BTC/XTM/SUI/ETH so far).<br/><br/>PoC: <br/>Nostr Spark / Native Asset Payment PoC<br/>Nostr Spark / Native Asset Payment PoC<br/><a href="https://floscodes.github.io/spark-poc/">https://floscodes.github.io/spark-poc/</a><br/><br/><br/>Discussion: <a href="https://github.com/nostr-protocol/nips/issues/2387">https://github.com/nostr-protocol/nips/issues/2387</a><br/><br/>#nostrdev #tari #xtm #spark #zaps 2026-07-24T08:48:01Z https://nostr.now/nevent1qqsvr3s4nqgzurvxmzws06jrgfslwxnnz99h43pq9d9evlc0tg96u0szyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66cjzjfxw In reply to <a href='/nevent1qqs2llugmk49gra6fx3vmj56ztk8zjnnyxfwvd9fsexn4q2yxp5eylspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsw4a7tm'>nevent1q…a7tm</a><br/>_________________________<br/><br/>Hi guys - I was thinking about zaps in general and I would like to propose this - maybe this would be an interesting approach:<br/><br/>🔥 Spark — a proposed Nostr extension for triggering native on-chain wallets directly from a profile.<br/><br/>No Lightning, no receipt event: just a `wallets` array in Kind 0 metadata and a Kind 9736 request that hands off to your wallet extension or app via deep link. Chain-agnostic by design (BTC/XTM/SUI/ETH so far).<br/><br/>PoC: <br/>Nostr Spark / Native Asset Payment PoC<br/><a href="https://floscodes.github.io/spark-poc/">https://floscodes.github.io/spark-poc/</a><br/><br/>Discussion: <a href="https://github.com/nostr-protocol/nips/issues/2387">https://github.com/nostr-protocol/nips/issues/2387</a><br/><br/>#nostrdev #tari #xtm #spark #zaps 2026-07-24T08:46:25Z https://nostr.now/nevent1qqsfcxs4yg6j9xa7zzt6kd0zvgvdsac4klwd7xgalkzlslanzzd26rczyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66czptavq In reply to <a href='/nevent1qqsfdc8xffgxdxh3jnzytghpwspgljeg086cvsk5ggpdsduz89lga7c3q8svt'>nevent1q…8svt</a><br/>_________________________<br/><br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhyetvv9ujudp5vf5kcmrfdahzumn9wshszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0wmugh3" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>fiatjaf</span> (<span class="italic">nprofile…ugh3</span>)</a></span> You said it yourself — people should be able to send tips in any way they want. I was thinking about it and so this is my proposal: an opt-in path for those who’d rather receive on-chain in their own wallet than via Lightning. 2026-07-10T06:10:15Z https://nostr.now/nevent1qqsfdc8xffgxdxh3jnzytghpwspgljeg086cvsk5ggpdsduz89lga7czyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66cgu204q 🔥 Spark — a proposed Nostr extension for triggering native on-chain wallets directly from a profile.<br/><br/>No Lightning, no receipt event: just a `wallets` array in Kind 0 metadata and a Kind 9736 request that hands off to your wallet extension or app via deep link. Chain-agnostic by design (BTC/XTM/SUI/ETH so far).<br/><br/>PoC: <a href="https://floscodes.github.io/spark-poc/">https://floscodes.github.io/spark-poc/</a><br/>Discussion: <a href="https://github.com/nostr-protocol/nips/issues/2387">https://github.com/nostr-protocol/nips/issues/2387</a><br/><br/>#nostrdev #tari #xtm #spark #zaps 2026-07-08T13:14:55Z https://nostr.now/nevent1qqsyrcktj8y2jsyr4x4786ntw6skr5h2r22xtvn8v6qxaf5fc2llwmgzyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66c89wttn In reply to <a href='/nevent1qqsfrkvs04wh60a2ka6f3etfe203w7d9pa7n84czlelmz2gtu227glg6nngwm'>nevent1q…ngwm</a><br/>_________________________<br/><br/>🤣🤣 2026-06-24T16:41:18Z https://nostr.now/nevent1qqs82ga5c8wdspa70quar579g5hlq27tafmmvr9y7jm5xfv72wjng6czyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66cvkul8y In reply to <a href='/nevent1qqsz5q5u5vdj62wfa6rqm7ujsg85549d7a2psc662av8j3afhnxhg7grgmlg7'>nevent1q…mlg7</a><br/>_________________________<br/><br/>Just dropping this here for #xtm 2026-06-21T09:37:14Z https://nostr.now/nevent1qqsw8e4q9lxvm6zm7508tfqvfsp464xu4t4ddrv3wewpt8pygu8upyczyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66cqedse5 In reply to <a href='/nevent1qqsv03464rkkr97uksa0v86rhd8rlwqhp56jpq5axpcuqt4fsu22d7cpzfmhxue69uhk7enxvd5xz6tw9ec82csjzdchc'>nevent1q…dchc</a><br/>_________________________<br/><br/>Just introduced a design pivot for multi-asset zaps.<br/><br/>Shifting heavy crypto complexity from the client to native wallets using dynamic ⁠deeplink_templates⁠ in Kind 0. Keeps events tiny and clients asset-agnostic. <br/>#nostrdev #tari #zaps #nip57 2026-06-21T07:17:27Z https://nostr.now/nevent1qqswuty5fxj60xjz5lzw7sfs28y4sk825p0u7jktxl4uljyv63nplnczyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66cj3xnfm In reply to <a href='/nevent1qqszzl9kenr0sjlycfakrnhjatpqc2x90j75uk2ty3xzf8vnj343a6g03vq2y'>nevent1q…vq2y</a><br/>_________________________<br/><br/>Just introduced a design pivot for multi-asset zaps.<br/><br/>Shifting heavy crypto complexity from the client to native wallets using dynamic ⁠deeplink_templates⁠ in Kind 0. Keeps events tiny and clients asset-agnostic. github.com/nostr-protocol/nips...<br/>#nostrdev #tari #zaps #nip57 2026-06-20T17:04:14Z https://nostr.now/nevent1qqsz5q5u5vdj62wfa6rqm7ujsg85549d7a2psc662av8j3afhnxhg7gzyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66c0av933 Just introduced a design pivot for multi-asset zaps.<br/><br/>Shifting heavy crypto complexity from the client to native wallets using dynamic ⁠deeplink_templates⁠ in Kind 0. Keeps events tiny and clients asset-agnostic. <a href="https://github.com/nostr-protocol/nips/issues/2387">https://github.com/nostr-protocol/nips/issues/2387</a><br/>#nostrdev #tari #zaps #nip57 2026-06-20T17:03:34Z https://nostr.now/nevent1qqspz65g0elewc3hvs0nv9n4sxe53wd4unhv0m3667l8hgqt2p3c40szyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66ct5nk6w In reply to <a href='/nevent1qqszzl9kenr0sjlycfakrnhjatpqc2x90j75uk2ty3xzf8vnj343a6g03vq2y'>nevent1q…vq2y</a><br/>_________________________<br/><br/>Dropping this here so <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qy2hwumn8ghj7cnpwdehq6tnw3hkctn0wfnj7qgcwaehxw309a5kucn00qh8yetvv9uhxtnvv9hxgtcqyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6nzn5fw" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>fiatjaf</span> (<span class="italic">nprofile…n5fw</span>)</a></span> can take a look. Would love to hear your thoughts on extending NIP-57 for non-LN sovereign assets! 2026-06-18T15:37:50Z https://nostr.now/nevent1qqszzl9kenr0sjlycfakrnhjatpqc2x90j75uk2ty3xzf8vnj343a6gzyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66ca2r4c2 Idea: Let&#39;s bring native, on-chain zaps to Nostr without adding a single byte of profile metadata! 🪙<br/><br/>The trick: We can deterministically derive a Tari identity directly from our native Nostr keys. This allows us to extend NIP-57 and support sovereign P2P zaps natively in-client—no extra profile tags needed.<br/><br/>Just opened a proposal issue on GitHub. Let me know what you think: <a href="https://github.com/nostr-protocol/nips/issues/2387">https://github.com/nostr-protocol/nips/issues/2387</a><br/><br/>#nostrdev #tari #zaps #nip57 @fiatjaf 2026-06-18T15:35:02Z https://nostr.now/nevent1qqsd75wnp2ry5yqyjq4zt8u9qznxfwp3k36aedtjdmthlxu2msafwuczyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66chuflxl In reply to <a href='/nevent1qqsyvzqqsx2qvheyvgse256smcrde68nt8eukpslzsnkp5umzx7qn3gdrytsy'>nevent1q…ytsy</a><br/>_________________________<br/><br/>Word 🙌 2026-06-10T14:35:00Z https://nostr.now/nevent1qqsfgugjx7n9dfkpj2wp727a9rc235gcd7fq0xeelf0mfj05unca8wszyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66cvvzva9 In reply to <a href='/nevent1qqsp2vqtnmh06de8sjds5n2dxa4mqpmtgtdgq6pe5t7qfg0w6a2upmspp4mhxue69uhkummn9ekx7mqumree7'>nevent1q…ree7</a><br/>_________________________<br/><br/>Many people are tired of messaging apps that own your identity. So I authored a messenger client on the XMTP protocol that doesn&#39;t. No phone number, no server, no accounts — just a wallet key you control.<br/>xmes.org | github.com/floscodes/xmes<br/>#privacy #decentralized #rust #xmtp 2026-06-08T13:04:48Z https://nostr.now/nevent1qqs9uufspcwntnlp5k4vza4ua65jzatyugpmaag9g070r85rhqdvmwqzyp7tuwvqaeqr8w9e7rgz7pecr4py2aau28s8mkkyekspvadrlj66c3ky0m7 In reply to <a href='/nevent1qqsffk2z0u4jpp645a8f63afypq2wqwn4s2wuts74cx4e6q5kgvcnzspp4mhxue69uhkummn9ekx7mqc9v6jg'>nevent1q…v6jg</a><br/>_________________________<br/><br/>Absolutely. 2026-06-01T19:35:40Z