Alex Browne
Alex Browne
@luandt-ibl the `could not connect to peer` warning is expected. It can happen if another peer is behind a NAT or firewall, or if they are no longer online. What's...
Thanks @SvenMeyer we're looking into this.
It also looks like `CollectibleMainInfoValue` is hard-coded to 2.0624 ETH.
I am able to reproduce similar results by following the instructions you shared. I'm coordinating with our devops engineer to see if there is anything wrong with our Mesh nodes...
I spent a lot more time investigating this today. Here's what I found out: 1. The order filter and other configuration options match between our Mesh nodes on Kovan and...
While the CPU optimizations we're working on will help with this, I'm starting to think that they won't be enough to fully address the problem. I also opened https://github.com/0xProject/0x-mesh/issues/822 to...
Quick update: We have seen that CPU optimizations have an impact here. We also recently opened https://github.com/0xProject/0x-mesh/pull/848 which should help further. Planning to implement some of the other improvements mentioned...
This should be fixed by #692. We just need to run more simulations/tests to confirm.
Possibly fixed by https://github.com/0xProject/0x-mesh/pull/733
@jalextowle can you confirm whether this is fixed by #733?