📅 Original date posted:2017-10-10
📝 Original message:Paul,
It's a two-way peg.
There's nothing preventing transfers back to the main chain.
They work in the exact same manner.
Cheers,
Greg
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
> On Oct 9, 2017, at 6:39 PM, Paul Sztorc <truthcoin at gmail.com <mailto:truthcoin at gmail.com>> wrote:
>
> 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.
>
> Paul
>
> On Oct 9, 2017 9:24 PM, "Tao Effect via bitcoin-dev" <bitcoin-dev at lists.linuxfoundation.org <mailto:bitcoin-dev at lists.linuxfoundation.org>> wrote:
> Dear list,
>
> In previous arguments over Drivechain (and Drivechain-like proposals) I promised that better scaling proposals — that do not sacrifice Bitcoin's security — would come along.
>
> I planned to do a detailed writeup, but have decided to just send off this email with what I have, because I'm unlikely to have time to write up a detailed proposal.
>
> The idea is very simple (and by no means novel*), and I'm sure others have mentioned either exactly it, or similar ideas (e.g. burning coins) before.
>
> This is a generic sharding protocol for all blockchains, including Bitcoin.
>
> Users simply say: "My coins on Chain A are going to be sent to Chain B".
>
> Then they burn the coins on Chain A, and create a minting transaction on Chain B. The details of how to ensure that coins do not get lost needs to be worked out, but I'm fairly certain the folks on this list can figure out those details.
>
> - Thin clients, nodes, and miners, can all very easily verify that said action took place, and therefore accept the "newly minted" coins on B as valid.
> - Users client software now also knows where to look for the other coins (if for some reason it needs to).
>
> This doesn't even need much modification to the Bitcoin protocol as most of the verification is done client-side.
>
> It is fully decentralized, and there's no need to give our ownership of our coins to miners to get scale.
>
> My sincere apologies if this has been brought up before (in which case, I would be very grateful for a link to the proposal).
>
> Cheers,
> Greg Slepak
>
> * This idea is similar in spirit to Interledger.
>
> --
> Please do not email me anything that you are not comfortable also sharing with the NSA.
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org <mailto:bitcoin-dev at lists.linuxfoundation.org>
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>;
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171009/f3c63867/attachment-0001.html>;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171009/f3c63867/attachment-0001.sig>;
Tao Effect [ARCHIVE] /
npub1r0…vdpg3
2023-06-07 18:06:59
in reply to nevent1q…xepg
Author Public Key
npub1r0g954grld59fuphzsypmuuhpdunq67f729afmp44h2mxvth2hts4vdpg3Published at
2023-06-07 18:06:59Event JSON
{
"id": "cf2a4ddd77568d609b1334a3f603959b2c2d66cb1bbb99fb6cfd72127cb1086e",
"pubkey": "1bd05a5503fb6854f03714081df3970b79306bc9f28bd4ec35add5b3317755d7",
"created_at": 1686161219,
"kind": 1,
"tags": [
[
"e",
"fd580ac0183fd4c89c8d00875bacd50db237c5eb014e289c09c9a01a5d7dc865",
"",
"root"
],
[
"e",
"c419a070de233b36de8d63585952165e858526570bf2ab77dc661a9bbe8e4034",
"",
"reply"
],
[
"p",
"7ac0bd39b854f24cbf067103758f3a9d398c23832d6d75824d190ae35c6c23be"
]
],
"content": "📅 Original date posted:2017-10-10\n📝 Original message:Paul,\n\nIt's a two-way peg.\n\nThere's nothing preventing transfers back to the main chain.\n\nThey work in the exact same manner.\n\nCheers,\nGreg\n\n--\nPlease do not email me anything that you are not comfortable also sharing with the NSA.\n\n\u003e On Oct 9, 2017, at 6:39 PM, Paul Sztorc \u003ctruthcoin at gmail.com \u003cmailto:truthcoin at gmail.com\u003e\u003e wrote:\n\u003e \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 for the drivechain that make it impossible for any side-to-main transfer to succeed.\n\u003e \n\u003e One-way pegs have strong first-mover disadvantages.\n\u003e \n\u003e Paul\n\u003e \n\u003e On Oct 9, 2017 9:24 PM, \"Tao Effect via bitcoin-dev\" \u003cbitcoin-dev at lists.linuxfoundation.org \u003cmailto:bitcoin-dev at lists.linuxfoundation.org\u003e\u003e wrote:\n\u003e Dear list,\n\u003e \n\u003e In previous arguments over Drivechain (and Drivechain-like proposals) I promised that better scaling proposals — that do not sacrifice Bitcoin's security — would come along.\n\u003e \n\u003e I planned to do a detailed writeup, but have decided to just send off this email with what I have, because I'm unlikely to have time to write up a detailed proposal.\n\u003e \n\u003e The idea is very simple (and by no means novel*), and I'm sure others have mentioned either exactly it, or similar ideas (e.g. burning coins) before.\n\u003e \n\u003e This is a generic sharding protocol for all blockchains, including Bitcoin.\n\u003e \n\u003e Users simply say: \"My coins on Chain A are going to be sent to Chain B\".\n\u003e \n\u003e Then they burn the coins on Chain A, and create a minting transaction on Chain B. The details of how to ensure that coins do not get lost needs to be worked out, but I'm fairly certain the folks on this list can figure out those details.\n\u003e \n\u003e - Thin clients, nodes, and miners, can all very easily verify that said action took place, and therefore accept the \"newly minted\" coins on B as valid.\n\u003e - Users client software now also knows where to look for the other coins (if for some reason it needs to).\n\u003e \n\u003e This doesn't even need much modification to the Bitcoin protocol as most of the verification is done client-side.\n\u003e \n\u003e It is fully decentralized, and there's no need to give our ownership of our coins to miners to get scale.\n\u003e \n\u003e My sincere apologies if this has been brought up before (in which case, I would be very grateful for a link to the proposal).\n\u003e \n\u003e Cheers,\n\u003e Greg Slepak\n\u003e \n\u003e * This idea is similar in spirit to Interledger.\n\u003e \n\u003e --\n\u003e Please do not email me anything that you are not comfortable also sharing with the NSA.\n\u003e \n\u003e \n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org \u003cmailto:bitcoin-dev at lists.linuxfoundation.org\u003e\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev \u003chttps://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\u003e\n\u003e \n\u003e \n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171009/f3c63867/attachment-0001.html\u003e\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 833 bytes\nDesc: Message signed with OpenPGP\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171009/f3c63867/attachment-0001.sig\u003e",
"sig": "55b48014c14edab7515ea8e27a690e1f463d5a2b40b5f36ab63357ae8d5684fb57ced2fe016ee4f1783f5179b623b7f7addd92f285edd86efbe961e9b5afc212"
}