š
Original date posted:2018-11-16
š Original message:
Good morning Rusty,
> > > I apologize that this wasn't fleshed out before the summit, but I
> > > overestimated the power of Scriptless Scripts so had mentally deferred
> > > this.
> >
> > My understanding is that SS is as powerful as we thought, at least for some of the applications we were hoping to use it for.
> > However, implementing SS is hard without Schnorr, because script magic with `OP_CODESEPARATOR` is magic, and we essentially stalled out and said "maybe wait for Schnorr instead".
>
> No, we don't get static invoices. That was my hope; that we could do
> static invoicing without an extra interaction.
At first I thought it was possible, but on reflection, you are correct.
We need some way for the payee to dynamically provide a new payment hash (or payment point under SS).
This is because our proof-of-payment essentially means the payer learns a secret.
So we cannot commit to a fixed secret if we want the static invoice to be shareable among multiple payers.
So the payee does need to generate new secrets each time it wants to be paid, and give a unique secret to the payer as separate unique proofs-of-payment.
Regards,
ZmnSCPxj
ZmnSCPxj [ARCHIVE] /
npub1g5ā¦3ms3l
2023-06-09 12:52:51
in reply to nevent1qā¦0dl4
Author Public Key
npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3lPublished at
2023-06-09 12:52:51Event JSON
{
"id": "e4c6673d746e1ecef145edf0ef45e5fde89b849543b1e1e26fa95193f314ab20",
"pubkey": "4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861",
"created_at": 1686315171,
"kind": 1,
"tags": [
[
"e",
"f52ed755f445a0de1c13cc6ab6ec7060fe02d8d163c9cb6cd3cc24885062d6a0",
"",
"root"
],
[
"e",
"1febfb1698f0d62a76757be80fa4cb8ebea15ec4c935423607ab6831e8d00a20",
"",
"reply"
],
[
"p",
"13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425"
]
],
"content": "š
Original date posted:2018-11-16\nš Original message:\nGood morning Rusty,\n\n\u003e \u003e \u003e I apologize that this wasn't fleshed out before the summit, but I\n\u003e \u003e \u003e overestimated the power of Scriptless Scripts so had mentally deferred\n\u003e \u003e \u003e this.\n\u003e \u003e\n\u003e \u003e My understanding is that SS is as powerful as we thought, at least for some of the applications we were hoping to use it for.\n\u003e \u003e However, implementing SS is hard without Schnorr, because script magic with `OP_CODESEPARATOR` is magic, and we essentially stalled out and said \"maybe wait for Schnorr instead\".\n\u003e\n\u003e No, we don't get static invoices. That was my hope; that we could do\n\u003e static invoicing without an extra interaction.\n\nAt first I thought it was possible, but on reflection, you are correct.\nWe need some way for the payee to dynamically provide a new payment hash (or payment point under SS).\n\nThis is because our proof-of-payment essentially means the payer learns a secret.\nSo we cannot commit to a fixed secret if we want the static invoice to be shareable among multiple payers.\nSo the payee does need to generate new secrets each time it wants to be paid, and give a unique secret to the payer as separate unique proofs-of-payment.\n\nRegards,\nZmnSCPxj",
"sig": "0e528ad373e5bf96a487680e40712ac408094c9af3eb8dc3f9ec203d69aae0d5d34d31478ed810d5ffab8018462098f9f674b7212b9f5bcab439eb5ee38639c6"
}