fix: set 1000 sats as minimum amount that can be withdrawn

[ws4charlie]

Description

This PR is to prevent Bitcoin dust-amount withdrawals from registration. It set 1000 satoshis as the minimum amount that can be withdrawn from zEVM.

Closes: 2326

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Include instructions and any relevant details so others can reproduce.

• Tested CCTX in localnet
• Tested in development environment
• Go unit tests
• Go integration tests
• Tested via GitHub Actions

Checklist:

• I have added unit tests that prove my fix feature works

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.68%. Comparing base (f95f0e9) to head (abbe673).

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #2362   +/-   ##
========================================
  Coverage    68.67%   68.68%           
========================================
  Files          304      304           
  Lines        19154    19159    +5     
========================================
+ Hits         13154    13159    +5     
  Misses        5351     5351           
  Partials       649      649           

Files	Coverage Δ
x/crosschain/keeper/evm_hooks.go	83.42% <100.00%> (+0.48%)	⬆️

[kingpinXD]

LGTM,
Is there a way to double check that the original TX is reverted?

[ws4charlie]

LGTM, Is there a way to double check that the original TX is reverted?

Yeah. It was reverted in my local network. See

[kingpinXD]

LGTM, Is there a way to double check that the original TX is reverted?

Yeah. It was reverted in my local network. See

I mean, would it make sense to add an e2e test and check the balance? The user should not have any loss of funds I guess , since the PostTxProcessing hook reverts the entire tx?

If you think an e2e test is not necessary just checking it would be a good idea

[ws4charlie]

LGTM, Is there a way to double check that the original TX is reverted?

Yeah. It was reverted in my local network. See

I mean, would it make sense to add an e2e test and check the balance? The user should not have any loss of funds I guess , since the PostTxProcessing hook reverts the entire tx?

If you think an e2e test is not necessary just checking it would be a good idea

Seems just checking is okay. Also the 'unsupported address' validation was tested against mainnet on v17 release, the zEVM 'withdraw' tx just failed.