Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Back to post

Revisions 2

one year ago
How to correct parse full message-graph for smart-contract call?
How to correct parse full message-graph for smart-contract call?
1/ Is it realy so complicated to get parent message, or I missed some method or something else? => This is out of my knowledge. 2/ **How much can I trust method getBlockByUtime? Is it possible that for some unix time I will (not get block)/(get next block)/(any options)?** => `getBlockByUtime` is a method used to fetch a block that was produced closest to a given Unix time. It's not 100% precise due to the fact that block times are not strictly enforced in the protocol, and there's network latency and other factors at play. So while you can generally trust getBlockByUtime to give you a block close to the specified Unix time, you should not rely on it to provide a perfectly accurate block for a precise moment in time. It's always a good practice to handle edge cases where you might not get a block or get a subsequent block. **Also note that this method might return blocks from different shardchains for the same time since different shardchains are essentially separate blockchains running in parallel.**
1/ Is it realy so complicated to get parent message, or I missed some method or something else? => This is out of my knowledge. **How much can I trust method getBlockByUtime? Is it possible that for some unix time I will (not get block)/(get next block)/(any options)?** => `getBlockByUtime` is a method used to fetch a block that was produced closest to a given Unix time. It's not 100% precise due to the fact that block times are not strictly enforced in the protocol, and there's network latency and other factors at play. So while you can generally trust getBlockByUtime to give you a block close to the specified Unix time, you should not rely on it to provide a perfectly accurate block for a precise moment in time. It's always a good practice to handle edge cases where you might not get a block or get a subsequent block. **Also note that this method might return blocks from different shardchains for the same time since different shardchains are essentially separate blockchains running in parallel.**
one year ago
Original
How to correct parse full message-graph for smart-contract call?

1/ Is it realy so complicated to get parent message, or I missed some method or something else? => This is out of my knowledge. **How much can I trust method getBlockByUtime? Is it possible that for some unix time I will (not get block)/(get next block)/(any options)?** => `getBlockByUtime` is a method used to fetch a block that was produced closest to a given Unix time. It's not 100% precise due to the fact that block times are not strictly enforced in the protocol, and there's network latency and other factors at play. So while you can generally trust getBlockByUtime to give you a block close to the specified Unix time, you should not rely on it to provide a perfectly accurate block for a precise moment in time. It's always a good practice to handle edge cases where you might not get a block or get a subsequent block. **Also note that this method might return blocks from different shardchains for the same time since different shardchains are essentially separate blockchains running in parallel.**