Create Network Transaction from Signatures - Coinbase Developer Documentation

Body

application/json

ConstructionCombineRequest is the input to the /construction/combine endpoint. It contains the unsigned transaction blob returned by /construction/payloads and all required signatures to create a network transaction.

network_identifier

object

required

The network_identifier specifies which network a particular object is associated with.

Show child attributes

network_identifier.blockchain

string

required

Example:

"bitcoin"

network_identifier.network

string

required

If a blockchain has a specific chain-id or network identifier, it should go in this field. It is up to the client to determine which network-specific identifier is mainnet or testnet.

Example:

"mainnet"

network_identifier.sub_network_identifier

object

In blockchains with sharded state, the SubNetworkIdentifier is required to query some object on a specific shard. This identifier is optional for all non-sharded blockchains.

Show child attributes

network_identifier.sub_network_identifier.network

string

required

Example:

"shard 1"

network_identifier.sub_network_identifier.metadata

object

Example:

{
  "producer": "0x52bc44d5378309ee2abf1539bf71de1b7d7be3b5"
}

unsigned_transaction

string

required

signatures

object[]

required

Signature contains the payload that was signed, the public keys of the keypairs used to produce the signature, the signature (encoded in hex), and the SignatureType. PublicKey is often times not known during construction of the signing payloads but may be needed to combine signatures properly.

Show child attributes

signing_payload

object

required

SigningPayload is signed by the client with the keypair associated with an AccountIdentifier using the specified SignatureType. SignatureType can be optionally populated if there is a restriction on the signature scheme that can be used to sign the payload.

Show child attributes

signing_payload.hex_bytes

string

required

Hex-encoded string of the payload bytes.

signing_payload.address

string

[DEPRECATED by account_identifier in v1.4.4] The network-specific address of the account that should sign the payload.

signing_payload.account_identifier

object

The account_identifier uniquely identifies an account within a network. All fields in the account_identifier are utilized to determine this uniqueness (including the metadata field, if populated).

Show child attributes

signing_payload.account_identifier.address

string

required

The address may be a cryptographic public key (or some encoding of it) or a provided username.

Example:

"0x3a065000ab4183c6bf581dc1e55a605455fc6d61"

signing_payload.account_identifier.sub_account

object

An account may have state specific to a contract address (ERC-20 token) and/or a stake (delegated balance). The sub_account_identifier should specify which state (if applicable) an account instantiation refers to.

Show child attributes

signing_payload.account_identifier.sub_account.address

string

required

The SubAccount address may be a cryptographic value or some other identifier (ex: bonded) that uniquely specifies a SubAccount.

Example:

"0x6b175474e89094c44da98b954eedeac495271d0f"

signing_payload.account_identifier.sub_account.metadata

object

If the SubAccount address is not sufficient to uniquely specify a SubAccount, any other identifying information can be stored here. It is important to note that two SubAccounts with identical addresses but differing metadata will not be considered equal by clients.

signing_payload.account_identifier.metadata

object

Blockchains that utilize a username model (where the address is not a derivative of a cryptographic public key) should specify the public key(s) owned by the address in metadata.

signing_payload.signature_type

enum<string>

SignatureType is the type of a cryptographic signature. * ecdsa: r (32-bytes) || s (32-bytes) - 64 bytes * ecdsa_recovery: r (32-bytes) || s (32-bytes) || v (1-byte) - 65 bytes * ed25519: R (32-byte) || s (32-bytes) - 64 bytes * schnorr_1: r (32-bytes) || s (32-bytes) - 64 bytes (schnorr signature implemented by Zilliqa where both r and s are scalars encoded as 32-bytes values, most significant byte first.) * schnorr_poseidon: r (32-bytes) || s (32-bytes) where s = Hash(1st pk || 2nd pk || r) - 64 bytes (schnorr signature w/ Poseidon hash function implemented by O(1) Labs where both r and s are scalars encoded as 32-bytes values, least significant byte first. https://github.com/CodaProtocol/signer-reference/blob/master/schnorr.ml )

Available options:

ecdsa,

ecdsa_recovery,

ed25519,

schnorr_1,

schnorr_poseidon

public_key

object

required

PublicKey contains a public key byte array for a particular CurveType encoded in hex. Note that there is no PrivateKey struct as this is NEVER the concern of an implementation.

Show child attributes

public_key.hex_bytes

string

required

Hex-encoded public key bytes in the format specified by the CurveType.

public_key.curve_type

enum<string>

required

CurveType is the type of cryptographic curve associated with a PublicKey. * secp256k1: SEC compressed - 33 bytes (https://secg.org/sec1-v2.pdf#subsubsection.2.3.3) * secp256r1: SEC compressed - 33 bytes (https://secg.org/sec1-v2.pdf#subsubsection.2.3.3) * edwards25519: y (255-bits) || x-sign-bit (1-bit) - 32 bytes (https://ed25519.cr.yp.to/ed25519-20110926.pdf) * tweedle: 1st pk : Fq.t (32 bytes) || 2nd pk : Fq.t (32 bytes) (https://github.com/CodaProtocol/coda/blob/develop/rfcs/0038-rosetta-construction-api.md#marshal-keys)

Available options:

secp256k1,

secp256r1,

edwards25519,

tweedle

signature_type

enum<string>

required

Available options:

ecdsa,

ecdsa_recovery,

ed25519,

schnorr_1,

schnorr_poseidon

hex_bytes

string

required

Response

Expected response to a valid request

ConstructionCombineResponse is returned by /construction/combine. The network payload will be sent directly to the construction/submit endpoint.

signed_transaction

string

required

MESH

Body

Response