feat: implement WASM plugin system for transaction decoding #113
Description
What problem does this solve?
Different dapps have complex transaction structures that require specialized decoding logic to display meaningful information to users. Currently, Nexum core would need to be modified for each dapp's custom format, which doesn't scale.
Describe the solution
Implement a WASM-based plugin system for the TUI that allows dapps to define custom decoding methodologies for transactions and signatures. Plugins would be loaded at runtime and provide human-readable transaction breakdowns specific to their protocol.
Alternatives considered
- Hard-coding decoders for popular protocols (doesn't scale, requires core updates for each protocol)
- Using ABI decoding only (insufficient for complex multi-step transactions)
- JavaScript plugins (security and sandboxing concerns, platform-specific)
Implementation notes
- Define plugin interface with transaction/signature input and decoded output format
- Use wasmtime or similar for sandboxed WASM execution
- Implement plugin discovery/loading mechanism in TUI
- Performance target: <10ms per decode operation
- Security: plugins should have no network/filesystem access
- Plugin registry for discovering available decoders