MASQrauder

This card should wait on #676 ... This will be obsolete/irrelevant if we adopt [https://github.com/alloy-rs](https://github.com/alloy-rs) (the planned successor to [https://github.com/ethers-rs](https://github.com/ethers-rs)) which I recommend. We'd prefer to do a single migration...

error[E0512]: cannot transmute between types of different sizes, or dependently-sized types --> /Users/sswing/.cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.3.15/src/sockaddr.rs:176:9 | 176 | mem::transmute::(v4); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: source type: `SocketAddrV4` (48 bits) = note: target...

For the rust-web3/json-rpc follow-ups after this card, I recommend we consider adopting [https://github.com/alloy-rs](https://github.com/alloy-rs) (the planned successor to [https://github.com/ethers-rs](https://github.com/ethers-rs)). The determining factor is if we think alloy-rs is ready for use....

This will be obsolete/irrelevant if we adopt [https://github.com/alloy-rs](https://github.com/alloy-rs) (the planned successor to [https://github.com/ethers-rs](https://github.com/ethers-rs)) which I recommend. We'd prefer to do a single migration instead of 1 from rust-web3 to ethers-rs...

Other suggestions for `shared_lib` -> `core_lib`, `common_lib` Structure suggestions to avoid repetition: ``` shared_lib/ message/ actor/ payment/ configuration/ data ui/ command/ type/ configuration/ bootstrap/ runtime/ ``` I don't feel strongly...