-
Notifications
You must be signed in to change notification settings - Fork 326
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
ADR: Domain Decomposition #162
Conversation
### Connection | ||
|
||
```rust | ||
trait Connection { |
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.
Should these really be traits? IBC objects like Connection, Channel, Packet are all concrete types that don't vary across chains. Clients are more of an interface and do vary depending on the chain, so we end up with concrete types like the Tendermint Client, Grandpa Client, Local Client, etc.
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.
Agreed, if those don't vary across chain then they should definitely be plain structs, and we leave it to the traits to abstract over operations, etc. rather than data.
Codecov Report
@@ Coverage Diff @@
## master #162 +/- ##
=========================================
+ Coverage 13.6% 35.1% +21.4%
=========================================
Files 69 137 +68
Lines 3752 8576 +4824
Branches 1374 2961 +1587
=========================================
+ Hits 513 3012 +2499
- Misses 2618 5374 +2756
+ Partials 621 190 -431
Continue to review full report at Codecov.
|
This is implemented, can we go ahead and merge this @ancazamfir? |
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.
Looks good at this point. I think we should update this along with the implementation.
* Initial sketch of domain decomposition * Add dependencies outline * Add potential components names next to operations * update based on relayer spec * Align with relayer-spike * update the status * fix typos and add the second foreign client * Reviewed ADR 004 Co-authored-by: Romain Ruetschi <romain@informal.systems> Co-authored-by: Anca Zamfir <zamfiranca@gmail.com> Co-authored-by: Adi Seredinschi <adi@informal.systems>
Domain Decomposition
[to address #326]
The objective here is to outline the dependency graph for the relayer that will facilitate
Still a work in progress, probably needs to be scoped down. But the ideas are ready for critique☺️
rendered
For contributor use:
docs/
) and code commentsFiles changed
in the Github PR explorer