Ethereum has revolutionized the way developers interact with decentralized systems, and at the heart of this ecosystem lies Ether (ETH) — the native cryptocurrency that powers transactions and smart contract execution on the network. Whether you're deploying contracts, transferring value, or testing decentralized applications, understanding how to manage Ether and multiple Ethereum addresses is essential.
In this comprehensive guide, we’ll walk through practical steps for checking balances, funding accounts, sending Ether between addresses, and switching between sender identities using sbt-ethereum. You’ll learn not only the commands but also best practices for secure and efficient Ethereum development.
Understanding Ether and Its Role in Ethereum
Ether (ETH) serves as the fuel — or "gas" — for the Ethereum blockchain. Every transaction that modifies the state of the network, such as sending funds or interacting with a smart contract, requires a small amount of ETH to cover computational costs.
While reading data from a smart contract is free, any write operation incurs a fee paid in ETH. Fortunately, you don’t need large amounts to get started — just $10 to $20 worth of ETH can support extensive development and testing.
⚠️ Important Note: While ETH enables network interactions, most financial dApps should avoid using it as a primary store of value due to its high volatility. Instead, consider stablecoins like USDC or DAI, which are pegged to real-world currencies and offer more predictable value.
Checking Ether Balances Across Addresses
One of the first things you’ll want to do is verify the balance of your Ethereum addresses. The ethAddressBalance command makes this simple.
Using Address Aliases
Instead of typing long hexadecimal addresses, sbt-ethereum lets you assign aliases:
sbt:eth-command-line> ethAddressBalance default-sender
0 ether (address: 0x1144f4f7aad0c463c667e0f8d73fc13f1e7e86a2)You can also use ENS names:
sbt:eth-command-line> ethAddressBalance pejorative.eth
0.36043144606611496 ether (~30.31 USD)Default Sender and Current Sender
sbt-ethereum uses the concept of a current sender — the address that will be used by default for outgoing transactions. You can check it with:
sbt:eth-command-line> ethAddressSenderPrintThis shows whether the current sender is your default or has been overridden in the session.
If no address is specified in a balance check, the command defaults to the current sender.
👉 Discover how to securely manage multiple crypto wallets and streamline your blockchain interactions.
Funding an Ethereum Address
Before performing any transactions, your address must hold a small amount of ETH for gas fees.
How to Acquire ETH
The easiest method is purchasing ETH via platforms like Coinbase. Once acquired:
- Go to your Ethereum wallet.
- Click “Send”.
- Transfer funds to your
default-senderaddress.
To find your default sender:
sbt:eth-command-line> ethAddressSenderDefaultPrint🔐 Security Tip: Always verify your wallet passphrase before sending funds. Use ethKeystoreWalletV3Validate to confirm access:sbt:eth-command-line> ethKeystoreWalletV3Validate 0x1144f4f7aad0c463c667e0f8d73fc13f1e7e86a2A successful validation means your credentials are correct and your funds will be accessible.
⚠️ Warning: If you lose your passphrase or wallet file, your funds are irrecoverable. Back up yoursbt-ethereumshoebox regularly usingethShoeboxBackup.
After funding, recheck your balance:
sbt:eth-command-line> ethAddressBalance
0.1 ether (~15.30 USD)Now you're ready to transact!
Testing Transactions: The Ping Command
To test connectivity and transaction capability without transferring value, use the ethTransactionPing command. This sends 0 ETH from an address to itself — a lightweight way to confirm everything works.
When you run:
sbt:eth-command-line> ethTransactionPingYou’ll see a detailed transaction preview including gas cost (typically around 0.0002 ETH). Confirm with y to submit.
After success, check Etherscan by pasting your full hex address (not alias) into the search bar. You’ll see the new 0-value transaction recorded on-chain.
Your balance decreases slightly due to gas fees — proof that even "free" actions have a cost on Ethereum.
Creating a Second Ethereum Address
Managing multiple addresses enhances security and enables complex workflows. To create a new one:
sbt:eth-command-line> ethKeystoreWalletV3CreateYou’ll be prompted to set a passphrase. The system generates a new keypair and stores it securely.
Verify access:
sbt:eth-command-line> ethKeystoreWalletV3Validate 0x13e3d8d785cdeb1d18f298dcf07ea35a659e157dAssign an alias for convenience:
sbt:eth-command-line> ethAddressAliasSet secondary-address 0x13e3d8d785cdeb1d18f298dcf07ea35a659e157dNow you can reference secondary-address instead of the full hex string.
💡 Pro Tip: Use tab completion! Typedfordefault-sender, orsforsecondary-address.
Sending Ether Between Addresses
Use ethTransactionEtherSend to transfer ETH between accounts.
Since the current sender is still default-sender, funds will come from there unless changed.
To send 0.01 ETH to your secondary address:
sbt:eth-command-line> ethTransactionEtherSend secondary-address 0.01 etherYou’ll see:
- Recipient and sender addresses
- Value: 0.01 ETH
- Estimated gas fee (~0.0000882 ETH)
- Total cost
Confirm with y. Once mined, check the balance:
sbt:eth-command-line> ethAddressBalance secondary-address
0.01 ether (~1.50 USD)Success! The transfer is now immutable on the blockchain.
Switching Between Sender Addresses
By default, sbt-ethereum uses your default-sender. But you can override this temporarily using:
sbt:eth-command-line> ethAddressSenderOverrideSet secondary-addressNow all outgoing transactions originate from secondary-address. Verify with:
sbt:eth-command-line> ethAddressSenderPrintTry sending back 0.005 ETH:
sbt:eth-command-line> ethTransactionEtherSend default-sender 0.005 etherThis time, the “From” address is your secondary wallet. After confirmation, both balances reflect the updated values.
This flexibility allows developers to simulate multi-user scenarios and manage different roles within dApps.
👉 Learn how top developers manage multiple blockchain identities efficiently and securely.
Frequently Asked Questions (FAQ)
Q: Why do I need ETH if I’m not storing value in it?
A: Even if your app uses stablecoins, you still need ETH to pay gas fees for every transaction on Ethereum. Without it, your transactions won’t be processed.
Q: Can I recover my funds if I forget my passphrase?
A: No. Ethereum wallets are non-custodial — your passphrase is the only way to access your account. Store it securely offline and consider using a hardware wallet for added protection.
Q: What happens if I send ETH to the wrong address?
A: Transactions on Ethereum are irreversible. Always double-check recipient addresses before confirming. Using ENS names (e.g., alice.eth) reduces human error.
Q: How much ETH should I keep in each address?
A: Keep minimal ETH in development addresses — just enough for gas. For production or long-term storage, use cold wallets and multi-signature setups.
Q: Is it safe to reuse addresses?
A: Yes, Ethereum addresses can be reused safely. However, for privacy reasons, some prefer generating new addresses per use case.
Q: What’s the difference between default sender and current sender?
A: The default sender is set during configuration, while the current sender is what’s actively used — which can be temporarily overridden during a session without changing the default.
Final Thoughts
Mastering Ether management and multi-address workflows is foundational for any Ethereum developer. From checking balances and funding accounts to securely switching senders and transferring value, these skills empower you to build robust decentralized applications.
Always remember:
- Secure your passphrases.
- Backup your wallet files.
- Monitor gas costs.
- Use stablecoins for value-sensitive applications.
With practice, these operations become second nature — enabling faster iteration and more reliable deployments.