Shunkichi Sato

What are the use cases? Why not adopt a dedicated, single query or endpoint that covers the entire state?

Can I interpret this as combining the currently separate queries—`FindDomains`, `FindAccounts`, `FindAssets`, etc.—and executing them all at once against `impl StateReadOnly`, effectively providing functionality equivalent to an RDB JOIN? Alternatively,...

As long as the queries are based on the same `StateView`, no state changes can be interleaved and it should be safe to merge their results—so is that not currently...

Finally, I understand the issue. Indeed, there is no guarantee that queries issued by the client are based on the same `StateView`. Perhaps the node could maintain a snapshot at...

It seems that archival nodes typically maintain a large number of snapshots proactively, rather than creating them reactively in response to queries.

It seems to me that the explicit height check added in PR #5380 has revealed an underlying issue

In the current implementation, what happens to the behavior of the client or the explorer if they receive a large number of blocks at once?

If there is a use case that truly requires automation, one option is to introduce an off-chain worker that subscribes to pipeline events and converts them into certain transactions. In...

@aoyako - By making the guardians a multisig account, you gain that protection. If you inspect the transaction history for the Propose and Approve instructions, you can see exactly who...

We had a docker build problem with the toolchain file, but as far as I remember we didn't figure out the cause. I guess it was maybe a toolchain mismatch...