GRIN/nym

Files

T

Jędrzej Stuczyński c9c0de1fba Offline signing (#3175 )

* renamed secp265k1 to secp256k1

* added optional 'explicit_signer_data' argument for sign method

* wip

* made client signer generic

which required to undertake an adventure into coconut bandwidth trait bounds...

* separate wrapper for TxSigner

* moves signing-related features to separate module

* fixed build of binaries from outside default workspace

* offline signing example

* fixed wallet build

* post rebasing formatting

* fixed bity integration build

* making clippy happier

* fixed post-rebase bip39 dependency version

2023-03-27 10:15:30 +01:00

src

Offline signing (#3175 )

2023-03-27 10:15:30 +01:00

Cargo.toml

Feature/rename nymd to nyxd (#2696 )

2023-01-05 15:35:47 +00:00

README.md

Wrap up Bity order signature and verification into simple structs, so it is easy for them to use (#1661 )

2022-10-06 11:00:49 +01:00

README.md

Buy NYM with Bity

This crate allows Bity to verify orders for purchasing NYM tokens. The same crate is used by the wallet to sign orders for purchases.

Signing

The Nym Wallet user will sign an order message provided by Bity to create a signed order with the following fields:

account_id: n1jw6mp7d5xqc7w6xm79lha27glmd0vdt3l9artf
message: "This is the order message from Bity"
order signature: 
{
  "account_id": "n1jw6mp7d5xqc7w6xm79lha27glmd0vdt3l9artf",
  "public_key": {
    "@type": "/cosmos.crypto.secp256k1.PubKey",
    "key": "A/zqdyeyPhCEXB9pyVLdNb5er+eds5ayboCdEEHK3Uom"
  },
  "signature_as_hex": "31C522B9B5C522A93CE14BE38E2D380CA166F69E952DF6F5D45B3B9CCDAAFE9115FBDF8539092986391C46885242E6E4CF806EEC1BB869A28D0E6D347C52121A"
}

The signature field of the order contains a JSON representation of:

the Cosmos address of the signer (account_id)
the Cosmos public key
a hex string digest of the Bity order message signed by the user

Note: the signature_as_hex is not in recoverable form (e.g. allows recovering the public key from the signature in secp256k1). This is why the public key is supplied along with the account id, as the prefix cannot be recovered.

Verification

Verification has been wrapped up into taking a single struct that can be parsed from JSON:

{
  "account_id": "n1jw6mp7d5xqc7w6xm79lha27glmd0vdt3l9artf",
  "message": "This is the order message from Bity",
  "signature": << ORDER SIGNATURE JSON GOES HERE >>
}

The following will be checked:

the account_id supplied matches:
- the account id derived from the public key
- the account id field in the order signature JSON
the account id is for Nym mainnet
the signature is for the message
all data structures parse correctly
- nested structs
- account ids
- Cosmos public keys