Replying to Avatar calle

This should exist:

txtr - A Bitcoin transaction relay network over Nostr

A plebian underground network of Bitcoin nodes that relay each other's transactions upon encountering them on Nostr. This should not aim to be part of Bitcoin Core and therefore also should not look for explicit support.

What it achieves:

- Removes the ability of chainalysis companies to determine which IP a transaction originated from (they achieve this via millions of P2P connections and other timing-based methods).

- What Dandelion does but without the DDoS vector.

Here is how it could work:

- You run the txtr daemon locally next to your Bitcoin Core.

- All txtr daemons publish Bitcoin transactions on nostr and listen for transactions from other users.

- When you want to make a tx on your Bitcoin Core, you don't send it over the P2P network but via txtr which publishes the tx on Nostr.

- If any txtr daemon encounters a Bitcoin tx on Nostr, it sends it to the Bitcoin network over the P2P connections of the local Bitcoin Core client.

Interesting properties:

- Only your relay knows your IP which you can easily hide.

- You could be connected to tens or even hundreds of relays, you can switch as often as you like. Permanence does not matter in this context.

- You can publish every tx from a new pubkey. Identities do not matter in this context.

- Depending on the tx volume on a particular relay, your txtr daemon could randomly chose to relay some txs and some not, you don't need to cooperate therefore you can't be DDoS'd.

Transactions transmitted over relays - txtr

Generelly a cool idea. But wouldn't we achieve the same thing by simply *publishing* our txs via a rotating set of "reputable" Electrum servers?

Say Sparrow had the option to set two Electrum servers: A for incoming/validating (my own node), B for outgoing/publishing (Craig's curated list of public Electrum nodes. Blockstream, Emzy etc)

No need for extra daemons, reliance on a extra network infra etc

Reply to this note

Please Login to reply.

Discussion

No replies yet.