📅 Original date posted:2017-10-10
📝 Original message:What if two sidechains are implemented at once? What if people get excited
about one sidechain today, but a second even-better one is published the
very next week? What if the original mainchain decides to integrate the
features of the sidechain that you just one-way pegged to?
In these cases, the user looses money, whereas in the two-way peg they
would not lose a thing.
While the one-way peg is interesting, it really doesn't compare.
Paul
On Oct 10, 2017 4:19 PM, "Lucas Clemente Vella" <lvella at gmail.com> wrote:
2017-10-09 22:39 GMT-03:00 Paul Sztorc via bitcoin-dev <bitcoin-dev at lists.
linuxfoundation.org>:
> That is only a one-way peg, not a two-way.
>
> In fact, that is exactly what drivechain does, if one chooses parameters
> for the drivechain that make it impossible for any side-to-main transfer to
> succeed.
>
> One-way pegs have strong first-mover disadvantages.
>
I understand the first-mover disadvantages, but I keep thinking that if the
new chain is Pareto optimal, i.e. is in all aspects at least good as the
original chain, but in some so much better to justify the change, the
initial resistance is an unstable equilibrium. Like a herd of buffaloes
attacking a lion: the first buffalo to attack is in awful disadvantage, but
if a critical mass of the herd follows, the movement succeeds beyond
turning back, and every buffalo benefited, both those who attacked the lion
and those that didn't (because the lion was chased away or killed).
--
Lucas Clemente Vella
lvella at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171010/a29725fb/attachment.html>;
Paul Sztorc [ARCHIVE] /
npub10t…w9uu9
2023-06-07 18:07:03
in reply to nevent1q…ycv7
Author Public Key
npub10tqt6wdc2neye0cxwyphtre6n5uccgur94khtqjdry9wxhrvywlq6w9uu9Published at
2023-06-07 18:07:03Event JSON
{
"id": "dd17e51e39a1294e2e25019dcb2899df903ef067271cb6b8890194566b8e2881",
"pubkey": "7ac0bd39b854f24cbf067103758f3a9d398c23832d6d75824d190ae35c6c23be",
"created_at": 1686161223,
"kind": 1,
"tags": [
[
"e",
"fd580ac0183fd4c89c8d00875bacd50db237c5eb014e289c09c9a01a5d7dc865",
"",
"root"
],
[
"e",
"0f422eb8b13afcc10a9790e939b36eed60643fcfe151f21260bb99d88112dfb5",
"",
"reply"
],
[
"p",
"2dae58c027d374a9ac9ad1529dad7f069996a4b442b390d1b7a56b186aa6a0c2"
]
],
"content": "📅 Original date posted:2017-10-10\n📝 Original message:What if two sidechains are implemented at once? What if people get excited\nabout one sidechain today, but a second even-better one is published the\nvery next week? What if the original mainchain decides to integrate the\nfeatures of the sidechain that you just one-way pegged to?\n\nIn these cases, the user looses money, whereas in the two-way peg they\nwould not lose a thing.\n\nWhile the one-way peg is interesting, it really doesn't compare.\n\nPaul\n\nOn Oct 10, 2017 4:19 PM, \"Lucas Clemente Vella\" \u003clvella at gmail.com\u003e wrote:\n\n2017-10-09 22:39 GMT-03:00 Paul Sztorc via bitcoin-dev \u003cbitcoin-dev at lists.\nlinuxfoundation.org\u003e:\n\n\u003e That is only a one-way peg, not a two-way.\n\u003e\n\u003e In fact, that is exactly what drivechain does, if one chooses parameters\n\u003e for the drivechain that make it impossible for any side-to-main transfer to\n\u003e succeed.\n\u003e\n\u003e One-way pegs have strong first-mover disadvantages.\n\u003e\n\nI understand the first-mover disadvantages, but I keep thinking that if the\nnew chain is Pareto optimal, i.e. is in all aspects at least good as the\noriginal chain, but in some so much better to justify the change, the\ninitial resistance is an unstable equilibrium. Like a herd of buffaloes\nattacking a lion: the first buffalo to attack is in awful disadvantage, but\nif a critical mass of the herd follows, the movement succeeds beyond\nturning back, and every buffalo benefited, both those who attacked the lion\nand those that didn't (because the lion was chased away or killed).\n\n-- \nLucas Clemente Vella\nlvella at gmail.com\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171010/a29725fb/attachment.html\u003e",
"sig": "48087ec4e0371a905103651bb8faf4418f573a23f754ff8d512ee538e8774d592f57a190c167e1d72b4b81f5215829d88f687bda51fdbd540695359e7f2b9ccc"
}