Should there be a JSON-RPC method for querying all Native Tokens?

[PaulRBerg]

Open research question. We should look at what Fuel does.

Without a method provided by the client, users would need to rely on blockchain explorers and indexers (The Graph, Envio, etc.) to find out what NTs exist on Sablier.

That shouldn't be so bad given that that is the status quo on vanilla Ethereum, but it might take a while until we establish partnerships with incumbent explorers and indexers, so we may wish to consider offering native support for queries like this.

More research needed.

CC @sablier-labs/sabvm

[IaroslavMazur]

Are you asking whether the Mainnet nodes should be able to communicate SabVM's internal state of the Native Tokens statistics to the outside world?

If yes, then, I believe it's important that this information is readily-available to anyone interested in fetching it.

However, we can only guarantee the nodes contain such method(-s) as part of their API if it's the nodes that we, ourselves, control that we're talking about. Right?

---

That shouldn't be so bad given that that is the status quo on vanilla Ethereum

Yes and no: the vanilla Ethereum only has ETH as the asset for which the problem from the OP is true, while in our case, there will, eventually, be hundreds of NTs, complicating the situation many times over.

[PaulRBerg]

I am specifically referring to obtaining a list of all Native Tokens and other global metrics. I'm not sure what you mean by "internal state of the Native Tokens". Querying information such as the balance of a user can be obtained through the NT opcodes.

we can only guarantee the nodes contain such method(-s) as part of their API if it's the nodes that we, ourselves, control that we're talking about. Right?

I don't understand this point/ question.

the vanilla Ethereum only has ETH as the asset

Good point

[IaroslavMazur]

I'm not sure what you mean by "internal state of the Native Tokens". Querying information such as the balance of a user can be obtained through the NT opcodes.

I was mainly talking about the user balances, yeah.

For an external party to query this info "through the NT opcodes", they'd need to be executed by some public contract functions. Contract functions exposed to the queriers by the RPCs.

I don't understand this point/ question.

Let me phrase it differently: can we really guarantee that all of the RPC providers will provide NT querying functionality in their interface? Is there a way for us to enforce the interface? Would an RPC that wants to participate in our network, but doesn't want to provide that functionality, be punished somehow for this (such that they change their mind about cooperating)?