-
Notifications
You must be signed in to change notification settings - Fork 171
[consensus] Remove Relay #2674
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
base: main
Are you sure you want to change the base?
[consensus] Remove Relay #2674
Conversation
Deploying monorepo with
|
| Latest commit: |
d50e51b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8d07aef8.monorepo-eu0.pages.dev |
| Branch Preview URL: | https://remove-relay.monorepo-eu0.pages.dev |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
commonware-mcp | d50e51b | Jan 02 2026, 09:23 PM |
| @@ -779,4 +775,4 @@ | |||
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 we assume re-broadcast is handled by the application (for getting the payload around after epoch change)?
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.
Like for certify, we could add a RetryableAutomaton with repropose but that seems a little jank.
| run_1k(ed25519::fixture); | ||
| } | ||
|
|
||
| fn requires_repropose<S, F>(fixture: F) |
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 is a useful test regardless of what we do here.
Closes: #2394