public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: yanmaani@cock.li
To: AdamISZ <AdamISZ@protonmail.com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bulletin boards without selective censorability for bitcoin fungibility markets
Date: Wed, 25 Nov 2020 01:52:08 +0000	[thread overview]
Message-ID: <60346b02bca27cc14a950373490250ac@cock.li> (raw)
In-Reply-To: <sTHQz03Yb85tmjxs3cwtzPXi8pYKR0jGYhIN0pJWV-h6FuMkevKS41kRnuXcNA9z1QN8T0KZlewLCpsExyJV7h-MlFuGJ41onn9T0QYaMBA=@protonmail.com>

On 2020-11-23 12:24, AdamISZ via bitcoin-dev wrote:
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Monday, 23 November 2020 00:40, AdamISZ via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> 
>> Canvassing opinions/critiques from those working on bitcoin and 
>> related protocols.
>> 
>> See the attached gist for a write-up of an outline of an idea, which 
>> is conceived for joinmarket but can apply in other scenarios where 
>> there is market for liquidity and in which privacy is a very high 
>> priority (hence 'bitcoin fungibility markets' can certainly include 
>> coinswap along with coinjoin, but possibly other things):
>> 
>> https://gist.github.com/AdamISZ/b52704905cdd914ec9dac9fc52b621d6
> 
> Greg Maxwell pointed out to me on IRC that this idea doesn't work:
> there is only a receipt on the commitment to the offer (message) from
> the maker, not on the plaintext version, hence there is nothing
> stopping the maker from falsely claiming censorship after not sending
> the plaintext.
> 
> Reflecting on this a bit more, my intuition is that this problem is
> much more difficult than I had hoped; if there is a solution I suspect
> it involves much more sophisticated ideas. Many solutions just end up
> begging the question by presuming the existence of an uncensorable BB
> in order to create a new one; and/or use the blockchain for that
> function, but that is too slow and expensive, usually. I'd be happy to
> be proved wrong, though :)
> 
> waxwing
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Blockchains are bad for this, because you don't want for it to cost 
money to use your bulletin board. However, the problem was solved more 
than a decade ago. Look into FMS, which combines Usenet/mailing lists 
with a web of trust for spam resistance.


      parent reply	other threads:[~2020-11-25  1:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23  0:40 [bitcoin-dev] Bulletin boards without selective censorability for bitcoin fungibility markets AdamISZ
2020-11-23 12:24 ` AdamISZ
2020-11-23 13:53   ` Ruben Somsen
2020-11-25  1:52   ` yanmaani [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60346b02bca27cc14a950373490250ac@cock.li \
    --to=yanmaani@cock.li \
    --cc=AdamISZ@protonmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox