e-money / bep3 Goto Github PK

For effective token swap cost management, security, and to promote the desired swap transactional activity, we should define the swap fees as we introduce swap Trxs for each supported token class.

It is necessary to add an option for tokens not to be burned when transferred using an out-going swap, but rather store them on a module account while waiting for the tokens to return.

The reason for this is that we have several mechanisms that acts on the total circulalating supply (ie. inflation of stablecoins and NGM tokens), and it is thus necessary not to have this artificially reduced when representations of our tokens enter other networks.

It's worth keeping the existing option of burning tokens for non-native tokens.

The 3 swap supplies (Incoming/Outgoing/Current) quantities relate to the bank supply but are additional quantities affecting the swaps biz logic. Presently managing their movements are operationally opaque. We should add an aggregating sink point for us to monitor them reaping the typical benefits of palatable alert management, gain insights, etc...

As an implementation suggestion, we can analyze the existing generated swap events from the swap transactions and enhance, collect them externally to Prometheus as the SDK appears to set a precedent for.