Another week and more progress, no more blinding signing unless that’s your jam: https://github.com/tee8z/keymeld
Next up is adapter signature support
Finally finished up the first draft of a tool that enables generating a musig2 signature inside aws enclaves. One piece of a bigger puzzle solved, on ward
Getting to this point has been a grind but I have successfully broadcasted a dlctix funding transaction that merges funds from escrow transactions (which were atomically swapped from hodl invoices) on mutinynet.
The transaction:
The site I have running https://www.5day4cast.com/ that nostr:nprofile1qqsvh2ee4ctthn53t8fwgpuz72d90ydgju2pdwxu2sg7csl3jec2e7spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9rhwvaz7tmvda3kzmrgdaehgw3hxumnwtcx509eh and I created the dlctix contract to see who can predict the weather better.
Hopefully I win the 5000sat bet 👀
Shot out to nostr:nprofile1qqs0awzzutnzfj6cudj03a7txc7qxsrma9ge44yrym6337tkkd23qkgpr4mhxue69uhkummnw3ezumt4w35ku7thv9kxcet59e3k7mf0qythwumn8ghj7un9d3shjtnnw3hkuetj9e3k7mf0e3rlc8 for the great protocol design and crate for dlctixs
Getting to this point has been a grind but I have successfully broadcasted a dlctix funding transaction that merges funds from escrow transactions (which were atomically swapped from hodl invoices) on mutinynet.
The transaction:
The site I have running https://www.5day4cast.com/ that nostr:nprofile1qqsvh2ee4ctthn53t8fwgpuz72d90ydgju2pdwxu2sg7csl3jec2e7spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9rhwvaz7tmvda3kzmrgdaehgw3hxumnwtcx509eh and I created the dlctix contract to see who can predict the weather better.
Hopefully I win the 5000sat bet 👀
Still wish coinkite accepted lightning payments instead of just onchain, but it get it haha
I never realized how cheap satscards are, this is an incredible product, 10/10 would recommend giving as a gift to people
The bitcoin ecosystem is turning into a permaculture, will not explain further
Instead of removing the datacarrier flag, we have the onchain data to see what’s a reasonable default that allows the majority of transactions to propagate, maybe that’s a palatable step towards reducing the delta between corporate miner mempools and regular node mempools?
find those nodes that support onion message forwarding 👀 https://github.com/tee8z/onion_routing_finder
Side-note, vibe coding python scripts for simple data analysis while double checking that the data is accurate can be pretty productive
find those nodes that support onion message forwarding 👀 https://github.com/tee8z/onion_routing_finder
🚀 Meet the new Voltage Platform – the easiest way to integrate Bitcoin and soon stablecoin payments into your business.
We’ve removed the complexity:
✅ No node or channel management
✅ No liquidity provisioning
✅ No blockchain exposure required
With just a few API calls, your team can start sending and receiving instant global payments using Bitcoin or stablecoins — and settle in USD or BTC. Our credit-based wallet model lets you transact now and pay later, improving capital efficiency while reducing operational overhead.
🔐 Send and Receive Bitcoin with zero exposure to volatility
📊 Use our dashboard to monitor payments, manage teams, and streamline compliance
💡 Built for developers, CFOs, and product teams alike
Available today in development beta, with mainnet coming soon: https://voltage.cloud/payments
Just the beginning, come build 🔨
nostr:nevent1qqsqd4rhzal97ad6qju53tpe9wutcemd3k3yedpwmza8cdplywvaxnqppemhxue69uh5qmn0wvhxcmmvrwsm5e
Ngl something that makes me as nervous about the mempool accelerators affect on the accuracy of fee estimation from a regular bitcoin core node are the plans of a futures market for block space. This will distort the accuracy of what it cost to get a transaction mined within a given range of blocks as these futures pricing and timing will most likely be private between a large miner and a service provider. Making it quite difficult for applications/protocols that require get a block mined within a given range to actually accomplish this goal. Especially if something in that futures market acts is a surprising way (flood of futures transactions all coming due at the same time pushing out what would normally get included just looking at one’s own mempool estimation). Something to think about when building new or expanding existing protocols, you may not be able to get your transaction mined within a given range just based on the data feed from the “spot market” (price from the mempool), you’ll need some way to know what future contracts are settling at a given price to see what is truly required.
New weird software just dropped, keysend messages around to all your lightning node buddies:
I added the ability to easily Doppler to a box running in the cloud! Should make it much easier to build against a regtest or signet cluster of nodes and share with a team: https://github.com/tee8z/doppler?tab=readme-ov-file#deploy-on-digitalocean
Example of what it looks like when deployed
Have a test site running on mutinynet, no nostr chat/alerting yet as I focused my time on making the buy-in and pay-out screens plus getting the deployment working. Nostr chat and alerts up next. I open sourced the coordinator code this weekend as well for those curious: https://github.com/5day4cast/coordinator
Build more weird software, make the odd tool nobody but you might use, enjoy the craft of making something