Struct nazgul::dlsag::DLSAG

pub struct DLSAG {
    pub challenge: Scalar,
    pub responses: Vec<Scalar>,
    pub ring: Vec<(RistrettoPoint, RistrettoPoint, Scalar)>,
    pub key_image: RistrettoPoint,
    pub b: bool,
}

Dual Linkable Spontaneous Anonymous Group Signature for Ad Hoc Groups

DLSAG: Non-Interactive Refund Transactions For Interoperable Payment Channels in Monero

This is a a novel linkable ring signature scheme that enables for the first time refund transactions natively in Monero

Read the paper on how to use it to implement payment channels.

Please read tests at the bottom of the source code for this module for examples on how to use it

Fields

challenge: Scalar

responses: Vec<Scalar>

ring: Vec<(RistrettoPoint, RistrettoPoint, Scalar)>

key_image: RistrettoPoint

b: bool

Trait Implementations

impl Clone for DLSAG

fn clone(&self) -> DLSAG

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl KeyImageGen<(RistrettoPoint, Scalar, Scalar), RistrettoPoint> for DLSAG

fn generate_key_image<Hash: Digest<OutputSize = U64> + Clone + Default>(
    k: (RistrettoPoint, Scalar, Scalar)
) -> RistrettoPoint

Some signature schemes require the key images to be signed as well. Use this method to generate them

impl KeyImageGen<(Scalar, RistrettoPoint, Scalar), RistrettoPoint> for DLSAG

fn generate_key_image<Hash: Digest<OutputSize = U64> + Clone + Default>(
    k: (Scalar, RistrettoPoint, Scalar)
) -> RistrettoPoint

Some signature schemes require the key images to be signed as well. Use this method to generate them

impl Link for DLSAG

fn link(signature_1: DLSAG, signature_2: DLSAG) -> bool

This is for linking two signatures and checking if they are signed by the same person

impl Sign<(RistrettoPoint, Scalar, Scalar), Vec<(RistrettoPoint, RistrettoPoint, Scalar)>> for DLSAG

fn sign<Hash: Digest<OutputSize = U64> + Clone + Default, CSPRNG: CryptoRng + RngCore + Default>(
    k: (RistrettoPoint, Scalar, Scalar),
    ring: Vec<(RistrettoPoint, RistrettoPoint, Scalar)>,
    secret_index: usize,
    message: &Vec<u8>
) -> DLSAG

To sign you need k your private key, and ring which is the public keys of everyone except you. You are signing the message

The private key k in this case is your private key, the public key of the other end of the channel and a random bitstring generated by hashing-to-scalar: the transaction ID, and output index.

The ring contains public key pairs from the blockchain together with their random bitstrings as mentioned above.

This implementation of sign(...) is for the user who has the private key for the right side of the channel

impl Sign<(Scalar, RistrettoPoint, Scalar), Vec<(RistrettoPoint, RistrettoPoint, Scalar)>> for DLSAG

fn sign<Hash: Digest<OutputSize = U64> + Clone + Default, CSPRNG: CryptoRng + RngCore + Default>(
    k: (Scalar, RistrettoPoint, Scalar),
    ring: Vec<(RistrettoPoint, RistrettoPoint, Scalar)>,
    secret_index: usize,
    message: &Vec<u8>
) -> DLSAG

To sign you need k your private key, and ring which is the public keys of everyone except you. You are signing the message

The private key k in this case is your private key, the public key of the other end of the channel and a random bitstring generated by hashing-to-scalar: the transaction ID, and output index.

The ring contains public key pairs from the blockchain together with their random bitstrings as mentioned above.

This implementation of sign(...) is for the user who has the private key for the left side of the channel

impl Verify for DLSAG

fn verify<Hash: Digest<OutputSize = U64> + Clone + Default>(
    signature: DLSAG,
    message: &Vec<u8>
) -> bool

To verify a signature you need the message too