From: alicexbt <alicexbt@protonmail•com>
To: Erik Aronesty <erik@q32•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] ossification and misaligned incentive concerns
Date: Sun, 05 Nov 2023 18:43:18 +0000 [thread overview]
Message-ID: <GX-kBpIk-vgpoFHURyyNZTdxcfvNhMx9cSnKgBB6SRz6lggoivBTqt81IwZSAjFSPv-nVKE0_ZX6pzEGFS7bZRoJI6TXqmCxwU6HI28AnfE=@protonmail.com> (raw)
In-Reply-To: <CAJowKgJXxS3L=pQR=jhSXBgdDR9k5mwPyKhKkuFESw5_qOgdrQ@mail.gmail.com>
Hi Erik,
> currently, there are providers of anonymity services, scaling services, custody, and other services layered on top of bitcoin using trust-based and federated models.
>
> as bitcoin becomes more popular, these service providers have increasingly had a louder "voice" in development and maintenance of the protocol
> is anyone else worried about this?
Yes. I share your concerns about the growing influence of centralized service providers on Bitcoin's development. Although there is nothing much we can do about it especially
when trusted, centralized, custodial, federated etc. projects keep getting funded. Only solution is to build better things and be positive.
Example: Everyone is aware of the risks involved in a project that takes custody of funds, provide privacy without KYC. There are several examples from past in which similar
projects with some volume ended up getting shutdown by governments. With [covenants and statechains][0], it is possible to use bitcoin (p2p ecash) with privacy and involves no custody.
There are other [benefits][1] of payment pools (w/ covenants) in terms of privacy. Hopefully we agree to do soft fork in next year or so.
[0]: https://github.com/AdamISZ/pathcoin-poc
[1]: https://gnusha.org/bitcoin-wizards/2019-05-21.log
/dev/fd0
floppy disk guy
Sent with Proton Mail secure email.
------- Original Message -------
On Friday, November 3rd, 2023 at 11:54 PM, Erik Aronesty via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> currently, there are providers of anonymity services, scaling services, custody, and other services layered on top of bitcoin using trust-based and federated models.
>
> as bitcoin becomes more popular, these service providers have increasingly had a louder "voice" in development and maintenance of the protocol
>
> holders generally want these features
>
> but service providers have an incentive to maintain a "moat" around their services
>
> in summary, making privacy, scaling and vaulting "hard" for regular users, keeping it off-chain and federated... is now incentivised among a vocal, but highly technical, minority
>
> is anyone else worried about this?
next prev parent reply other threads:[~2023-11-05 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 18:24 Erik Aronesty
2023-11-05 14:39 ` JK
2023-11-05 14:59 ` Erik Aronesty
2023-11-05 17:25 ` JK
2023-11-05 18:43 ` alicexbt [this message]
2023-11-05 21:00 ` Ryan Grant
2023-11-07 8:58 vjudeu
2023-11-07 12:24 ` JK
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='GX-kBpIk-vgpoFHURyyNZTdxcfvNhMx9cSnKgBB6SRz6lggoivBTqt81IwZSAjFSPv-nVKE0_ZX6pzEGFS7bZRoJI6TXqmCxwU6HI28AnfE=@protonmail.com' \
--to=alicexbt@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=erik@q32$(echo .)com \
/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