Failed to publish tx ... pool : connection already teared down
Got this error in the console while running the program. The subscription feature also does not work, it just endlessly loads. I assume these issues are connected. The pub0 has been configured with default settings and is running in the background. The log starts by saying listening on xyz. Then it constantly switches from connected to disconnected

.
Looks like this is an issue of pub0sub dependency, not behaving as it should be.
Probably you can try with https://github.com/itzmeanjan/harmony/releases/tag/v0.9.2, which uses Redis.
It nearly worked! I now get a block fetching error. Could this be due to the node itself?

It does not appear to be a node problem unless there is a flag I am not running geth with.
Though as far as I understand it looks like Ethereum Node's RPC related issue.
This happens here https://github.com/itzmeanjan/harmony/blob/4572d3712321cdaeb20e3313067f71ad3b3268dd/app/listen/header.go#L110-L116, I wonder is the blockchain mining blocks ?
Depends on how mining is defined. I am running harmony on goerli testnet.
Used the most recent version with Ropsten (POW testnet) and it worked flawlessly!
Is it possible to modify harmony so it can be used with other EVM clones such as BSC?
Thanks!
I myself used harmony with Polygon PoS chain. As long as BSC nodes implement the txpool RPC methods which harmony uses, it should work.
Interesting. It is weird that this did not work with the goerli geth node.
To be more specific https://geth.ethereum.org/docs/rpc/ns-txpool is what exactly is required by harmony.
I think you should update go eth to v1.10.17
I think you should update go eth to v1.10.17
You're correct. Similar issue was present in ette, which was detected & fixed https://github.com/itzmeanjan/ette/pull/69
If one has time, feel free to send PR or I'll raise one sometime this week.