tee8z

Finally, safely use secrets with your agents without having all of them leak by the agent reading them

https://github.com/tee8z/via

Made a little arcade style game this weekend. It’s pretty fun, can play for free in practice mode or enter into the daily competition, highest score wins the pot of sats:

https://proofofscore.win/

If you try it out let me know what you think!

Repo with how it works:

https://github.com/tee8z/proofofscore

A site that can attest to weather predictions you’d say 👀

https://www.4casttruth.win/

This should be the last big re-write , but really proud of this work.

I finally got keymeld (MuSig2 in AWS enclaves) to survive restarts. The core problem: every time an enclave restarts, it loses its master keypair. That keypair is what decrypts participant private keys during keygen—so losing it means all your encrypted session data in SQLite becomes useless. Participants would have to re-register and regenerate aggregate keys from scratch. Not acceptable for production.

The solution is AWS KMS envelope encryption. On first boot, KMS generates a Data Encryption Key (DEK). The enclave encrypts its master private key with that DEK using AES-256-GCM, then stores both the KMS-encrypted DEK and the DEK-encrypted master key in SQLite. On restart, the enclave sends the encrypted DEK back to KMS, gets the plaintext DEK, decrypts the master key, and replays completed keygen sessions from the database to restore state.

What I didn’t expect: stress testing this with 100+ parallel sessions completely broke things. VSock connections under heavy load turned out to be unreliable—connections dropping, timeouts everywhere. Ended up building a proper connection pool with health checks and auto-reconnection. But the bigger rewrite was the concurrency model. The original architecture had too much shared state and locking. Ripped that out, reduced shared state, and converted many commands to batched versions. Much higher throughput now.

The result: 1000 parallel adaptor signature sessions with 3 signers each, completing in ~4 minutes. Worth the pain.

Also added proper testing infrastructure “just test-kms-e2e”restarts enclaves and verifies the keys survived, “just stress adaptor 100” hammers it with parallel sessions. Local dev uses Moto to mock KMS.

Single signing support is next. 👀​​​​​​​​​​​​​​​​

The goods:

https://github.com/tee8z/keymeld/pull/11#issue-3770532164

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

https://github.com/tee8z/keymeld

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:

https://mempool.space/tx/1e81e3ad0dc49270a39ac4eea29fb3c2d572a1ae412ef8037abbe60a8c59e26b?mode=details

The site I have running https://www.5day4cast.com/ that

and I created the dlctix contract to see who can predict the weather better.

Hopefully I win the 5000sat bet 👀

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

New weird software just dropped, keysend messages around to all your lightning node buddies:

https://github.com/tee8z/send_sats

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

Finding the sweet spot for highest success rate with lightning payments 👀

More progress made this weekend, finally have payouts working. Next step is adding in a nostr chat and emitted notifications from the coordinator to users about a competition they are in. A test site on a signet coming soon™️

I think dlctix sweet spot for a viable product will be person to person future contracts used as way to hedge risk in people’s lives and businesses, this is something the traditional financial system doesn’t really support in any meaningful way. Future contracts are really a product used by much larger institutions to hedge risk, which the traditional financial system optimized for, but these sorts of products could be useful if package in a clean UX.

alright let’s see if this wallet of yours works tapbc1qqqszqspqqzzpprh6m04jcxvqh3hh9q3hnlf4x7ns6qhy73sgww8hg8yug25smj0qcss9xk6yuc0z9tmwgvfpsg6c5vukehqahgt42tdu85nxh585nmvdagvpqssylsm6277gyn3t9c4t6qntwluclu82chmqgqzamxegzdsf0mlmnzlpgqkgrpww4hxjan9wfek2unsvvaz7tm4de5hvetjwdjjumrfva58gmnfdenjuenfdeskucm98gcnqvpj8y8kgdze

In the spirit of "building in the open" here's a fuzzy video show 3 users entering into a competition, creating an aggregate signature via musig2 and broadcasting the funding transaction of a dlctix contract after the coordinator's wallet successfully signs it. Next will be getting the payout out functionality working/hooked up along with a nostr public chat group.

Once the features have all landed, and there's been a bit of code clean up, all the code will be open sourced

https://streamable.com/c91tsg

Technologies used so far:

• bdk-wallet in the browser and server: https://github.com/bitcoindevkit/bdk
• nostr-sdk in the browser and server: https://github.com/rust-nostr/nostr/tree/master/crates/nostr-sdk
• dlctix in the browser and server: https://github.com/conduition/dlctix

The bitcoin regtest environment is being manager and run via doppler locally as well (creating the bitcoin node, esplora instance and a few connected lightning nodes): https://github.com/tee8z/doppler

I’ve decided I’m going to open source this project I’ve been grinding on that is a coordinator for a dlctix competition around weather predictions. Basically users will create entries for a few points of predictions across a number of cities and compete against others in the competition for coin (flow feels similar to daily fantasy sports). The coordinator can be fully untrusted and is non-custodial of users funds. Payouts can be on-chain or lightning and entry fees are paid in lightning. The competitions is a dlc contract on chain and the competition outcome is determine by an oracle that attests to who won. Code is still actively being worked on and not really just yet to release it, but keep an eye out, more to come soon 👀

Been cooking this weekend 👀

DLC related tech is the most slept on in bitcoin dev IMO, but it has the potential to make some very interesting products. I think people dismiss it due to it behind hard to build and scale. It also has to be tailored for whatever you use-case is, rarely vanilla DLCs get you all the way there

Big release for Doppler! v0.4.0 An Esplora instance can be attached to any Bitcoind setup in a simulation doppler file. Take a peak at the example Doppler setup 👀 github.com/tee8z/doppler/… github.com/tee8z/doppler/… It turned out to be a challenge, but I'm excited to start using it!

For anyone that tried to use Doppler’s https://github.com/tee8z/doppler release binaries in the past on an Apple computer, I finally got around to fixing the build and the latest release will work on a Mac now, cheers 🍻

With all the soft fork talk

Taking a much needed break up in Maine with my wife, a lovely place. I could definitely see myself moving here

Come vote for your favorite pepes using nostr!

https://pepe.vote/

Hackathon project for tabconf done by me,

Get ready for some simulation magic, preview of new look for Doppler 👀

Build pipelines are hard, a lesson that never ends

I’m starting to realize with window.nostr and the ability to display or pay a lightning invoice, that gives a developer a lot of cryptographic primitives that makes creating a dlctix client in the browser possible, I’m kind excited to see what I can make with them

Does anyone know of a good open source example on how to implement nostr login, with extensions or with having the user create their own keys in the browser ( having the key creation offloaded to rust wasm)?

Always satisfying getting a side project to “working”, but then the real beast of deploying shows up to ruin the fun

Youth brings change and energy, if you find a problem to solve young nothing wrong with going all in

Highly recommend making a trip to New Hampshire white mountains if you ever get the chance, they are quite the sight and an incredible place to backpack, picture from my most recent trek there

“Split a commit, make your code reviews life easier, it can’t be that hard…” absolutely rugged myself, thankfully “git reset —hard” exists and learned to push it remotely before trying to get fancy with git a long time ago

https://github.com/BitcoinCoderBob/Satogram Lightning spam is good for the network, change my mind

So much of the world runs on people NOT flipping a switch I bet https://cdn.nostr.build/i/f8620db9d3a0dbfeeb2b7d858a40ddfab4cc1d04131232aa506ea9716d9fe6f2.jpg

Does anyone know why it’s “bad” for a bitcoin miner to also be a lightning routing node? ie. Are there possible exploits a miner is able to do to its peers/channel partners that are not possible for regular routing nodes? I feel like I’ve heard “don’t just a miner that’s also a routing node” but don’t quite remember why, will sling some sats around to whoever has a solid answer

Magic https://cdn.nostr.build/i/3b5edf52905b422b8e3a93e7a9c052bd13fb9e09a3bf8aa22bf5bf6d358ba494.png

“You guys are missing the fish from the forest”

Man, I can’t seem to get this verification to work with nostrnest damn haha

Out here trying to open some channels cheaply, but the mempool is all full of NFT transactions, tough day

So bullish on nostr