Content pfp
Content
@
0 reply
18 recasts
21 reactions
Tempe.degen 🎩 pfp
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 🎩 pfp
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 🎩 pfp
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 🎩 pfp
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 🎩 pfp
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
Bixbite 👽 pfp
Bixbite 👽
@bixbite
So what about the transactions that just disappeared and are not showing up as pending or confirmed? Where did those go? 🤷‍♀️
1 reply
0 recast
0 reaction
Tempe.degen 🎩 pfp
Tempe.degen 🎩
@tempetechie.eth
Some may have dissapeared due to another tx with the same order number ("nonce" number) being confirmed. And some may still appear on block explorer as pending even though another tx with the same nonce was confirmed. The block explorer still has some issues, so don't rely 100% on it. I'll make another thread on that.
1 reply
0 recast
0 reaction
Bixbite 👽 pfp
Bixbite 👽
@bixbite
Does anyone know how many validator nodes are running? & is there a blockchain maintenance schedule of some sorts that will take snapshots of the chain every X blocks - this can help reduce future re-sync times. Also, if its one node / validator how would the config error occur? .... genuinely interested in this topic.
1 reply
0 recast
0 reaction
Tempe.degen 🎩 pfp
Tempe.degen 🎩
@tempetechie.eth
There's only one "validator" node, it's called a sequencer node. It's run by Conduit, as far as I know. The other nodes are not sequencers, but they can read data or transmit transactions to the sequencer. Conduit will issue a report soon explaining how the config error happened. I'm interested in learning that, too.
1 reply
0 recast
1 reaction