posaggen
commented
3 years ago Hi Seifeldin,
Thanks for your email! It's great to hear your suggestions about Shuttleflow. Just as you have said, currently the shuttle-in transaction without having the minimum transaction amount will not be processed.
The shuttle-in wallet for each conflux address is a smart contract and the contract logic blocks users to withdraw the deposit token. It becomes convenient for users of centralized exchange to do cross chain transactions, since the shuttle-in transaction is just a simple transfer or ERC20 transfer, they do not even need to have a decentralized wallet. The tradeoff is we need to ensure the safety of shuttle-in wallet so its contract is immutable and the deposited token cannot be withdrawn.
Be affected by Ethereum Berlin hard fork, we are working on a new shuttle-in process and the shuttle-in wallet will be deprecated. People will be required to install metamask and interact with Shuttleflow smart contract to finish a crosschain transaction. At that time, there will be no minimal shuttle-in value and shuttle-in fee anymore.
Best, Fan
On Fri, Apr 2, 2021 at 7:46 PM Seifeldin-Hashem @.***> wrote:
Hello Shuttleflow Team,
It's a pleasure to be addressing you, I am a big fan of the Conflux project and would hope to see it grow into a huge success. Today I am writing to you about a problem which affects me personally, and proposing a solution which could benefit all Shuttleflow users.
I propose the addition of a mechanism to the Shuttleflow Protocol which would allow the release of "locked" funds. Shuttle-in transactions which do not meet the requirement for minimum transfer amount are prone to having the funds locked away indefinitely and potentially lost forever.
It is possible for a user to begin a shuttle-in transaction without having the minimum transaction amount. The funds can be successfully transferred from the user's wallet to the address generated by Shuttleflow over the ETH or BSC network. However, once the funds reach the cross-chain bridge they are barred from crossing to the conflux network and reaching user's Conflux wallet. This situation leaves the user without access or control over their own tokens, and in danger of losing their tokens if the address generated by Shuttleflow is changed in the future.
Therefore I propose that funds that reach the cross chain bridge be subjected to a waiting period. Transfers which meet the minimum amount requirement would pass through immediately. Otherwise the tokens would be held at the bridge for a period of three to seven days.
The holding period would be acceptable by small investors looking to transfer their holdings onto the conflux network. The holding period would also act as a deterrent for 'bad actors' which are mentioned in this article https://medium.com/conflux-network/important-shuttleflow-update-increase-in-minimum-deposit-amount-87ec33da8927 .
Thank you for your attention and consideration, I wish you all the best.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Conflux-Chain/shuttleflow/issues/172, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABK4SAEROIK6IWUYPWJIY6DTGWU77ANCNFSM42IX75DQ .
Seifeldin-Hashem
Hello Shuttleflow Team,
It's a pleasure to be addressing you, I am a big fan of the Conflux project and would hope to see it grow into a huge success. Today I am writing to you about a problem which affects me personally, and proposing a solution which could benefit all Shuttleflow users.
I propose the addition of a mechanism to the Shuttleflow Protocol which would allow the release of "locked" funds. Shuttle-in transactions which do not meet the requirement for minimum transfer amount are prone to having the funds locked away indefinitely and potentially lost forever.
It is possible for a user to begin a shuttle-in transaction without having the minimum transaction amount. The funds can be successfully transferred from the user's wallet to the address generated by Shuttleflow over the ETH or BSC network. However, once the funds reach the cross-chain bridge they are barred from crossing to the conflux network and reaching user's Conflux wallet. This situation leaves the user without access or control over their own tokens, and in danger of losing their tokens if the address generated by Shuttleflow is changed in the future.
Therefore I propose that funds that reach the cross chain bridge be subjected to a waiting period. Transfers which meet the minimum amount requirement would pass through immediately. Otherwise the tokens would be held at the bridge for a period of three to seven days.
The holding period would be acceptable by small investors looking to transfer their holdings onto the conflux network. The holding period would also act as a deterrent for 'bad actors' which are mentioned in this article.
Thank you for your attention and consideration, I wish you all the best.