Goal clerk rawsend: HTTP 400 Bad Request

1

Hello everyone.

OS: Ubuntu 20.04.01
Net: Mainnet
Parameters: Default

I’m setting up a node now.
Catching up is complete.
So I ran “goal clerk rawsend” to join the consensus and get it online,
but I got “Couldn’t broadcast tx with algod: HTTP 400 Bad Request”.

What went wrong? The following is my operation log.

Thank you very much.

sudo -u algorand -E algokey generate -f spendingkeyfile (Handa: memo mnemonic)
sudo -u algorand -E goal account import (Handa: input mnemonic)
sudo -u algorand -E goal account addpartkey -a 6ZD… --roundFirstValid 18916339 --roundLastValid 22410739
sudo -u algorand -E goal account changeonlinestatus -a 6ZD… -o=1 -t online.tx
sudo -u algorand -E algokey sign -k spendingkeyfile -t online.tx -o online.tx.signed
sudo -u algorand -E goal clerk rawsend -f online.tx.signed
Warning: Couldn’t broadcast tx with algod: HTTP 400 Bad Request: TransactionPool.Remember: transaction V7Z…: overspend (account 6ZD…, data {_struct:{} Status:Offline MicroAlgos:{Raw:0} RewardsBase:0 RewardedMicroAlgos:{Raw:0} VoteID:[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] SelectionID:[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] VoteFirstValid:0 VoteLastValid:0 VoteKeyDilution:0 AssetParams:map Assets:map AuthAddr:AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAY5HFKQ AppLocalStates:map AppParams:map TotalAppSchema:{_struct:{} NumUint:0 NumByteSlice:0} TotalExtraAppPages:0}, tried to spend {1000})
Encountered errors in sending 1 transactions:
V7Z…: HTTP 400 Bad Request: TransactionPool.Remember: transaction V7Z…: overspend (account 6ZD…, data {_struct:{} Status:Offline MicroAlgos:{Raw:0} RewardsBase:0 RewardedMicroAlgos:{Raw:0} VoteID:[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] SelectionID:[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] VoteFirstValid:0 VoteLastValid:0 VoteKeyDilution:0 AssetParams:map Assets:map AuthAddr:AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAY5HFKQ AppLocalStates:map AppParams:map TotalAppSchema:{_struct:{} NumUint:0 NumByteSlice:0} TotalExtraAppPages:0}, tried to spend {1000})

1 Like
2

A blind guess: there wasn’t enough Algo on the account you tried to send from:

overspend (account 6ZD..., 
...
tried to spend {1000})
2 Likes
3

Thank you very much.
I’m so embarrassed.
I put some ALGO in my wallet and it worked.

$ sudo -u algorand -E goal account list
Please enter the password for wallet ‘HandaWallet’:
[offline] Unnamed-0 6ZD… 10100000 microAlgos *Default
$ goal node status
Last committed block: 18935371
Time since last block: 2.0s
Sync Time: 0.0s
Last consensus protocol: GitHub - algorandfoundation/specs at bc36005dbd776e6d1eaf0c560619bb183215645c
Next consensus protocol: GitHub - algorandfoundation/specs at bc36005dbd776e6d1eaf0c560619bb183215645c
Round for next consensus protocol: 18935372
Next consensus protocol supported: true
Last Catchpoint:
Genesis ID: mainnet-v1.0
Genesis hash: wGH…
$ sudo -u algorand -E goal account addpartkey -a 6ZD… --roundFirstValid 18935400 --roundLastValid 22410739
Participation key generation successful
$ sudo -u algorand -E goal account changeonlinestatus -a 6ZD… -o=1 -t online.tx -d
Please enter the password for wallet ‘HandaWallet’:
$ sudo -u algorand -E algokey sign -k spendingkeyfile -t online.tx -o online.tx.signed
$ sudo -u algorand -E goal clerk rawsend -f online.tx.signed
Raw transaction ID BTRZ4I3NH6RLB773CO6KFY6RE2LEGPWSSMKFH5KIU57WRPF2EGVQ issued
Transaction BTRZ4I3NH6RLB773CO6KFY6RE2LEGPWSSMKFH5KIU57WRPF2EGVQ still pending as of round 18935400
Transaction BTRZ4I3NH6RLB773CO6KFY6RE2LEGPWSSMKFH5KIU57WRPF2EGVQ committed in round 18935402

4

Hi team, I am not sure if here you can help me with this issue, but I don´t found the solution.

Issue: Encountering an “HTTP 400 Bad Request” error when attempting to send a transaction using goal clerk rawsend.

Context:

  • Original Algorand Account (Sender): N44XKK7V3AOCI6FMPCTVM3OITUQOHN2SIV3DEJZUVEFKABQXRICM63SCMA
  • Rekeyed Account (Current Authorization): GW7IF6VTXGU5LR3PWKT2O46IVY5OXWEJH6GOCPFRESDMTT2IWY4Y7VHUT4
  • Objective is to eliminate the rekey and restore control to the original account.
  • The account was rekeyed to another address, and the aim is to revert this rekey.

Steps Taken:

  1. Created a zero Algo transaction from the original account to itself, setting the --rekey-to flag to the original account’s address.
  2. Successfully signed the transaction using the private key associated with the original account.
  3. Attempting to send the signed transaction results in the error.

Error Message:

vbnetCopy code

goal clerk rawsend -f transaccion_firmada.txn
Warning: Couldn't broadcast tx with algod: HTTP 400 Bad Request: transaction {...} invalid: nonempty AuthAddr but rekeying is not supported

Details of the Signed Transaction (transaccion_firmada.txn):

  • Sender, Receiver, and Rekey-to Address: N44XKK7V3AOCI6FMPCTVM3OITUQOHN2SIV3DEJZUVEFKABQXRICM63SCMA
  • FirstValid (fv): 1471672
  • LastValid (lv): 1472672
  • Genesis ID: “mainnet-v1.0”
  • Fee: 1000 microAlgos
  • Type: “pay”
  • The transaction is a zero Algo payment meant to revert the rekey.

Additional Information:

  • The Algorand node being used for the transaction is up to date and synchronized.
  • The error persists despite the transaction being within the valid round range and being correctly signed.

Seeking:

  • An explanation for the “HTTP 400 Bad Request: AuthAddr but rekeying is not supported” error.
  • A solution to successfully revert the rekey operation and restore control to the original Algorand account.
5

You should have created a complete new thread for your own issue, rather than comment on a 2 year old completely unrelated thread.

The account N44XKK has been rekeyed to GW7IF6. This means the private key (mnemonic) for N44XKK is no longer used to sign transactions for that account. If you wish to remove the rekey, you must sign the transaction removing the rekey using the GW7IF6 private key. If you do no have the private key for GW7IF6, then N44XKK is no longer under your control.

I’m now locking this thread to prevent further posts to it. Please use your new thread if you need additional assistance.