PulseDEV

Whatever that mean

Oh yes, we did. The bridge txns were stuck during the attacks. The txns only goes thru after the attack. So that's something that we need to forewarn.

And other geeky stuff.

So 50/50 we get a new testnet

Where did the idea came from?

If txs were pending from a ddos attack

Or can you just upstream

So queuing till the attack finishes is logical.

Just need to add a fore warn that txn might delay during high gas/usage.

Fair usage.

So we are ok ? Or more fixes

Sorry English is not first language

I share what I can.

=== View, Stop and Remove Docker Containers/Images sudo docker ps -a sudo docker stop CONTAINER_ID sudo docker container prune sudo docker images -a sudo docker image rm -f IMAGE_ID === Remove Validator Keys folder sudo rm -rf /blockchain/validator_keys

Lets not subtlety ask wen launch disguise as any more bugs...😉

Well it's question if anymore bugs to fix

Why am i missing all the blocks? 19 missed 2 scheduled. Any idea?

inside consensus folder maybe next to beacon