-
Notifications
You must be signed in to change notification settings - Fork 38
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(providers): add connect_builtin example #34
Changes from 2 commits
f3caa8e
1ab217c
61252e0
25ec522
e78a249
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
//! Example of using the `RootProvider<N, T: BoxTransport>::connect_builtin` to create a provider | ||
//! from a connection string. The connection string can be a HTTP, WS or IPC endpoint. | ||
|
||
use alloy::node_bindings::Anvil; | ||
use alloy_network::Ethereum; | ||
use alloy_provider::{Provider, RootProvider}; | ||
use alloy_transport::BoxTransport; | ||
use eyre::Result; | ||
use futures_util::StreamExt; | ||
|
||
#[tokio::main] | ||
async fn main() -> Result<()> { | ||
let anvil = Anvil::new().block_time(1).try_spawn()?; | ||
let http = anvil.endpoint(); | ||
let ws = anvil.ws_endpoint(); | ||
|
||
// Instantiate a HTTP transport provider by passing the http endpoint url | ||
let http_provider = | ||
RootProvider::<Ethereum, BoxTransport>::connect_builtin(http.as_str()).await?; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. More of a general comment and a personal opinion but I'm not a fan of the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Possibly beyond the scope of the intended PR but I would also prefer to see the parameter being strongly typed ( |
||
|
||
// Get latest block number | ||
let block_number = http_provider.get_block_number().await?; | ||
|
||
println!("Latest block number: {:?}", block_number); | ||
|
||
// This requires the `pubsub` and `ws` features to be enabled on alloy-provider | ||
let ws_provider = RootProvider::<Ethereum, BoxTransport>::connect_builtin(ws.as_str()).await?; | ||
|
||
let sub = ws_provider.subscribe_blocks().await?; | ||
|
||
let mut stream = sub.into_stream().take(2); | ||
|
||
println!("Awaiting blocks..."); | ||
|
||
let handle = tokio::spawn(async move { | ||
while let Some(block) = stream.next().await { | ||
println!("{:?}", block.header.number); | ||
} | ||
}); | ||
|
||
handle.await?; | ||
|
||
let ipc_path = "/tmp/reth.ipc"; | ||
|
||
// This requires the `pubsub` and `ipc` features to be enabled on alloy-provider | ||
// This would throw a runtime error if the ipc does not exist | ||
let ipc_provider = RootProvider::<Ethereum, BoxTransport>::connect_builtin(ipc_path).await?; | ||
|
||
let _block_number = ipc_provider.get_block_number().await?; | ||
|
||
Ok(()) | ||
} |
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.
Why are these required and not accessible on the
alloy
namespace?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.
Compiler doesn't the recognize them as the same type when used with
alloy-provider
(w/o the namespace). Ref: #26There 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.
Ah I see, then this should be resolved once that upstream PR has been merged