Skip to main content

Get Wallet Address

Derives a wallet address from an encrypted private key without creating a blockchain connection.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Inputs​

This node has no inputs.

Output​

  • Wallet Address - The wallet address derived from the private key.

Options​

  • Encrypted Private Key - The wallet's encrypted private key from the credential vault.
  • AES Key - The AES encryption key used to decrypt the private key.

How It Works​

The Get Wallet Address node derives a wallet address from a private key. When executed, the node:

  1. Retrieves the encrypted private key and AES key from credentials
  2. Decrypts the private key using the AES key
  3. Derives the public key from the private key
  4. Computes the wallet address from the public key
  5. Returns the wallet address

Requirements​

  • An encrypted private key stored in the credential vault
  • The corresponding AES key for decryption
  • Both credentials must be properly formatted

Error Handling​

The node will return errors for:

  • Missing or invalid encrypted private key
  • Missing or invalid AES key
  • Decryption failures
  • Invalid private key format
  • Key derivation errors

Usage Notes​

  • This operation is performed locally and doesn't require network access
  • The same private key always produces the same address
  • The address is compatible with all Ethereum-based chains
  • No blockchain connection is needed
  • This is faster than creating a full client connection
  • Use this when you only need the address, not transaction capabilities

Example​

Getting the address for a stored wallet:

Options:

  • Encrypted Private Key: (from credential vault)
  • AES Key: (from credential vault)

Output:

  • Wallet Address: 0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb

Common Use Cases​

Address Verification: Confirm which address corresponds to a stored private key.

Multi-Chain Operations: Get the same address for use across different blockchain networks.

Address Display: Show users their wallet address without exposing the private key.

Configuration Validation: Verify that credentials are correctly stored before executing flows.

Address Lookups: Retrieve addresses for logging, monitoring, or reporting.

Conditional Logic: Branch automation based on the wallet address.

tip

Use this node when you need to know the wallet address but don't need to make transactions. It's more efficient than creating a full client connection.

info

The wallet address is derived deterministically from the private key. Running this node multiple times with the same credentials always returns the same address.

Get Wallet Address vs Create Client​

Use Get Wallet Address when:

  • You only need the address
  • No blockchain interaction is required
  • Performance is critical
  • Working offline

Use Create Client when:

  • You need to send transactions
  • You need to query the blockchain
  • You need to interact with contracts
  • Full wallet functionality is required

Security Notes​

  • This node never exposes the decrypted private key
  • The address is public information and safe to display
  • Credentials remain encrypted in the vault
  • Decryption happens only in memory during execution
  • No sensitive data is logged or stored