Skip to main content

Generate Wallet

Generates a new cryptocurrency wallet with a random private key and returns the wallet address along with the encrypted private key.

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 newly generated wallet address (e.g., "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb").
  • Encrypted Private Key - The wallet's private key encrypted with AES, encoded as a hexadecimal string.

Options​

  • AES Key - The AES encryption key used to encrypt the private key. Store this in the credential vault for security.

How It Works​

The Generate Wallet node creates a new Ethereum-compatible wallet. When executed, the node:

  1. Retrieves the AES key from the credential vault
  2. Generates a random cryptographically secure private key
  3. Derives the public key and wallet address from the private key
  4. Encrypts the private key using AES encryption
  5. Returns both the wallet address and encrypted private key

Requirements​

  • An AES key stored in Robomotion's credential vault
  • Sufficient system entropy for secure random number generation

Error Handling​

The node will return errors for:

  • Missing or invalid AES key in credentials
  • AES key decoding failures
  • Wallet generation failures
  • Encryption errors

Security Best Practices​

  • Store the encrypted private key securely in your credential vault
  • Never log or display the decrypted private key
  • Save the encrypted private key immediately after generation
  • Use separate wallets for different purposes (testing, production, etc.)
  • Back up encrypted private keys in a secure location
  • Keep the AES key separate from the encrypted private keys

Usage Notes​

  • Each execution generates a completely new wallet
  • The wallet is compatible with all Ethereum-based chains
  • The same wallet address will work on Ethereum, Polygon, BSC, etc.
  • Newly generated wallets start with zero balance
  • You need to fund the wallet before it can send transactions
  • Store both outputs for future use

Example​

Generating a new wallet:

Options:

  • AES Key: (stored in credential vault)

Output:

  • Wallet Address: 0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb
  • Encrypted Private Key: a1b2c3d4e5f6... (hex-encoded encrypted data)

Complete wallet setup flow:

  1. Generate Wallet - Create new wallet
  2. Store to Vault - Save encrypted private key to credential vault
  3. Log Address - Record the address for funding
  4. Fund Wallet - Send initial ETH/tokens to the address
  5. Create Client - Use the wallet for automation

Common Use Cases​

Automated Account Creation: Generate wallets for new users or customers automatically.

Testing Environments: Create disposable wallets for testing automation flows.

Multi-Wallet Strategies: Generate multiple wallets for distributing assets or operations.

Temporary Wallets: Create short-lived wallets for specific tasks or transactions.

Wallet Pools: Generate a pool of wallets for rotation or load distribution.

Bot Wallets: Create dedicated wallets for trading or monitoring bots.

warning

Generated wallets start with zero balance. You must send cryptocurrency to the address before the wallet can send transactions or pay gas fees.

danger

The encrypted private key and AES key together provide full access to the wallet. Treat these as highly sensitive credentials. If either is compromised, the wallet's funds are at risk.

Storage Recommendations​

After generating a wallet:

  1. Save the encrypted private key to Robomotion credential vault
  2. Save the wallet address to a secure database or configuration
  3. Document the wallet's purpose and creation date
  4. Set up monitoring for the wallet address
  5. Create a backup of the encrypted private key

AES Key Management​

  • Use a strong, randomly generated AES key (256-bit recommended)
  • Store the AES key separately from encrypted private keys
  • One AES key can encrypt multiple wallet private keys
  • Rotate AES keys periodically for enhanced security
  • Never hardcode AES keys in your automation flows
tip

Generate a batch of wallets at once and store them for future use. This is more efficient than generating wallets on-demand during automation execution.