kukks

Building in the shadows for a better future.

Public Key

npub1y24gz5gwucl79vtv4ctwpysl0r5m4xyzu2rgulnr44ks3t5mt92q4nz2ad

NIP-05 Address

kukks@kukks.org

NIP-57 Address

kukks@kukks.org

Profile Code

nprofile1qqsz925p2y8wv0lzk9k2u9hqjg0h36d6nzpw9p5w0e366mgg46d4j4qpz9mhxue69uhkummnw3ezuamfdejj7qg4waehxw309aex2mrp0yhxummnw3ezucn89ua8g5al

Publishing to

nostr.wine

relay.nostr.bg

relay.nostr.band

Author Public Key

npub1y24gz5gwucl79vtv4ctwpysl0r5m4xyzu2rgulnr44ks3t5mt92q4nz2ad

Show more details

Last Notes

2024-12-20 22:19:02

- reply

I don't want to waste my time. He spends too much energy with vague, overreaching statements and fuds other people's work constantly.

2024-12-20 22:11:39

- reply

That comparison chart is completely nonsensical and obviously written with full bias

2024-11-24 20:22:36

- reply

Ego is the worst detractor to productivity.

2024-11-16 15:16:32

- reply

Easily still one of the best bitcoin product
ads ever made to me. The delivery of the ad was amazing, the delivery of the full product still needs to ship 😂

2024-11-15 20:23:21

- reply

I'm sorry Gigi, take care of yourself.

2024-11-06 21:23:28

- reply

If not quake, maybe doom?

2024-11-02 10:17:23

- reply

It's my fault for the lack of awareness. I don't promote my work much because I feel my time is best spent researching and building the tech. I rely on people to discover, understand and help promote it, which hasn't been very effective so maybe this is where I should change. I’m better with code than with words though, as the quote goes. 😁
This plugin is something I took on myself to develop but it was only the first step in the grand scheme of things. Zksnacks supported me immensely and we were going to take over the world, where every spend was actually a coinjoin, until the samourai situation unfolded.
There's still hope, but it will have to execute differently now. The tech is sound and is agnostic of use, whether it is privacy, scaling, or both.
Just need to get the message across to get the right resources and connections.

2024-11-02 06:39:11

Everyone was too busy focusing on postmix tools to realize you don't need a postmix tool if everything can happen in a mix!
PSA: @nprofile…kvl9 with the coinjoin plugin has been able to handle payment batching in coinjoin directly since day one of its release.
And a (not so) secret project that I have been working on for years will soon transform coinjoins into one of the best payment protocols out there with massive cost savings and privacy gains for everyone involved
#nevent1q…pw9p
Previous mentions about this: https://twitter.com/MrKukks/status/1619294492854747138

2024-10-25 05:09:53

- reply

Link? It's zerolink, so there should be at least different identities for each output + one for all inputs iirc

2024-10-24 03:51:36

- reply

A little part of me dies at every upstream merge, but your code quality has gotten orders of magnitude better lately! I just had to hack around the old stuff so much that it is now a much harder job maintaining it.

2024-10-22 19:19:59

- reply

It was a well known address. Ricochet was a very sloppy mess that relied heavily on exchanges also being sloppy and too slow to detect the very clear heuristic. Ricochet should have used paynyms, but also made each hop a more realistic tx pattern.

2024-10-17 19:51:18

- reply

Savage but awesome!

2024-10-17 06:18:34

- reply

I don't think it is just about a simple direct cost-per-enemy, but rather to spread hope of an alternative for Russians than dying in the frontline in a senseless war.

2024-10-11 21:23:34

- reply

Hit the 69th minute on this note

2024-10-11 18:44:14

- reply

I'm not saying it isnt, it obviously is. But it's not going to be the next firebase/parsley database with the same performance profile that you can get for free with the extra open protocol magic. You should definitely build your own proprietary, optimized backend but the point is that the "less optimal" nostr req is still there to not gatekeep data flows

2024-10-11 16:00:57

- reply

The " other stuff" in nostr are just different constructs of notes. If you're using nostr as simply a database for your app then you're just not aiming for real usage. But being able to interop through a common format in a well defined communication layer is the golden goose.

2024-10-10 16:00:23

- reply

Jealous of the event attendees, have fun! Guess I'll just play with some nuts at home..

2024-10-09 21:23:17

- reply

Cell phone connections are probably correlated to the imei of the sim card, and nat only hides internal devices but still gets an ip as a collective?

2024-10-09 21:13:48

- reply

Would have said yes few years back but got too much cooking in the shadows now 😁

2024-10-09 21:12:33

- reply

Oh sure, i just perceived that the initial post was insinuating "just use a vpn" was the best choice.
And no debate over the whirlpool one 😅

2024-10-09 20:59:22

- reply

You are overestimating the effectiveness of a vpn here. The reality here is that we are focusing on very sophisticated difficult to execute attack vectors. The vpn is your only shield for all identities pushing to the relay here. Sure, https/wss encrypts the content, but an attacker that has compromised a vpn operator will listen to events on nostr relays that the vpn has connections to by its users, and can artificially delay data transfer to do timing analysis on events to correlate which ip sent which events with which pubkeys.

2024-10-09 20:39:43

- reply

I like the approach of fulmo and nostr unconfs, where they simply rotate across the globe. That way you can reach the widest diverse audience and speakers.

2024-10-09 20:34:02

- reply

Correct me if I am wrong, but wouldn't using something like rise up vpn, a third party operated service, give each third party all the data needed to correlate everything?
A vpn operator knows every source ip and their every destination and action and the promise of no logging is just that, a promise.
This is literally why people use Tor, and generate separate tor circuits per required identity.
PS, regarding wabisabi, circuits are constructed in advanced to prevent delays around tor circuit execution (although I think this is overkill), but also input, output registrations and anonymous credential reissuances has randomized delays built into it by design to prevent such correlation. Happy to answer more if you want to know more.

2024-10-06 07:30:09

- reply

Whole separate world of bitcoiners outside of US that will never get (American mainstream) spotlight because of this too

2024-10-02 11:39:50

- reply

Just try? Theoretically supported but haven't tried.

2024-10-02 06:12:25

- reply

Not exclusively ark related actually, but it does tie in very well!

2024-09-30 12:40:28

- reply

Never left 😅

2024-09-27 21:03:38

- reply

I did, seems like I got a case of mad bull disease🐂

2024-09-27 10:58:33

- reply

https://image.nostr.build/8e55d4c7abb66f966567c397b8073626b9cbebec23c607d80f643f0b13183a3b.png

2024-09-26 21:09:24

A new era of bitcoin privacy and payments is coming. Fuck, I'm suddenly so bullish.

2024-09-14 10:07:30

- reply

Without going into any of the expected books that are inevitably mentioned into these circles like 1984 (which also had a good impact on my resolve around my work focus), I think "the boy who was raised as a dog" left a profound mark on me. https://mindsplain.com/mindsplain-book-review-the-boy-who-was-raised-as-a-dog/

2024-09-09 19:18:09

- reply

Xm3 is still just so good, and the last Gen of the folding design. Every newer model between Sony and bose ditched it to look more hip so they're even more likely to snap in your bag..
But for in-ear, I really love the jabra ones. Just make sure to not buy their oval shaped tip variants as you'll need to buy third party tips for superior noise cancelation

2024-09-06 19:38:47

- reply

Lol wtf, freemasons is just a wannabe macho cigar club not a satanic cult 😂.
And hey, if we're going there, the true church of satan is probably the most bitcoin philosophically aligned organization ever.
https://www.churchofsatan.com
Just read their intro text and tell me I'm wrong.

2024-09-04 08:02:17

- reply

But have you cooked every single of them?

2024-09-02 19:21:20

- reply

https://youtu.be/TIy3n2b7V9k

2024-08-25 04:19:30

- reply

I always find these scare tactics super silly. It's such a trivial tool to rebuild and execute in a million different ways. The endless legal hell can't be worth it

2024-08-23 15:56:58

- reply

Everything always sucks eventually

2024-06-15 11:29:49

Dystopian resistant.
https://mempool.space/tx/f86a753247eb96405cc9b20845915e2f6fb52283d0705bd715ff292178d97871

2024-06-09 16:06:46

- reply

Just send directly to the pubkey, maybe with a tweak with your pubkey and note id?

2024-06-06 20:13:25

- reply

Thank you for this, fixed a bug in the nostr plugin for btcpay and released!

2024-06-06 09:44:48

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 18: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 06:01:55

- reply

Grow up and stop being so salty.

2024-05-02 17:17:26

- reply

Private comms over nostr is unsolvable (user and relay level) without bundling in tor or another privacy network

2024-04-19 16:38:07

- reply

Glad I'm not the only depressed pessimist here

2024-04-13 09:37:21

- reply

Amazing! Your website was so helpful to me way back

2024-04-12 07:10:05

- reply

Just add a tag for content type and go nuts!

2024-04-10 08: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 07:34:54

- reply

The dreaded jaf arrays will forever be your legacy

2024-04-09 12:48:16

- reply

I'm shocked

2024-04-09 11:52:07

- reply

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

2024-04-09 11: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 18: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 18: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 17:58:48

- reply

That one's my fault, sorry @fiatjaf 😂

2024-04-08 06:12:56

- reply

It doesn't work in that direction

2024-04-05 05:14:08

- reply

This is the only correct answer

2024-03-07 09: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 16:42:05

- reply

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

2024-02-15 06:04:14

- reply

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

2024-02-04 21:25:02

- reply

Will you be selling this?

2024-01-13 11: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 11:02:46

- reply

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

2024-01-12 17: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 09: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 13: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 12: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 18:02:03

- reply

What did you use?

2023-09-22 17: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 07:25:14

- reply

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

2023-08-13 09: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 12: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 17:58:29

- reply

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

2023-06-25 18:05:25

- reply

But sir you should use the new btcpayserver checkout

2023-06-23 18:12:47

- reply

Nein*

2023-06-19 05:14:55

- reply

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

2023-06-19 05: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 16: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 08: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 07: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 04:43:51

- reply

https://t.me/nostr_protocol/5647

2023-06-15 20: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 19: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 19:19:01

- reply

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

2023-06-15 19: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 08:12:20

- reply

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

2023-06-14 06: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 08: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 14:11:58

- reply

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

2023-05-28 16: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 11:35:14

- reply

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

2023-05-09 18:15:58

- reply

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

2023-05-09 07:31:45

- reply

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

2023-05-08 19:41:38

- reply

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

2023-05-08 19:40:07

- reply

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

2023-05-08 19: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 19:16:41

- reply

*force close*

2023-05-08 12:36:10

- reply

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

2023-05-08 11:14:53

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

2023-05-07 16:33:48

- reply

Do you code in a bee suit or what?