Skip to content
This repository has been archived by the owner on Jan 29, 2024. It is now read-only.

GW: Improve Cross-msg fee UX and mechanics #93

Open
adlrocha opened this issue Apr 15, 2023 · 0 comments
Open

GW: Improve Cross-msg fee UX and mechanics #93

adlrocha opened this issue Apr 15, 2023 · 0 comments
Labels

Comments

@adlrocha
Copy link
Contributor

The way we currently charge the cross-msg fee when users want to send cross-net messages is bit counter-intuitive. If a user sends a request to send X FIL the fee is deducted from the amount they requested to send, ending up in the arrival of only X - fee FIL to the destination. This is not the way blockchains usually work. The correct behavior is:

  • The user sends a request to send X FIL.
  • The blockchain/actor checks that the account has at least X + fee FIL in its balance, and deducts it from it.
  • X FIL arrive at destination.
    The reason why we didn't go with this approach is because the gateway can't deduct balance directly from an account actor without the owner sending enough FILs in the transaction. We should explore to what extent we can implement this fully on-chain in the actor. Worst case scenario, we implement the IPC agent so for cross-net messages it always sends the amount requested by the user plus the fee, so the underlying behavior is the one users are currently used to (so we would be handling the UX through the off-chain frontend instead of fully on-chain in the gateway actor).
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant