HiveSQL
Search…
TxLimitOrdersCreates

Blockchain operations

    limit_order_create
    limit_order_create2

Columns

Name
Description
owner
account who filled a limit order
orderid
an order ID defined by the owner. It must be unique
amount_to_sell
amount of asset
amount_to_sell_symbol
symbol of the asset
min_to_receive
The target asset expected price (limit_order_create only)
min_to_receive_symbol
The target asset expected symbol (limit_order_create only)
exchange_rate
The target asset expected price (limit_order_create2)
fill_or_kill
flag to specify if the order should be killed (removed) from the order book if it cannot be filled immediately
expiration
expiration time for the order

Description

This table contains operations broadcasted to the blockchain when users want to buy or sell assets on the internal market.
min_to_receive and min_to_receive_symbol are used by limit_order_create operation only and will be left to NULL for other operations.
exchange_rate is used by limit_order_create 2operation only and will be left to NULL for other operations
The meaning of fill_or_kill is the same as literally, either fill (match) or kill (close). That is to say that when the user puts an order, if it can be filled, it will be filled and if it cannot be filled, it will be closed. So fill_or_kill can also be counted as a means to cancel an order
expiration is to specify when the order will expire. It can even be any time within 28 days. The order is automatically canceled when it expires, so this is also another way to cancel an order.
Last modified 5mo ago
Copy link