# MIP-16: JSON-RPC Query Methods

**URL:** <https://forum.monad.xyz/t/mip-16-json-rpc-query-methods/546>\
**Category:** MIPs\
**Created:** [September 21, 2026, 10:36pm UTC](https://forum.monad.xyz/t/mip-16-json-rpc-query-methods/546 "2026-09-21T22:36:13Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![typedarray](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.monad.xyz/typedarray/32/424_2.png) [@typedarray](https://forum.monad.xyz/u/typedarray)\
**Post date:** [October 7, 2026, 4:06pm UTC](https://forum.monad.xyz/t/mip-16-json-rpc-query-methods/546/3 "2026-10-07T16:06:03Z")

</div>

Thanks for the feedback, here are my responses.

1. **Distinguishing between incomplete node data and empty replies**.

The latest version of the proposal better specifies this behavior ([link](https://github.com/monad-crypto/MIPs/blob/typedarray/mip-16-review/MIPs/MIP-16.md#block-range)). It introduces the concept of a server / implementation _availability window_ for each method, which the server must compare against each request, and respond with an error if the requested block range falls outside of the window.

1. **Pagination / limit within the block**.

We also added a section that better specifies the “Block-aligned pagination” behavior ([link](https://github.com/monad-crypto/MIPs/blob/typedarray/mip-16-review/MIPs/MIP-16.md#block-aligned-pagination)). TL;DR - the server is allowed to return greater than the user-requested number of events to ensure that the response is block-aligned. We also renamed `limit` to `target`, which better describes how it works. To address your scenario directly, the server would finish collecting data from block 2 and then return 200 events.

---

_[View the full topic](https://forum.monad.xyz/t/mip-16-json-rpc-query-methods/546)._