Finally, safely use secrets with your agents without having all of them leak by the agent reading them
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:
If you try it out let me know what you think!
Repo with how it works:
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:
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
and I created the dlctix contract to see who can predict the weather better.
Hopefully I win the 5000sat bet 👀
7/21/2025, 3 engagements
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
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)?
8/20/2024, 1 engagement
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
7/1/2024, 1 engagement