search

Near-One / rainbow-token-connector

ERC-20/NEP-141 Token Connector for Rainbow Bridge
62 stars 18 forks source link

Implement an ability to block users from using a bridged token #50

Open alexauroradev opened 3 years ago

alexauroradev commented 3 years ago

This feature will be required for many stablecoins to work with us. In case this won't be implemented, they're going to block Ethereum-side token connector, which would literally mean that all holders of bridged tokens are penalised.

mfornet commented 3 years ago

Can you elaborate more about this requirement. Do you mean that we should have ability to prevent blacklisted users from interacting with a particular bridge token (sending, depositing and receiving) ?

If that is the case I don't see how it can be done in a decentralized way, and more over I'm against implementing this feature for this particular connector.

Maybe one solution (long term) is having a new connector, with different properties than this one. Then for sure stablecoins that have this requirement should block this connector, and only allows using the new one.

alexauroradev commented 3 years ago

The blocking can be implemented on the level of an individual token -- this would be enough. Literally, the flow should be the following: 1) Connector is creating a vanilla NEP141 token. 2) In case of stablecoins, if the feature of blocking users is required, this token contract can be updated to support this function with the full access key that we possess. 3) The control of this contract is passed to an entity that governs the token to be able to block certain users.