kukks

I come bearing gifts.
Introducing DotNut - a C# library implementing the Cashu protocol
https://github.com/Kukks/DotNut
The best part about this is the naming opportunities honestly. 😂

2024-06-04 20:41:06

- reply

Zksnacks was built through years of sweat and blood by @nopara73 with no funding. Everything had to be researched and built from scratch, with not even a fraction of available research, resources and tooling. The amount of work that has been put into it and over such a long span of time is incomprehensible unless you've seen it unfold in front of you leading to the giant zksnacks ended up being.
Mutiny's journey is still young but what they've built on a relatively small startup budget is insane.
Your coinjoin protocol is barely a protocol and is so basic and missing key aspects that nobody that's been in this long enough will take seriously. And if you want their level of resources commit to it and raise money like mutiny did.
Every post about coinjoin, you spam/hijack shilling your stuff. It's rude, and really annoying.

2024-06-04 08:01:55

- reply

Grow up and stop being so salty.

2024-04-19 18:38:07

- reply

Glad I'm not the only depressed pessimist here

2024-04-13 11:37:21

- reply

Amazing! Your website was so helpful to me way back

2024-04-12 09:10:05

- reply

Just add a tag for content type and go nuts!

2024-04-10 10:37:25

- reply

It's in our plans to create a bridge between the pos app and nostr markets but we're a bit overloaded for now

2024-04-10 09:34:54

- reply

The dreaded jaf arrays will forever be your legacy

2024-04-09 14:48:16

- reply

I'm shocked

2024-04-09 13:52:07

- reply

I'm the best influencer ever is what you're saying.

2024-04-09 13:38:23

- reply

It was way back when we were trying to come up with a similar deterministic backup and key derivation: https://t.me/nostr_protocol/6910

2024-04-08 20:57:46

- reply

I'm simply a realist with all my dreams of perfect fungibility and freedom slowly drowning under the sands of time

2024-04-08 20:48:38

- reply

As @npub1der…xzpc knows very well, I'm ready when you are to bring the pessimism back into your life

2024-04-08 19:58:48

- reply

That one's my fault, sorry @fiatjaf 😂

2024-04-08 08:12:56

- reply

It doesn't work in that direction

2024-04-05 07:14:08

- reply

This is the only correct answer

2024-03-07 10:41:46

The state of the Bitcoin community in a bull market is such an embarrassment. Principles, and freedom tech all thrown out so that we can simp for the statists and their corrupt financial instruments, all for a few extra digits.
Do better

2024-03-06 17:42:05

- reply

How does it work offline? Doesn't one need to reissue to verify and prevent doublespend?

2024-02-15 07:04:14

- reply

I believe this is the phenomenon commonly known as "being uncomfortable"

2024-02-04 22:25:02

- reply

Will you be selling this?

2024-01-13 12:10:08

- reply

And once you get wabisabi payjoin, it gets even better, because the receiver breaks down the payment directly to denominations (if they want) and the sender wouldnt even know where his payment went, while still having a proof of payment! This avoids requiring yet another coinjoin transaction to break the link from sender and receiver. And even better, the receiver doesn't even learn the coins used that fulfilled the payment!

2024-01-13 12:02:46

- reply

Sir, but I already built it in BTCPay since February last year 😭

2024-01-12 18:38:03

- reply

Yup! We added this hidden feature inside the btcpay wallet years ago when I found out that bitcoin is an officially supported uri schema 😁

2023-12-21 10:21:21

The @npub155m…dcvg coinjoin plugin now supports automated, private coin consolidation during low-fee markets.
https://void.cat/d/Cd8y8XNRyvTYhLRztZcBkG.webp

2023-12-18 14:03:28

- reply

At this point, it's not that big of a deal to not ask for it, maybe we can drop the requirement for the info.

2023-12-15 13:11:45

- reply

I think it's mostly people running older versions that are hitting this now. I would wait a few more months. my lnurl lib has it disabled by default (there is an option though)

2023-10-01 20:02:03

- reply

What did you use?

2023-09-22 19:34:56

- reply

There's something really special about this project. It's very addictive and pleasing to see these developments happening as ongoing threads

2023-09-22 09:25:14

- reply

Happy to discuss my coinjoin plugin and rationale behind it in person instead of this unproductive attitude.

2023-08-13 11:50:02

On July 28th, I submitted my proposal to @HRF for the Serverless Payjoin bounty: Payjoin over Nostr.
You can read the protocol addendum here: https://github.com/Kukks/BTCPayServer.BIP78/blob/nostr/BTCPayServer.BIP78.Nostr/README.md
The proposal is incredibly simple in nature, just as BIP78 was designed to be, to increase adoption chances. All logic within the Payjoin protocol stays the same, so the version is still 1. It is asynchronous (receiver can process later when back online), encrypted (communication is end-to-end encrypted), and lightweight (no server requirement, leverages existing Nostr network).
In addition to this, I also added building blocks for a new experimental addition: Nostr Payjoin Market.
If your wallet supports receiving Payjoin, you can share a static payjoin endpoint using the Nostr Coinjoin Discovery protocol (https://github.com/nostr-protocol/nips/pull/384). Other wallets, which support Payjoin but want to send money to wallets that don't, can use these static endpoints to enhance their transactions. The goal? Make every transaction to every wallet a coinjoin.
See the sample wallet code and additional detailed description: https://github.com/Kukks/BTCPayServer.BIP78/tree/nostr/BIP78SampleWallet
See quick video demo of prototype:
https://youtu.be/WASFXMue2tI

2023-06-29 14:58:03

I've often said that social Nostr is the most boring variant of what can be done, but even that isn't boring! It's beautiful seeing clients that can mimic every other closed platform's UX, but are still interoperable.
Reddit, Facebook, Twitter, Twitch, etc.
Nostr is everything!
This is really cool: https://live.snort.social/live/naddr1qq9rzd3c8qcrxwfexy6qygrrle333hzctq70u95pp7rd6z0p307hd24uyjsqs88zs4hnxpgya5psgqqqwenscgn3np

2023-06-27 19:58:29

- reply

We released that fix in the fix release at btcprague breakfast 😂

2023-06-25 20:05:25

- reply

But sir you should use the new btcpayserver checkout

2023-06-23 20:12:47

- reply

Nein*

2023-06-19 07:14:55

- reply

This is basically the sybil protection of joinmarket, using fidelity bonds

2023-06-19 07:14:10

- reply

My relay implementation supports this but I fear it would be too much of a ux issue, and it requires on a balance mechanism within the relay

2023-06-17 18:57:54

- reply

In btcpay we have a concept of pull payments where a store can generate one with a specific amount and currency and once you share the url to it, another wallet or service can pull from it until the threshold is reached. Even has a feature so that it resets the amount at intervals, so would work great with this kind of thing. Only issue is that it's yet another api protocol that would need to be supported by wallets and services

2023-06-16 10:12:19

- reply

This is easily becoming the best nostr bot. Would be cool if we can get some sub protocol to define "radios" or "playlists" through sequential notes

2023-06-16 09:08:07

- reply

Not violent enough, let's come up with a loophole. Appeasing gatekeepers never works out in the end, but an alternative entrance does.

2023-06-16 06:43:51

- reply

https://t.me/nostr_protocol/5647

2023-06-15 22:05:47

- reply

Yes, unfortunately the pseudo code worked but the reality of how nostr was used was different entirely long term (please appreciate how long it took me to find this message)
https://i.nostrimg.com/045cd8fba6cf7e0a13d0af0dfaf9c70f832a03ffe4b6a1653d48d0ce145f4c28/file.jpg

2023-06-15 21:20:22

- reply

Why write code at all? I should be at 0 lines and just force @fiatjaf to keep going for all of us!

2023-06-15 21:19:01

- reply

No, but there is a tweetduck open source clone of tweetdeck that we can potentially port easily

2023-06-15 21:18:16

Working on massively simplifying my relay code of NNostr https://github.com/kukks/nnostr. Recently, @lontivero asked me why my relay logic was so different to the rest, so here is my story:
Back in 2021, we had to do assumptions on how clients would utilize subscriptions and filters. There were only
A handful UI clients back then doing mostly the same thing and realistically 0 users as all the notes were just tests. Would everyone generally just create identical subscriptions? Would they have massive filters sets per subscription? Would filters be a template that everyone mix and matched into subscriptions? Was anyone even going to use any of this?
As usual I went nuts and started building it super optimized from the get go. Every filter from every subscription was hashed and used as an identifier so that no duplicate sql call would be needed when users requested the same filters.
Realistically though, nip01 still needed to mature and the filter spec gradually changed to introduce more convenience, such as paging and date ranges. This made writing clients way more efficient, but unfortunately made my optimizations just a bunch of crazy useless magic as filters were always different due to more precise query capabilities.
I'm still happy with my relay code though, it comes with unique features such as a builtin balance system, fee charge on new keys and on per event basis, dynamic event fee based on event size, a chat bot for administration, and other fun stuff.
Soon I'll be changing the filtering code to a more simplistic style, and I'm hopeful to eventually also find some more crazy stuff to build for it! I do have some interesting client side nostr bitcoin stuff being prototyped on the other end 😉
Always looking for feedback and ideas, feel free to reach out!

2023-06-14 15:57:13

- reply

One hell of a bounty 🤣

2023-06-14 10:12:20

- reply

Actually it's from the tweetoshi guys. Tweetdeck something else entirely

2023-06-14 08:26:41

- reply

Currently fixing my relay as it needs a few quality of life improvements (it was designed with nostr protocol as at 2021 when there were no users, few clients, and different nip1 parameters) so assumptions were made for optimizations).
But yes, I suggest an update first. I'm still heavily iterating on functionality and the btcpay plugin system is still in its infancy which causes incompatibility between versions of plugins and btcpay.
In the meantime, I'll create a dedicated channel somewhere so that BTCPay coinjoin users can provide direct feedback. Unsure if it should be on nostr, or our mattermost server (https://chat.btcpayserver.org)

2023-06-12 10:05:34

- reply

Yes, it's there but I'm still tweaking additional stuff around my nostr library to optimize things. Also released a standalone app that manages your Wasabi wallet to use it but we need a new wasabi release first

2023-05-31 16:11:58

- reply

https://media1.giphy.com/media/3CiLrTgKkqL0k/giphy.gif

2023-05-28 18:51:37

- reply

I read somewhere that it is currently closed source, does not use tor, and also sends then xpub for tracking to their server. If that's true, it would be insane to recommend it

2023-05-18 13:35:14

- reply

Please note that Wasabi still needs to do a new release for this to work :)

2023-05-09 20:15:58

- reply

This us this https://github.com/lnurl/luds/pull/203

2023-05-09 09:31:45

- reply

https://i.imgur.com/LdUSUZU.png
Primal.net and Plebstr render the same way

2023-05-08 21:41:38

- reply

Did it again, can see the different in amtheyst @npub1pls…kx8j

2023-05-08 21:40:07

- reply

Plebstr though I'm switching between amethyst and it constantly so not sure which one I used then 😅

2023-05-08 21:21:57

- reply

Always hard to compete with centralized solutions that offer smooth experience as a dedicated team is there to manage the heavy lifting...
But we do our best to still offer the best anyway, and we have some insane things planned to solve these issues once and for all, but resources are tight and we're a small team that live on ramen. 😂

2023-05-08 21:16:41

- reply

*force close*

2023-05-08 14:36:10

- reply

High fees also make channel settlement more fragile. LN is not there yet as a full solution :(

2023-05-08 13:14:53

Updated the btcpay nostr plugin, zaps should be more stable now, but need some help testing plox

2023-05-07 18:33:48

- reply

Do you code in a bee suit or what?

2023-04-30 20:09:22

- reply

I think there is a sort by contributor and show ranking settings on the crowdfund app that were made specifically for this usecase :)

2023-04-25 11:59:36

- reply

>dergigi idea
https://media1.giphy.com/media/W0c3xcZ3F1d0EYYb0f/giphy.gif

2023-04-24 20:14:58

- reply

Actually there is some counterparty risk, if you stay offline too long (and don't use watchtowers)

2023-04-24 20:12:22

- reply

Yeah I had the same misinterpretation too in the initial btcpay nostr plugin. Just released a new version today getting rid of all requirements (all existing Ln addresses become zappable on install)

2023-04-24 20:10:37

- reply

Welcome to our timezone 😉

2023-04-24 20:06:45

- reply

You can also host btcpay on a local, private server 😉

2023-04-24 20:04:33

- reply

As of the latest version of nostr plugin, you just install it and make sure to have a lightning address and you're golden.

2023-04-17 00:10:42

- reply

Would be cool to enable some of the btcpay plugins on the voltage btcpay offering 💡

2023-04-15 10:03:48

- reply

NNostr has naddr support too as of a few weeks ago sir

2023-04-15 08:52:14

- reply

Thanks for the feedback. Can you open an issue on https://github.com/Kukks/BTCPayServerPlugins so I don't forget?

2023-04-14 15:27:25

The initial version of lightning prisms in #[0] is out!
https://i.imgur.com/8ElyPTA.png
#[1]

2023-04-14 15:21:10

- reply

Where is this? My NNostr lib has its own Bech32 encoder and doesn't have that check

2023-04-14 07:11:59

- reply

I was under the assumption that the nostrpubkey provided in the lnurlp should match the nip5 or the user being zapped so that the payment request is actually receipted by that same user? Maybe we cna make the nip a bit clearer if that isn't the case.

2023-04-13 20:25:13

- reply

Wtf? I assumed it was supposed to have been signed by the zapper else anyone can just lie about zaps from everyone?

2023-04-13 20:21:33

- reply

Yeah sorry, protocol design unfortunately :(

2023-04-13 15:59:58

- reply

lol no

2023-04-13 15:59:34

- reply

They are different "prisms". Each source defines its own splits

2023-04-13 15:23:46

- reply

Tell me about it..
https://i.imgur.com/rDfGOqL.png
https://i.imgur.com/Dwr9mtR.png

2023-04-13 15:21:27

- reply

Yes definitely that. I can see pablo's zaps on you. I guess my batching also helps with your dopamine addiction <3

2023-04-13 15:15:19

- reply

oh god, please don't make me go back

2023-04-13 15:13:09

I was promised zaps; where are my zaps?

2023-04-13 15:01:51

- reply

There is a 2 min batching period (or if >10 zaps) to reduce server rape.

2023-04-13 13:09:56

- reply

baby steps 😂

2023-04-13 12:58:53

Coming soon 👀
https://void.cat/d/GjScxXQLV98gYxNn6Fa7zj.webp
cc #[0]
#[1]

2023-03-28 15:05:18

- reply

I find code to be my easiest form of communication 😅

2023-03-24 01:10:17

- reply

Beats my paint variant any day 🤣

2023-03-22 16:46:17

- reply

The most boring part of nostr is the social media part. A lot of things can be done without nostr using some alternative complex magic but the beauty of a unified generic protocol that everyone can pickup easily is priceless.

2023-03-22 09:35:33

- reply

It's already out, just install btcpayserver and use the new coinjoin plugin 😁

2023-03-22 09:34:48

- reply

I'll publish a NIP on the exact specs soon; also working on a standalone tool to configure wasabi config with a UI

2023-03-22 09:32:56

- reply

oh shit, i didn't know, but yes 😂

2023-03-22 07:38:07

- reply

How does a relay force a client to show an ad? How do you know that a client actually shows the ad instead of lying?
I think the incentives here are tricky. In your definition, you assume a client and a relay have a trusted relationship to prevent malice.
This is more suited on a client and user relation. Relays need a different approach imo

2023-03-14 19:46:09

- reply

We pair programmed it together

2023-03-14 19:45:40

- reply

#[3]

2023-03-14 18:57:34

Ok guys, after 2 years of being lazy I finished my relay 😂
https://github.com/Kukks/NNostr
Looking for testers!
Supports payment to register, payment per event, and payment per event size, via btcpay

2023-03-10 08:55:57

- reply

wow, jealous of your tshirt weather

2023-03-09 19:14:36

- reply

Don't quit your job has been the conclusion of many asking that question over the years 😂

2023-03-08 13:07:56

- reply

Maybe try the nip21 nostr: scheme?

2023-03-06 20:40:08

- reply

They are rejected from joining the coinjoin round. All coinjoin protocols today are atomic in nature and incapable of stealing funds.