How I can extract or generate signature?

NefeluM · February 10, 2023, 9:59am

Hello, I have a seed phrase (mnemonic). How I can convert it to Signature for sui json-rpc transactions? Can I use my software (for example - python) without sui cli-client? And how I can do this? For example, sui_executeTransactionSerializedSig need signature.

SarvariSetare · February 22, 2023, 2:25pm

@NefeluM
I also had a problem with access not with mnemonic. I tried to use keys from devnet to testnet and their types was different and there wasn’t instruction how to solve that. Only at the discord one of the moderators shared thу link. But I didn’t understand any word of this

github.com

MystenLabs/sui/blob/a69fd88a5842f521a603e3dd192dbf9fd0fe4fb3/sdk/typescript/src/cryptography/ed25519-keypair.ts#L125-L148


      
          /**
           * Derive Ed25519 keypair from mnemonics and path. The mnemonics must be normalized
           * and validated against the english wordlist.
           *
           * If path is none, it will default to m/44'/784'/0'/0'/0', otherwise the path must
           * be compliant to SLIP-0010 in form m/44'/784'/{account_index}'/{change_index}'/{address_index}'.
           */
          static deriveKeypair(mnemonics: string, path?: string): Ed25519Keypair {
            if (path == null) {
              path = DEFAULT_ED25519_DERIVATION_PATH;
            }
            if (!isValidHardenedPath(path)) {
              throw new Error('Invalid derivation path');
            }
            const { key } = derivePath(path, mnemonicToSeedHex(mnemonics));
            const pubkey = getPublicKey(key, false);
          
            // Ed25519 private key returned here has 32 bytes. NaCl expects 64 bytes where the last 32 bytes are the public key.
            let fullPrivateKey = new Uint8Array(64);
            fullPrivateKey.set(key);

This file has been truncated. show original

Maybe someone help me finally

fastfrank · February 24, 2023, 10:16am

As far as keypairs go, prior to Sui 0.21.0 the keypair encoding structurally (using ed25519 as example):

Keypair on disk is encoded as base64 string
Decoding that string to bytes resulted in a 65 byte list
Byte 0 contained the key scheme:
Value of 0 indicates ed25519
Value of 1 indicates secp256k1
Value of 2 indicates secp256r1
For ed25519: The next 32 bytes were the Public key
For ed25519: The remaining 32 bytes were the Private key

However; in 0.21.0 it was changed where the Public key was dropped.
Now the keystring decodes to a 33 byte list
The first byte is still the key scheme
The remaining 32 are the Private key

fastfrank · February 24, 2023, 10:20am

The seed phrase (words) need to be converted to bytes representing a seed to your key generation.

You need to do this to get a private key and from that a public key

You also need to identify the derivation path, varies based on key type

You can generate the key pair using the sui keytool

See: sui keytool import -h on the command line.