#plugin #signer #signing #helper #vade #key #messages

deprecated vade-signer

signing helper for vade plugins

1 unstable release

0.0.1 Aug 25, 2022

#60 in #signer

43 downloads per month
Used in 3 crates

Custom license

14KB
142 lines

Vade Signer

crates.io Documentation Apache-2 licensed

About

Small helper module to support signing in Vade plugins.

Configuring signer for vade projects

Some Vade plugins need a signer to be able to sign messages. The signer is usually created and passed to the plugin`s constructor, e.g. for using a local signer:

use vade_evan_substrate::resolver::{ResolverConfig, VadeEvanSubstrate};
use vade_signer::{LocalSigner, Signer},
let signer: Box<dyn Signer> = Box::new(LocalSigner::new());
let resolver = VadeEvanSubstrate::new(ResolverConfig {
    signer,
    target: "127.0.0.1".to_string(),
});

When signing remotely, signing_url will be called with a POST request. The messages that should be signed is passed to the server alongside a reference to a key like this:

{
    "key": "some-key-id",
    "type": "some-key-type",
    "message": "sign me please"
}

Two types of of responses are supported. Successful signing results are give in this format:

{
  "messageHash": "0x52091d1299031b18c1099620a1786363855d9fcd91a7686c866ad64f83de13ff",
  "signature": "0xc465a9499b75eed6fc4f658d1764168d63578b05ae15305ceedc94872bda793f74cb850c0683287b245b4da523851fbbe37738116635ebdb08e80b867c0b4aea1b",
  "signerAddress": "0x3daa2c354dba8d51fdabc30cf9219b251c74eb56"
}

Errors can be signaled this way:

{
    "error": "key not found"
}

Dependencies

~7–22MB
~332K SLoC