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.

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

[Feature Request] Send tokens to a different address than the sender address #211

Closed
john-light opened this issue May 19, 2021 · 1 comment

Comments

@john-light
Copy link

john-light commented May 19, 2021

Problem

The bridge seems to only send tokens to the same address as the sender address, only on the opposite network. For example if the user is sending USDT from 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Ethereum then the bridge will send RUSDT to 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on the RSK network.

However, some RSK wallets (such as Liquality) do not generate the same RSK address as the Ethereum address. This results in difficulty for users of these wallets when using the bridge, who must then figure out a series of complicated steps to export their seed, import in another wallet, find the correct derivation path the addresses were generated on, etc.

Solution

Allow users to input a custom receiving address for the transaction they are sending across the bridge.

@pmprete
Copy link
Contributor

pmprete commented May 19, 2021

Hi John we are aware of this issue, we are working to allow sending funds to other addresses on version 2, this will be released in this quarter. It's taking us a while as there are security concerns in case you send the funds to a contract on the other network, we are in the process of auditing the code.
Thanks for contributing! :)

@pmprete pmprete closed this as completed May 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants