Privacy and self-custody services with a central point-of-failure are not stable long-term.

No Bullshit Bitcoin

AgoraDesk / LocalMonero P2P Exchange to Shut Down on November 7

AgoraDesk, a no-KYC peer-to-peer Bitcoin trading platform, announced that it has begun the winding-down process of its operations.

No Bullshit Bitcoin

zkSNACKs to Suspend Its Coinjoin Coordination Service on June 1st

zkSNACKs, the company pioneering the development of Wasabi Wallet, is shutting down its coinjoin coordination service, effective from June 1st, 202...

No Bullshit Bitcoin

Samourai Dojo v1.25.0: Removed Whirlpool CLI

Samourai Dojo is an end-to-end bitcoin wallet backing server for powering Samourai Wallet and other light clients.

No Bullshit Bitcoin

Phoenix Wallet to Stop Serving US Customers on May 3rd

Phoenix wallet users in the United States are encouraged to close their channels and empty their wallets prior to May 3, 2024.

No Bullshit Bitcoin

Sparrow Wallet v1.9.0: Remove Whirlpool Client & Soroban-related Features

Sparrow is a free and open source desktop Bitcoin wallet focused on security and privacy.

No Bullshit Bitcoin

Samourai Wallet Founders Arrested & Charged with Money Laundering, Unlicensed Money Transmitting Offenses

U.S. Department of Justice (DOJ) Prosecutors are alleging Samourai Wallet laundered over $100 million in criminal proceeds.

The cull we're seeing in the past couple weeks is just the beginning, but it's a good sign: They're pushing back because we're gaining ground. If you want to run a privacy business, i see 3 choices: - Decentralize your business (no single PoF) - Mask yourself (build pseudonymously) - Comply (by KYCing)

@craigraw How do you feel working on Sparrow Wallet, now that we're seeing the US government prosecute the Samourai devs?

I made a self-hosted Lightning Address webserver, because for some reason I couldn't find any good ones out there already.

GitHub

GitHub - conduition/lnaddrd: A self-hosted server to provide yourself with a Lightning Address.

A self-hosted server to provide yourself with a Lightning Address. - conduition/lnaddrd

This is what powers my snazzy new `conduition@conduition.io` LN address 😇

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

The Noise protocol is to Web3 what TLS is to Web2. Noise is used by Wireguard, the Lightning Network, I2P, even WhatsApp to enable secure communication with all kinds of different handshake styles. If you've never played with Noise before, I would encourage you to read the spec.

Noise Protocol Framework

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 - conduition/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. - conduition/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).

Sounds like IPFS to me. Why not just upload blobs to IPFS instead and skip the extra dev work?

Hey @nick, zebra-lucky and I are trying to merge Bitcoin Taproot support into the ZCash Foundation's Rust implementation of FROST. Open to feedback or suggestions 😎

GitHub

Add frost-secp256k1-tr crate (BIP340/BIP341) by zebra-lucky · Pull Request #584 · ZcashFoundation/frost

add frost-secp256k1-tr crate with support of BIP0340, BIP0341

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.

They picked me! My Ticketed DLC concept has been selected for the backdropbuild.com v3 cohort 😇 Check out my repository here to watch the commits coming in over the next few weeks/months 👀

GitHub

GitHub - conduition/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. - conduition/dlctix

My end goal is to execute a real ticketed DLC on mainnet with volunteers from Nostr and StackerNews.

Prediction: headlines in 2040 will look like: - "EU bans sale of 'non-approved' phones and laptops" - "Australia cracking down on illegal computation" - "New 'client-side safeties' mandated for all devices produced for sale in USA" Governments can't tolerate our ability to circumvent them with code. The EU is already trying to force backdoors into E2EE messengers. Someday they will escalate to banning general-purpose computing hardware because it can do things they don't like: deepfakes, bitcoin, encryption, TOR. Draconian laws will never stop coming, but we dont have to stop them - We need only slow them down enough that we can out-engineer their weak-ass laws. Wanna help slow them down? Donate to the Satoshi Action Fund or the EFF today using Bitcoin. https://www.satoshiaction.io/

Electronic Frontier Foundation

Defend Privacy and Free Speech

Don’t let tyrants co-opt tech. Join EFF and help fight back.

Anyone with STARK experience know how to build and validate a simple proof of secp256k1 discrete logs and SHA256 hashes? I know ZeroSync must be doing this as part of their blockchain sync proofs. But i'm looking for a self-contained way to build and validate the proofs in rust.