Describe the bug
It is possible in the current system to have different switchboard types at outbound (src) and inbound (dst) which makes it easy to pay different fees at source and use a different (can be costlier) at destination. Also in case of a fraud packets, all switchboards need to trip that packet.
Expected behavior
The configuration should be consistent for a message/packet. Validation from switchboard is an important step and
Solution
To solve this, it is decided to use proposeForSwitchboard where the switchboard function will be taken as input and all the roots will be stored against this switchboard along with proposal count and packetId.
ameeshaagrawal
commented
1 year ago
Describe the bug It is possible in the current system to have different switchboard types at outbound (src) and inbound (dst) which makes it easy to pay different fees at source and use a different (can be costlier) at destination. Also in case of a fraud packets, all switchboards need to trip that packet.
Expected behavior The configuration should be consistent for a message/packet. Validation from switchboard is an important step and
Solution To solve this, it is decided to use
proposeForSwitchboardwhere the switchboard function will be taken as input and all the roots will be stored against this switchboard along with proposal count and packetId.