Link Signer
Last updated
Last updated
Each subaccount can have at most one linked signer at a time. A linked signer can perform any execute on behalf of the subaccount it is linked to. Use the Linked Signer query to view your current linked signer.
A max of 5 link signer requests every 7 days per subaccount. (weight=50). Use the Linked Signer Rate Limit query to check a subaccount's linked signer usage and remaining wait time.
tx
object
Yes
tx.sender
string
Yes
Hex string representing the subaccount’s 32 bytes (address + subaccount name) of the tx sender.
tx.signer
string
Yes
A bytes32
sent as a hex string; includes the address (first 20 bytes) that’ll be used as the sender's
signer. the last 12 bytes can be set to anything.
tx.nonce
string
Yes
signature
string
Yes
The solidity typed data struct that needs to be signed is:
sender
: a bytes32
sent as a hex string; includes the address and the subaccount identifier of the primary subaccount to add a signer to.
signer
: a bytes32
sent as a hex string; includes the address (first 20 bytes) that’ll be used as the sender's
signer.
Notes:
the last 12 bytes of the signer
field do not matter and can be set to anything.
set signer
to the zero address to revoke current signer on the provided sender
.
A link signer transaction object. See section for details on the transaction fields.
This is an incrementing nonce, can be obtained using the query.
Signed transaction. See section for more details.
See more details and examples in our page.
nonce
: the tx_nonce
. This is an incrementing nonce, can be obtained using the query.
Success
Failure