Issue 329 cross chain verifier deploy

[auracule007]

Summary #329

Implements issue #329 by adding a deployment script for the cross-chain-verifier Soroban contract. The script builds the verifier WASM, deploys it with Stellar CLI, and initializes the deployed contract using a root validator key as the admin address.

Changes

• Added scripts/deploy_cross_chain_verifier.sh

  • Accepts --source-account
  • Accepts root validator keys via repeated/comma-separated --root-validator-key
  • Supports --root-validator-keys-file
  • Supports optional --admin, --network, --rpc-url, --network-passphrase, --wasm, --no-build, and --dry-run
  • Deploys the verifier WASM with stellar contract deploy
  • Invokes initialize --admin <address> after deployment

• Added .gitattributes

  • Keeps shell scripts LF-normalized for Unix-compatible execution

Notes

The verifier contract currently initializes with a single admin address, so the deployment script uses the first supplied root validator key as the initializer admin unless --admin is explicitly provided.

Validation

• cargo fmt --all -- --check
• cargo clippy --locked --all-targets --all-features -- -D warnings
• cargo test --locked
• cargo test -p cross-chain-verifier

Not Completed Locally

• npm run lint because eslint was not installed/available in web/node_modules
• WASM release build because the retry was not approved after the first run timed out

Branch / Commit

• Branch: issue-329-cross-chain-verifier-deploy
• Commit: 25fbc4d Add cross-chain verifier deploy script

Closes #329

[drips-wave]

@auracule007 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[auracule007]

@EDOHWARES Please review this PR and check workflow