Skip to content
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

Processor modularity #289

Closed
kayabaNerve opened this issue May 8, 2023 · 1 comment
Closed

Processor modularity #289

kayabaNerve opened this issue May 8, 2023 · 1 comment
Labels
feature New feature or request processor

Comments

@kayabaNerve
Copy link
Member

Right now, the Scheduler expects a UTXO interface. I'm not saying we can't cram an account-based chain such as ETH into it, yet we likely want to have networks specify their scheduler.

Ideally, we could also modularize out fuzzy matching (outputs + plan ID match, as used in Monero) vs strict matching (we know a TX ID before we sign the TX). The latter would let us chain TXs, instead of waiting for on-chain appearance. This would massively increase the complexity of #284 though, as it'd be n-depth RBF instead of 1-deep RBF.

@kayabaNerve
Copy link
Member Author

kayabaNerve commented Jul 3, 2024

Partially done during the Ethereum integration and superseded by #569.

@kayabaNerve kayabaNerve reopened this Jul 3, 2024
@kayabaNerve kayabaNerve closed this as not planned Won't fix, can't repro, duplicate, stale Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request processor
Projects
None yet
Development

No branches or pull requests

1 participant