"Sell me this preimage." You can verifiably purchase the solution to any NP-Complete problem using Bitcoin (and Lightning), combined with zero-knowledge proofs. - Buy the solution to a sudoku puzzle - Buy the prime factors of an RSA key - Bridge HTLCs with PTLCs - Buy a valid proof-of-work - and more...

Conduition

Verifiably Buy Solutions to NP Problems with Bitcoin

Using zero-knowledge proofs to convert a standard HTLC into the purchase of a secret with arbitrary properties.

You can settle Discreet Log Contracts with Chaumian ECash!

Conduition

Discreet Log Contracts with Ecash Notes

Settling Bitcoin smart contracts instantly off-chain using a Chaumian Ecash mint as a trusted blind intermediary.

@calle and other ecash devs: Do you think this would make a candidate NUT extension on the cashu spec? Feedback appreciated 😎

GitHub

Discreet Log Contracts settled with Chaumian ECash by conduition · Pull Request #6 · conduition/conduition.io

Available for reading here: https://conduition.io/cryptography/ecash-dlc/ Suggestions/fixes appreciated 🙂

I made a Rust library for 2-way async TCP sockets with a Noise-powered authenticated encryption layer. Uses the NNpsk0 handshake protocol.

GitHub

GitHub - conduition/tokio-noise: A Noise protocol encryption layer on top of tokio streams.

A Noise protocol encryption layer on top of tokio streams. - conduition/tokio-noise

I suppose bitcoin devs love #Rust for the same reasons they love Bitcoin. The scarcity and careful auditing of variables passed around in memory mirrors the scarcity and careful auditing of UTXOs passed around Bitcoin's ledger. Allocating new memory is as much an event as mining new bitcoins: Regular, but noted and tracked. In Rust, a value may be borrowed many times, but its value may be consumed only once. Bitcoins can likewise be IOU'd countless times, but ultimately only belong to one script-pubkey. By comparison, languages like Go and Javascript feel very... inflationary. They have an opaque, centralized, bloated, and omnipotent garbage collector attached to every runtime which allocates and deallocates memory as it pleases. Memory can be needlessly duplicated thousands of times entirely by accident, or over-collateralized by shared mutable references. Some languages are the opposite, like C: Total anarchy. "Sure, allocate as much memory as you'd like. Deallocate it whenever. Read whatever you want, write wherever. Just try not to segfault." Only Rust, like Bitcoin, strikes the perfect balance of organized chaos: a rehearsed ballet, in which all the dancers know their movements by heart.

As part of the #BackdropBuild Hackathon, I elected to commit myself to making a prototype of the 'Ticketed DLC' protocol I proposed a few months back. 37 days later, here I am with a working prototype. Setting a deadline for yourself can really make a difference - Who knew?

GitHub

GitHub - tee8z/dlctix: Ticketed Discreet Log Contracts (DLCs) to enable instant buy-in for wager-like contracts on Bitcoin.

Ticketed Discreet Log Contracts (DLCs) to enable instant buy-in for wager-like contracts on Bitcoin. - tee8z/dlctix

There is certainly plenty of optimization and upstream-interop work left to do, and having PTLCs on Lightning would make this SO much more efficient on-chain. But as a proof of concept anyone can play with today, I'm incredibly happy with the result. Running against regtest, all tests are passing, and simulated players can buy into simulated DLCs simply by buying SHA256 preimages (e.g. via Lightning).

I can't put into words how good it feels to make ticketmaster engineers salty enough that they feel obliged to send me hate mail.