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.

Sign up for GitHub

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

Jump to bottom

fusdc: quiet "unexpected channel" log on outgoing forwards #11047

Open
0xpatrickdev opened this issue Feb 24, 2025 · 0 comments
Open

fusdc: quiet "unexpected channel" log on outgoing forwards #11047

0xpatrickdev opened this issue Feb 24, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@0xpatrickdev
Copy link
Member

0xpatrickdev commented Feb 24, 2025 •
edited
Loading

What is the Problem Being Solved?

In the Forward path, Settler logs:

Settler.14  38 unexpected channel { actual: 'channel-62', expected: 'channel-21' }"

This is not an unexpected channel - this is a notification about our outgoing transfer from the settlementAccount. This happens in Forward's happy path.

Description of the Design

Something like #11046 in an upgrade-compatible way.

Security Considerations

Scaling Considerations

Test Plan

  • Settler should not log "unexpected channel" during a forward
  • Settler should retain precious state (mintedEarly) across upgrade

Upgrade Considerations

A new state variable and stateShape would be a breaking change for the SettlerKit kind and any active instances.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(settler): narrow "unexpected channel" log Agoric/agoric-sdk
1 participant
@0xpatrickdev