-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: move local signers to a separate crate, fix wasm #306
Conversation
03f82dc
to
3154b86
Compare
3154b86
to
c4a5737
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this makes sense to me!
use crate::{TransportError, TransportResult}; | ||
use alloy_json_rpc::ResponsePacket; | ||
/// Future for transport-level requests. | ||
pub type TransportFut<'a, T = alloy_json_rpc::ResponsePacket, E = TransportError> = Pbf<'a, T, E>; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unrelated changes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wasming network as much as possible, it compiles now on wasm32-wasi
or if getrandom.features = ["js"]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Closes #262, but does not fix wasm for alloy-network. This is because
k256
always importsgetrandom
through multiple dependencies that userand_core
.Closes #294
Fix wasm checks for most crates, see
wasm-wasi
GHA job. This job should have the same results aswasm32-unknown-unknown
withgetrandom/js
. Only crates that we cannot make compile is Trezor (libusb), GCP (idk), IPC (no fs)Closes #74