Tier 2 support

Sign transactions for Tier 2 chains using Privy raw sign functionality over transaction hashes

For chains supported at the Tier 2 level, you can invoke Privy’s raw sign functionality to sign over a hash, e.g. the hash of a transaction. You can then use the returned signature to submit and send your transaction.

Alternatively, you can provide the bytes to hash with a specific encoding and a hash_function, and get the same response.

For examples of how to use raw sign for a specific chain, see this recipe.

Sign a raw hash or bytes (with encoding and hash_function) along the blockchain’s cryptographic curve using the wallet’s private key. Make a POST request to

https://api.privy.io/v1/wallets/{wallet_id}/raw_sign

Usage

curl --request POST \
--url https://api.privy.io/v1/wallets/{wallet_id}/raw_sign \
--header 'Authorization: Basic Y20xNWh4eDUyMDVlNWx2NHVkdmE3enBqejoybWhVOWhhVTFQYjhYNXV1cVdxQVRIdW5xTWIyUlBKRm5GSHRzWDVzbXNkdUJRUDZtTW05YldmalBwS3hocjJQZHNHY0Q5NkFUeDc5em03WWhicUZLWkM4' \
--header 'Content-Type: application/json' \
--header 'privy-app-id: <privy-app-id>' \
--data '{
"params": {
    "hash": "0x0775aeed9c9ce6e0fbc4db25c5e4e6368029651c905c286f813126a09025a21e"
    }
}'

A successful response will look like:

{
    "data": {
        "signature": "0x0775aeed9c9ce6e0fbc4db25c5e4e6368029651c905c286f813126a09025a21e",
        "encoding": "hex"
    }
}

Alternatively, you can provide bytes to hash with a specific encoding and hash function, and gets a similar response.

curl --request POST \
--url https://api.privy.io/v1/wallets/{wallet_id}/raw_sign \
--header 'Authorization: Basic Y20xNWh4eDUyMDVlNWx2NHVkdmE3enBqejoybWhVOWhhVTFQYjhYNXV1cVdxQVRIdW5xTWIyUlBKRm5GSHRzWDVzbXNkdUJRUDZtTW05YldmalBwS3hocjJQZHNHY0Q5NkFUeDc5em03WWhicUZLWkM4' \
--header 'Content-Type: application/json' \
--header 'privy-app-id: <privy-app-id>' \
--data '{
"params": {
    "bytes": "0a0234ea220809701d7a17a77e04408093e981a6335a66080112620a2d747970652e676f6f676c65617069732e636f6d2f70726f746f636f6c2e5472616e73666572436f6e747261637412310a15417009bf59e27d2031a23a61e1590289fc3d21b3cd121541132b98ed6fb80a2d45f177cdef091ae2d9dc115418e80770a0bee581a633",
    "encoding": "hex",
    "hash_function": "sha256"
    }
}'

Authorization

Authorization · string · required

App secret authentication.

Headers

privy-app-id · string · required

ID of your Privy app.

privy-authorization-signature · string

Request authorization signature. If multiple signatures are required, they should be comma separated.

Path

wallet_id · string · required

ID of the wallet.

Body

params · object · required

Hide child attributes

Option 1: Sign a pre-computed hash

hash · string

The hex-encoded hash to sign, prefixed with 0x. Use this option when you have already computed the hash.

Option 2: Hash bytes before signing

bytes · string

The bytes to hash and sign. Use this option to provide raw data that will be decoded using the specified encoding then hashed using the specified hash_function.

encoding · string

The encoding scheme for the bytes. Required when using bytes. Available options: utf-8, hex

hash_function · string

The hash function to hash the bytes. Required when using bytes. Available options: keccak256, sha256

You must provide either hash OR the combination of bytes, encoding, and hash_function. These parameter sets are mutually exclusive.

Response

data · object · required

Hide child attributes

signature · string

The signature, prefixed with 0x.

encoding · string

The encoding of the signature.

error · object

Hide child attributes

code · string

The error code.

message · string

The error message.