From: yanmaani@cock•li
To: Prayank <prayank@tutanota•de>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP - Automated and Secure Communication
Date: Sun, 06 Dec 2020 19:14:13 +0000 [thread overview]
Message-ID: <23794877f2c4b7eb69aff1fe83e41da1@cock.li> (raw)
In-Reply-To: <MNtH225--3-2@tutanota.de>
The reason Samourai did not propose a BIP is that that was not a
proposal to improve the Bitcoin protocol.
You could write a specification for it, but this mailing list is
probably the wrong venue.
On 2020-12-06 18:20, Prayank via bitcoin-dev wrote:
> Hello Everyone,
>
> I know there have been lot of controversial and heated discussions
> involving Samourai in past. Ignoring everything including the tweets
> in which Samourai team mentioned no interest in proposing a BIP
> related to automated and secure communication used in Soroban, I
> wanted to know if enough people would be interested in a BIP because
> it may help other bitcoin projects in future.
>
> Tweets: https://twitter.com/SamouraiWallet/status/1334977957157367810
> [1]
>
> https://twitter.com/SamouraiDev/status/1335103101188104194 [2]
>
> Ben also tweeted that a BIP would make sense:
> https://twitter.com/benthecarman/status/1334977096079306753 [3]
>
> I think we should keep all the controversial things aside and do
> everything that helps Bitcoin. It's mentioned in the medium article
> that it can help other projects like joinmarket, coinswap, snickr etc.
>
> https://link.medium.com/uBvIJUSLQbb
>
> The source code for a client library in Java is available here
> https://code.samourai.io/wallet/soroban-client-java and the source
> code for the Go based server component is available here
> https://code.samourai.io/wallet/samourai-soroban
>
> Let me know if a BIP for such implementation to be used by other
> bitcoin projects makes sense and if anyone willing to help me in
> creating a BIP.
>
> Thanks.
>
> -- Prayank
>
> Links:
> ------
> [1] https://twitter.com/SamouraiWallet/status/1334977957157367810?s=19
> [2] https://twitter.com/SamouraiDev/status/1335103101188104194?s=19
> [3] https://twitter.com/benthecarman/status/1334977096079306753?s=19
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2020-12-06 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 18:20 Prayank
2020-12-06 19:14 ` yanmaani [this message]
2020-12-06 19:36 ` Luke Dashjr
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=23794877f2c4b7eb69aff1fe83e41da1@cock.li \
--to=yanmaani@cock$(echo .)li \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=prayank@tutanota$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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