With high power comes high responsibility - not the guy who wired the TV in my room 😬
nostr:note1jx4jdgkl9l7le9d7hh98f3f64fagnl4hkyr4m70pd2uardpm8dsskl7ck0
Going all in nostr
Had a blast today at Adopting Bitcoin Cape Town building #BTClock
Yes, I’m going to give a workshop on Friday and will be there on Saturday and the road trip as well!
nostr:note1lxre8m6xffkltn4zs83rahwc7pn68804wrulfg3tlw8umqs2qvpswerta9
Guess where I am #ZapTime #BTClock 
I feel I need to apply for this position 😂
I will give #BTClock workshop in Cape Town next week! Build your own limited edition BTClock, reserve a kit at https://btclock.store/product/btclock-workshop-set-adopting-bitcoin-cape-town/
Please order before the weekend so I know how many kits to bring. See you next week? nostr:note1lxre8m6xffkltn4zs83rahwc7pn68804wrulfg3tlw8umqs2qvpswerta9
End of this month my work at nostr:npub1zwne90qpp0g20u99gcr44ukc42vhyg9yfw2tuc8kv9r00er9xwlqm5tult ends, where I built www.resin.estate a nostr (NIP-99) based marketplace which aims to also offer interesting financing options, preferably without a bank.
Follow nostr:npub1zwne90qpp0g20u99gcr44ukc42vhyg9yfw2tuc8kv9r00er9xwlqm5tult posts to keep updated. If you’re interested in the technical side, I just wrote quite some thorough README’s
Frontend:
https://github.com/DaedalusLabs/RESIN/blob/main/README.md
Backend:
https://github.com/DaedalusLabs/RESIN-backend/blob/main/README.md
If you want to play around with the event kind that I used, I’ve created https://create-event.resin.estate for that. Would love to talk about the process and considerations so feel free to hit me up or invite me for a talk at Bitcoin events.
Related: I will decommission nostr3.daedaluslabs.io and nostr4.daedaluslabs.io soon . AFAIK there is no kind to signal this yet...?
nostr:nevent1qvzqqqqqqypzpdgj0gyv7vmpvf6gqzjrs7yp48ucup9ecdc3d6fdu5jsfxrrt3pzqqs8yfq7kaznde253fh5mxyd9dq8hy92ukyv0wzcnsrc25gcly4dwngzzk2xk nostr:nevent1qvzqqqqqqypzpdgj0gyv7vmpvf6gqzjrs7yp48ucup9ecdc3d6fdu5jsfxrrt3pzqqs8yfq7kaznde253fh5mxyd9dq8hy92ukyv0wzcnsrc25gcly4dwngzzk2xk
End of this month my work at nostr:npub1zwne90qpp0g20u99gcr44ukc42vhyg9yfw2tuc8kv9r00er9xwlqm5tult ends, where I built www.resin.estate a nostr (NIP-99) based marketplace which aims to also offer interesting financing options, preferably without a bank.
Follow nostr:npub1zwne90qpp0g20u99gcr44ukc42vhyg9yfw2tuc8kv9r00er9xwlqm5tult posts to keep updated. If you’re interested in the technical side, I just wrote quite some thorough README’s
Frontend:
https://github.com/DaedalusLabs/RESIN/blob/main/README.md
Backend:
https://github.com/DaedalusLabs/RESIN-backend/blob/main/README.md
If you want to play around with the event kind that I used, I’ve created https://create-event.resin.estate for that. Would love to talk about the process and considerations so feel free to hit me up or invite me for a talk at Bitcoin events.
I'm quite surprised how few clients support NIP-17 DMs (uses NIP-44 to not leak metadata), so I started building a tool for ourselves to provide support for our future users in a user-friendly way. I ended up with this Telegram-like web-client to send giftwrapped DM's that is actually useful for anyone. It's available via https://resin.estate/chat
I'm considering continuing developing it as a separate tool, as I think this is quite an improvement over what is available now.
End of this month my work at nostr:npub1zwne90qpp0g20u99gcr44ukc42vhyg9yfw2tuc8kv9r00er9xwlqm5tult ends, where I built www.resin.estate a nostr (NIP-99) based marketplace which aims to also offer interesting financing options, preferably without a bank.
Follow nostr:npub1zwne90qpp0g20u99gcr44ukc42vhyg9yfw2tuc8kv9r00er9xwlqm5tult posts to keep updated. If you’re interested in the technical side, I just wrote quite some thorough README’s
Frontend:
https://github.com/DaedalusLabs/RESIN/blob/main/README.md
Backend:
https://github.com/DaedalusLabs/RESIN-backend/blob/main/README.md
If you want to play around with the event kind that I used, I’ve created https://create-event.resin.estate for that. Would love to talk about the process and considerations so feel free to hit me up or invite me for a talk at Bitcoin events.
🚀 GitHub Actions over Nostr DVM's
Working with nostr:nprofile1qyt8wumn8ghj7cn9wehjumn0wd68yvfwvdhk6tcpg4mhxue69uhkkdnywp3kjmm80q6xvctzde5hq6m4xemkccm9x3ex5a3nvenx56rkxenkxatwv33hsancdcm8qmm9wyexscmwxd5kgtn0de5k7m30qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcqyrts65qfz5ztnyk3swyz9teyt40kkwskhqkez7kt0yjvaas76jkwu4295fp on this Proof of Concept ^^
https://cdn.satellite.earth/43463990dd11c9506989e5eda915757cf3ec1b32e8d472579cd2ee18d5685f0d.mp4
Need to add this for #BTClock / #ZapTime too 😍
Most of it is a joke, but if you want a #ZapTime you can order them at
https://btclock.store/product/zaptime-built-and-tested-purple-no-frontlight/
PSA: Here it is, the brand new, never before seen #ZapTime all-new, all-purple, trademark pending. Competitively priced $398. Expect updates once every two years. Source verifiable if you come to a secret location TBD. Authorized sellers can apply for the waitlist now.
Anyone successfully implemented Nsec Bunker remote signers with NDK in TypeScript? 👀 I do see a ndk nip46signer but looking at the code I don’t see how I could implement the nostrconnect:// string flow. The bunker:// flow I got working. Stuck for 3 hours already…
If you say JS, do you mean TypeScript? 😁 😁
I might actually rebrand the purple edition to ZapTime, what do you think? ;)
Never mind nostr:npub1fnspdyh362svdejkxqkkt4t8qvlg53jfsdn3ntxx3v2lcc5rgv8q5x8x8y I just released an update 3.3.1 with support for local public pool. Please test if it works for you :)
What port is the API, and can you send me the example of the API output? you can change the values and your BTC address of course and send it in a DM
Without an API that would be impossible yes ;)
It's already in there, just make sure you use the btc address without the worker name (so without the part after the dot).
You can update via https://web-flasher.btclock.dev
The "p" tag helps with identifying events meant for a specific user. Also the NIPs specify a way for a sender which relay to deliver the encrypted message.
That specific chosen relay could enforce authentication before kind 1059 events get delivered that are meant for a specific pubkey. I hope this clear it up a bit 😉
OK, past few days were quite wild. I am currenly in El Salvador because I was attending the Adopting Bitcoin conference. My very limited internet connection here made it quite difficult to engage, I mostly just got push notifications. Hereby I want to take the opportunity to tell the story from my side.
TL;DR: We were just having fun, we thought it was okay. Apperently it's not and nvk is is so upset that he felt he had to file a GitHub takedown request. I feel that's not how bitcoiners behave.
### How it started
I have been working on the #BTClock since April '23. It started of some sort of bet where I challenged myself to make a BTC ticker as cheap as possible. I just ordered seven eInk displays on AliExpress with the intention of showing information related to bitcoin using an ESP32.
Why seven? Because the words BITCOIN and SATOSHI both consist of seven letters and connecting more screens to the ESP32 did not seem possible without adding I/O-port expanders.
Yes. The idea was inspired (among other projects) by Blockclock, which also uses eInk displays. I don't own one, so I couldn't "reverse engineer" or use any direct inspiration of it but the way you can combine multiple eInk displays to display information in an useful way is very limited.
After getting the schematic right. I created a 3D printable case for it (https://www.thingiverse.com/thing:6009628) and named it BTClock after someone's idea in the Dutch Noderunners community. Since it consists of seven characters I thought it's the perfect name since it fits the seven displays too.
nostr:note19zp3c8lsm4s5lwvuscu4dll3clkzvajrwthvqed5q7s83mazrr2swc6mqe
### May 2023
This allows you to create a BTClock for ±70 euro (if you own a 3D printer).
I shared the progress of the project in the MakerBits telegram group. Ben Arc checked with nvk how he felt about it, and I have seen his responsse where he replied with that he felt honored and that I should go ahead. In hindsight, I should've asked Ben to forward this to me but I wouldn't expect this to "haunt" me like it did last week.
After sharing the very spaghetti-y schematic in some Telegram groups, someone replied that he was working on making an actual PCB out of it. After some DM'ing back and forth we got our first PCB prototype that needed some work. After 4 iterations we finally got it how we wanted and were able to sell DIY kits. The PCB is real artwork, so we wanted to show it off. Therefore we added a acrylic backplate to be able to protect it while still able to see the proof-of-work by Madbo, the PCB artwork designer. We used a lot of through hole components to make it accesible for anyone who has a soldering iron.
### August 2023
In August 2023 we finally got the kits ready, while the initial plan was to only sell the DIY kit within the Dutch Noderunners community, I brought smoe with me to Baltic Honeybadger '23 as well, where it proved to be pretty succesful while sitting next to Ben in the chilling lounge.
I got a lot of encouraging and positive remarks about the project, including Daniel Prince (@princeysov) who tweeted about this (https://x.com/Princey21M/status/1698257536418267624).
It appeared that this tweet firstly poked the lion, since nvk sent some of his coinkite employees to me after this tweet, a group of 4 people asked a lot of questions while filming me (without my consent, I didn't realize this when they were asking it but when they walked away it was clear to see the iPhone was recording video).
Not a lot later, nvk sent out a tweet which was clearly about the BTClock project without explicitly mentioning the name (https://x.com/nvk/status/1698423362819682400)
However, in my opinion this did still fit the message I read he wrote to Ben that he was more flattered than upset. It was only then when I learned about how he reacted to Foundation Passport and how he behaves regarding the SeedSigner project.
### March 2024
During Bitcoin Atlantis in March 2024, there was a nice space for the MakerBits projects including the BTClock, the software by this time has many improvements, including real-time new block notifications by utilizing the Mempool.space Websocket API. Since the hardware is also open source, many alternative faceplates are available including a stainless steel one and a completely white one. Multiple people witnessed nvk walking passed the maker space while looking at me, but he did not engage or whatsoever. I would expect if he would take offense by the product, he would've approached me by now but he didn't. He does know who I am though, both in real-life and I'm posting enough on my social media accounts (Nostr and Xitter) to find me there as well.
### Fast forward to November 2024
A lot has happened in the development of the BTClock, among other things I added a BitAxe integration and Nostr Zap Notifications to the software and we managed to add frontlight to the eInk displays which I really think sets the BTClock apart from other "tickers" like the Blockclock mini.
The Blockclock mini hasn't had any updates for two years (since October 3rd, 2022) which seems to be like the Blockclick mini can be considered end-of-life.
I therefore was very suprised that when I woke up on November 14th, I received an e-mail that the BTClock GitHub organization was flagged because of alleged trademark infringement of the BTClock.
This was according to a report by Coinkite to GitHub. The letter I shared in the MakerBits Telegram group was ONLY sent to GitHub, not to me (although I haven't been home for a while so I don't know something is waiting in my physical mailbox).
Luckily git is decentralized version control and there are already mirrors of the hardware and software source available. Also GitHub allows me to appeal but haven't taken the chance to do so.
Although I do understand that the concept of trademarks exists for a reason, I feel this a very cowardly move and certainly not something that I would expect from fellow bitcoiners. Just sending me a DM on Nostr, X or Telegram is the least I would expect. I don't mean to offend or infringe, and would be happy to discuss options if open to it. Either in DM or out in the open.
I'm all about transparency so nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 here is my invitation to discuss this out in the open. I'm sorry that we seem to upset you. what is it that bothers you, can we find a way to let the projects co-exist? Or even see if the BTClock software can adapted to your Blockclock mini hardware.
If I just paid your 🍕, zap me biatch 😁
The first version of the #BTClock
#ThrowbackThursday 
We just launched the #noderunners #bitcoin mining pool, join us at https://noderunners.network/en/pool
We do things to bitaxes you wouldn’t believe… nostr:note1skwzldfc3uqa80w9e8fv0pk5u0a03rh66lkdz3f3u4jrmygsmm4suece2d
Tick, tock, next hash! You can now connect your #BTClock to your #BitAxe when updating to version 3.1.8 via the web flasher or if you are running 3.1.1 also via the WebUI over the air ( nostr:npub1ql2zzp3g6yndgz05js7wdc4qkr88wkyne5nw2cc7csrtzqs0yeesgwrxya wen WebSocket API? 😁) 
💯 it sure was