-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
TxPool ServiceBuilder and Context #456
Conversation
1239580
to
bc777d5
Compare
1f4461b
to
ac2a7f6
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.
Some minor nits, design looks good
broadcast: broadcast::Sender<TxStatusBroadcast>, | ||
txs: Vec<ArcTx>, | ||
) -> Vec<anyhow::Result<Vec<ArcTx>>> { | ||
// Check if that data is okay (witness match input/output, and if recovered signatures ara valid). |
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.
The new CheckedTranasction
type will make this easier once Victor has finished implementing in fuel-vm.
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.
Yeah, it makes a lot of sense to have it.
Remove
Interface
and move its functionality toTxPool
struct.introduce
ServiceBuilder
andContext