Ian Culp

Currently running into this on Ubuntu 20.04 LTS. Followed the instructions here, https://developers.cardano.org/docs/get-started/installing-cardano-node/#linux Verified each of those dependencies installed.

Okay, was able to move forward. I looked inside the config.sub and config.guess files in libsodium/build-aux/, both of which were somehow html responses with 503 errors. Copied both files from...

I've tried several urls, the main one and dappnodes and a couple others and I'm getting the same error about 4881

@michaelsproul it doesn't ignore the error for me. Idk if it's because it's for network gnosis, but it shuts down on that error #4559

I just ran into this on a freshly downloaded snap, it was syncing on 1.38.0 although extremely slowly, restarted to update to 1.38.1 and gave me this error

I had this issue on testnet recently, I think I missed a resharding or something. If the number to the right of the at is staying the same, then I...

Check out the release notes for 1.38.0 there was a resharding that needed to be completed before the protocol upgrade which happened early this morning. You missed it so probably...

Syncing op-sepolia from scratch with v1.7.3 node and v1.101311.0 geth, I've now encountered this, running unpruned Prysm nodes on v5.0.3, stuck at 8366372, running op-node with --l1.beacon-archiver=$OP_NODE__L1_BEACON_ARCHIVE and --l1.beacon=$OP_NODE__L1_BEACON ```...

> There is no way to do it. Let me take the liberty to say, is there really a team maintaining this chain? It moves forward for me using an...

This happened recently to one of my polygon archival nodes, tx with id 250 was in the txpool