Avatar
/dev/fd0
6681268ace4748d41a4cfcc1e64006fb935bbc359782b3d9611f64d51c6752d9

Researching these 3 things this week to see if self custodial and decentralized chaumian ecash is possible

No. The reason I couldn't find the event on relay is because it never got published. Connection to relay was closed after publishing first event. So removing this line after first sleep fixes the issue:

`relay_manager.close_all_relay_connections()`

It was just created and event id was printed.

Kind 1 event gets published but cannot find Kind 4 event on that relay published by publish_dm_event()

What could be the reason? Here's the python script if you want to test: https://pastebin.com/raw/dNFNB9XF

You will have to clone [python-nostr](https://github.com/jeffthibault/python-nostr) and save this python script inside python-nostr directory to run it

Replying to Avatar Max

We made 610 Bitcoins anonymous with a single coinjoin transaction: https://mempool.space/tx/fb596c9f675471019c60e984b569f9020dac3b2822b16396042b50c890b45e5e

Stack sats, stay private.

Number of inputs: 327

Number of outputs: 279

Value: 610.74252451 BTC

Fee rate: 50.53 sats/vbyte

Input anonset: 4.48

Output anonset: 7.15

Isn't it obvious that first 2 inputs are linked to first 7 outputs? What kind of anonymity did these achieve in this transaction?

A paper from 2020 co-authored by Christian Decker shared that 10% nodes hold 80% liquidity:

LN: A second path towards centralization of the bitcoin economy - https://arxiv.org/pdf/2002.02819.pdf

Liquidity in 2024: https://mempool.space/lightning/nodes/rankings/liquidity

Maybe someone could write another paper with present stats including use of custodial wallets

Replying to Avatar fiatjaf

https://github.com/commerceblock/mercurylayer/blob/testnet_guide/docs/testnet_guide.md

Instructions for experimenting with Mercury Layer on testnet.

Mercury Layer is an implementation of the statechains concept in which the server is fully blind and doesn't even have to know it is doing anything related to Bitcoin. All it does is generate keys, sign things and delete keys.

An amazing technology that works today but could be made 10x better with APO.

or CTV

... there is a proof of concept built by waxwing which does the same thing trustlessly using OP_CTV on signet

https://github.com/AdamISZ/pathcoin-poc

If filtering is not censorship, why do you dislike filtering done by twitter? why work on nostr?

Problem exists outside twitter as well. There is no agreement on any covenant proposal.

Are there any other organizations supporting bitcoin privacy projects, in addition to HRF and OpenSats?

Replying to Avatar Cyph3rp9nk

Idea of coinjoin implementation on Liquid.

Through the pegins and pegouts in the Liquid network we could follow the trace of a user, although it is true and it must be taken into account that the bitcoins that are delivered in the pegout are not linked to the bitcoins sent in the pegin. In principle, if I am not mistaken, a sort of FIFO queue is used and blockstream also performs consolidation processes of the addresses containing the bitcoins in the pegin.

This adds privacy in the Bitcoin chain, but we could still track through liquid even with confidential transactions.

As I mentioned before, with sideswap we avoid this because when you do a pegout you are really doing a swap, for small amounts they use their cache hotwallet and the actual pegout is done a posteriori thus unlinking it from the delivered coins and breaking the traceability, but desirably this would work for all amounts and not depend on a third party.

We could adapt joinstr to work on Liquid and confidential transactions, with this we would achieve that after a pegin + a coinjoin with joinstr it would be impossible to follow the trace and given the above mentioned peculiarities in which there is no relationship between the bitcoin of the pegin and the pegout + coinjoin + confidential transactions, with a single round of coinjoin would be more than enough and much more economical than current solutions.

nostr:npub1v6qjdzkwgaydgxjvlnq7vsqxlwf4h0p4j7pt8ktprajd28r82tvs54nzyr You see the crazy idea? maybe I'll get to work on it.

Liquid is a fork of core managed by federation

I want to build projects for bitcoin

use it for dbcache to do IBD faster

Bitcoin meetup in Mumbai on 4 Jan 2024. Invite-only.