cBridge 2.0 Testnet Feedback Reward Second-week Winners Announced

3 min read

As we launched the cBridge 2.0 test network (test-cbridge-v2.celer.network) on October 19, we started a simple feedback campaign in the meanwhile to motivate and collect feedback from users during the beta testing process in order to maximize the user experience.

During the past two weeks of cBridge 2.0 beta, we received more than 300 test feedbacks from both English and Chinese communities.

Below is the list of feedback of high quality and the corresponding users we selected for the second week of testing.

English Community Feedback

1.

good to has a caution for high Slippage amount same as low slippage

——0xe8BC56125D018853Ee394332a734f86337B41ceF

2.

I found two problems left over from version 1.0 of cbridgeV1. These two problems must be fixed. The first problem is that V1 has conducted a code security audit, but no information about the audit can be seen from bridgeV1. Code security audit can greatly increase product credibility. After the cbridgeV2 code security audit is completed, the information about the successful audit or the logo of the audit institution is disclosed on the cbridgeV2. The second problem is that cbridgeV2 has no problem to submit feedback. The project party needs to help users solve the problems that may appear to be too long waiting time, transaction failure, too long response time, and unable to confirm the transaction.

——0xC64477fB2064b19C07b956f734D7256fF2939E38

3.

  • Support more language versions
  • Increase the blackboard page, this page displays TVL, 24HVolume
  • Add a learning page, this page is directly linked to blog.celer.network
  • Change the UI of the farm page, this page needs more green and vitality

——0x82fB8b5464fE80F79c68C8f0674Bef0955fa00E5

4.

For the new system, I have several suggestions:

  • Support more wallet login
  • The online multi language version makes it more convenient for non English speaking countries such as South Korea, Japan, Russia and so on
  • Add more functions, such as cross chain cancellation, one click cancellation of liquidity, cross chain acceleration, etc

——0xABDed695fa2B78DE1e265d8033c9e5200C8308D3

5.

As a blockchain product, users must be guided to see the main advantages of the product intuitively. But our products don’t do that. Add the currently supported cross chain asset logo, cross chain time, total cross chain assets and other information at the bottom of the product home page. Let people see this information as soon as they open our products.

——0x34FA15b687D30cB4Ca0E0dCa1AfcAe4c553D80ce

6.

Even if the add Liquidity transaction passes normally, “Your Total Liquidity”

Will not be updated unless the browser is updated.

——0xE9236a5eB81181e716E7AD29C75798CE397A8CD1

7.

The current UI has no via concept at all. The UI of a web page needs to be designed according to the color system and characteristics of the logo. The current UI has nothing to do with celer’s logo. The modification opinion is to change the color system of the web page to the main color system of celer’s logo, and add blockchain, Internet, high technology and other elements to the web page to make the web page look full of a sense of science and technology.

——0x6C599d56A3991164b47203557DeE532A3877D08d

8.

I think it should add the description about cross-chain, including the minimum cross-chain amount, the maximum cross-chain amount, the estimated time of cross-chain arrival, and the cross-chain handling fee.

——0xdF68F9528c4c1ca1df17Bc7B22DFBf80390F9669

9.

I’ve tried cBRIDGE v2 test site (bridge transfers between goerli, bsc, fantom testnets and add liquidity in USDT and CELR for all networks) As a result bridge transfers were fast as much as possible but while adding liquidity pending time was so slow. This is testnet it must be much faster, after mainnet with much user it will be so much slow I think, my only advice works on this improving and decreasing the pending time.

——0x3b021Ac943F89bF747aef43dCcB3c6377B417aEB

10.

“Transfer my funds” in transfer page not align correctly. half of “y” in phrase not shown——0xe8BC56125D018853Ee394332a734f86337B41ceF

Chinese Community Feedback

11.

当我要transfer时,选择从以太坊测试网向Fantom测试网转1000USDT时。From一栏中的1000,没有USDT这四个英文字母,但是有logo。To一栏中的999.390562,有USDT这四个英文字母,但是没有logo。这个地方虽然是小细节,但是强迫症的用户根本就受不了啊,需要上下统一格式,要有单位就都有,要有logo也都有。

——0x472c41C7d89136626B21c60f81c9e05eB2EFcdA4

12.

  • 画面很简洁我很喜欢,但是光线的颜色太压抑了,希望能调整一下光线颜色。
  • 用户执行完具体操作完后,比如跨链、提供流动性的操作,没有提示需要等待的时间或提醒。
  • 增加更多的跨链资产,最好是能让项目方自己来申请。 
  • 开放api或者sdk借口,做成一个开放性跨链桥平台。

——0x8252045E10Dec459CC21a79efD2217E7Bb34fF86

13.

体验下来主要有两个问题,第一 :UI背景色是黑色,但是部分系统提示文字也是黑色的,这样根本就看不清楚系统提示。第二 :transfer时在币种选择框,无法使用币种缩写进行搜索。现在以为币种少,这个问题没什么影响,等到币种多了以后,很影响用户体验。在币种搜索框,只能通过币种的全称进行搜索像“celer ”“Tether”,不能使用“celr”与“usdt” 。我上传一张图,能很清晰的说明这两个问题。

——0x868f8318072C0D1d6fb1fc1DCceaC1F47623Bac1

14.

提一个建议,增加一个提醒功能。现在的cbridge2.0只能通过meta钱包链接,也就是说只能在浏览器使用。大部分使用完跨链后就去做别的事情了,没办法一直盯着cbridge2.0的链接。提醒功能需要拉起浏览器的授权提醒,跨链完后或者是上链打包后对用户进行浏览器消息提醒,这样用户可以在电脑办公的时候就能看到跨链成功的系统。原理跟展现模式与微博私信提醒类似

——0x049d90412FD96fA2e262F9A509504E581868fce2

15.

在选择完要进行兑换的两个币种及网络时,显示预计所需时间。或者是在点击兑换后的详情页面中,能显示预计所需时间。这个提示还是很有必要的。

——0xd46299ddb46721D5A553d05261f6b3BDAAf5c235

16.

1.现在是黑色界面,能不能加一个调亮页面的按键,就像选择白天跟黑夜模式一样。长时间盯着黑色调会使人眼睛变得很疲劳,加一个变成白色调的模式。2.钱包地址这里加一个复制功能以及切换地址功能。现在切换钱包只能在小狐狸钱包切换,这样比较麻烦,最好在cbridge就可以选择切换钱包,然后再去小狐狸钱包授权。

——0x68E727Ffc8EdA800D71B1035914F159E1Ab9685b

17.

  • 不够简洁,表达清楚的情况下,可去掉不必要的词语,如“transfer my fund”,
  • 在Liquidity页面,希望增加具体的各个流动性池的Rewards选项;
  • 图标希望能稍微大点,让人一目了然。

——0x08f0938250735DC157Edfd981488D7e5A97826e0

18.

可以在这个页面上增加投票功能,让celer更加社区化,更加去中心化,持币用户可以在页面上发起或参与投票。还可以在这个页面上增加使用帮助功能,点开以后有各种使用过程中可能会遇到的问题:讲解使用方法的介绍视频,如何连接到以太坊钱包,如何领取流动性奖励,应该用哪种网络类型的BNB或者ETH,是否适应Brave或者Google浏览器,可以将跨链中的资产转移到另一个钱包地址吗。

——0x0C78d063122D1666Fc7cF0b0622262500815775c

19

增加区块浏览器选项,平台用户可以通过这个选项可以任意查看区块上的交易信息。这个区块浏览器应该是支持多链交易信息查询与显示。

——0xc0797b73634fED285FFDDF64dB9E053B238BE808

20.

當我點下Unlock Reward後,跳出類似要我 approve transaction 之類的畫面,但我的 Metamask 沒有反應,於是刷新畫面後,View Reward 的畫面變成已經 unlock完成,可以 claim 的狀況,但按下 claim 後卻沒有任何反應。

——​​0x1de40a67c9aa3b2650becd5decebb762a30b9268

For the above cBridge 2.0 test network quality feedback, our engineering team will carry out relevant discussions and further optimization. We greatly appreciate the proactive feedback from the community users, and we will deliver feedback rewards soon!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: