Kelpdao

Kelpdao wallets are Ethereum tools for importing rsETH

Kelpdao wallets are Ethereum-compatible apps that display and transfer rsETH once you add its ERC-20 contract address on Ethereum Mainnet. Select chain ID 1, import 0xA1290d69c65A6Fe4DF752f95823FAe25cB99e5A7, and confirm the wallet reads the symbol rsETH with 18 decimals. Adding the token creates no blockchain transaction and moves no balance; it tells the interface which contract to query for your Ethereum account.

Account-level transfer controls sit above the wallet interface

The rsETH contract can reject an account transfer even while its wallet reports a positive balance.

The rsETH proxy executes an upgradeable implementation with address-level transfer controls. The rsETH implementation permits an authorized manager to block transfers to and from a selected address for 24 hours. Reapplying the control resets its end to 24 hours from the latest call. During an active block, an administrator also has a function that moves the address's entire rsETH balance to a configured custody address. The wallet still reads balanceOf normally, so a visible balance alone does not prove the contract will accept a transfer.

Contract identity creates a separate failure mode. An Ethereum address contains 20 bytes, rendered as 40 hexadecimal characters; the 0x prefix produces 42 visible characters. Ethereum Mainnet uses chain ID 1. The same rsETH ticker on Base, Arbitrum, or another EVM network does not identify the Ethereum contract. EIP-55 letter casing adds a checksum, making the complete mixed-case address the strongest import field.

The five-stage path from import to confirmed transfer

The rsETH wallet workflow has five stages, and only the final two require an Ethereum transaction.

The first three stages stay off-chain or use read-only JSON-RPC calls. They require 0 signatures, 0 token approvals, and 0 gas. A transfer starts when the wallet encodes transfer(address,uint256), estimates an Ethereum fee, and requests authorization. Broadcasting follows signing; combining those actions in one button does not change their separate control boundaries.

A recipient needs a normal Ethereum address, not a separate rsETH address. The same account holds ETH for gas and ERC-20 balances recorded by their respective contracts.

How do you import rsETH in MetaMask?

MetaMask imports rsETH through its custom-token control while the wallet remains on Ethereum Mainnet.

The Ethereum Mainnet rsETH contract is 0xA1290d69c65A6Fe4DF752f95823FAe25cB99e5A7, and the token reports 18 decimals.

MetaMask extension and mobile

Open the token-management control from the Ethereum account, choose the custom-token option, and paste the complete contract address. MetaMask reads the token metadata before presenting the import confirmation. The preview should identify rsETH and 18 decimals. Confirming adds the asset row to that wallet interface without requesting a contract approval or Ethereum signature.

Rabby portfolio view

Rabby discovers many EVM assets from account activity and portfolio data. If rsETH remains absent, its custom-token control accepts the Ethereum contract address. Confirm Ethereum Mainnet before adding it because Rabby supports multiple EVM chains. A discovered entry and a manual entry query the same on-chain balance; discovery only removes the data-entry step.

Trezor Suite and Ledger signers

Trezor Suite groups ERC-20 assets under an Ethereum account and identifies tokens from their contracts. A Ledger signer connected through MetaMask or Rabby keeps authorization on the hardware-held account while the software supplies the token view. In both arrangements, importing rsETH changes the interface. It does not copy the hardware key into the connected application.

Token discovery and manual display are separate layers

Custom-token import changes the wallet's asset registry while Ethereum keeps the rsETH ledger unchanged.

The interface stores a network, contract address, symbol, and decimal count, then calls balanceOf(account) through an Ethereum node. ERC-20 defines 6 core methods: totalSupply, balanceOf, transfer, transferFrom, approve, and allowance. It also defines 2 required events, Transfer and Approval. The 3 familiar metadata calls - name, symbol, and decimals - are optional in the standard, although rsETH implements them for wallet formatting.

The contract maintains one integer balance for each Ethereum address. Two wallet apps querying the same chain, account, and rsETH contract therefore retrieve the same base-unit value, even when only one app places rsETH in its visible asset list.

Automatic discovery and manual import reach the same ledger; they differ in how the interface learns the contract.

Amount precision and Ethereum gas govern every transfer

A further page states it in practice. rsETH precision controls the transferred integer, while Ethereum gas controls the separate ETH payment.

Eighteen-decimal amount encoding

One rsETH equals 10 ¹⁸ base units, and 1 base unit equals 0.000000000000000001 rsETH. The contract receives an integer; the wallet draws the decimal point. In transfer(address,uint256), the first 4 calldata bytes contain selector a9059cbb, followed by 2 ABI words of 32 bytes each. Ethereum pads the 20-byte recipient into the first word and places the amount in the second, producing 68 calldata bytes.

A wallet might show fewer than 18 decimal places on screen, yet it must preserve the full base-unit amount internally. Review the expanded amount before signing when the display rounds a small remainder.

EIP-1559 fee fields

An ERC-20 transfer executes contract code, so its gas use exceeds the 21,000-gas baseline for a simple ETH transfer. An EIP-1559 type-2 transaction carries 2 fee caps: the maximum fee per gas and maximum priority fee per gas. Ethereum burns the base-fee portion and directs the priority portion to the block proposer. The protocol limits a one-block base-fee adjustment to 12.5% under its normal elasticity formula.

The payable total remains market-set: multiply gas used by the effective gas price. Wallets quote gas prices in gwei, where 1 gwei equals 1,000,000,000 wei or 10 ⁻⁹ ETH. The rsETH balance cannot pay this Ethereum fee, so the sending account needs ETH as well.

Transaction records separate contract rejection from display problems

Ethereum transaction records distinguish a contract rejection from a wallet-only display issue.

Broadcasting returns a 32-byte transaction hash, displayed as 64 hexadecimal characters plus the 0x prefix, or 66 characters altogether. Before inclusion, the receipt remains absent and its block number is null. After execution, receipt status 1 denotes success and status 0 denotes failure; either state consumes gas. Each transaction from a conventional externally owned account carries a nonce, and inclusion increments that account sequence by 1. Ethereum schedules 12-second slots, and 32 slots form a 6.4-minute epoch. A slot offers an inclusion opportunity, not a deadline, so track the hash instead of assuming a fixed confirmation time.

Choosing a wallet setup for regular or long-term rsETH holding

rsETH wallet choice should follow signing frequency, key location, and the number of required authorizers.

Software wallet for frequent transfers

Kelpdao wallets built around MetaMask provide direct custom-token entry and broad Ethereum application connectivity. Rabby emphasizes multi-chain asset discovery and transaction previews. Both create standard Ethereum calls to the same rsETH contract. A software-held key reduces signing friction, which suits accounts used regularly for transfers and contract interactions.

Hardware-backed account for deliberate signing

Ledger and Trezor devices keep the signing key separate from the browser or portfolio interface. MetaMask, Rabby, or Trezor Suite prepares the transfer, while the device authorizes it. This setup adds a physical confirmation step without creating a different rsETH token type. The relevant balance still belongs to the device-controlled Ethereum address.

Shared control through Safe

Safe uses an Ethereum smart account with an owner threshold rather than one software or hardware key. A 2-of-3 configuration requires any 2 of 3 listed owners to authorize execution. Safe itself holds the rsETH balance, and each completed transfer pays Ethereum gas. This structure fits shared treasury control where one person should not authorize movement alone.

Choose MetaMask or Rabby for speed, hardware-backed signing for key separation, and Safe when several owners must approve the same transfer.