pnk

{ "id": "a42b9141961e4a9bf0bd3f92621ad104e84e6c63ecc0ed18a2535e1308bce4f1", "pubkey": "8c081a7cb6034e8a056dfd76d4eb0f5cddd18587b513f6c681fbd8940fe83002", "created_at": 1786868177, "kind": 0, "tags": [ [ "alt", "User profile for chrizzz" ], [ "name", "chrizzz" ], [ "display_name", "chrizzz" ], [ "picture", "https://blossom.ditto.pub/e588a891ace0f71f9bb81f1c1ecf1346721434e3e747caa462bb5dec187aae09.svg" ], [ "banner", "https://blossom.ditto.pub/07ddf3853bd482555a50239ed450adca46581e5db31fbb986153193d27d99c06.svg" ], [ "about", "iykyk" ], [ "nip05", "[email protected]" ], [ "lud16", "[email protected]" ], [ "client", "Amethyst" ] ], "content": "{\"pubkey\":\"8c081a7cb6034e8a056dfd76d4eb0f5cddd18587b513f6c681fbd8940fe83002\",\"name\":\"pnk\",\"display_name\":\"pnk\",\"about\":\"iykyk\",\"picture\":\"https://blossom.ditto.pub/e0a327b25d3dd9005118f27491ec96865a4caae90f01c6391de11a56c15fc55a.png\",\"banner\":\"https://blossom.ditto.pub/07ddf3853bd482555a50239ed450adca46581e5db31fbb986153193d27d99c06.svg\",\"nip05\":\"\",\"lud16\":\"[email protected]\",\"social\":{\"follower_count\":74,\"following_count\":396},\"stats\":{\"video_count\":5,\"horizontal_videos\":0,\"vertical_videos\":5,\"note_count\":12,\"reaction_count\":120,\"comment_count\":36,\"repost_count\":1,\"first_activity\":\"2025-11-15T14:58:03Z\",\"last_activity\":\"2026-04-28T06:14:11Z\",\"total_events\":177},\"engagement\":{\"total_reactions\":12,\"total_comments\":0,\"total_reposts\":0,\"unique_reactors\":8,\"unique_commenters\":0,\"unique_reposters\":0,\"total_loops\":48.58333333333334,\"total_views\":203},\"displayName\":\"pnk\",\"website\":\"\"}", "sig": "68c82b6c3f80975f65629fe43b877464d8c408af87d15563b7fcdf52d5b16388109df9311cd99bd3e6f5cb52d7be147b9c9ab7df7feb174489c728be44515c9e" }

Last Notes

2026-09-12 16:05:56 UTC

- reply

I don't think 10% is disproportionate. There was a bug that all Bitcoin could be taken. What would be appropriate in your opinion?

2026-09-12 13:07:17 UTC

- reply

you mean use and recommend like coldcard?

2026-09-11 06:19:11 UTC

- reply

Clarkson's Farm

2026-09-11 06:00:35 UTC

- reply

timing
#nevent1q…g09r

2026-09-07 09:05:27 UTC

- reply

Let's ask @npub1xr7…2gqh why he left

2026-09-07 08:55:31 UTC

- reply

a little too cocky

2026-09-07 08:49:30 UTC

- reply

Bluetooth keyboard + mouse + Android desktop mode

2026-09-04 14:06:49 UTC

- reply

We now

2026-09-04 14:03:02 UTC

- reply

Maybe now is the time to ditch Telegram?!

2026-09-02 14:25:40 UTC

- reply

I think I saw it further down my timeline

2026-09-02 14:25:10 UTC

- reply

So its not just me

2026-09-02 06:41:07 UTC

- reply

you're joking.. that stupid number in the picture is the ping?! i couldn't figure it out

2026-09-02 06:38:08 UTC

- reply

your tits have spoken

2026-09-02 06:34:40 UTC

- reply

that's why divine is good

2026-09-02 06:21:50 UTC

- reply

TIL littlefs

2026-09-02 06:14:38 UTC

do you ever want to unfollow an account just because you don't like the avatar?

2026-09-02 06:13:17 UTC

- reply

what's the current one?

2026-09-02 06:05:50 UTC

- reply

2% up it's $100 now, joke's on you

2026-09-02 05:58:03 UTC

- reply

more like a mountain of fuckers

2026-09-01 19:01:51 UTC

- reply

"residual hardware failures that are likely related to the damage suffered from the overheating incident last week"
https://status.proton.me/incidents/lj22kf1nc8yz

2026-09-01 14:15:26 UTC

- reply

People want to be where their friends are, just ask my wife

2026-09-01 14:10:09 UTC

- reply

Yeah people brought this up during the Coldcard Incident of 2026

2026-09-01 08:21:57 UTC

- reply

#nevent1q…z09f

2026-08-31 14:40:43 UTC

- reply

How much would these tokens be?

2026-08-31 14:17:44 UTC

- reply

Haha same
#nevent1q…vadv

2026-08-31 14:17:18 UTC

- reply

#nevent1q…vadv

2026-08-31 14:17:07 UTC

- reply

Peach at a Crossroads
A letter from our founder.
Dear Peach users, Peach community,
You have been loving Peach since 2022.
Today, Peach is at a crossroads.
Let me rewind the journey with you.
How Peach started
I am Bitcoin class of 2018. (@proofofsteph talking.)
That year I went down the rabbit hole. 2019 was the maxi year. Bitcoin just blew my mind from so many different perspectives. I felt like I had found my crew and the right catalyst to help improve the state of the world. I was thinking about Bitcoin 24/7, traveled to so many meetups and conferences all over the world. Working in my fiat job wasn't a good use of my time and energy anymore. I had to align my brain power with my economic activity. How could I contribute? I am a builder, a leader and an entrepreneur at heart.
And just like that, Peach started in my head in 2020.
I initially built Peach for myself. How to acquire Bitcoin "the good way", without sacrificing privacy and security, but still through an easy-to-navigate platform?
The space was wide open. On one hand, I saw a bunch of trading platforms… Kraken, Coinbase, etc. It really sounded like it was for the crypto bros and the traders. On the other hand, I saw some smaller brokers, often founder-led. Really cool options, but most still required KYC and were not supported on mobile. And then I saw peer-to-peer marketplaces. Interesting choices to stack sats: KYC-free, decentralized order book meaning no honeypot of data, and many payment methods available including local ones.
And here enters Peach.
What Peach was built to be
A cool and approachable everyday brand. A brand that is welcoming to your wife, sister and grandma.
A mobile-first marketplace built from scratch.
The best peer2peer experience in Bitcoin. A product thought through in every corner for the user to feel like it's seamless, easy, secure and even fun. In Peach, the product is doing the tough work behind the scenes, the user just gets guided by the flow.
A back-end infrastructure for the team to manage dispute resolution, directly inside the users' app.
All in self-custody, with an embedded wallet built with bdk, encrypted payment data and chat messages with the user's PGP key.
And a KYC-free model, with a company registered in Switzerland!
This is the last point I want to talk about today.
KYC-free… and legal
KYC-free!!! 🤯 AND legal with regard to the dear fiat government laws!
I absolutely didn't want to open a business where the company would be responsible for the user's funds.
I absolutely didn't want to open a business where compliance would be my full-time job instead of product building.
So, miraculously, I found a way with the Swiss regulators. Back in 2022, I worked on a compliance case where I argued and presented the following:
Peach's trades are purely bipartite. The seller funds the escrow with their own keys and the buyer signs a message confirming that the release address belongs to them. This is done under the hood when using the Peach wallet, and the user does it manually when using an external wallet.
The escrow mechanism and role are purely technical, to ensure the trade's safety. The escrow is not a third economic party in transferring funds. All the outputs of the escrow are predefined before the contract between a buyer and a seller starts, and the output can't be altered. Even in the cases where the seller loses a dispute and the funds have to be sent to the buyer without the seller's signature — which happened at a rate of 0.03% over the past year — the sats are sent to the buyer one hour after Peach gets a single sig of the escrow (4320 blocks after the escrow creation date).
The unique app device ID is hashed and stored, ensuring one device is one account.
The payment data are hashed and stored, ensuring one person is one account.
Based on those compliance mechanisms, Peach was allowed by a Swiss SRO in 2022 to run a KYC-free marketplace with daily and monthly trading limits.
What changed this year
Peach got licensed in 2022 and got audited successfully by an independent audit company in 2023, 2024 and 2025.
But this year, the regulator has decided that the rule of yesterday is not the rule of today. You know… 1984 and all. What was true yesterday is not true today.
So, last month I received a letter. Despite a successful independent audit, the regulator — for an unknown reason — is arguing to requalify and reconsider the compliance agreement that they themselves approved some years ago.
I am not gonna lie to you, I knew from day 1 that it would happen one day or another. I often tweet "Stack sats while you still can" for a reason.
I am not giving up and complying yet. At least not without answering to the regulator. I will be fully honest too: if I lose the argument, I won't go against it either. Peach has been a legal business since day 1, and I intend to keep it this way.
What happens now: escrow-free, temporarily
While the assessment of the situation is ongoing, we have decided to pause the current Peach escrow model.
Meanwhile, and temporarily until we get the final ruling, we have decided to keep operating… escrow-free.
Only the following users will be able to create sell offers:
KYC'd users
Special users that we whitelist manually (currently no one is whitelisted)
Users with zero lost disputes AND more than 60 trades as a seller
Users with zero lost disputes AND more than 30 trades as a seller AND more than 80 trades in total
One detail: if a user is not KYC'd, they cannot be in more than 1 trade at a time. This is a protection against one bad seller trying to scam multiple buyers at once.
The in-app dispute system will still be available to help out, but Peach won't have a signature in the escrow anymore.
We will also still take 2% fees out of the release transactions… to pay our bills, you know.
The crossroads
I don't know what the future holds for Peach. What I know is that Peach is not just a marketplace. Peach is a brand, a reputation, a user base and a community.
Peach is now at a crossroads.
The p2p marketplace may or may not continue as usual with an escrow model.
Maybe the time has come to diversify. Peach is ideally positioned to develop a suite of self-custodial services, to become the Bitcoin companion you'll recommend to your wife, grandma and sister.
Maybe this route will have to continue without me.
The path will unfold over the coming weeks. I will keep you posted.
Thanks.
August 31st, 2026

2026-08-31 14:12:17 UTC

- reply

Sounds like fake news

2026-08-31 09:25:00 UTC

- reply

Never heard this before

2026-08-31 09:10:16 UTC

- reply

Put relays behind Tor without contact addresses

2026-08-31 08:46:57 UTC

- reply

I have JIT disabled. The crash seems to happen in libmonochrome_64.so and I saved the log file in case you want it

2026-08-30 17:12:59 UTC

- reply

typo of the year

2026-08-30 17:12:00 UTC

- reply

it's coming through the mostr bridge.. zap @npub1hxx…g75y instead

2026-08-30 17:09:30 UTC

@npub1hxx…g75y lately my Vanadium crashes a lot (not every time) when visiting https://www.bitrefill.com I tried to look at the log but it's very long

2026-08-28 08:23:30 UTC

- reply

Everyone's eating taco bell on divine now

2026-08-27 17:47:49 UTC

- reply

Retest of..?

2026-08-27 17:40:06 UTC

- reply

ghey

2026-08-27 08:14:56 UTC

- reply

Yes works again 🤝

2026-08-27 07:23:04 UTC

@npub1ktt…yhz0 wss://nostr.oxtr.dev seems to be down

2026-08-27 06:48:42 UTC

- reply

interesting. ok i need to experiment a bit more with that then. thanks.

2026-08-27 06:45:21 UTC

- reply

@npub1v0l…qj49 you have 4 read relays and 2 don't work and 2 don't allow me to post

2026-08-26 17:38:35 UTC

- reply

but you are connecting to another host, yes? tmux in the terminal gets killed?

2026-08-26 08:13:10 UTC

- reply

https://xcancel.com

2026-08-25 13:11:16 UTC

- reply

Will try, github doesn't like my account. Is there an official gitworkshop.dev copy? Don't know who or what Five is:
https://gitworkshop.dev/npub16p8v7varqwjes5hak6q7mz6pygqm4pwc6gve4mrned3xs8tz42gq7kfhdw/relay.damus.io/jumble

2026-08-24 12:17:56 UTC

- reply

@npub1v0l…qj49 could we replace the webtorrent player in dtan?

2026-08-24 12:13:19 UTC

- reply

but it doesn't clean up after itself so the downloaded data just sits there until you clean up manually. we should try to integrate:
https://thaunknown.github.io/webtorrent-player/
into @npub1dta…4qs6

2026-08-24 10:14:35 UTC

- reply

wait a minute.. dtan.xzy HAS a webtorrent player!! it's just a bit hidden: there is a small arrow in the file list next to video files

2026-08-24 09:40:13 UTC

- reply

maybe this is the reason
#nevent1q…8r4h

2026-08-24 09:23:48 UTC

- reply

fair enough. can i send you a patch?

2026-08-23 11:31:09 UTC

- reply

Why can't people just admit their were wrong. It's not the end of the world, you know..

2026-08-23 07:44:09 UTC

- reply

Your reply was irrelevant regarding the original note

2026-08-23 07:27:08 UTC

- reply

Keys were not stolen, they were guessed. Big difference

2026-08-23 05:53:24 UTC

- reply

It's not an app and keys were not stolen

2026-08-23 05:43:31 UTC

- reply

About kind 2004, I have no idea and don't even know who proposed it. The description says:
"This event works exactly like a kind 1 and should follow NIP-10 for tagging."
Only explanation I can come up with is that you can filter torrent comments: if your client doesn't support viewing 2003s seeing comments on that event would be odd. But then again I'm sure that's the case with other kinds already.

2026-08-23 05:07:36 UTC

- reply

I was considering adding webtorrent support to https://dtan.xyz or https://nostrapps.github.io/ntorrent but we already have too many nostr clients (imho) and nobody is gonna go somewhere else to watch a movie. Would be a killer feature 😉 @npub180c…h6w6 is already beating us to it 😅

2026-08-22 16:19:15 UTC

- reply

Yes, only display. For now I'd like to add a button for video torrents to stream on an external website
(https://ferrolho.github.io/magnet-player/):
https://blossom.ditto.pub/84271d65eaca566a178f67a3a5edac155bb12a004038f7929b9acf75b20c925f.png
But what I really would like to have is webtorrent support to stream directly in jumble. How do you feel about that? 🙂

2026-08-22 15:14:59 UTC

@npub1syj…f6wl if I add support for NIP-35 kind 2003 (Torrent) events to jumble would you accept it?

2026-08-21 15:35:59 UTC

I'm not using AI mainly because for the questions I have I wouldn't trust the answer anyway. So since I can't trust the answer I can also instead use an open protocol with a bunch of very regarded people with lots of strong opinions to ask my questions and roll the dice. So here is my question:
Which animal is the most patient?
#asknostr #asknostrai

2026-08-21 12:02:11 UTC

- reply

Well you could argue that Bitcoin withdrawal transactions are not free either

2026-08-20 14:01:11 UTC

- reply

I am once again asking...
#nevent1q…r8m3

2026-08-18 07:19:35 UTC

We should have a bot like @npub1c4v…cqk7 that scans for YouTube links, downloads the video with yt-dlp, uploads them to a random blossom server, maybe mirror a bit and post a reply note.

2026-08-18 06:15:00 UTC

PSA: if you are downloading videos from YouTube and upload them to a blossom server PLEASE use:
```
$ cat ~/.config/yt-dlp/config
--postprocessor-args "ffmpeg:-bitexact"
```
otherwise the sha256 hashes are all different and we get multiple copies.
Thank you for your attention to this matter.

2026-08-16 07:30:35 UTC

- reply

Lots of strong opinions about this one

2026-08-15 18:38:37 UTC

- reply

I'm running a pruned node on my pixel in termux. No heat or battery issues and never got oom killed

2026-08-15 10:12:21 UTC

- reply

Wait. This was filed on March 16.. was the issue private until now or something?
https://github.com/WalletWasabi/WalletWasabi/issues/14410

2026-08-15 09:59:10 UTC

- reply

Is it possible to add this to the PWA via Web Bluetooth API?

2026-08-14 09:04:03 UTC

- reply

But reloading pages other than / doesn't work, obviously.

2026-08-14 08:59:48 UTC

Oh I can also run @npub17n4…fyh9 (using much less memory and faster and no JS) with:
```
$ darkhttpd $HOME/jumble/dist/ --port 5173
```
instead of:
```
$ npm run preview
```

2026-08-14 07:45:52 UTC

- reply

I grew up in a place where 24-hours are used but everybody says "let's meet at 3" not "at 15"

2026-08-13 07:37:29 UTC

- reply

Using it all the time

2026-08-12 10:28:08 UTC

- reply

https://github.com/guardianproject/orbot-android/issues/1730

2026-08-12 09:18:19 UTC

- reply

What are you using your relay for?

2026-08-12 08:50:36 UTC

- reply

With battery? Probably not 😅 but I never had an issue with battery usage. What's your issue exactly?

2026-08-12 08:46:15 UTC

- reply

Not accurate from my experience. Are you using the aggregator feature?

2026-08-12 07:31:23 UTC

- reply

@npub1hxx…g75y does Vanadium protect me? 👀

2026-08-12 06:28:37 UTC

- reply

I still think @npub1w27…z70r is the easiest to use with nostr

2026-08-12 06:14:46 UTC

- reply

Jumble on localhost

2026-08-11 09:54:49 UTC

- reply

Try #asknostr next time

2026-08-09 10:32:07 UTC

- reply

If the majority of nodes say it's valid then it's valid on the longer time chain

2026-08-09 10:24:18 UTC

- reply

By that logic I could run my own modified node and claim all mined blocks are invalid because my node rejects them

2026-08-09 08:17:29 UTC

- reply

Why are they invalid now if they haven't been invalid before?

2026-08-07 11:45:00 UTC

@npub1nzh…z7rp should it be possible to send sats to v3.coinos.io?
https://blossom.ditto.pub/e69d48b9347359a739d513220365ba6d60283178a6f1485c1522a825d08423b9.jpeg

2026-08-06 20:04:23 UTC

- reply

Very cool

2026-08-06 18:47:01 UTC

- reply

https://blossom.ditto.pub/88790e8346f90dfc186b19e3fe38d872b6887801979348dde2eb43e837ac2804.gif

2026-08-06 10:26:40 UTC

- reply

Cheery

2026-08-06 08:52:32 UTC

- reply

Yes

2026-08-06 08:09:53 UTC

- reply

it's dangerous out there

2026-08-05 16:43:36 UTC

- reply

What's the latest blockclock rumor?

2026-08-05 12:16:41 UTC

- reply

to..?

2026-08-05 11:12:00 UTC

- reply

Cool stuff

2026-08-05 11:01:04 UTC

- reply

Do you know of any other AI shows?

2026-08-05 10:12:38 UTC

- reply

I was worried about this too a while ago when Jumble asked for this permission but turns out it's necessary to use signers like Amber

2026-08-05 09:00:15 UTC

- reply

#nevent1q…0e4v

2026-08-05 08:41:25 UTC

Cracking Unsafe Bitcoin Wallets + Coldcard Mk4 Warning (Insecure Dice Based Seeds & Private Keys) [oj_W3xOlt6U]
https://blossom.ditto.pub/e9a30241ba64851534e839e2514fdf89fabdf75272f22807e3440c2d93056c74.webm
Published on Oct 31, 2023
A short video that looks at unsafe Bitcoin wallets that were likely created using low numbers of dicerolls leading to poor wallet BIP39 seed security, making it easy for scammers to access the private keys. I also look at how many folk lost funds doing this and which hardware/software could have been used to create these insecure wallets in the first place. It also include a demo of how this can still happen with Coldcard Mk4, even running the latest firmware.
00:00 - Introduction
01:04 - Your Wallet Existed before you Created It
01:12 - About the tool used for cracking wallets (Modified BTCRecover)
01:29 - Which types of wallets were checked
02:09 - What I found
03:20 - The Dilemma of finding wallets with funds...
03:35 - Understanding the Importance of Entropy
03:51 - Ongoing risk for low numbers of dice rolls
04:52 - Checking Wallet Safety (Seedsigner, Krux, Jade, Bitbox02 & Ian Coleman's BIP39 tool)
05:15 - Coldcard Mk4 Issues & Warning
06:33 - Increased risk associated with wallets letting users choose their own seed words
06:54 - Important disclaimer in terms of identifying how these wallets were generated
07:04 - Alternatives
08:18 - Summary and Conclusion

2026-08-04 17:38:48 UTC

- reply

I don't get it

2026-08-04 14:27:52 UTC

- reply

#nevent1q…jskz

2026-08-02 07:25:29 UTC

- reply

crazy

2026-08-01 11:39:18 UTC

- reply

but preview runs and I can use it

2026-08-01 11:15:30 UTC

- reply

it's a stretch from these posts

2026-08-01 10:39:45 UTC

- reply

lol