Running a node - matcher orderbook returns empty results

[koray1396]

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,

# Matcher settings
  matcher {
    # Enable/disable matcher
    enable = yes

    # Matcher's account address
    account = ""

    # Matcher REST API bind address
    bind-address = "127.0.0.1"

    # Matcher REST API port
    port = 6886

    # Minimum allowed order fee
    min-order-fee = 300000

    # Fee of order match transaction
    order-match-tx-fee = 300000

    # Matcher's directories
    matcher-directory = ${waves.directory}"/matcher"
    data-directory = ${waves.matcher.matcher-directory}"/data"
    journal-directory = ${waves.matcher.matcher-directory}"/journal"
    snapshots-directory = ${waves.matcher.matcher-directory}"/snapshots"

    # Snapshots creation interval
    snapshots-interval = 1d

    # Invalid/Expired orders cleanup interval
    order-cleanup-interval = 5m

    # Maximum allowed amount of orders retrieved via REST
    rest-order-limit = 100

    # Base assets used as price assets
    price-assets = [

    ]

[0xae]

Hello there, you need to config the matcher account address:
checkout my config:

matcher { .... account = "3NN56Z7FwaPs5m6zxqFfBYZgKEb8hn8xso5" .... }

[alexeykiselev]

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.

[username1565]

Hm...

I also see the empty orderbook, after running Matcher REST API on my node, and after change the matcher to my matcher, in waves-lite-client.
Also, I see the empty "markets": [] in response of GET /markets/orderbook on my matcher.

Thelefore, Is this possible to make the synchronization of the markets and settings,
but no orders and synchronize this, between existing matchers in the Mainnet?
Is there any list of existing matchers?
I see here: http://dev.pywaves.org/nodes/ only a few nodes has enabled matcher - status yes.
So, I think, if matcher address or matcher's public-key or/and matcher URL's, will be published in some list,
then new matcher can loading the actual markets and settings from that MATCHER REST API, to let the network - working decentralized, or no?
Maybe, that new matcher, can loading the orders and reside the orders on an instance of this new matcher, but after cancel the order, in this case, this info need to update for many matchers, while synchronization going, and there can be destructive delays (yeap, few seconds is a destructive delays for High-frequency trading).

Also, maybe, will be better to let for the network selecting the best and faster matcher, after ping by uptime, and make transactions faster and all calculations - distributed.
For example, if WAVES network will have 500kk transactions / per nanosecond.