Content pfp
Content
@
0 reply
0 recast
0 reaction
Tempe.degen 🎩 @ Devcon BKK pfp
Tempe.degen 🎩 @ Devcon BKK
@tempetechie.eth
Careful When Using Degen Chain Bridge Or How I Lost 785,000 DEGEN Bridging from Degen Chain to Base 🤦‍♂️ A thread 🧵⬇️
50 replies
19 recasts
74 reactions
Tempe.degen 🎩 @ Devcon BKK pfp
Tempe.degen 🎩 @ Devcon BKK
@tempetechie.eth
1/ Today, I wanted to increase my amount of locked DEGEN in the Vault, so I bridged 900k DEGEN (in 2 transactions) from Degen Chain to Base. I received only about 115k DEGEN back on Base. When I realized what happened, I was confused by two things: 1. Firstly, the amount I received was much lower than I expected (an 87% slippage!!!) 2. Secondly, the bridge transaction concluded in a few minutes, even though the Degen Chain Bridge UI states it’s going to take 7 days. Let’s investigate further what happened…
6 replies
1 recast
15 reactions
Tempe.degen 🎩 @ Devcon BKK pfp
Tempe.degen 🎩 @ Devcon BKK
@tempetechie.eth
2/ If you go to the Degen Chain Bridge website (https://bridge.degen.tips/) and prepare a DEGEN bridge transaction from Degen Chain to Base, you will notice the vast difference between the sending and receiving values (in this example, 90k DEGEN vs 38k DEGEN):
1 reply
0 recast
9 reactions
Tempe.degen 🎩 @ Devcon BKK pfp
Tempe.degen 🎩 @ Devcon BKK
@tempetechie.eth
3/ This is where I failed in my due diligence because I assumed I would receive on Base the same amount of DEGEN that I sent to the bridge. So, I didn’t pay attention to the receiving number in the UI. Why did I assume that? 🤔 Because it is the norm with canonical bridges (e.g., the official bridges of L2/L3 chains) that you receive back the same amount as you send. Heck, even most commercial bridges will bridge you the same amount (minus a small fee).
2 replies
0 recast
7 reactions
Tempe.degen 🎩 @ Devcon BKK pfp
Tempe.degen 🎩 @ Devcon BKK
@tempetechie.eth
4/ Instead, I was more focused on the part that said the bridging process would take 7 days (which is expected from canonical bridges of optimistic chains, which Degen Chain is). And the part which said the bridging would cost me a small application fee. This was unusual for a canonical chain, but I was fine with it. In my case, the application fees for both transactions together were about 1400 DEGEN, which wasn’t too bad. In the example above (bridging 90k DEGEN), the bridge fee is 164 DEGEN:
1 reply
0 recast
10 reactions
Tempe.degen 🎩 @ Devcon BKK pfp
Tempe.degen 🎩 @ Devcon BKK
@tempetechie.eth
5/ But this does not explain the vast difference between the send value and receive value (in our example: 90k DEGEN vs. 38k DEGEN). Why would you receive so little back? 🤔 When I researched what happened with my bridge transactions, I noticed that the DEGEN I bridged was first swapped to ETH on the Degen Chain. Then, this ETH was bridged to Base, where it was swapped back to DEGEN and sent to my Base address.
1 reply
0 recast
12 reactions
Tempe.degen 🎩 @ Devcon BKK pfp
Tempe.degen 🎩 @ Devcon BKK
@tempetechie.eth
6/ So in our example (bridging 90k DEGEN), if you submit the bridge transaction, the first thing that happens in the background is that 90k DEGEN gets swapped to 0.069 ETH. If you check CoinGecko, you’ll see that 90k DEGEN should give you 0.164 ETH instead:
1 reply
0 recast
9 reactions
Tempe.degen 🎩 @ Devcon BKK pfp
Tempe.degen 🎩 @ Devcon BKK
@tempetechie.eth
7/ Why such a difference? 🤔 It is because the DEGEN/ETH pool on the Degen Chain has too little liquidity, which means that if you swap a bigger amount, you’ll get much less ETH back (aka big slippage). In the example, instead of 0.164 ETH you only get 0.069 ETH. This 0.069 ETH then gets bridged over to Base, where it is swapped for 38k DEGEN. And this is how you end up with much less DEGEN than what you started with.
1 reply
0 recast
15 reactions
Tempe.degen 🎩 @ Devcon BKK pfp
Tempe.degen 🎩 @ Devcon BKK
@tempetechie.eth
8/ But wait, why does a canonical bridge swap the native coin (DEGEN) into ETH? Why doesn’t it just bridge DEGEN directly without doing a swap in between? 🤔 Well, now we’re getting into the second part of the problem: It looks like the Degen Chain Bridge does NOT actually use the canonical bridge. This is why DEGEN gets swapped into ETH during the bridging process instead of being sent to Base directly. And it also explains why the bridging process happens within a few minutes instead of 7 days (which is a normal time period for canonical bridges of optimistic chains).
2 replies
1 recast
14 reactions
Tempe.degen 🎩 @ Devcon BKK pfp
Tempe.degen 🎩 @ Devcon BKK
@tempetechie.eth
9/ How to Prevent Swapping Errors Like Mine in the Future There are three major UI changes that need to be implemented into the Degen Chain Bridge (cc @decentxyz & @jacek): 1. Remove the alert about the 7-day waiting period. This alert is incorrect and leads users to believe they are using a canonical bridge when they are not. 2. The Max slippage value is confusing/incorrect. It leads people to believe that the max slippage for the bridge swap is 1%, which is not true. 3. Disable the Swap button if slippage is greater than 5%. Let the user manually select a higher slippage percentage in the settings. This is a very common practice on DEXes to protect users.
7 replies
1 recast
24 reactions
Tempe.degen 🎩 @ Devcon BKK pfp
Tempe.degen 🎩 @ Devcon BKK
@tempetechie.eth
10/ Also, please update the FAQ below the bridge UI:
5 replies
0 recast
12 reactions
Pau 🎩 ⛓️‍💥 pfp
Pau 🎩 ⛓️‍💥
@p4u
Here my 1000 $degen
2 replies
0 recast
1 reaction
Tempe.degen 🎩 @ Devcon BKK pfp
Tempe.degen 🎩 @ Devcon BKK
@tempetechie.eth
Very much appreciated, Pau! ❤️
0 reply
0 recast
0 reaction