bitcoin_devs
Bitcoin Dev Project

100% free and open-source resources for bitcoin devs.

bitcoin + FOSS = ₿OSS

Public Key

npub10p33xu03t8q7d9nxtks63dq4gmt4v4d3ppd5lcdp4rg9hxsd0f8q7mn2l2

NIP-05 Address

Profile Code

nprofile1qqs8sccnw8c4ns0xjen9mgdgks25d46k2kcssk60uxs635zmngxh5nspz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dskun7sl

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub10p33xu03t8q7d9nxtks63dq4gmt4v4d3ppd5lcdp4rg9hxsd0f8q7mn2l2

Show more details

Last Notes

2026-05-26 19:53:42 UTC

Calling all freedom tech builders! We are seeking volunteers for a live design review at the Oslo Freedom Forum Making Freedom Tech Beautiful workshop.
Face it. Freedom tech only matters if people can actually use it. Even the most powerful applications fall short if they feel confusing or too technical.
Watch @nprofile…f5fs of @nprofile…09x5 and our very own @nprofile…6vgm use AI to apply tried and true UX principles and draw inspiration from award winning design. Participants will leave with a Claude skill that preserves the exact process from the workshop.
𝐌𝐚𝐤𝐞 𝐲𝐨𝐮𝐫 𝐚𝐩𝐩 𝐚𝐬 𝐞𝐦𝐩𝐨𝐰𝐞𝐫𝐢𝐧𝐠 𝐚𝐬 𝐭𝐡𝐞 𝐝𝐞𝐜𝐞𝐧𝐭𝐫𝐚𝐥𝐢𝐳𝐞𝐝, 𝐜𝐞𝐧𝐬𝐨𝐫𝐬𝐡𝐢𝐩 𝐫𝐞𝐬𝐢𝐬𝐭𝐚𝐧𝐭 𝐭𝐞𝐜𝐡𝐧𝐨𝐥𝐨𝐠𝐲 𝐢𝐭 𝐢𝐬 𝐛𝐮𝐢𝐥𝐭 𝐨𝐧.
Make it something individuals all over the world can understand, adopt, and rely on.
Builders need not be physically present for the workshop. Priority given to projects funded by @nprofile…rzcm.
Sound like something you're interested in? Reply to this post or send us a DM!
https://technicaldifficulties.io/nostr/bdp/events/off2026_makingfreedomtechbeautiful.png

2026-05-23 01:50:25 UTC

- reply

𝐂𝐨𝐧𝐭𝐫𝐢𝐛𝐮𝐭𝐢𝐨𝐧𝐬 𝐭𝐨 𝐝𝐝𝐮𝐬𝐭 𝐛𝐲 𝐡𝐚𝐫𝐢𝐬𝐦𝐮𝐳𝐚𝐟𝐟𝐞𝐫 𝐚𝐧𝐝 𝐬𝐢𝐝𝐡𝐚𝐫𝐭𝐡_𝟐𝐤𝟎𝟒
𝐶𝑜𝑛𝑡𝑟𝑖𝑏𝑢𝑡𝑖𝑜𝑛𝑠 𝑡𝑜 𝑑𝑑𝑢𝑠𝑡, 𝑎𝑛 𝑒𝑥𝑝𝑒𝑟𝑖𝑚𝑒𝑛𝑡𝑎𝑙 𝑡𝑜𝑜𝑙 𝑐𝑟𝑒𝑎𝑡𝑒𝑑 𝑏𝑦 𝑏𝑢𝑏𝑏1𝑒𝑠71 𝑡ℎ𝑎𝑡 𝑖𝑚𝑝𝑙𝑒𝑚𝑒𝑛𝑡𝑠 𝑡ℎ𝑒 𝐵𝐼𝑃-451 𝐷𝑢𝑠𝑡 𝑈𝑇𝑋𝑂 𝐷𝑖𝑠𝑝𝑜𝑠𝑎𝑙 𝑃𝑟𝑜𝑡𝑜𝑐𝑜𝑙. 𝐹𝑖𝑛𝑑𝑠 𝑎𝑛𝑑 𝑠𝑎𝑓𝑒𝑙𝑦 𝑑𝑖𝑠𝑝𝑜𝑠𝑒𝑠 𝑜𝑓 “𝑑𝑢𝑠𝑡 𝑎𝑡𝑡𝑎𝑐𝑘” 𝑈𝑇𝑋𝑂𝑠 𝑖𝑛 𝑜𝑛-𝑐ℎ𝑎𝑖𝑛, 𝑑𝑒𝑠𝑐𝑟𝑖𝑝𝑡𝑜𝑟-𝑏𝑎𝑠𝑒𝑑 𝑤𝑎𝑙𝑙𝑒𝑡𝑠.
🔗 https://github.com/bip451/ddust
https://technicaldifficulties.io/nostr/bdp/boss/2026/portfolio_projects_ddust.jpg

2026-05-23 01:48:12 UTC

- reply

𝐑𝐞𝐨𝐫𝐠 𝐏𝐥𝐚𝐲𝐠𝐫𝐨𝐮𝐧𝐝 𝐛𝐲 𝐧𝐨𝐚𝐡𝐣𝐨𝐞𝐫𝐢𝐬
𝑇𝑜𝑜𝑙 𝑓𝑜𝑟 𝑒𝑥𝑝𝑙𝑜𝑟𝑖𝑛𝑔 𝑓𝑜𝑟𝑘𝑠, 𝑡𝑖𝑝 𝑑𝑖𝑣𝑒𝑟𝑔𝑒𝑛𝑐𝑒, 𝑎𝑛𝑑 𝑟𝑒𝑜𝑟𝑔 𝑏𝑒ℎ𝑎𝑣𝑖𝑜𝑟 𝑎𝑐𝑟𝑜𝑠𝑠 𝑚𝑢𝑙𝑡𝑖𝑝𝑙𝑒 𝑛𝑜𝑑𝑒 𝑏𝑎𝑐𝑘𝑒𝑛𝑑𝑠.
🔗 https://github.com/noahjoeris/reorg-playground
https://technicaldifficulties.io/nostr/bdp/boss/2026/portfolio_projects_noahjoeris.jpg

2026-05-23 01:45:38 UTC

- reply

𝐂𝐨𝐧𝐭𝐫𝐢𝐛𝐮𝐭𝐢𝐨𝐧𝐬 𝐭𝐨 𝐏𝐚𝐲𝐣𝐨𝐢𝐧 𝐏𝐥𝐮𝐠𝐢𝐧 𝐟𝐨𝐫 𝐁𝐓𝐂𝐏𝐚𝐲 𝐒𝐞𝐫𝐯𝐞𝐫 𝐛𝐲 𝐕𝐚𝐥𝐞𝐫𝐚𝐅𝐢𝐧𝐞𝐁𝐢𝐭𝐬
𝐴 @nprofile…xhfg 𝑝𝑙𝑢𝑔𝑖𝑛 𝑡ℎ𝑎𝑡 𝑎𝑑𝑑𝑠 𝐴𝑠𝑦𝑛𝑐 𝑝𝑎𝑦𝑗𝑜𝑖𝑛 (𝐵𝐼𝑃-77) 𝑠𝑢𝑝𝑝𝑜𝑟𝑡 𝑡𝑜 𝑡ℎ𝑒 𝑐ℎ𝑒𝑐𝑘𝑜𝑢𝑡 𝑓𝑙𝑜𝑤. 𝑇ℎ𝑒 𝑝𝑙𝑢𝑔𝑖𝑛 𝑢𝑠𝑒𝑠 𝐶# 𝑏𝑖𝑛𝑑𝑖𝑛𝑔𝑠 𝑡𝑜 𝑡ℎ𝑒 𝑅𝑢𝑠𝑡 𝑃𝑎𝑦𝑗𝑜𝑖𝑛 𝐷𝑒𝑣 𝐾𝑖𝑡 𝑔𝑒𝑛𝑒𝑟𝑎𝑡𝑒𝑑 𝑣𝑖𝑎 𝑈𝑛𝑖𝐹𝐹𝐼.
🔗 https://github.com/ValeraFinebits/btcpayserver-payjoin-plugin
https://technicaldifficulties.io/nostr/bdp/boss/2026/portfolio_projects_valerafinebits.jpg

2026-05-23 01:41:11 UTC

- reply

𝐍𝐨𝐝𝐞 𝐏𝐚𝐲𝐣𝐨𝐢𝐧 𝐃𝐞𝐦𝐨 𝐛𝐲 𝐱𝐬𝐭𝐨𝐢𝐜𝐮𝐧𝐢𝐜𝐨𝐫𝐧𝐱
𝐴 𝑁𝑜𝑑𝑒 𝑝𝑎𝑦𝑗𝑜𝑖𝑛 𝑑𝑒𝑚𝑜 𝑖𝑛 𝑇𝑦𝑝𝑒𝑠𝑐𝑟𝑖𝑝𝑡 𝑡ℎ𝑎𝑡 𝑟𝑒𝑝𝑙𝑖𝑐𝑎𝑡𝑒𝑠 𝑡ℎ𝑒 𝑓𝑢𝑛𝑐𝑡𝑖𝑜𝑛𝑎𝑙𝑖𝑡𝑦 𝑜𝑓 𝑝𝑎𝑦𝑗𝑜𝑖𝑛-𝑐𝑙𝑖, 𝑡ℎ𝑒 𝑟𝑒𝑓𝑒𝑟𝑒𝑛𝑐𝑒 𝑖𝑚𝑝𝑙𝑒𝑚𝑒𝑛𝑡𝑎𝑡𝑖𝑜𝑛 𝑓𝑜𝑟 𝑡ℎ𝑒 𝑝𝑎𝑦𝑗𝑜𝑖𝑛 𝑝𝑟𝑜𝑡𝑜𝑐𝑜𝑙.
🔗 https://github.com/xstoicunicornx/node-payjoin
https://technicaldifficulties.io/nostr/bdp/boss/2026/portfolio_projects_xstoicunicornx.jpg

2026-05-23 01:36:01 UTC

- reply

𝐃𝐮𝐬𝐭-𝐂𝐥𝐞𝐚𝐧𝐞𝐫 𝐛𝐲 𝐣𝐨𝐥𝐚𝐡𝟏
𝐴 𝑏𝑖𝑡𝑐𝑜𝑖𝑛 𝐶𝐿𝐼 𝑡𝑜𝑜𝑙 𝑡ℎ𝑎𝑡 𝑑𝑒𝑡𝑒𝑐𝑡𝑠 𝑑𝑢𝑠𝑡 𝑎𝑡𝑡𝑎𝑐𝑘 𝑈𝑇𝑋𝑂𝑠 𝑖𝑛 𝑦𝑜𝑢𝑟 𝑤𝑎𝑙𝑙𝑒𝑡 𝑎𝑛𝑑 𝑠𝑤𝑒𝑒𝑝𝑠 𝑡ℎ𝑒𝑚 𝑠𝑎𝑓𝑒𝑙𝑦 𝑢𝑠𝑖𝑛𝑔 𝑃𝑆𝐵𝑇𝑠.
🔗 https://github.com/Jolah1/dust-cleaner
https://technicaldifficulties.io/nostr/bdp/boss/2026/portfolio_projects_jolah1.jpg

2026-05-23 01:34:20 UTC

- reply

𝐀𝐧𝐚𝐥𝐲𝐬𝐢𝐬 𝐨𝐟 𝐏𝐨𝐬𝐭-𝐁𝐈𝐏 𝟑𝟐𝟒 𝐏𝟐𝐏 𝐓𝐫𝐚𝐟𝐟𝐢𝐜 𝐛𝐲 𝐑𝐚𝐳𝐨𝐫𝐁𝐞𝐬𝐭
𝐴 𝑝𝑟𝑜𝑗𝑒𝑐𝑡 𝑡𝑜 𝑑𝑒𝑡𝑒𝑟𝑚𝑖𝑛𝑒 𝑖𝑓 𝑃2𝑃 𝐵𝑖𝑡𝑐𝑜𝑖𝑛 𝑒𝑛𝑐𝑟𝑦𝑝𝑡𝑒𝑑 𝑡𝑟𝑎𝑓𝑓𝑖𝑐 𝑖𝑠 𝑑𝑒𝑡𝑒𝑐𝑡𝑎𝑏𝑙𝑒 𝑏𝑦 𝐼𝑆𝑃𝑠
🔗 https://github.com/RazorBest/bip324-traffic-analysis
https://technicaldifficulties.io/nostr/bdp/boss/2026/portfolio_projects_razorbest.jpg

2026-05-23 01:32:29 UTC

- reply

𝐒𝐮𝐩𝐞𝐫𝐒𝐜𝐚𝐥𝐚𝐫 𝐛𝐲 𝟖𝟏𝟒𝟒𝟐𝟐𝟓𝟑𝟎𝟗
𝐼𝑚𝑝𝑙𝑒𝑚𝑒𝑛𝑡𝑎𝑡𝑖𝑜𝑛 𝑜𝑓 𝑆𝑢𝑝𝑒𝑟𝑆𝑐𝑎𝑙𝑎𝑟 — 𝐵𝑖𝑡𝑐𝑜𝑖𝑛 𝐿𝑖𝑔ℎ𝑡𝑛𝑖𝑛𝑔 𝑐ℎ𝑎𝑛𝑛𝑒𝑙 𝑓𝑎𝑐𝑡𝑜𝑟𝑖𝑒𝑠 𝑡ℎ𝑎𝑡 𝑜𝑛𝑏𝑜𝑎𝑟𝑑 𝑁 𝑢𝑠𝑒𝑟𝑠 𝑖𝑛 𝑜𝑛𝑒 𝑠ℎ𝑎𝑟𝑒𝑑 𝑈𝑇𝑋𝑂. 𝑁𝑜 𝑠𝑜𝑓𝑡 𝑓𝑜𝑟𝑘 𝑟𝑒𝑞𝑢𝑖𝑟𝑒𝑑.
🔗 https://superscalar.win
https://technicaldifficulties.io/nostr/bdp/boss/2026/portfolio_projects_8144225309.jpg

2026-05-23 01:29:52 UTC

- reply

𝐑𝐨𝐨𝐭𝐒𝐜𝐨𝐩𝐞 𝐛𝐲 𝐚𝐚𝐫𝐨𝐧-𝐫𝐞𝐜𝐨𝐦𝐩𝐢𝐥𝐞
𝑇𝑎𝑝𝑟𝑜𝑜𝑡 𝑠𝑐𝑟𝑖𝑝𝑡-𝑝𝑎𝑡ℎ 𝑎𝑛𝑎𝑙𝑦𝑧𝑒𝑟 𝑤𝑖𝑡ℎ 𝑤𝑖𝑡𝑛𝑒𝑠𝑠 𝑓𝑒𝑡𝑐ℎ, 𝑀𝑒𝑟𝑘𝑙𝑒 𝑝𝑟𝑜𝑜𝑓 𝑟𝑒𝑐𝑜𝑛𝑠𝑡𝑟𝑢𝑐𝑡𝑖𝑜𝑛, 𝑎𝑛𝑑 𝑎𝑑𝑑𝑟𝑒𝑠𝑠 𝑣𝑒𝑟𝑖𝑓𝑖𝑐𝑎𝑡𝑖𝑜𝑛.
🔗 https://github.com/aaron-recompile/rootscope
https://technicaldifficulties.io/nostr/bdp/boss/2026/portfolio_projects_aaron-recompile.jpg

2026-05-23 01:27:43 UTC

- reply

𝐋𝐢𝐠𝐡𝐭 𝐂𝐥𝐢𝐞𝐧𝐭 𝐁𝐥𝐨𝐜𝐤 𝐅𝐢𝐥𝐭𝐞𝐫 𝐑𝐞𝐬𝐞𝐚𝐫𝐜𝐡 𝐛𝐲 𝐩𝐮𝐫𝐬𝐳𝐤𝐢
𝐵𝑒𝑛𝑐ℎ𝑚𝑎𝑟𝑘𝑖𝑛𝑔 𝐵𝐼𝑃-158 𝑎𝑔𝑎𝑖𝑛𝑠𝑡 𝐵𝑖𝑛𝑎𝑟𝑦 𝐹𝑢𝑠𝑒 𝑓𝑖𝑙𝑡𝑒𝑟𝑠, 𝑤𝑖𝑡ℎ 𝑟𝑒𝑝𝑟𝑜𝑑𝑢𝑐𝑖𝑏𝑙𝑒 𝑑𝑎𝑡𝑎𝑠𝑒𝑡𝑠, 𝑤𝑎𝑙𝑙𝑒𝑡 𝑠𝑐𝑒𝑛𝑎𝑟𝑖𝑜𝑠, 𝑎𝑛𝑑 𝑔𝑟𝑜𝑢𝑛𝑑-𝑡𝑟𝑢𝑡ℎ 𝑣𝑎𝑙𝑖𝑑𝑎𝑡𝑖𝑜𝑛 𝑜𝑛 𝑟𝑒𝑎𝑙 𝑚𝑎𝑖𝑛𝑛𝑒𝑡 𝑑𝑎𝑡𝑎.
🔗 https://purszki.github.io/bitcoin_research_01
https://technicaldifficulties.io/nostr/bdp/boss/2026/portfolio_projects_purszki.jpg

2026-05-23 01:22:46 UTC

- reply

With over 50 projects built during this phase, here are some favorites:
𝐁𝐢𝐭𝐜𝐨𝐢𝐧 𝐏𝐈𝐑 𝐛𝐲 𝐰𝐞𝐢𝐤𝐞𝐧𝐠𝐜𝐡𝐞𝐧
𝑄𝑢𝑒𝑟𝑦 𝑡ℎ𝑒 𝑏𝑖𝑡𝑐𝑜𝑖𝑛 𝑈𝑇𝑋𝑂 𝑠𝑒𝑡 𝑤𝑖𝑡ℎ𝑜𝑢𝑡 𝑟𝑒𝑣𝑒𝑎𝑙𝑖𝑛𝑔 𝑤ℎ𝑖𝑐ℎ 𝑎𝑑𝑑𝑟𝑒𝑠𝑠𝑒𝑠 𝑦𝑜𝑢'𝑟𝑒 𝑖𝑛𝑡𝑒𝑟𝑒𝑠𝑡𝑒𝑑 𝑖𝑛.
🔗 https://github.com/Bitcoin-PIR/Bitcoin-PIR
https://technicaldifficulties.io/nostr/bdp/boss/2026/portfolio_projects_weikengchen.jpg

2026-05-23 01:18:25 UTC

The Chaincode Labs ₿OSS Challenge may be over, but the building continues! Check out these incredible portfolio projects that participants worked on during the program 👇
https://bosschallenge.xyz/portfolioprojects
https://technicaldifficulties.io/nostr/bdp/boss/2026/portfolio_projects_recap.jpg

2026-05-23 01:04:02 UTC

- reply

https://blossom.primal.net/d8f5b92e2bc65bfee1bae9ce569467702bb32a57040dcd558c64513b61da2790.png

2026-03-08 15:07:24 UTC

- reply

Nice!! The Himalayan Ibex is such a good choice and the t-shirt design came out beautiful. Design is hard and we appreciate you sharing the process because sometimes going through all these iterations can be frustrating. Love the tagline of "far from the noise" too 😉

2026-02-27 18:41:27 UTC

https://technicaldifficulties.io/nostr/bdp/pangolin/merkle_winner.png
The pangolin mascot naming contest has a winner...
🎉👋 MEET MERKLE! 👋🎉
The name is a nod to the cryptographer Ralph Merkle who created a number of technologies that are fundamental to bitcoin.
He is most famous for co-inventing public key cryptography and creating the Merkle trees we all know and love.
Congratulations to @nprofile…5njj for submitting the winning entry on nostr. To celebrate, we will be releasing some special content on Merkle trees next month.
The runner up was Petunia 🌸 Honorable mentions go to those that submitted the names Scaly, Petey, Pauldron, Ronnie, Pangoshi, Bitsy, Nacho, Toshi, and Leroy. In the coming days we will be reaching out to you so we can send stickers your way!
Thanks everyone for your participation! The names you submitted were so good we may have to expand the Merkle family tree to include new friends 😉

2026-02-25 18:48:25 UTC

- reply

LAST CALL! 📣 1 day left to submit a name for our new mascot
We've seen some awesome suggestions come through but there is still time to get your entries in.
There is no limit to the amount of times you can enter. Open to participants anywhere in the world.
🌎🌍🌏
https://technicaldifficulties.io/nostr/bdp/pangolin/1dayleft.png
#nevent1q…pcqy

2026-02-23 22:30:35 UTC

- reply

Just 3 days left to submit your best, most creative names for our new mascot.
We're seeing some really good submissions so far. Keep them coming!
https://blossom.primal.net/0fdb16b265a11bb4a15066cddffc9fa01b34b08f418c889f197f1625a5aa26a4.png
#nevent1q…pcqy

2026-02-17 20:18:30 UTC

HELP! This little pangolin started hanging around our website.
It’s been at least a month and it doesn’t look like it’s going away anytime soon.
What should we name it?
https://technicaldifficulties.io/nostr/bdp/pangolin/namingcontestvideo.mp4
When we launched our new website in December this fellow quickly showed up.
Now it needs a name and we want your suggestions!
Reply to this thread with your best name and if it is chosen, you will win a BDP swag pack.
Stickers will also be sent to honorable mentions 😉
https://technicaldifficulties.io/nostr/bdp/pangolin/namecontestpolaroids.png
Pangolins are solitary, curious creatures known for their armor-like scales & quiet determination. Like the best open-source contributors, they build, explore, & protect what matters. To us they represent the kind of thoughtful, persistent energy we see in bitcoin devs daily.
You have 10 days, until 2/26 to share your best, most clever, and imaginative names.
There is no limit to the amount of times you can enter. Let’s see those names!

2025-12-30 20:48:18 UTC

The ₿OSS Challenge is designed to get you started in a career in open source. Deadline to apply is tomorrow, December 31.
Don't overthink it. Apply now and change your life in 2026.
https://technicaldifficulties.io/nostr/bdp/boss/compilation_testimonials_2025.mp4
https://bosschallenge.xyz
#bitcoin #softwareengineering #softwaredeveloper

2025-12-28 00:18:54 UTC

MacGyver left the start up life to work on silent payments.
Do you crave professional freedom to work on the things you believe are most impactful?
Take the ₿OSS Challenge and make 2026 the year you make the career change you've dreamed of.
https://technicaldifficulties.io/nostr/bdp/boss/macgyver_slp_2025.mp4
https://bosschallenge.xyz

2025-12-28 00:13:48 UTC

THERE ARE FOUR DAYS LEFT TO APPLY FOR THE ₿OSS CHALLENGE
Since 2024 the ₿OSS Challenge has helped 20 developers become full time bitcoin open source software contributors.
Number 21 could be you. Apply now💪
https://technicaldifficulties.io/nostr/bdp/boss/4_day_countdown.mp4
https://bosschallenge.xyz

2025-12-22 20:44:32 UTC

Enlightening! Testing! Inspiring!
That is how 2025 alum Sangbida describes the ₿OSS Challenge.
When she took it she was working on corporate side of #bitcoin. Now she is funded by @nprofile…g8xl to contribute to Core Lightning ⚡️
https://technicaldifficulties.io/nostr/bdp/boss/sangbida_2025.mp4
What’s stopping you? Start your career in bitcoin open source software (₿OSS) and change your life forever.
Applications close in 10 days on Dec 31. Program kicks off the week of January 12.
https://bosschallenge.xyz

2025-12-22 20:16:11 UTC

https://technicaldifficulties.io/nostr/bdp/boss/10_day_countdown.mp4
There are just 10 days* left to apply to the ₿OSS Challenge.
* roughly 1,440 blocks
Write code used by countless people across the world.
Work on the best problems with the brightest minds.
Achieve professional freedom.
Join the ₿OSS Challenge today 👇
https://bosschallenge.xyz

2025-12-19 15:56:49 UTC

📢 ATTN: developers interested in bitcoin open-source
👀 We are looking for participants for voluntary usability testing.
🖥️ During the session you’ll be asked to share your thoughts while interacting with a website prototype.
https://blossom.primal.net/86224ab9994f40d483c9b27166a7f8439727acff9233ec71cbcd126b14fbeb64.gif
If this sounds like something you'd be interested in, sign up here 👇
https://docs.google.com/forms/d/e/1FAIpQLSe3k1nJkfAE891CC5V2hPyyvB1Cosp3nOlpBG57gYInkhwfHg/viewform
Selected participants will be contacted to schedule a remote session with the designer.
Thank you in advance. We would love your participation! ✨
https://blossom.primal.net/2d42287daa966185fd464b3782e723838e6e08bc5e95536c988cb8932e2c046b.png

2025-12-18 21:49:00 UTC

Meet David:
https://technicaldifficulties.io/nostr/bdp/boss/david_2025.mp4
Before signing up for the BOSS Challenge, David was an algebra teacher.
After it he got a grant from @nprofile…5h0z and now he’s a full time bitcoin open-source developer working on compact block relay at Localhost Research.
If you're interested in Bitcoin open source development, this is the path for you.
Be like David and take the BOSS Challenge today 🚀
Apply by Dec 31st.
https://bosschallenge.xyz

2025-12-17 19:15:28 UTC

- reply

This clip is from the latest episode of the @nprofile…h02q Podcast. Thank you Stephan for having us on your show!
Watch the full episode to learn more about the BOSS Challenge:
Spotify: https://open.spotify.com/episode/0LtinmbIFD2dFcrx1UjMnQ
Official site: https://stephanlivera.com/episode/706/
Rumble: https://rumble.com/v73335i-start-your-career-in-bitcoin-with-oss-challenge-with-satsie-macgyver-and-sa.html
Youtube: https://www.youtube.com/watch?v=K_x4AQIibZY

2025-12-17 19:11:30 UTC

Want a career in #bitcoin open source but feeling intimidated?
Sangbida Chaudhuri and MacGyver talk about their experience on the Stephan Livera podcast transitioning from the corporate world to bitcoin open source development.
Join us for the bosschallenge.xyz and change your career in 2026.
https://technicaldifficulties.io/nostr/bdp/boss/SLP_2025_BOSS_devs.mp4

2025-12-16 20:55:06 UTC

- reply

This clip is from the latest episode of the @nprofile…h02q Podcast. Thank you Stephan for having us on your show!
Watch the full episode to learn more about the BOSS Challenge:
Spotify: https://open.spotify.com/episode/0LtinmbIFD2dFcrx1UjMnQ?si=sByRbJdUTyazGuibJo2r9A&nd=1&dlsi=5e9133cbabb549b4
Official site: https://stephanlivera.com/episode/706/
Rumble: https://rumble.com/v73335i-start-your-career-in-bitcoin-with-oss-challenge-with-satsie-macgyver-and-sa.html
Youtube: https://www.youtube.com/watch?v=K_x4AQIibZY

2025-12-16 20:47:38 UTC

New Year, New You, New Career in Bitcoin
Don’t miss your chance to get your dream job working on Bitcoin. Get funded by Spiral, BTrust, Blockstream, Brink and others to contribute to something meaningful.
Apply for the BOSS Challenge today
http://bosschallenge.xyz
https://technicaldifficulties.io/nostr/bdp/boss/BOSS_overview1_SLP_2025.mp4

2025-12-15 22:03:01 UTC

Reminder that applications for the ₿OSS Challenge close in roughly 2 weeks!
Make 2026 the year you start a career in bitcoin open source software 🏃‍➡️
https://technicaldifficulties.io/nostr/bdp/boss/btrustdevday_2025_boss.jpeg
https://bosschallenge.xyz

2025-12-03 22:23:54 UTC

- reply

Meet the devs from the 2025 program supported by @nprofile…5h0z , @nprofile…xv7m , Maelstrom Fund, @nprofile…4mnp , and @nprofile…g8xl to work full-time on bitcoin open source development 👇
🔧 Sangbida
Project: Core LN
Funded by: @nprofile…g8xl
github.com/sangbida
🟣🥕 @nprofile…qw49
Project: Bitcoin Core
Funded (announced soon)
Writes at habla.news/u/purplekarrot.net
purplekarrot.net
🛠️ @nprofile…utnx
Project: Payjoin
Funded by Maelstrom Fund
benalleng.com
🏗️ zealsham
Project: Payjoin
Funded (announced soon)
github.com/zealsham
🤫 Ron
Project: Silent Payments
Funded by Maelstrom Fund
github.com/macgyver13
❄️ Beulah
Project: FROST
Funded (announced soon)
github.com/BEULAHEVANJALIN
⚙️ Rita
Project: LDK Node
Funded by @nprofile…4mnp
github.com/camillarhi
🧰 Chuks
Project: LDK Node
Funded by @nprofile…4mnp
github.com/chuksys
⚡ elnosh
Project: Channel Jamming Research & LDK
Funded by: @nprofile…5h0z & Chaincode Labs
github.com/elnosh
🔩 Janb
Project: Bitcoin Core
Funded (announced soon)
github.com/Janb84

2025-12-03 22:16:42 UTC

The ₿OSS Challenge is back 🎉
Start your career in bitcoin open source software (₿OSS) and change your life forever.
https://bosschallenge.xyz
Serious about a career in bitcoin open source software?
Do you dream of professional freedom? Do you want your work to have a profound impact? Are you looking for some of the most challenging engineering problems?
Take the ₿OSS Challenge and start yourself on a new path
https://bosschallenge.xyz/img/section-background.png
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
❓ HOW DOES IT WORK? ❓
The challenge kicks off the week of January 12
🗓️ 30 days to complete a series of code-based technical challenges
🛣️ 2 additional months for anyone willing to continue the adventure
If you are willing to do the work, we'll give you what you need to get to where you want to go.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
🧑‍🤝‍🧑 LEARNING IS BETTER WITH FRIENDS 🧑‍🤝‍🧑
That’s why we’re delighted to announce ₿OSS Challenge partnerships with:
- @nprofile…4mnp
- @nprofile…2cgl
- @nprofile…qg98
- @nprofile…xl9q
- @nprofile…c7ux
- zzmjxy in China
- My Satoshis in Burundi
🌍 Live in one of these regions? Reach out to connect with others doing the ₿OSS Challenge!
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Funding for bitcoin open source development is earned by demonstrating proof of work. There is no cheat code.
🧡 Come do the work and good things will happen. 🧡
The ₿OSS Challenge gives you structure while fostering the proactive, self-starter spirit that is required in open-source.
Join the challenge.
See how far you will go.
Change your life in 2026.
⏰ Applications close: December 31
🎯 Program begins: January 12
🌎 Open to everyone. Totally free.
Application: bosschallenge.xyz
#bitcoin

2025-12-03 22:09:51 UTC

- reply

Thank you so much Shawn! That means a lot 🥰 🧡

2025-12-01 22:26:43 UTC

Well, we finally did it. We got a logo for the Bitcoin Dev Project got a logo and a new website to match it.
https://technicaldifficulties.io/nostr/bdp/pangolin/logo_reveal.gif
For the last few years you have trusted the Bitcoin Dev Project (BDP) to bring high quality, open-source tools and education to the developer community.
Today, as a symbol of our ongoing commitment to this mission, we are proud to reveal a fresh look.
🌿 🌿 🌿
Let’s start with the pangolin in the room
Yes, that is a pangolin. Is this unexpected? Yes. Is it intentional? Very much.
Pangolins are solitary, curious creatures known for their armour-like scales and quiet determination. Like the best open-source contributors, they build, explore, and protect what matters. To us, they represent the kind of thoughtful, persistent energy we see in the bitcoin dev community every day.
https://technicaldifficulties.io/nostr/bdp/pangolin/pr_pangolin.png
🌿 🌿 🌿
How it began
In 2023, BDP was born from a desire to build for the developer ecosystem. We created efficiency boosting tools like Bitcoin Search and ChatBTC. From there, a suite of educational products and even games emerged with things like Decoding Bitcoin and Saving Satoshi. This past year we rounded our offerings out with the Common Application which helps contributors apply for funding.
https://technicaldifficulties.io/nostr/bdp/pangolin/bdp_launch_product_cards.png
BDP has been lovingly designed to serve the developer community in a way that is approachable and encouraging, yet without compromising the hard work and discipline required of bitcoin development.
There is much more to bitcoin tech than what is seen at the surface. That is why we created BDP to be a place where you can grow your technical skills without the noise.
Anyone in the world should be able to participate in bitcoin development. If you do the work, BDP is there to help you reach your goals.
https://technicaldifficulties.io/nostr/bdp/pangolin/pangolin_tools.png
🌿 🌿 🌿
A reimagined website
You’ve seen the logo but that’s not all. This makeover goes far beyond that. Instead, the BDP website has been completely reimagined to deliver more moments of delight, improved navigation, and easy access to our tools and resources.
The new illustrations, icons, and vibrant color palette are all inspired by the pangolin’s natural habitat. With an earthy, nature-inspired theme, the website is warm and inviting, reflecting BDP’s goal of being a welcoming entry point into bitcoin development.
https://technicaldifficulties.io/nostr/bdp/pangolin/accent_colors.png
Despite all the changes, you’ll still find the things you have come to expect from BDP: learning material, developer tools, and funding guidance. BDP provides new opportunities for you to explore and take meaningful steps toward becoming a bitcoin developer.
https://technicaldifficulties.io/nostr/bdp/pangolin/new_website_abovefold.png
🌿 🌿 🌿
Design secrets
For more on how the logo and website came to life, check out this blog post by our amazing designer Sanya.
https://medium.com/@bitcoindevs/glow-up-95008146d653
https://technicaldifficulties.io/nostr/bdp/pangolin/Monseratt_example.png
https://technicaldifficulties.io/nostr/bdp/pangolin/Quicksand_example.png
🌿 🌿 🌿
From the bottom of our hearts, thank you.
We’re deeply passionate about the work we do and grateful for your support.
To those that don’t know us: While getting confused with BDK is arguably a good problem to have, we hope you’ll stick around and get to know us. We’re in this for the long haul and would love for you to join in the adventure.
https://bitcoindevs.xyz

2025-11-03 16:10:02 UTC

- reply

📢 Are you a Rust dev that wants to learn more about bitcoin? Then you need to check out Bitcoin Dojo!
🦀 Learn bitcoin protocol development with free, hands-on coding challenges. Reinforce your Rust skills while learning something new about bitcoin. It's a win-win 😉
Find it at 👉 https://bitcoindojo.dev
Use the beta access code EMWQSA to start learning today 🫡
#nevent1q…snem

2025-10-15 18:46:57 UTC

Reminder that there is still time to apply for the Bitcoin Scholarship!
Contribute to bitcoin and get a full year of your college tuition covered in return. Open to applicants anywhere in the world.
Sound too good to be true? Meet the 2025 winner, Ishaana Misra.
https://technicaldifficulties.io/nostr/bdp/scholarship_2025_ishaana.png
Ishaana taught herself C++ in high school and became the youngest contributor to Bitcoin Core in the process. She is now a freshman at MIT and president of the MIT Bitcoin Club.
Congrats Ishaana! Her story shows that even as a student you can make meaningful contributions to bitcoin.
Ready to apply for the scholarship? Click the link below!👇
https://bitcoinscholarship.xyz/

2025-10-01 21:10:18 UTC

📣 ICYMI: Chaincode Labs is (again) awarding a scholarship to attract the brightest minds to work on bitcoin. 🎓
The scholarship covers 100% tuition for an undergraduate anywhere in the world. Last year's winner started at MIT last month.
Applications close soon. Don't let this opportunity pass you by!
More details can be found here 👇
https://bitcoinscholarship.xyz/

2025-09-16 14:55:03 UTC

Did you know, the bitcoin-dev mailing list has over 20,000 posts going back to June 2011?
If each post takes 30 min to read (on average), that’s over 400 days of nonstop reading!
To be fair,
1️⃣ Posts aren't easily searchable
2️⃣ If a thread spans multiple months back it can be broken
3️⃣ Your inbox probably has enough emails competing for your attention
Things can easily go ignored & unread. Few, if any, can say they have read it all.
For the rest of us, we started working into a way to download the mailing list straight to your brain. While we haven’t quite figured that out (yet), we've built the next best thing…
Meet 📚 Bitcoin TLDR v2 📚, a collection of summaries for the bitcoin-dev, lightning-dev, and Delving Bitcoin mailing lists.
➡️ tldr.bitcoinsearch.xyz
https://github.com/bitcoinsearch/tldr/raw/refs/heads/main/public/images/TLDR-v2-demo.mp4
The mailing lists are known for being some of the best places to get updates on bitcoin development.
🔨 It’s where the builders go to propose new ideas, gather feedback, and hash it out.
Whether you are trying to stay on the cutting edge, or are catching up on bitcoin’s rich technical history, Bitcoin TLDR is made for you.
TLDR summarizes every individual mailing list post while also creating summaries at the thread level.
With daily updates, thread summaries remain fresh based on new replies so you never miss a beat. 👀
Visit the Active Discussions section to see what’s trending: https://tldr.bitcoinsearch.xyz/posts#active-discussions
https://technicaldifficulties.io/nostr/bdp/tldr/tldr_v2_activediscussions.png
If you’re already subscribed to the mailing lists but feel overwhelmed, try out the Bitcoin TLDR newsletter. It’s got weekly summaries of all the latest activity, providing a manageable way for you to stay on top of it all.
https://tldr.bitcoinsearch.xyz/newsletters
https://technicaldifficulties.io/nostr/bdp/tldr/tldr_v2_newsletters.png
How Does It Work?
- The Scraper Repo
This scrapes through Delving Bitcoin and the Bitcoin Dev Mailing List, fetches mailing list pages, and stores them locally.
A parser processes those files to extract clean metadata and message content.
Finally, an indexer pushes the structured documents into an index in Elasticsearch for search and analysis.
- The Summarizer
The summarizer repo has two main parts. First, it makes sure Elasticsearch always has the latest full thread data by syncing the combined XML files. Second, it adds short AI summaries to posts that don’t have one yet. This way, Elasticsearch stores both the complete thread summaries, and individual post.
Third, it creates AI summaries for the full thread, creating a combined summary.
- The TLDR Frontend
This renders summaries for each thread and post, and displays them with a beautiful UI.
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Bitcoin TLDR is completely free and open-source. It’s designed to help more people engage with high signal bitcoin and lightning tech discussions. Give it a try and let us know what you think!
➡️ tldr.bitcoinsearch.xyz

2025-07-30 20:05:13 UTC

🚀 ICYMI we recently launched a common application for bitcoin grants!
Apply for funding once. Reach multiple bitcoin grant organizations.
https://technicaldifficulties.io/nostr/bdp/grants-app-demo.mp4
Are you a bitcoin open-source software (₿OSS) contributor? Are you tired of filling out multiple applications for funding?
Now you don’t have to.
The Common Grants App is one application that gets you in front of:
- @nprofile…5h0z
- @nprofile…xv7m
- @nprofile…y7cf
- Brink
- Maelstrom
- - - - - - - - - -
Here’s how it works:
1. Fill out one form
2. Pick the orgs
3. Submit
4. Each org receives your app
5. They contact you if they are interested
- - - - - - - - - -
Why this matters:
✅ Saves time
✅ Saves effort
✅ Reach 5 bitcoin funding orgs
✅ No duplicate work
More time building. Less time on the paperwork.
❌ No chasing 5 different forms across 5 sites
❌ No unnecessary overhead
✅ One unified application flow
- - - - - - - - - -
Who’s it for?
- ₿OSS contributors
- App builders
- Educators
- Privacy researchers
- Anyone building for Bitcoin
- - - - - - - - - -
Built with ♥️ by @nprofile…uvtq
Big thanks to @nprofile…04uy, @nprofile…gh4s , @nprofile…6vgm
- - - - - - - - - -
Ready to apply? 👇
https://grants.bitcoindevs.xyz/

2025-07-10 18:33:54 UTC

- reply

Wait, before you go! There is a contributor missing from the thank you tweet, https://github.com/IgboPharaoh ! We are so sorry. Thank you for your efforts building Bitcoin Transcripts.
The social media intern responsible for this mistake has been assigned to mailroom duty until further notice.

2025-07-10 15:04:57 UTC

🧰 Too much bitcoin tech knowledge is trapped in videos and podcasts
If only there was an easy way to unearth those insights and gems… 🤔
We wondered that too, so we redesigned Bitcoin Transcripts! 🚀
https://technicaldifficulties.io/nostr/bdp/transcriptsv2/transcriptsv2_homepage.png
🔍 Bitcoin Transcripts is a filterable library of transcripts from:
• dev meetups
• conferences
• podcasts
• panels
Skim talks, quote insights, and search by keyword.
All in one place.
👉 https://btctranscripts.com
⛏️ Missed a workshop or podcast episode?
No worries.
You can now quickly search by keyword or topic and read the conversation in minutes instead of watching hours of video,
Accelerating your speed to insights.
🧑‍🏫 Bitcoin Transcripts is perfect for:
- bitcoin devs digging into prior research
- educators creating content
- researchers analyzing protocol history or
- enthusiasts who prefer reading over listening
Taproot workshops, Lightning panels, it’s all in there.
Open-source and built by the community 🧡
This project stands on the shoulders of contributors like Bryan Bishop (https://heybryan.org/) who manually transcribed hundreds of talks.
Now, with modern tools, we can scale that effort for the whole community.
https://technicaldifficulties.io/nostr/bdp/transcriptsv2/transcriptsv2_bryantyping.png
Many thanks to our contributors:
- Dev: @nprofile…7k9s , Jamal (https://github.com/jrakibi), Emmanuel (https://github.com/Emmanuel-Develops), @nprofile…gh4s
- Data & architecture: Andreas (https://www.kouloumos.com/), Urvish (https://github.com/urvishp80)
- Vision: @nprofile…z4ak
- Design: Tobi (https://x.com/Adeoye_G), Khush (https://x.com/ikhushh7), @nprofile…qdk5
- Product: @nprofile…ez5h
- Inspiration: Bryan Bishop (https://heybryan.org/)
What’s next?
We’ll keep adding transcripts from upcoming events and backfill any important historic talks we missed. 🔍
Would love your help editing transcripts as well.
Dive in, explore, and let us know what you think! 👇
btctranscripts.com

2025-04-30 19:51:06 UTC

- reply

Yes! The more BOSS devs the merrier!
https://blossom.primal.net/623c7e12aeda2c8c88f323af610a458e000df9ba6c0550201366b6a32f037a92.gif

2025-04-30 19:49:31 UTC

- reply

This is great! We love to see it!! 🚀

2025-04-01 19:14:08 UTC

Slots are filling up fast for our Warnet track at Friday's #MITBitcoinExpo Hackathon!
We stand up a network of Bitcoin Core nodes. You use Bitcoin Core's functional test framework to write attacks in Python and take them down.
This event is open to hackers around the globe. Participants can be in-person or remote. And did we mention the $3,000 prize from the MIT Bitcoin Club?
👉 Head over to https://mitbitcoin.devpost.com to sign up today!
https://technicaldifficulties.io/nostr/bdp/WarnetShirtImage.png
We'll also have we’ll have additional prizes for Warnet track winners that are able to join in person. These gorgeous coasters by A+ Engrave are just one example! 🤩
https://technicaldifficulties.io/nostr/bdp/mit2025/slatecoaster.jpeg
https://technicaldifficulties.io/nostr/bdp/mit2025/corkcoasters.jpeg
https://technicaldifficulties.io/nostr/bdp/mit2025/warnetmug.jpeg

2025-03-03 15:39:23 UTC

𝐓𝐡𝐞 𝐁𝐢𝐭𝐜𝐨𝐢𝐧 𝐃𝐞𝐯 𝐏𝐫𝐨𝐣𝐞𝐜𝐭 𝐡𝐚𝐬 𝐚 𝐭𝐫𝐚𝐜𝐤 𝐚𝐭 𝐭𝐡𝐞 𝐌𝐈𝐓 𝐁𝐢𝐭𝐜𝐨𝐢𝐧 𝐄𝐱𝐩𝐨 𝐇𝐚𝐜𝐤𝐚𝐭𝐡𝐨𝐧, 𝐚𝐧𝐝 𝐢𝐭 𝐡𝐚𝐬 𝐚 $𝟑,𝟎𝟎𝟎 𝐩𝐫𝐢𝐳𝐞!
Participants have 30 hours, starting April 4 and are welcome to hack from around the globe.
🌍 We repeat, you do not have to attend in person 🌎
𝐌𝐨𝐬𝐭 𝐡𝐚𝐜𝐤𝐚𝐭𝐡𝐨𝐧 𝐭𝐫𝐚𝐜𝐤𝐬 𝐚𝐫𝐞 𝐚𝐛𝐨𝐮𝐭 𝐛𝐮𝐢𝐥𝐝𝐢𝐧𝐠, 𝐛𝐮𝐭 𝐧𝐨𝐭 𝐭𝐡𝐢𝐬 𝐨𝐧𝐞. 𝐓𝐡𝐢𝐬 𝐢𝐬 𝐚𝐛𝐨𝐮𝐭 𝐛𝐫𝐞𝐚𝐤𝐢𝐧𝐠 🔨
For the Bitcoin Dev Project track, the goal is to take down the bitcoin network. We stand up a network of bitcoin core nodes. You and your team take down as many as possible.
Whichever team brings down the most in the shortest amount of time wins. Monitor extreme and yet unknown network behaviors, discover vulnerabilities, and build a stronger, more resilient bitcoin.
https://m.primal.net/PSUQ.png
This track is for hackers with some level of coding skill, & the ability to use the command line interface (CLI). Familiarity with Bitcoin Core, esp. the JSON-RPC interface is useful. A general understanding of how blockchains and distributed networks work will come in handy.
Who's ready to win? Sign up below! 👇
https://mitbitcoin.devpost.com/

2025-02-23 19:49:35 UTC

- reply

This tool was initially made for the @nprofile…3hr7 website. You can find it here: https://bitcoinops.org/en/tools/reorg-calculator/
https://m.primal.net/PIbN.png

2025-02-23 19:47:56 UTC

New tool in Decoding Bitcoin!
REORG CALCULATOR ⚒️
Computes the probability that an attacker could reorganize z blocks with a given % of the total network hashrate
Here’s the probability of an attacker reorganizing 6 blocks with 30% of the total hashrate
https://bitcoindevs.xyz/decoding/reorg-calculator
https://m.primal.net/PIbM.png

2025-02-21 19:12:57 UTC

Buckle up for today's #DecodingBitcoin post. It's a long one but we promise it's worth your time.
Today we're going to break down how to sign a #bitcoin segwit transaction using a real example from the BIP-143 test vectors (that’s one of the segwit BIPs!)
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/titleimage.png
𝑁𝑜𝑡𝑒: 𝑡ℎ𝑖𝑠 𝑒𝑥𝑎𝑚𝑝𝑙𝑒 𝑖𝑠 𝑓𝑜𝑟 𝑎 𝑠𝑒𝑔𝑤𝑖𝑡 𝑣0 𝑡𝑟𝑎𝑛𝑠𝑎𝑐𝑡𝑖𝑜𝑛 𝑠𝑜 𝑠𝑜𝑚𝑒 𝑜𝑓 𝑡ℎ𝑒 𝑠𝑝𝑒𝑐𝑖𝑓𝑖𝑐𝑠 𝑎𝑟𝑒 𝑑𝑖𝑓𝑓𝑒𝑟𝑒𝑛𝑡 𝑓𝑜𝑟 𝑙𝑒𝑔𝑎𝑐𝑦 𝑎𝑛𝑑 𝑡𝑎𝑝𝑟𝑜𝑜𝑡 (𝑠𝑒𝑔𝑤𝑖𝑡 𝑣1) 𝑡𝑟𝑎𝑛𝑠𝑎𝑐𝑡𝑖𝑜𝑛𝑠. 𝐻𝑜𝑤𝑒𝑣𝑒𝑟, 𝑡ℎ𝑒 𝑔𝑒𝑛𝑒𝑟𝑎𝑙 𝑐𝑜𝑛𝑐𝑒𝑝𝑡𝑠 𝑎𝑟𝑒 𝑠𝑡𝑖𝑙𝑙 𝑡ℎ𝑒 𝑠𝑎𝑚𝑒!
The transaction we'll be working with has two inputs. The first is a legacy P2PK input–we won’t be covering that today.
Instead, we’re going to focus on the second input, the P2WPKH (native segwit) one.
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning1.png
Since this example came from one of the BIP-143 test vectors, we know what the final, signed transaction looks like. The goal is to recreate this:
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning2.png
First, we create the base transaction, the transaction without any signatures.
We’ll start with the
- version number
- marker & flag fields (to indicate the tx is segwit)
- locktime
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning3.png
𝐴 𝑛𝑜𝑡𝑒 𝑜𝑛 𝑠𝑒𝑔𝑤𝑖𝑡 𝑣𝑠. 𝑙𝑒𝑔𝑎𝑐𝑦 𝑡𝑟𝑎𝑛𝑠𝑎𝑐𝑡𝑖𝑜𝑛𝑠: 𝐵𝑒𝑐𝑎𝑢𝑠𝑒 𝑎𝑡 𝑙𝑒𝑎𝑠𝑡 𝑜𝑛𝑒 𝑜𝑓 𝑡ℎ𝑒 𝑖𝑛𝑝𝑢𝑡𝑠 𝑖𝑠 𝑠𝑒𝑔𝑤𝑖𝑡 (𝑛𝑎𝑡𝑖𝑣𝑒 𝑜𝑟 𝑤𝑟𝑎𝑝𝑝𝑒𝑑), 𝑡ℎ𝑒 𝑡𝑟𝑎𝑛𝑠𝑎𝑐𝑡𝑖𝑜𝑛 𝑖𝑠 𝑎𝑙𝑠𝑜 𝑐𝑜𝑛𝑠𝑖𝑑𝑒𝑟𝑒𝑑 𝑠𝑒𝑔𝑤𝑖𝑡.
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning4.png
Here’s what we have so far:
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning5.png
Let’s add inputs! Recall that all inputs come from existing transactions. That means for each input, we need to find the transaction it came from and get:
1. that transaction’s ID
2. the output index
𝐖𝐡𝐚𝐭’𝐬 𝐚𝐧 𝐨𝐮𝐭𝐩𝐮𝐭 𝐢𝐧𝐝𝐞𝐱?
Every transaction has a list of outputs. The “output index” is a way to reference a specific output from the list.
We need to ask, "from a transaction’s list of outputs, which one corresponds to the input I care about?”
For each input, two more things are needed: the 𝐬𝐜𝐫𝐢𝐩𝐭𝐒𝐢𝐠 (placeholder for data required to spend the input), and a 𝐬𝐞𝐪𝐮𝐞𝐧𝐜𝐞 𝐧𝐮𝐦𝐛𝐞𝐫 (usually 0xFFFFFFFF)
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning6.png
After adding all the inputs, the transaction looks like this:
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning7.png
Remember when we said the scriptSig would be a placeholder? Here’s why those fields are currently empty:
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning8.png
Time to add outputs! For each output, we include the
- amount (in satoshis)
- scriptPubKey: the locking script that defines the rules for how the output can be spent
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning9.png
Things are starting to come together!
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning10.png
A few more things are needed before we can get to signing. First is setting up the 𝐰𝐢𝐭𝐧𝐞𝐬𝐬 field.
This is where the signature and corresponding public key go for segwit transactions.
The witness field starts off empty. This is different from legacy transactions where signatures are placed directly in the scriptSig field.
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning11.png
The next thing that’s needed is the 𝐬𝐜𝐫𝐢𝐩𝐭𝐂𝐨𝐝𝐞.
The scriptCode for a P2WPKH (pay-to-witness-public-key-hash) input is:
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning12.png
𝑊ℎ𝑎𝑡’𝑠 𝑡ℎ𝑎𝑡 20 𝑏𝑦𝑡𝑒 𝑝𝑢𝑏𝑘𝑒𝑦 ℎ𝑎𝑠ℎ?
𝐸𝑎𝑟𝑙𝑖𝑒𝑟 𝑤𝑒 𝑠𝑎𝑤 𝑒𝑎𝑐ℎ 𝑜𝑢𝑡𝑝𝑢𝑡 ℎ𝑎𝑠 𝑎 𝑠𝑐𝑟𝑖𝑝𝑡𝑃𝑢𝑏𝐾𝑒𝑦 (𝑟𝑢𝑙𝑒𝑠 𝑓𝑜𝑟 ℎ𝑜𝑤 𝑡𝑜 𝑠𝑝𝑒𝑛𝑑 𝑡ℎ𝑒 𝑜𝑢𝑡𝑝𝑢𝑡). 𝐴𝑙𝑠𝑜, 𝑟𝑒𝑐𝑎𝑙𝑙 𝑡ℎ𝑎𝑡 𝑡ℎ𝑒 𝑖𝑛𝑝𝑢𝑡 𝑡𝑜 𝑜𝑛𝑒 𝑡𝑟𝑎𝑛𝑠𝑎𝑐𝑡𝑖𝑜𝑛 𝑖𝑠 𝑡ℎ𝑒 𝑜𝑢𝑡𝑝𝑢𝑡 𝑓𝑟𝑜𝑚 𝑎𝑛𝑜𝑡ℎ𝑒𝑟.
𝑇ℎ𝑒 20 𝑏𝑦𝑡𝑒 𝑝𝑢𝑏𝑘𝑒𝑦 ℎ𝑎𝑠ℎ 𝑖𝑠 𝑒𝑥𝑡𝑟𝑎𝑐𝑡𝑒𝑑 𝑓𝑟𝑜𝑚 𝑡ℎ𝑒 𝑐𝑜𝑟𝑟𝑒𝑠𝑝𝑜𝑛𝑑𝑖𝑛𝑔 𝑜𝑢𝑡𝑝𝑢𝑡'𝑠 𝑠𝑐𝑟𝑖𝑝𝑡𝑃𝑢𝑏𝐾𝑒𝑦.
Here’s the 𝐬𝐜𝐫𝐢𝐩𝐭𝐂𝐨𝐝𝐞 for the example we’re working on:
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning13.png
Lastly, three important hashes are required.
The first is 𝐡𝐚𝐬𝐡𝐏𝐫𝐞𝐯𝐨𝐮𝐭𝐬. It’s the double SHA256 hash of all input outpoints (outpoint = the transaction id + output index)
The second is 𝐡𝐚𝐬𝐡𝐒𝐞𝐪𝐮𝐞𝐧𝐜𝐞, the double SHA256 hash of all input sequence numbers.
The third is 𝐡𝐚𝐬𝐡𝐎𝐮𝐭𝐩𝐮𝐭𝐬, the double SHA256 hash of all outputs.
That’s everything (finally!). Let’s put it all together into something that can be signed!
When signing a transaction, the spender actually signs a hash of the transaction data, not the entire transaction itself. This hash is called the 𝐬𝐢𝐠𝐡𝐚𝐬𝐡.
The data used to create the sighash is called the 𝐩𝐫𝐞𝐢𝐦𝐚𝐠𝐞.
For a transaction input, the preimage is made of these items:
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning14.png
The sighash_type indicates which parts of the transaction the signature is committing to.
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning15.png
After hashing the preimage twice with SHA-256, we’re left with the sighash.
At last! It’s time to do some signing!
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning16.png
There are a few steps for signing a segwit (v0) transaction.
First, the signer’s private key is used to create an ECDSA signature for the sighash.
The resulting signature has two parts, 𝑟 and 𝑠.
In ECDSA, there are actually two valid s values for every signature: a "high" value and a "low" value.
Both are mathematically valid, but bitcoin requires using the low s value to prevent transaction malleability (that means altering a transaction's ID!)
After selecting the low s value, the signature must be encoded into DER format. This is how it’s structured:
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning17.png
And here’s what the DER encoded signature looks like for our example:
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning18.png
The last step is to add a byte at the end for the sighash type. If we look back at the preimage made earlier we see this example is using SIGHASH_ALL (0x01).
The full code for the signing step looks like this:
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning19.png
Remember the transaction witness field we set space aside for? It’s now time to put the signature in it 🚀
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning20.png
This is how the witness field is structured:
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning21.png
Which works out to be this for our example:
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning22.png
With the completion of the witness field, the transaction is now signed!
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning23.png
This is what the final signed transaction hex looks like broken down:
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning24.png
Bonus: You can use the Bitcoin Core CLI decoderawtransaction command to examine all the parts of the raw transaction hex
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/txsigning25.png
* ~ * ~ * ~ * ~ * ~ * ~
If you made it to the end, give yourself a pat on the back. If you enjoyed it, be sure to like this post so we know to make more like it!
* ~ * ~ * ~ * ~ * ~ * ~
This material is from Decoding Bitcoin, your go-to resource for understanding bitcoin, #privacy, and #decentralization.
You can visit https://bitcoindevs.xyz/decoding/transaction-signing for the full lesson with all the code examples, as well as more free, interactive content.
For more of a challenge, play chapters 4, 5, and 6 of @nprofile…fqsf (https://savingsatoshi.com) to learn about public-private key cryptography, digital signatures, and transaction building 😺
https://technicaldifficulties.io/nostr/bdp/segwittxsigning/savingsatoshi.jpg
Hope you learned something new about transaction signing. If you enjoyed this, share it with a friend and don’t forget to follow us, @nprofile…uvtq for more content like this.
Thanks for reading!

2025-01-30 15:27:45 UTC

We’ve got a good #DecodingBitcoin post for you today. The topic? 𝐄𝐧𝐝𝐢𝐚𝐧𝐧𝐞𝐬𝐬, AKA the order of bytes in a computer’s memory.
When we put it like that it sounds a little boring, but there’s something interesting, and dare we say 𝑎𝑛𝑛𝑜𝑦𝑖𝑛𝑔, about how bitcoin handles endianness…
Before we get to that, let’s better understand what endianness is.
Imagine reading directions in different languages: while English is written and read from left to right, Arabic text flows from right to left.
https://technicaldifficulties.io/nostr/bdp/endianness_1.png
Similarly, computers have two ways to store data:
1. 𝐁𝐢𝐠-𝐞𝐧𝐝𝐢𝐚𝐧 (BE): Most significant byte first
2. 𝐋𝐢𝐭𝐭𝐥𝐞-𝐞𝐧𝐝𝐢𝐚𝐧 (LE): Least significant byte first
https://technicaldifficulties.io/nostr/bdp/endianness_2.png
When computers with different byte orders try to communicate, they can misread each other. It’s like two people reading numbers from opposite directions.
https://technicaldifficulties.io/nostr/bdp/endianness_3.png
𝐁𝐢𝐠-𝐞𝐧𝐝𝐢𝐚𝐧 𝐬𝐭𝐨𝐫𝐞𝐬 𝐭𝐡𝐞 𝐦𝐨𝐬𝐭 𝐬𝐢𝐠𝐧𝐢𝐟𝐢𝐜𝐚𝐧𝐭 𝐛𝐲𝐭𝐞 𝐟𝐢𝐫𝐬𝐭. This is similar to how humans read numbers and Hex in most cases: starting with the most important information.
Suppose we want to store the number 12345678 (hexadecimal: 0x00BC614E) in memory. In big-endian, the bytes are stored in this order:
00 BC 61 4E
https://technicaldifficulties.io/nostr/bdp/endianness_4.png
Observe that:
- The 𝐦𝐨𝐬𝐭 𝐬𝐢𝐠𝐧𝐢𝐟𝐢𝐜𝐚𝐧𝐭 𝐛𝐲𝐭𝐞 (00) is stored at the 𝐥𝐨𝐰𝐞𝐬𝐭 𝐦𝐞𝐦𝐨𝐫𝐲 𝐚𝐝𝐝𝐫𝐞𝐬𝐬 (00).
- The 𝐥𝐞𝐚𝐬𝐭 𝐬𝐢𝐠𝐧𝐢𝐟𝐢𝐜𝐚𝐧𝐭 𝐛𝐲𝐭𝐞 (4E) is stored at the 𝐡𝐢𝐠𝐡𝐞𝐬𝐭 𝐚𝐝𝐝𝐫𝐞𝐬𝐬 (03).
Big-endian is considered more "human-readable" because the data is stored in the order we naturally read it.
𝐋𝐢𝐭𝐭𝐥𝐞-𝐞𝐧𝐝𝐢𝐚𝐧 𝐬𝐭𝐨𝐫𝐞𝐬 𝐭𝐡𝐞 𝐥𝐞𝐚𝐬𝐭 𝐬𝐢𝐠𝐧𝐢𝐟𝐢𝐜𝐚𝐧𝐭 𝐛𝐲𝐭𝐞 𝐟𝐢𝐫𝐬𝐭. This might feel counter intuitive to humans but is more efficient for modern processors.
Using the same number 12345678 (0x00BC614E), here's how it looks in little-endian:
4E 61 BC 00
https://technicaldifficulties.io/nostr/bdp/endianness_5.png
This time, the 𝐥𝐞𝐚𝐬𝐭 𝐬𝐢𝐠𝐧𝐢𝐟𝐢𝐜𝐚𝐧𝐭 𝐛𝐲𝐭𝐞 (4E) is stored at the 𝐥𝐨𝐰𝐞𝐬𝐭 𝐦𝐞𝐦𝐨𝐫𝐲 𝐚𝐝𝐝𝐫𝐞𝐬𝐬 (00).
The 𝐦𝐨𝐬𝐭 𝐬𝐢𝐠𝐧𝐢𝐟𝐢𝐜𝐚𝐧𝐭 𝐛𝐲𝐭𝐞 (00) is stored at the 𝐡𝐢𝐠𝐡𝐞𝐬𝐭 𝐚𝐝𝐝𝐫𝐞𝐬𝐬 (03).
This "reversal" of bytes is common in the Bitcoin Core codebase.
In bitcoin, most data like transaction IDs, block headers, and amounts are all in little-endian format or with the bytes reversed.
https://technicaldifficulties.io/nostr/bdp/endianness_6.png
𝑁𝑜𝑡𝑒: 𝐸𝑛𝑑𝑖𝑎𝑛𝑛𝑒𝑠𝑠 𝑜𝑛𝑙𝑦 𝑎𝑝𝑝𝑙𝑖𝑒𝑠 𝑡𝑜 𝑖𝑛𝑡𝑒𝑔𝑒𝑟𝑠. 𝐼𝑡 𝑖𝑠 𝑛𝑜𝑡 𝑐𝑜𝑟𝑟𝑒𝑐𝑡 𝑡𝑜 𝑠𝑎𝑦 𝑎 ℎ𝑎𝑠ℎ 𝑖𝑠 𝑙𝑖𝑡𝑡𝑙𝑒-𝑒𝑛𝑑𝑖𝑎𝑛. 𝑆𝑖𝑛𝑐𝑒 𝑡ℎ𝑒𝑟𝑒’𝑠 𝑛𝑜 𝑜𝑓𝑓𝑖𝑐𝑖𝑎𝑙 𝑡𝑒𝑟𝑚 𝑓𝑜𝑟 𝑡ℎ𝑖𝑠 𝑤𝑒 𝑠𝑎𝑦 “𝑏𝑦𝑡𝑒 𝑠𝑤𝑎𝑝𝑝𝑒𝑑” 𝑜𝑟 “𝑟𝑒𝑣𝑒𝑟𝑠𝑒 𝑏𝑦𝑡𝑒𝑠”.
For readability, the bytes are swapped back to the style of big-endian when this data is displayed to humans. A block explorer is one example of where you can see this.
Bitcoin Core’s JSON-RPC interface was the first time block hashes were printed for human consumption. That was when someone decided to reverse the ordering of hash so that it looked like a human readable integer.
https://technicaldifficulties.io/nostr/bdp/endianness_7.png
It turns out the real block hash, the actual sha256 value you get if you compute the hash yourself, is:
e4b1d56439d46d9070e58c4368cccc97596fa908daf101000000000000000000
The zeros are actually on the right! At first glance it looks like this is a very large number, but we know the integer value of a block hash actually gets smaller as the difficulty increases.
It's clear that the bytes are reversed and in the style of little-endian. But why? We can thank Satoshi for that. Satoshi decided to interpret the block hash as a little-endian integer. The more zeroes there are on the right side, the smaller the (little-endian) integer.
Since most modern CPUs are little-endian, bitcoin uses it to optimize performance.
However, network protocols typically use big-endian, creating a mismatch 🙀
Big-endian is used for network communication (network byte order). Little-endian is used for bitcoin’s internal storage.
This duality requires developers to frequently, and sometimes frustratingly, convert between the two formats when working with bitcoin data.
Have you been the victim of an endianness oversight when writing bitcoin code? It's a common source of pain for developers new to bitcoin (and even the seasoned ones!)
As covered by the transaction ID example earlier, byte order confusion can be common.
https://technicaldifficulties.io/nostr/bdp/endianness_8.png
Another gotcha is length specification. When converting to little-endian, always specify the correct byte length:
https://technicaldifficulties.io/nostr/bdp/endianness_9.png
Hope you learned something new about endianness today. If you enjoyed this, share it with a friend and don’t forget to follow us, @nprofile…uvtq !
This material is from Decoding Bitcoin, your go-to resource for understanding #bitcoin, privacy, and decentralization.
Visit https://bitcoindevs.xyz/decoding for the full lesson, and more free, interactive content.
Thanks for reading!

2025-01-30 14:27:52 UTC

- reply

Thank you so much! Appreciate your support 😄

2025-01-24 20:52:47 UTC

There is an oft-repeated sentiment in the community that bitcoin does not need you. While bitcoin is designed to be resilient, we 𝑑𝑜 need you. Bitcoin needs all the talent and energy it can gather to solve some of the most difficult technical problems of our time.
Bitcoin in your hands changes everything.
https://m.primal.net/NyXB.png

2025-01-24 20:50:15 UTC

- reply

Thank you! We will pass your kind words onto our designers :)

2025-01-24 20:02:52 UTC

It’s #DecodingBitcoin time! Let’s go over the basic elements of a transaction.
Alice wants to send 5 BTC to Bob. She needs to create a bitcoin transaction using the unspent outputs (UTXOs) in her wallet.
https://m.primal.net/NyTN.png
UTXOs are unspent transaction outputs. They can be used as inputs for new transactions.
Think of them as "coins" in a wallet, waiting to be spent.
Alice checks her wallet and finds two UTXOs:
https://m.primal.net/NyTS.png
To create a transaction, Alice has to specify exactly which UTXOs to spend.
A UTXO is identified by the transaction it came from, specifically
- the transaction ID and
- an index that says where the UTXO is in the list of transaction outputs
https://m.primal.net/NyTY.png
Wallets usually store this information for you but you can also look it up on the blockchain.
Alice's wallet shows these available UTXOs:
- UTXO #1: 4 BTC (from Transaction 1, Output Index 1)
- UTXO #2: 2 BTC (from Transaction 2, Output Index 0)
Together, they provide enough funds (4 BTC + 2 BTC = 6 BTC) for the payment and any transaction fees.
Now Alice has everything she needs to identify her UTXOs. As she adds them to the transaction, she saves space for the signatures she will make later. These signatures authorize the spending of the UTXOs.
https://m.primal.net/NyTd.png
Now that the transaction inputs have been taken care of, it’s time to look at the outputs!
Alice needs to create two outputs:
- 5 BTC to Bob (the payment amount)
- 0.99 BTC back to Alice as change (there is a 0.01 BTC transaction fee)
https://m.primal.net/NyTg.png
Why do we have to make a separate output for change?
UTXOs must be spent in their entirety. You cannot partially spend a UTXO. Instead, you create a new output that sends the excess amount back to yourself as change.
https://m.primal.net/NyTl.png
Looks good! The transaction structure is now complete, but it’s not yet valid. Alice must sign it to prove she owns the inputs. We’ll cover that in a future lesson 🙂
Follow us @nprofile…uvtq to stay updated!
This material is from Decoding Bitcoin, your go-to resource for understanding #bitcoin, privacy, and decentralization.
If you enjoyed it, visit https://bitcoindevs.xyz/decoding for the full lesson, and more free, interactive content.
Thanks for reading!

2025-01-17 16:12:52 UTC

Are you tired of searching for "lightning" only to get results about sparks in the sky and ice hockey teams in Florida?
So are we. That's why we built Bitcoin Search, which pulls from a curated list of credible #bitcoin tech sources.
https://bitcoinsearch.xyz
We've built the world's largest collection of technical bitcoin-related resources: articles, podcast transcripts, blog posts, and more.
Sources are regularly monitored to make sure your search results are up-to-date.
We hand-pick sources for their contributions to technical bitcoin concepts. Examples include the Bitcoin-dev Mailing List, LN dev Mailing List, Bitcoin Optech, and many more.
Bookmark it and try it out today!
https://m.primal.net/NlEE.png

2025-01-16 19:06:41 UTC

- reply

Hooray we finally did it! Thanks for the reminder 😸
Proof of PR: https://github.com/bitcoin-dev-project/bitcoin-dev-project/pull/146
https://m.primal.net/NjjD.png

2025-01-14 20:12:16 UTC

What's the deal with #bitcoin fees? How are they calculated? Where do they go? Let's have a look with a #DecodingBitcoin post:
A transaction's fee is equal to the total amount of bitcoin in the inputs, minus the total amount of bitcoin in the outputs.
https://m.primal.net/Nggr.png
Here's how to calculate the fee for this transaction: https://mempool.space/tx/c27c4d2236fce2a7542e024408d7f89b95e50e42a2c3d10be499c3102ccb45ef
Fee = Input - (Output1 + Output2)
Fee = 299.99430000 - (0.00140000 + 299.99240000)
Fee = 299.99430000 - 299.99380000
Fee = 0.00050000
Fee = 50,000 sats
Remember: Sum(Inputs) should always be greater than Sum(Outputs)
https://m.primal.net/Nggt.png
Fees incentivise miners to include transactions in blocks. Without fees, miners would have little reason to put transactions into blocks!
In addition to fees, miners also receive a block reward.
Total miner revenue = fees + block reward
https://m.primal.net/Nggy.png
How do miners decide what transactions go into a block?
The short answer is miners will usually maximize revenue by prioritizing transactions with the highest fee rate (we've got a whole lesson fee rates coming!)
https://m.primal.net/NghA.png
While miners can choose which transactions to include based on fees, there's a minimum threshold, a "minimum relay fee" that must be met just for a transaction to be relayed through the network.
Transactions below this threshold are rejected by nodes. It helps prevent spam and DoS attacks on the network
https://m.primal.net/NghD.png
This brings us to an important question: What happens if you submit a transaction with a fee rate above the minimum but still too low for current network conditions?
That transaction could sit in the mempool for hours because the fee rate is too low for the high level of network activity. Even if you met the minimum, there can still be plenty of transactions with higher fee rates than yours, ones that miners will choose first.
https://m.primal.net/NghE.png
At this point, you have two main ways to "unstick" it:
1. RBF (Replace-by-Fee)
2. CPFP (Child Pays for Parent)
--------------------------------
That's all for now! We'll dive deeper into fee rates, RBF, and CPFP in a future post.
This material is from Decoding Bitcoin, your go-to resource for understanding #bitcoin, privacy, and decentralization.
If you enjoyed it, visit https://bitcoindevs.xyz/decoding for the full lesson, and more free, interactive content!
And don't forget to follow us for more posts about bitcoin tech and tools to help you in your developer journey 🚀

2025-01-13 23:49:54 UTC

Psst. Don't have enough hours in the day to read the mailing list and Delving Bitcoin? We have a secret weapon for you.
Bitcoin TLDR has daily summaries, available by post or by thread: https://tldr.bitcoinsearch.xyz
Here's today's summary of the bitcoin-dev mailing list:
- Ava Chow announced Bitcoin Core version 28.1. It makes adjustments to p2p configurations to enhance usability & reduce startup failures. It also has internal ID counting updates, enhancements in key handling, build system improvements, & a call for community participation in reporting bugs and joining the announcement list
- @nprofile…dmde raised concerns about the reliability of transaction timestamp data, specifically the vulnerability of nLockTime. It can be manipulated for unfair prioritization benefits, undermining the effectiveness of new prioritization rules.
- Yuval Kogman critiqued misconceptions around privacy mechanisms, focusing on wabisabi credentials & Wasabi wallet. He sheds light on the challenges with safeguarding privacy and security, emphasizing transparency, comprehensive security measures, & ethical considerations.
https://m.primal.net/NfUn.png

2025-01-11 19:51:40 UTC

- reply

Thanks for sharing Ross 😀
Enjoy!

2025-01-10 15:54:11 UTC

Let's talk about the 2 ways to track user balances on decentralized networks. Time for a #decodingbitcoin post:
1. Account Model (Ethereum): Tracks balances like a bank ledger (simple and intuitive).
2. UTXO Model (Bitcoin): Tracks specific unspent outputs from transactions (complex but powerful)
https://m.primal.net/Nagm.png
The account model is like your bank statement. Simple to understand and works well with smart contracts. The downside is it's less private and can be vulnerable to replay attacks.
https://m.primal.net/Nago.png
The UTXO model is like bills in a wallet. UTXOs (unspent transaction outputs) can only be spent once. Each transaction creates new UTXOs, and your balance is the sum of all your unspent UTXOs
https://m.primal.net/Nagx.png
This model has better privacy, prevents double spending, and allows for parallel transaction processing. The cons are it's more difficult to understand, is harder for complex applications, and requires UTXO management.
Here's a comparison chart of the two models:
https://m.primal.net/Nagp.png
This material is from Decoding Bitcoin, your go-to resource for understanding #bitcoin, privacy, and decentralization.
If you enjoyed it, visit https://bitcoindevs.xyz/decoding for the full lesson, and follow us for more free educational #bitcoin content!

2025-01-09 18:42:18 UTC

Like this note if you’re the world’s best ₿OSS contributor.
Repost if you’re going to become one this year.
https://m.primal.net/NZXC.jpg

2025-01-08 16:54:24 UTC

- reply

While Bitcoin Core is mostly C++ and Python, there are many great bitcoin projects written in Rust including LDK, Stratum V2, and Fedimint!

2025-01-08 16:48:35 UTC

- reply

Enjoy! Give it a go and let us know what you think 😃

2025-01-07 20:09:14 UTC

- reply

oh dear! thanks for letting us know. we'll get that sorted out 🫡

2025-01-07 19:32:14 UTC

- reply

oops. going to have a word with our social media intern 😄

2025-01-07 19:31:25 UTC

- reply

good catch! 😸 that link should be to: https://savingsatoshi.com/

2025-01-07 19:25:53 UTC

Want to learn #Rust but don't know where to start? We have a free course that covers the fundamentals of Rust using bitcoin based exercises. It's the best of both worlds.
🦀 rust + bitcoin = 🧡
https://btcdemy.thinkific.com
https://bitcoindevs.xyz/_next/static/media/btc-demy.60731301.png

2024-12-03 17:02:10 UTC

🚀 Help us save Satoshi!
And learn the fundamentals of bitcoin tech while you’re at it
📢 Introducing Saving Satoshi!
The world’s first interactive, practice-focused game to teach you bitcoin development.
www.savingsatoshi.com
Bitcoin tech can be hard to learn.
Yes, there are many incredible resources.
Our goal is to complement them and add our drop of interactivity to the ocean of learning.
Try Saving Satoshi today!
https://image.nostr.build/547d5f07b3c6912c5a351270c4b138100104572a10a5bf7e409cb92d3c1f8509.png
What will you learn?
- How to find and decode the hidden message in the genesis block
- Elliptic curve cryptography
- Message signing and verification
- Building a transaction
- Building a block template
- Bitcoin Script
- How the Lightning network works
- And so, so much more!
How is Saving Satoshi different?
- Logged in state to remember your progress
- Ability to share accomplishments publicly
- A real story to motivate you to learn
- Free and Open Source
https://image.nostr.build/f6b466dd0621495ac6339fc06ff979d8724189f68ea7fffa6ed598d38fad1b4e.png
Saving Satoshi started as a hackathon idea:
“How can we make bitcoin tech education more engaging and fun?”
Since then it’s become a game with 10 fun chapters, and support for both Python and JavaScript
Worldwide there are groups like TabConf and Scalar School playing together.
https://image.nostr.build/1c3adc83581cb1e2645da8ad65de6bf71dc5880d3c71d0da645d43463cd77fdc.jpg
Give Saving Satoshi a go today, and let us know what you think.
Shoutout to the team that helped bring this over the finish line
https://image.nostr.build/8b28802f8e9dab7abe19725194898890c783b48e0113237146f7690edae83415.jpg
Now be quick, Satoshi needs you!
www.savingsatoshi.com

2024-10-10 12:20:56 UTC

🚀 Decoding Bitcoin!
An interactive, exercise-first way to learn bitcoin development
100% free and open-source
👇 Dive into bitcoin tech with us below!
https://bitcoindevs.xyz/decoding
Decoding Bitcoin makes learning bitcoin tech easier, funner, and more efficient
It gives you the perfect mix of
- Concise explanations
- Real-world exercises
- Tons of interactive demos
https://image.nostr.build/16d5efa3ed839858f74ea709ae1d712c530ea024599671cbd9831516d797a179.jpg
Being able to play with interactive elements to understand Bitcoin concepts is the best way to solidify a working mental model
https://image.nostr.build/903f2dc837dae0c4d2b063f6ff710b984fb47ddbd76bf492fc356f75099e6824.gif
No libraries allowed, you’ll craft everything from scratch!
We support both JavaScript and Python (of course!)
Each bitcoin concept comes with its own exercise, so you’ll learn not just how things work, but also when and where to use them.
https://image.nostr.build/8e50c7c926389a8b39ac2fceef705f4031af604fd23bc36d8e62062938b3347e.png
By the end of each module, you’ll challenge yourself by creating a project to test your understanding.
https://image.nostr.build/c25ba3054e667f53b163033f44f9f8df198db160d51ed59e5cfa24c82c30f34b.png
We’ve started with the first module on Scripts.
More content is coming soon!
Please share your feedback on this first release—it helps us understand what you want to see next, whether it’s content or new features.

2024-08-29 17:53:10 UTC

Incredible walkthrough of our ecosystem!
Thank you to @npub1gjy…ektz for the deep dive!
We look forward to building more products, services, and infrastructure to enable the world to study and contribute to bitcoin FOSS.
#note1jnl…qhj3

2024-07-31 14:58:39 UTC

You spoke, we listened
🌘
https://image.nostr.build/9ec2895b3e6521278f0ad821c6bb01b26c5261274188f7cdb3756fc5fc321e8f.jpg

2024-07-18 15:27:25 UTC

📢 Introducing Bitcoin Search v2
Want to find that one specific technical bitcoin nugget?
You’re in luck!
There is only one place that allows you to search the depths of bitcoin’s technical ecosystem and retrieve the highest signal info about bitcoin tech.
🔗👇
https://www.bitcoinsearch.xyz
Bitcoin Search is unique
Unlike Google, when you search for “lightning”
We actually know what you mean
(Hint: It’s not electric sparks in the sky. Or an ice hockey team in Florida).
https://image.nostr.build/e838c8e404a555ab984daf2fc4211791214175dbbd660b0eec04633d65d3e6a8.jpg
Features
We let you sort and filter by categories that matter
- Authors and
- Sources
And in ways that matter
- Relevance and
- Date
And with views you love: dark 🌑 & light 🌞
Scope
The scope of the product is laser focused: bitcoin tech
Users can suggest sources deeper in the product. This bolsters our repo of bitcoin tech sources
We build pathways to scrape the data
Which grows our library of bitcoin tech literature and resources
Ecosystem of Knowledge Creation
Bitcoin Search thrives as a collaborative ecosystem.
As you do more Transcript Reviews and suggest new credible sources, our database continuously expands and improves, ultimately benefiting the entire Bitcoin technical community.
It’s a virtuous cycle of knowledge creation
https://image.nostr.build/e53f38fa46cacd4c402e300d5482f474907f3f2a9aef4ed9f9ac0aa4832c682c.png
We already had a live V1. Why build a V2?
We wanted to improve comprehension of the product for newer devs interested in bitcoin tech
While improving its usability, and increasing a sense of delight when using it.
https://image.nostr.build/ea145bef4a6ee0fe88b976c149bbc59f9abe2535bb4d27fe2b8d46709ff66ab0.png
Biggest thanks to the team!
Dev: Emmanuel, Solomon, Balogun, Otuedon
Design: @npub1xgl…fmlc
Dev Lead: Theo
Vision: Jonas
Product: @npub1a6n…s58k
So, give Bitcoin Search a go!
https://www.bitcoinsearch.xyz
Tell us what you like and don’t like. What’s missing. What should we do better?
And importantly - what kinds of products and tools are missing for bitcoin devs and builders in the ecosystem?

2024-07-02 16:21:33 UTC

Want to contribute to #Bitcoin FOSS development
But don't know where to start?
📢 Introducing Bitcoin Good First Issues!
A tool designed specifically for devs just entering bitcoin development.
https://bitcoindevs.xyz/good-first-issues
🤔 We know it’s hard to guess which projects to start with and what issues to tackle.
Bitcoin Good First Issues gathers beginner-friendly issues labelled Bug, Help Wanted, and (heh) Good First Issues.
It pulls them live for your from vetted Free Open Source Software projects.
🛠️ Why Give It a Go?
- Vetted Projects
- Easy Navigation
- Lowered Barrier to Entry
Whether you're just starting or already a developer, Bitcoin Good First Issues is built to accelerate your contributions.
Give it a roll and make a difference! Let’s build the future of bitcoin together.
👩‍💻 Check the image below to learn how the data flow works:
https://image.nostr.build/d06ce33d05df50add214ae4fc481b8cfb6d81c32616cfae6c364d8deb16f3b58.png
🖤 Biggest thanks to our team!
- Vision: Theo
- Ideation: Emmanuel, Solomon, Abubakar Ismail
- Design: Theo with thanks to paperpsych
- Dev: Theo, Solomon, Balogun
- Product: @npub1a6n…s58k
📃 Examples of vetted FOSS projects in Bitcoin Good First Issues
- BDK
- Core LN
- Eclair
- Fedimint
- LDK
- Polar
- Stratum Mining
We're looking forward to your feedback!

2024-06-06 19:50:25 UTC

Better search
For better learning
And better buidling
Coming.
https://i.nostr.build/KGXjg.png

2024-05-30 16:09:02 UTC

Soon
👀
https://image.nostr.build/5f86372e97ace4751d7ff9b065cf3668a05c78404d7b8ab0ac366720d6ace892.jpg

2024-05-15 18:29:54 UTC

We're building a ton of products
- Tool to make bitcoin concepts easier to grok
- Tool to make it easier to find issues to work on
- Tool to remove friction in finding bitcoin-related technical content
Soon

2024-05-14 02:51:01 UTC

👀
#note1u38…z5c0

2024-05-14 02:49:13 UTC

Hello, world!