BLISK folded into Mercury's blind. [~lightning](/~lightning/r/06bc1a977d)

06bc1a977d

This post addresses a shortcoming of the MercuryLayer project: advanced spending policies. The existing open-source implementation uses a “single signer” approach with a dedicated private key per coin. That model offers no authorization structure, which corporate entities with established approval processes need.

The approach below combines Boolean circuit Logic Integrated into the Single Key (BLISK) with the blind-signed, MuSig2-based statechain transfer protocol. It turns out that this requires almost no change to the MercuryLayer specification, and keeps BLISK entirely on the client side. Mercury’s protocol rests on exactly the principle that makes this possible: the client builds the aggregate key, the aggregate nonce and the challenge, and the server returns a blind share.

math

bitcoin

> ## Summary
> 
> This post addresses a shortcoming of the MercuryLayer project: advanced spending policies. The existing open-source implementation uses a “single signer” approach with a dedicated private key per coin. That model offers no authorization structure, which corporate entities with established approval processes need.
>
> The approach below combines Boolean circuit Logic Integrated into the Single Key (BLISK) with the blind-signed, MuSig2-based statechain transfer protocol. It turns out that this requires almost no change to the MercuryLayer specification, and keeps BLISK entirely on the client side. Mercury’s protocol rests on exactly the principle that makes this possible: the client builds the aggregate key, the aggregate nonce and the challenge, and the server returns a blind share.
> 
> ...