Amaru and alternative targets

[jeluard]

Here is the current status quo of amaru-ledger dependencies support when compiling for alternatives targets.

Wasm

Using cargo build --target wasm32-unknown-unknown

Name	Support
async-trait	✅
rust-bech32	✅
gasket-rs	❌
rust-hex	✅
num	✅
pallas-addresses	✅
pallas-codec	✅
pallas-crypto	✅
pallas-network	❌
pallas-primitives	✅
serde	❌
tokio	✅
tracing	✅

RiscV

Using cargo +nightly build -Zbuild-std=alloc,core,proc_macro,panic_abort --no-default-features --target riscv32im-risc0-zkvm-elf

Name	Support
async-trait	✅
rust-bech32	✅
gasket-rs	❌
rust-hex	✅
num	✅
pallas-addresses	❌
pallas-codec	❌
pallas-crypto	❌
pallas-network	❌
pallas-primitives	❌
serde	❌
tokio	❌
tracing	✅

[KtorZ]

It's quite debatable already that the ledger depends on pallas-network and tokio. Gasket as well sounds like something which could be pushed at the boundaries.

[jeluard]

tokio is only used for its Mutex (and indirectly by gasket). pallas-network is used for its Point definition, that should probably be defined in pallas-primitives (tracked here).
Makes sense to push gasket up, maybe in the amaru crate that acts as final glue layer.

Note that a bunch of pallas libs fail but only when used in amaru, they compile fine standalone somehow. The underlying issue is tracked here.

[jeluard]

As of #108 amaru-ledger compiles for both wasm and riscv. amarau-consensus will require a bit more work.