Content
@
0 reply
18 recasts
21 reactions
Tempe.degen π©
@tempetechie.eth
How the recent Degen Chain outage affected its dApps, and what to do about it. See the thread below π§΅β¬οΈ
30 replies
11 recasts
55 reactions
Tempe.degen π©
@tempetechie.eth
1/ As you may have noticed, due to a config error, Degen Chain suffered an outage which ended today. While Degen Chain is live again, there are numerous missing blocks - by my estimation, 36 hours worth of missing blocks.
4 replies
0 recast
9 reactions
Tempe.degen π©
@tempetechie.eth
2/ What does that mean? It means that transactions which were in these blocks are now back in the pending state (mempool). For example, a transaction that you made 4 days ago and went through successfully may now be pending again.
1 reply
0 recast
7 reactions
Tempe.degen π©
@tempetechie.eth
3/ (Important: Be aware that because the block explorer is not fully synced yet, a newly pending transaction may still appear as successful.)
1 reply
0 recast
6 reactions
Tempe.degen π©
@tempetechie.eth
4/ These pending transactions are now slowly being sent to the blockchain again and included in new blocks. You may see a confirmed transaction that was sent 3-4 days ago, but it now appears as though it was sent today.
3 replies
0 recast
9 reactions
Tempe.degen π©
@tempetechie.eth
5/ This may lead to some unexpected outcomes. One example is a token swap transaction. Often, swaps have a deadline, so if a swap is not completed within, say, 30 minutes, it will fail. These kinds of transactions will now be marked as failed, even though they appeared successful a few days ago.
1 reply
0 recast
7 reactions
Tempe.degen π©
@tempetechie.eth
6/ A similar issue occurred with /poidh claims. Some of the bounty votes and claims are now failed transactions, even though they were successful a few days ago. These will need to be voted on and claimed again. Please check if this has affected your recent bounty.
2 replies
0 recast
7 reactions