From: enclade <enclade@protonmail•com>
To: Devrandom <c1.bitcoin@niftybox•net>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Advancing the security of Neutrino using minimally trusted oracles
Date: Fri, 11 Feb 2022 02:39:15 +0000 [thread overview]
Message-ID: <eWWmEi8ofiungvQuh41R2FSA5vNK5HMUV4SeBkvSdocpP2Khh4p6BWq7WZuB3vYayj7V1ifgQvvrCIvCetm-RFjtlCQxtDRE1ZeafDPXoe8=@protonmail.com> (raw)
In-Reply-To: <CAB0O3SWYXOr6mhytgkTFmO3i_p2=WAXg9RsRxYXU7w2eowWtnw@mail.gmail.com>
That sounds completely reasonable.
Originally I had discussed privately making the protocol design completely interactive (client sends a nonce over DNS, oracle responds signing the nonce), but it was pointed out that making them use quantized timestamps mitigated a lot of the issues regarding denial of service, and allows for fault proofs to be significantly stronger.
Delivering the oracle messages over a write only channel like Kryptoradio or Blockstream Satellite would scale extremely well too. When the oracles produce agreeing messages (hopefully, the majority of the time except on block boundaries) the additional data is only 64 bytes per additional signer, so it makes sense to broadcast any a client may want to trust.
------- Original Message -------
On Thursday, February 10th, 2022 at 4:07 PM, Devrandom <c1.bitcoin@niftybox•net> wrote:
> This would be very useful for the Validating Lightning Signer project, since we need to prove to a non-network connected signer that a UTXO has not been spent. It allows the signer to make sure the channel is still active.
>
> ( the related design doc is at https://gitlab.com/lightning-signer/docs/-/blob/master/oracle.md )
>
> I think it would be useful if the oracles were non-interactive, so that they can communicate with the world over a one-way connection. This would reduce their attack surface. Instead of signing over a client-provided timestamp, we could pre-quantize the timestamp and emit attestations for each quantum time step.
prev parent reply other threads:[~2022-02-11 2:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 10:02 enclade
2022-02-10 21:07 ` Devrandom
2022-02-11 2:39 ` enclade [this message]
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='eWWmEi8ofiungvQuh41R2FSA5vNK5HMUV4SeBkvSdocpP2Khh4p6BWq7WZuB3vYayj7V1ifgQvvrCIvCetm-RFjtlCQxtDRE1ZeafDPXoe8=@protonmail.com' \
--to=enclade@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=c1.bitcoin@niftybox$(echo .)net \
/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