From: ZmnSCPxj <ZmnSCPxj@protonmail•com>
To: Chris Belcher <belcher@riseup•net>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Improving chaumian ecash and sidechains with fidelity bond federations
Date: Mon, 16 May 2022 11:26:38 +0000 [thread overview]
Message-ID: <HDg-_x4k8XbHnF6QHAI9vbT_8Pcy8OZrRJ4LwM4DHBTg0XV7ZmZCLWDmPYihVOtc_9_6DMBwRYoaDsLai7mSaP8jDC8KI5ij1edYaIb1iOU=@protonmail.com> (raw)
In-Reply-To: <21c0cdea-f929-b9a8-baa6-e33eb2cee80f@riseup.net>
Good morning Chris,
> I don't know yet exactly the details of how such a scheme would work,
> maybe something like each fidelity bond owner creates a key in the
> multisig scheme, and transaction fees from the sidechain or ecash server
> are divided amongst the fidelity bonds in proportion to their fidelity
> bond value.
Such a scheme would probably look a little like my old ideas about "mainstake", where you lock up funds on the mainchain and use that as your right to construct new sidechain blocks, with your share of the sideblocks proportional to the value of the mainstake you locked up.
Of note is that it need not operate as a sidechain or chaumian bank, anything that requires a federation can use this scheme as well.
For instance, statechains are effectively federation-guarded CoinPools, and could use a similar scheme for selecting federation members.
Smart contracts unchained can also have users be guided by fidelity bonds in order to select federation members.
Regards,
ZmnSCPxj
prev parent reply other threads:[~2022-05-16 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 10:26 Chris Belcher
2022-05-16 11:26 ` 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='HDg-_x4k8XbHnF6QHAI9vbT_8Pcy8OZrRJ4LwM4DHBTg0XV7ZmZCLWDmPYihVOtc_9_6DMBwRYoaDsLai7mSaP8jDC8KI5ij1edYaIb1iOU=@protonmail.com' \
--to=zmnscpxj@protonmail$(echo .)com \
--cc=belcher@riseup$(echo .)net \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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