📅 Original date posted:2015-07-23
📝 Original message:I think implicit QoS is far simpler to implement, requires less parties and is closer to what Bitcoin started out as: a peer-to-peer digital cash system, not a peer-to-let-me-handle-that-for-you-to-peer system.
jp
> On Jul 24, 2015, at 9:08 AM, Eric Lombrozo <elombrozo at gmail.com> wrote:
>
> By using third parties separate from individual miners that do bidding on your behalf you get a mechanism that allows QoS guarantees and shifting the complexity and risk from the wallet with little computational resources to a service with abundance of them. Using timelocked contracts it’s possible to enforce the guarantees.
>
> Negotiating directly with miners via smart contracts seems difficult at best.
>
>
>> On Jul 23, 2015, at 6:03 PM, Jean-Paul Kogelman via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>>
>> Doesn't matter.
>>
>> It's not going to be perfect given the block time variance among other factors but it's far more workable than guessing whether or not your transaction is going to end up in a block at all.
>>
>> jp
>>
>>
>>> On Jul 24, 2015, at 8:53 AM, Peter Todd <pete at petertodd.org> wrote:
>>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA256
>>>
>>>
>>>
>>>> On 23 July 2015 20:49:20 GMT-04:00, Jean-Paul Kogelman via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>>>>
>>>> And it's obvious how a size cap would interfere with such a QoS scheme.
>>>> Miners wouldn't be able to deliver the below guarantees if they have to
>>>> start excluding transactions.
>>>
>>> As mining is a random, poisson process, obviously giving guarantees without a majority of hashing power isn't possible.
>>>
>>>
>>> -----BEGIN PGP SIGNATURE-----
>>>
>>> iQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJVsYyK
>>> AAoJEMCF8hzn9Lnc47AH/28WlecQLb37CiJpcvXO9tC4zqYEodurtB9nBHTSJrug
>>> VIEXZW53pSTdd3vv2qpGIlHxuYP8QmDSATztwQLuN6XWEszz7TO8MXBfLxKqZyGu
>>> i83WqSGjMAfwqjl0xR1G7PJgt4+E+0vaAFZc98vLCgZnedbiXRVtTGjhofG1jjTc
>>> DFMwMZHP0eqWTwtWwqUvnA7PTFHxdqoJruY/t1KceN+JDbBCJWMxBDswU64FXcVH
>>> 0ecsk9nhLMyylBX/2v4HjCXyayocH8jQ+FpLSP0xxERyS+f1npFX9cxFMq24uXqn
>>> PcnZfLfaSJ6gMbmhbYG5wYDKN3u732j7dLzSJnMW6jk=
>>> =LY1+
>>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
Jean-Paul Kogelman [ARCHIVE] /
npub1sa…8y304
2023-06-07 15:42:58
in reply to nevent1q…rnkn
Author Public Key
npub1sa86gng3pvs3jgyt5majwcrhn8ck5qxgy9pjqxkh79u638cd7dys28y304Published at
2023-06-07 15:42:58Event JSON
{
"id": "6466d4dc9078a5c1105b9673c0dee8298faa95f169417601aa1364e522a6189f",
"pubkey": "874fa44d110b2119208ba6fb27607799f16a00c82143201ad7f179a89f0df349",
"created_at": 1686152578,
"kind": 1,
"tags": [
[
"e",
"95a36d78d6bf18f4b8ede735f044f5cc9630ae9f0b1198d008835777ff84eede",
"",
"root"
],
[
"e",
"77630d195eb36775384898083675fa46b68c3bb08f62cce0aceafc54df6a211b",
"",
"reply"
],
[
"p",
"e899768d254f3537af7e26455968583632d0ab0bd4c780445eacfa087ac80d8f"
]
],
"content": "📅 Original date posted:2015-07-23\n📝 Original message:I think implicit QoS is far simpler to implement, requires less parties and is closer to what Bitcoin started out as: a peer-to-peer digital cash system, not a peer-to-let-me-handle-that-for-you-to-peer system.\n\njp\n\n\u003e On Jul 24, 2015, at 9:08 AM, Eric Lombrozo \u003celombrozo at gmail.com\u003e wrote:\n\u003e \n\u003e By using third parties separate from individual miners that do bidding on your behalf you get a mechanism that allows QoS guarantees and shifting the complexity and risk from the wallet with little computational resources to a service with abundance of them. Using timelocked contracts it’s possible to enforce the guarantees.\n\u003e \n\u003e Negotiating directly with miners via smart contracts seems difficult at best.\n\u003e \n\u003e \n\u003e\u003e On Jul 23, 2015, at 6:03 PM, Jean-Paul Kogelman via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e \n\u003e\u003e Doesn't matter.\n\u003e\u003e \n\u003e\u003e It's not going to be perfect given the block time variance among other factors but it's far more workable than guessing whether or not your transaction is going to end up in a block at all.\n\u003e\u003e \n\u003e\u003e jp\n\u003e\u003e \n\u003e\u003e \n\u003e\u003e\u003e On Jul 24, 2015, at 8:53 AM, Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\u003e\u003e\u003e \n\u003e\u003e\u003e -----BEGIN PGP SIGNED MESSAGE-----\n\u003e\u003e\u003e Hash: SHA256\n\u003e\u003e\u003e \n\u003e\u003e\u003e \n\u003e\u003e\u003e \n\u003e\u003e\u003e\u003e On 23 July 2015 20:49:20 GMT-04:00, Jean-Paul Kogelman via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e\u003e\u003e \n\u003e\u003e\u003e\u003e And it's obvious how a size cap would interfere with such a QoS scheme.\n\u003e\u003e\u003e\u003e Miners wouldn't be able to deliver the below guarantees if they have to\n\u003e\u003e\u003e\u003e start excluding transactions.\n\u003e\u003e\u003e \n\u003e\u003e\u003e As mining is a random, poisson process, obviously giving guarantees without a majority of hashing power isn't possible.\n\u003e\u003e\u003e \n\u003e\u003e\u003e \n\u003e\u003e\u003e -----BEGIN PGP SIGNATURE-----\n\u003e\u003e\u003e \n\u003e\u003e\u003e iQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJVsYyK\n\u003e\u003e\u003e AAoJEMCF8hzn9Lnc47AH/28WlecQLb37CiJpcvXO9tC4zqYEodurtB9nBHTSJrug\n\u003e\u003e\u003e VIEXZW53pSTdd3vv2qpGIlHxuYP8QmDSATztwQLuN6XWEszz7TO8MXBfLxKqZyGu\n\u003e\u003e\u003e i83WqSGjMAfwqjl0xR1G7PJgt4+E+0vaAFZc98vLCgZnedbiXRVtTGjhofG1jjTc\n\u003e\u003e\u003e DFMwMZHP0eqWTwtWwqUvnA7PTFHxdqoJruY/t1KceN+JDbBCJWMxBDswU64FXcVH\n\u003e\u003e\u003e 0ecsk9nhLMyylBX/2v4HjCXyayocH8jQ+FpLSP0xxERyS+f1npFX9cxFMq24uXqn\n\u003e\u003e\u003e PcnZfLfaSJ6gMbmhbYG5wYDKN3u732j7dLzSJnMW6jk=\n\u003e\u003e\u003e =LY1+\n\u003e\u003e\u003e -----END PGP SIGNATURE-----\n\u003e\u003e _______________________________________________\n\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e",
"sig": "557193290418bfb81ab85832f21d0dc68b40dc6fbfce7e22026f48f0522779642fa8c4a8a343a3f62c6bf26184bd659d8e7c08ec1c3594d1a21359d930710c30"
}