Calling all Bitcoin builders!
Leave a comment below to let the SN community know what you're working on this week. It doesn't matter how big or small your project is, or how much progress you've made.
Just share what you're up to, and let the community know if you want any feedback or help.
If you missed last week's thread, here are the updates SN users shared from all their latest work projects.
I plan to start playing with Nosrt. Not in a sense of using it to publish content, but in a sense of building things on top of it, such as clients, tools, games, integrations, etc.
reply
Still trying to teach myself more about nixos operating system, so I can follow in @niftyne's footsteps.
reply
I wouldn't call it a project per se, but I got myself a tapsigner and am going to figure out how to use it to make a multisig for some non-KYC sats. Time to check out some BTC sessions tutorials....
reply
I finished yesterday to setup a lightning node with lnd, so i'll probably play with lightning payment this week, starting with this newly funded account on stacker.news !
reply
I'm making an orange-pilling kahoot style quiz game where participants can win bitcoin from the host.
reply
Working on the localization of Bitcoin Core in Colombian Spanish... I am also translating Tomer Strolight's 'Why Bitcoin?' in Spanish.
reply
Pretty cool - how did you get into the translating gig?
reply
I have a translation degree and have been working as a professional translator for 20 years. Now I am contributing to several Bitcoin and Nostr projects on a voluntary basis.
reply
We doing the same here at VEINTIUNO.world DM if you looking to team up
reply
Reading The Bitcoin Standard, each page I turn I gain more toxic maxi energy.
reply
excellent - listening to Saifedean on podcasts was a big part of my intro to the bitcoin space back in 2019! Am almost done listening to "The Mandibles" audiobook - what a story! Am looking forward to hearing Odell interview the author on Citadel Dispatch when I finish
reply
Built a nostr bot to post stats from the Dashboard. Programmed in Rust.
reply
Hi everyone, I try to develop an app supported by donations and some advertising so that new BITCOIN enthusiasts are attracted and motivated in its massive adoption by earning rewards in Satoshis through a simple game that I am developing
reply
I'm working on more nostr stuff.
  • I added a few nips to booger
  • Beginning to "see" the toy client that I'll build
  • Going to port booger to deno
I also have other stuff to do ...
reply
  • Also have a handful of founder <> VC intro requests to do
reply
You raising capital?
reply
No a founder friend is
reply
Let us know when SN is raising.
reply
who is we tho?
reply
I was speaking broadly. I am sure many in the community would be interested in participating, if they are legally able to, in a SN funding round. Even if not, I am sure they would be happy to network on your behalf to qualified investors they may know who might be interested.
reply
All good. I was just curio.
On myself.
Better eating habits, going out for a run more often, and less alcohol.
Already seeing the results, life is better every day!
reply
Reopening an old course management application I had made to integrate bitcoin payments with it. Maybe integrate a bit of Nostr in it 🤞
reply
Going to set up a paper wallet, which I’ve never done before. Is there anything major that a hodler with basic computer skills should know? I read that you should disconnect WiFi when generating your keys, but I’ve never done that when setting up a mobile wallet, hence my paranoia. bitaddress.org is the only place I’ve looked so far; I will shower some Sats on those who can help, thank you all
reply
reply
Thank you, looks awesome and so does the rest of the site
reply
Yup, best is to generate as much of the key as possible by hand with dice, calculate the checksum with some assistance, then verify that two separate devices/wallet software generate the same set of addresses. (To rule out to some extent a device/software being compromised).
There's some talk lately on methods to calculate the checksum by hand too but I haven't delved into that.
reply
This week I've been building the hidden services protocol, about half way done, sending an introducer request, propagating the introducer in the network, and currently getting a little stuck as something is mangling the reply routing header for the client introduction query. I expect I'll solve it by tomorrow sometime then up to the introduction request where the introducer will forward the query with a public key used to cloak the introduction on its path back to the client... ah yeah, and then the two sided forward and backwards message cycle. So maybe it will be complete by monday or tuesday next week.
With hidden service message processing complete I'm gonna need to move on to plugging in the network devices.
My colleague has completed the relay encrypted store unlock system, not sure where he's going next, but for sure in a week or two we start on the virtual network stuff with docker images.
reply
I am trying to build a reality together with other people in Genoa in Italy, we are trying to introduce Bitcoin to as many retailers as possible. It is really difficult because here in Genoa there is a lot of distrust about the new. I also try to add more people to the cause. Another project I am working on is a page on Nostr for my music group,with the implementation of zap it could come in handy as a support.
reply
Tell them Bitcoin is the return to a sound money standard, just digital this time instead of gold. This paper/fiat funny-money was just an odd historical parenthesis.
reply
This week I learned how to set up NIP-05 verification on my own domain for nostr. Now I'm looking into what services can be built around nostr and promote BTC, LN, and self custody.
reply
I'm still (slowly) working on a NIP for building something like websites on Nostr. It's taking me a while because there are a lot of security problems that HTML introduces that I have to address -- I'm trying to make it as easy as possible for implementors to not shoot themselves and their users in the foot.
The other part I need to complete is how hyperlinks should work, considering they must point to Nostr events. I have most of that done, but I'm thinking of new edge cases as I write.
It just occured to me that I should probably submit the NIP as-is so other devs can provide feedback. It's 80% finished anyways.
reply
A http-to-nostr bridge, of sorts! Very nice. The protocol has a natural mapping in it just a matter of translating it into domain/path format to encode it. I personally favor the idea of working through working through the implementation rather than building a spec in detail first. Implementation tends to show you gotchas that you would still have to work on even if your spec seemed bulletproof.
reply
A http-to-nostr bridge,
What I'm working on is not a bridge. Rather, these websites would exist on Nostr relays. You would post a special note (containing HTML) to several relays. Hyperlinks in that note would point to other notes (which could be on any relay). Interactivity would also be possible (I'm still working on the details of that).
I personally favor the idea of working through the implementation rather than building a spec in detail first. Implementation tends to show you gotchas that you would still have to work on even if your spec seemed bulletproof.
There isn't much to implement. HTML browsers are a dime a dozen, and any of them could be modified to access websites on Nostr.
reply
It's a namespace translation system. Effectively every link can be loaded from the local nostr node, there is not a "location" for notes. So I call it a bridge. But yes, the notes themselves are html so, idk. You could call it HTTostr or something :D
reply
It's a namespace translation system.
I don't understand what you mean by this. What I'm designing involves no translation of any kind. Moreover, there are no namespaces involved.
there is not a "location" for notes.
There absolutely are locations for these notes. The notes are posted to specific relays and nowhere else.
You could call it HTTostr or something
That name would be totally inappropriate, because HTTP is not involved in any way, shape, or form.
reply
I'm no expert on deploying distributed data networks, usually centralised clusters have to have failovers as at any given time a, potentially critical, request may fail and a whole segment of a document or a data source is unavailable. So I think it needs a DHT, at minimum, and due to the requirements, a key to URI encoding scheme.
reply
A big update for Satlantis 🫡
reply
Got a couple of things cooking. I submitted Nostore to the App Store for approval yesterday for iOS. Crossing my fingers!
I'm also working on a global name system (a la DNS) using bitcoin and nostr. We will see how that goes 🙈
reply
this weekend i set up a fun Lightning-powered AI tool using Mash, it’s not quite ready to share though… maybe I can polish up the MVP tonight
reply
Sadly taxes. I wish I was working on something more compelling.
reply
Nothing is more compelling than taxes. You're literally compelled to do them!
reply
Having some tricky conversations with people that are defensive from the get go and I want to build up a collaboration with them.
reply
Just recorded a new podcast episode, dropping Friday.
reply
It's Diabolik week! Gonna take a few of the DIabolik posters and turn 'em bitcoin.
reply
Nostr gave me the motivation to start coding again, after a hiatus of more than a decade. I haven't learned any new fancy programming language, so I still write almost exclusively in java.
  1. I wrote nostr-java, a library for creating and publishing events to relays (Still WIP, I will create a release very soon)
  2. I've recently started writing a "simple and naive" framework for creating bots. It's not production-ready yet, but it works, and I'm planning to use it for creating a bot that anyone can interact with and prove they are human (and not a bot). The bot will issue a profile badge upon successful verification. (60% done)
reply
Not a fan of the sentence-long idiom of java names but for sure plenty of great software has been written in Java, and as a gopher I like it that the language has static type respecting interfaces, which I think are a lot better than templates (I'm pretty handy with code generators).
Nostr needs some kind of captcha scheme to weed out some of the spam, it's one thing that it seems to me that it will need protection against once the crowds show up and the weeds come to spam and scam. Especially paid relays, who have an obligation to their customers to not be bogged down with garbage in between paid work.
reply
I'm actually integrating Google Recaptcha Entreprise to assess if the user is a bot or a human, and then I generate a profile badge accordingly.
I'm hoping to complete it next week.
reply