Soroban rs support in WASI

[merkle-maren]

Closes #6

soroban-rs running inside wasip2 containers. It took a chain of forks, but it works.

To test:

./client/wasi/build.sh
./client/wasi/run.sh account

Requires env vars for the RPC endpoint and account name.

Example:

$ ./run.sh account
RPC URL: https://mainnet.stellar.validationcloud.io/v1/***REDACTED***
Account: GBQQANXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

=== Account Info ===
Account ID:GBQQANXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Sequence:   264582668472025089

=== Native XLM Balance ===
Balance: 4.1499900 XLM (41499900 stroops)
Balance (via ledger entry): 4.1499900 XLM (41499900 stroops)

Depends on this stack of unmerged PRs:

• add wasm32-wasip2 networking support tokio-rs/tokio#7933 (released in 1.51.0)
• Add WASIp2 support paritytech/jsonrpsee#1628
• Wasip2 support rs-stellar-rpc-client#1
• Wasip2 support soroban-helpers#1

Build command:

RUSTFLAGS="--cfg tokio_unstable" cargo +nightly build --target wasm32-wasip2 --release

Requires unstable tokio and nightly Rust.

Not ready to ship. The blocker is the tokio PR — once that merges and stabilizes, the rest of this stack has a real path forward. This PR is proof the architecture works.

[merkle-maren]

Note: socket2 v0.6.3 includes rust-lang/socket2#639 eg. see https://github.com/rust-lang/socket2/blob/v0.6.3/src/sys/unix.rs

We can change the dependency there to "0.6.3" and remove the patch.

One step closer.

[merkle-maren]

mio 1.2.0 was just released including that patch. Now, work is progressing on the tokio pr

[merkle-maren]

tokio PR merged and released in v1.51.0 tokio-rs/tokio#7933

[voice-of-miyagi]

I confirm it works. A good verification. 👍