ISSUE #301: [Web3/Soroban]: Native XDR Serialization & RPC Binding for LotPassport Contract

[josealfredo79]

🎯 Problem Statement

SorobanAdapter currently generates simulated ledger hashes. It must integrate the official @stellar/stellar-sdk to execute real contract invocations against Soroban Testnet and Futurenet.

🛠️ Technical Tasks

• Configure @stellar/stellar-sdk isolated inside src/core/blockchain/.
• Implement buildRegisterLotTransaction() mapping domain parameters to contract types:
  • lot_code: Symbol
  • digest: BytesN<32>
  • producer_id: Address
  • altitude: u32
• Execute pre-flight simulation (server.simulateTransaction) to estimate CPU instructions and ledger read/write footprints.
• Parse Soroban result envelopes to return validated ledger sequence, txHash, and explorer URLs (Stellar Expert).

✅ Definition of Done (Acceptance Criteria)

• Standalone test runner script (scripts/test-soroban-register.ts) successfully submits a live transaction to Soroban Testnet.
• UI remains fully responsive even when Stellar RPC endpoints experience latency.

---

• Target Module: src/core/blockchain/SorobanAdapter.ts
• Estimated Bounty: 400 USDC / Drips Tier 3 (4–6 days)

[HazEOskA]

Hi — I’d like to take #7 if the 400 USDC bounty is funded and available to an external contributor.

GitHub: @HazEOskA

Implementation plan after assignment:

• integrate the official "@stellar/stellar-sdk" inside "src/core/blockchain/"
• implement deterministic XDR / Soroban value mapping for "lot_code", "digest", "producer_id", and "altitude"
• run "simulateTransaction" before submission and surface RPC / simulation failures explicitly
• return verifiable ledger sequence, tx hash, and explorer evidence instead of treating a generated hash as proof
• include a standalone Testnet runner and reproducible verification evidence

Before I start implementation, please confirm:

1. external contributors are eligible,
2. the payout route/network,
3. whether you can assign ISSUE #301: [Web3/Soroban]: Native XDR Serialization & RPC Binding for LotPassport Contract #7 to @HazEOskA.

I’ll wait for explicit confirmation/assignment before making code changes.

[jlsp124]

I started reviewing this and noticed the issue’s register_lot parameters don’t match the current contracts/lot_passport/src/lib.rs ABI. The adapter config also currently has a placeholder contract ID. Should #7 target the four-argument interface in the issue, or the current Rust contract interface? And for the live Testnet runner, should I deploy a fresh test contract or is there an existing Testnet contract ID I should use?