From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
To: Jeremy <jlrubin@mit.edu>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Bitcoin Advent Calendar] Oracles, Bonds, and Attestation Chains
Date: Sat, 18 Dec 2021 03:49:15 +0000 [thread overview]
Message-ID: <z3doYwv_p3_hnl2UZW9hC5_RYclAp4bu44ZdkNSZsaP4JtdvIMz2zOqrdoDiKKADe0zV1wHZ-1ZfEQ8kyLnACkejJplTrWRCh_kEy11VtN4=@protonmail.com> (raw)
In-Reply-To: <CAD5xwhjDBaQvP89eh4LhYZ3E+8RQycafr9mxeOrFbivd3e=LOw@mail.gmail.com>
Good morning Jeremy,
> Another interesting point: if you use a musig key for your staking key that is musig(a,b,c) you can sign with a until you equivocate once, then switch to b, then c. Three strikes and you're out! IDK what that could be used for.
You could say "oops, I made a mistake, can I correct it by equivocating just this time?".
Three strikes and you are out.
> Lastly, while you can't punish lying, you could say "only the stakers who sign with the majority get allocated reward tokens for that slot". So you could equivocate to switch and get tokens, but you'd burn your collateral for them. But this does make an incentive for the stakers to try to sign the "correct" statement in line with peers.
Note the quote marks around "correct" --- the majority of peers could be conspiring to lie, too.
Conspiracy theory time.....
Regards,
ZmnSCPxj
prev parent reply other threads:[~2021-12-18 3:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 18:24 [bitcoin-dev] [Bitcoin Advent Calendar] Oracles, Bonds, and Attestation Chains Jeremy
2021-12-18 1:00 ` ZmnSCPxj
2021-12-18 2:00 ` Jeremy
2021-12-18 3:49 ` ZmnSCPxj [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='z3doYwv_p3_hnl2UZW9hC5_RYclAp4bu44ZdkNSZsaP4JtdvIMz2zOqrdoDiKKADe0zV1wHZ-1ZfEQ8kyLnACkejJplTrWRCh_kEy11VtN4=@protonmail.com' \
--to=zmnscpxj@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jlrubin@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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