New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running a node - matcher orderbook returns empty results #1354
Comments
Hello there, you need to config the matcher account address:
|
Actually, Matcher is a semi-centralised part of the Waves network. So, orders reside on an instance of the matcher. But settlement happens on the blockchain. |
Hm... I also see the empty orderbook, after running Matcher REST API on my node, and after change the Thelefore, Is this possible to make the synchronization of the Also, maybe, will be better to let for the |
Hello,
I'm testing to running a node with matcher. Rest api seems to work fine, but market orderbook does not seem to get updated. Is this a normal behaviour?
/matcher/orderbook/{amountAsset}/{priceAsset} returns empty results, /matcher returns an empty string. My config is below.
PS: If this is normal, then I would suggest a websocket implementation for market depth as an alternative to rest api, since querying orders for multiple pairs regularly is very slow and quite uneffective due to overhead.
Thanks,
The text was updated successfully, but these errors were encountered: