Evercloud
Evercloud API changelog
- Remove "UNSTABLE" marks from
blockchain
API
- increase
Q_REQUESTS_MAX_SIZE
default to 64kb (now it is possible to send external inbound messages of size > 16kb, up to 64kb)
capabilities_flags
companion field to p8 config parametercapabilities
in: []
(empty list) filter now leads to an empty query result as expectednotIn: []
(empty list) filter now is ignored as expected
- Add new option
--query-max-timeout-arg
orQ_QUERY_MAX_TIMEOUT_ARG
. This adds upper boundary fortimeout
parameter in collection API queries. Default is 24 hours.
- master config
p30
,p40
,p42
fields types prev_code_hash
account fieldallow_latest_inconsistent_data
option in paginatedblockchain
queries:By default there is a delay of realtime data (several seconds) to ensure impossibility of data inserts before the latest accessible cursor. Now it became possible to disable this guarantee and thus - to reduce delay of realtime data by setting this flag to true.- two config options for reading external subscriptions health messages from Redis channel
subscriptions-health-redis-channel
subscriptions-health-timeout
blockchain.master_seq_no_range
behavior for edge cases (when boundaries are close to first and/or latests blocks) E.g. fortime_start=time_end=now
this function used to returnend<start
but now it returnsend=null
, because a masterblock for end doesn't exist yet.max_shard_gen_utime_string
andmin_shard_gen_utime_string
inBlockMaster
- faster and more reliable ArangoDB query for
blockchain.master_seq_no_range.end
Queries:
blockchain.workchain_blocks
. Useblockchain{ blocks }
instead.blockchain.workchain_transactions
. Useblockchain{ transactions }
instead.blockchain.account_transactions
. Useblockchain{ account{ transactions } }
instead.explainQueryAccounts
explainQueryTransactions
explainQueryMessages
explainQueryBlocks
explainQueryBlockSignatures
explainQueryZerostates
getAccountsCount
getTransactionsCount
getAccountsTotalBalance
QueryExplanation
andSlowReason
types
- Deleted accounts added to API (even old ones)
Subscription.remReceipts
subscription.
- Subscriptions improved: no more websocket reconnections on stable network, no missed data during short websocket reconnections caused by network problems
- Add new functions to
blockchain
root api:account
, allows:- to fetch account info (e.g. boc) via
info
field - to fetch transaction info via
transactions
(similar to now deprecatedblockchain.account_transactions
)
blocks
(is similar to now deprecatedworkchain_blocks
)transactions
(is similar to now deprecatedworkchain_transactions
)
- Support for
null
in scalar filter. e.g.filter: { last_paid: null }
. Means missing filter.
blockchain { workchain_blocks }
. Useblockchain{ blocks }
instead.blockchain { workchain_transactions}
. Useblockchain{ transactions }
instead.blockchain { account_transactions }
. Useblockchain{ account{ transactions } }
instead.
- In
blockchain.key_blocks
renameseq_no
argument tomaster_seq_no_range
.
account.init_code_hash
– account 's initial code hash (when it was deployed). All new accounts will have this field after such capability is enabled in the network.- Support
X-Evernode-Expected-Account-Boc-Version
http header.1
(default) means "return old boc version" ,2
– "return new boc version" (withinit_code_hash
field).
when
argument in all joined fields (for example, transaction.in_message'swhen
argument)- the following root queries:
explainQueryAccounts
explainQueryTransactions
explainQueryMessages
explainQueryBlocks
explainQueryBlockSignatures
explainQueryZerostates
getAccountsCount
getTransactionsCount
getAccountsTotalBalance
QueryExplanation
type
Last modified 6mo ago