mindstyle85

might be unrelated but this is a very common error for node runners, which usually means an instance is already running on that port on the localhost

ok so what we found out here is that while his first txs to the faucet addr have failed, all subsequent ones with higher gas price show success in explorer...

I just want to note that low/min self stake is a standard practice in tendermint chains, usually because validators rather self stake the minimum, then delegate via another address (preferably...

For POI issues we need those for stuck/not on chain head which need to redeploy the subgraphs, closing manually via remix etc, like Koen said.. and then there are those...

i am getting this on my subgraph QmbS7vmAWXJqsJEnAbvNSBYQXxCUmZWHFQygHPbyb3vy3N: ``` "fatalError": { "message": "Decoder error: Error(\"invalid type: null, expected a sequence\", line: 0, column: 0)" ``` full output: ``` { "data":...

@fattox yes pretty sure as all my other ones are syncing and no issues, and theres at least one other user with the same problem I am guessing you somehow...

if anyone wants to verify, just sync it from scratch again.. something is def broken.

these to are dead too (still)..... Nov 27 00:28:23.293 WARN Trying again after trace_filter RPC call failed (attempt #10) with result Err(Decoder("Error(\"invalid type: null, expected a sequence\", line: 0, column:...

Ok i found out what it is.. wouldnt it be great if it doesnt panic and tells you the syntax in the cost model doc is wrong? just a thought.....

for reference, tested in latest versions of chrome and brave: