Exchange Algorand (ALGO) to Ethereum (ETH)

A rekeyed Algorand account can send a payment authorized by another address. When tracing ALGO exchange funding, identify the transaction’s sender and receiver instead of treating every address in the signing record as a payment participant.

Three address roles in a rekeyed-account enquiry

RoleWhat the field describesQuestion for a payment review
Transaction senderThe account the payment is sent fromDoes this match the account whose history you are checking?
Authorized signerThe address whose spending key authorized the transactionAre you confusing authority with the account paying the amount?
Payment receiverThe destination specified by the paymentDoes it match the exchange funding instruction?
A role map, not a rekeying instruction. A valid address format or a recognized signer does not verify the intended payment.

A different signer need not mean the balance moved to a new account

Algorand’s rekeying documentation distinguishes an account’s stable public address from its spending authority. The signing reference explains that a rekeyed transaction can carry an authorization address separate from the sender. That distinction matters when a wallet export places sender and signer columns side by side. Do not replace one field with the other in your payment notes.

Imagine a fictional company account A whose payments are authorized through address B. A colleague looking at the signing record might ask why the exchange did not receive a payment from B. First check whether A actually sent the ALGO payment to the instructed recipient. The identity of the authorizer is a separate question; a screenshot naming B does not establish a transfer out of B’s own balance.

Questions to settle in the existing payment record

Which account supplied the amount?
Read the transaction sender in the actual payment record and compare it with the account history being reviewed. If an export labels a column only as address, request clarification rather than deciding that it must mean the sender, signer or receiver.
Which account was meant to receive the ALGO?
Compare the payment receiver and amount with the exchange instruction used for that payment. Signing authority does not replace this destination check. Keep the Ethereum receiving details in their own record so that an ALGO-side discrepancy is not mistaken for an ETH payout-address problem.
What was the confirmed payment outcome?
Obtain the result and transaction reference from the trusted wallet history. A signing prompt or an exported unsigned transaction is not proof of payment. If the concern is an unexpected authorization change, investigate account control separately and avoid approving further requests just to complete the exchange.

Explain the role mismatch without changing account control

A useful support note can identify the transaction, state which field looked unexpected and name the sender and receiver observed in the record. Public account information can help explain the discrepancy; private spending keys and seed phrases are unnecessary. Do not attempt a new rekey operation as a way to make an old transaction’s fields look more familiar.

This material concerns interpreting an existing ALGO payment. It does not instruct you to rotate keys, repair wallet access or send an additional transfer. Once the payment’s actual outcome is established, use the separate exchange record to check the ETH receipt. An unfamiliar signer alone proves neither missing funding nor a missing payout.

Sender and signer questions

Can the authorized signer differ from the payment sender?
Yes. Algorand documents that distinction for a rekeyed account. Read the payment sender separately.
Does a different signer prove the ALGO payment came from that signer’s balance?
No. Inspect the payment sender and transfer details rather than inferring the source from signing authority.
Should I rekey again to correct an old payment record?
No. Interpreting a record does not require changing account control. Investigate the existing transaction first.
What should I provide for a payment enquiry?
The transaction reference, observed sender and receiver, intended instruction and the specific field you question. Keep keys and seed phrases private.

Primary Algorand references

Reviewed:

ALGO to ETH: distinguish the sender from the signer | KOT.CASH