Update Validator

Updates validator information.

Usage

import { client } from './viem.config'
 
const { receipt } = await client.validator.updateSync({
  inboundAddress: 'validator.example.com:9000',
  newValidatorAddress: '0x742d35Cc6634C0532925a3b844Bc9e7595f0bEbb',
  outboundAddress: '203.0.113.10:9000',
  publicKey: '0x1111111111111111111111111111111111111111111111111111111111111111',
})
 
console.log('Transaction hash:', receipt.transactionHash)
Transaction hash: 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef

import { Account, Client } from 'viem/tempo'
 
export const client = Client.create({
  account: Account.fromSecp256k1('0x...'),
})

Asynchronous Usage

The examples above use a *Sync variant of the action, that will wait for the transaction to be included before returning.

If you are optimizing for performance, you should use the non-sync validator.update action and wait for inclusion manually:

import { client } from './viem.config'
 
const hash = await client.validator.update({
  inboundAddress: 'validator.example.com:9000',
  newValidatorAddress: '0x742d35Cc6634C0532925a3b844Bc9e7595f0bEbb',
  outboundAddress: '203.0.113.10:9000',
  publicKey: '0x1111111111111111111111111111111111111111111111111111111111111111',
})
const receipt = await client.transaction.waitForReceipt({ hash }).receipt

Recipes

Migrate a Node to New Infrastructure

Combine validator.get with update to point the record at new endpoints while keeping the validator's address and key.

import { client } from './viem.config'
 
const current = await client.validator.get({
  validator: '0x742d35Cc6634C0532925a3b844Bc9e7595f0bEbb',
})
 
const { receipt } = await client.validator.updateSync({
  inboundAddress: 'validator-2.example.com:9000',
  newValidatorAddress: current.validatorAddress,
  outboundAddress: '198.51.100.7:9000',
  publicKey: current.publicKey,
})

import { Account, Client } from 'viem/tempo'
 
export const client = Client.create({
  account: Account.fromSecp256k1('0x...'),
})

Rotate a Validator's Address

Reuse the existing record from validator.get and pass a fresh newValidatorAddress to rotate the address that identifies the validator on chain.

import { client } from './viem.config'
 
const current = await client.validator.get({
  validator: '0x742d35Cc6634C0532925a3b844Bc9e7595f0bEbb',
})
 
const { receipt } = await client.validator.updateSync({
  inboundAddress: current.inboundAddress,
  newValidatorAddress: '0x8ba1f109551bD432803012645Ac136ddd64DBA72',
  outboundAddress: current.outboundAddress,
  publicKey: current.publicKey,
})

import { Account, Client } from 'viem/tempo'
 
export const client = Client.create({
  account: Account.fromSecp256k1('0x...'),
})

Return Value

type ReturnType = {
  /** Transaction receipt. */
  receipt: TransactionReceipt
}

The transaction receipt.

Parameters

inboundAddress

• Type: string

Validator inbound address <hostname|ip>:<port>.

newValidatorAddress

• Type: Address

New address for this validator.

outboundAddress

• Type: string

Validator outbound IP address <ip>:<port>.

publicKey

• Type: Hex

Validator communication public key.

account (optional)

• Type: Account | Address

Account that will be used to send the transaction.

feePayer (optional)

• Type: Account | boolean

Fee payer for the transaction (TIP-1 gas sponsorship).

Pass true to defer the fee token to an external fee payer (e.g. a relay), or a local Account to co-sign the transaction as the fee payer.

feeToken (optional)

• Type: Address | bigint

Fee token for the transaction.

Can be an unpaused USD-denominated TIP-20 token address or ID.

gas (optional)

• Type: bigint

Gas limit for the transaction.

keyAuthorization (optional)

• Type: KeyAuthorization

Signed key authorization to include with the transaction, authorizing an access key to act for the sending account.

maxFeePerGas (optional)

• Type: bigint

Max fee per gas for the transaction.

maxPriorityFeePerGas (optional)

• Type: bigint

Max priority fee per gas for the transaction.

nonce (optional)

• Type: number

Nonce for the transaction.

nonceKey (optional)

• Type: 'expiring' | 'random' | bigint

Nonce key for the transaction (TIP-1009 2D nonces).

Use 'expiring' to select an expiring nonce, which enables concurrent transaction submission without nonce ordering. Use 'random' to select a random key.

throwOnReceiptRevert (optional)

• Type: boolean
• Default: true

Whether a Sync action throws when the receipt reports a revert.

validAfter (optional)

• Type: number

Unix timestamp after which the transaction can be included.

validBefore (optional)

• Type: number

Unix timestamp before which the transaction must be included.