soroban-rpc: review endpoints

[tsachiherman]

Review current Soroban API, identify higher level non-network functionality that could be moved to JS SDK. Remove those endpoints. (needs a new ticket to cover effort)

[mollykarcher]

Expected outcome of this would be a document detailing which endpoints we are removing and/or moving, as well as dependent issues for moving each of those individual endpoints.

[paulbellamy]

First proposal was here, but moved to stellar-deprecated/soroban-docs#289 for better review & discussion

[tsachiherman]

by writing getLedgers you meant "retrieve the txclosemeta for a series of ledgers", right ?
I think that I'd like to be avoid going that path, unless you can see any concrete use for that.
i.e. I'd like to avoid exposing internal data structures as part of our API.

[tsachiherman]

The getNetwork seems to be beyond network passphrase. maybe we should rename it into getStatus and retrieve bunch of more info ? i.e. rpc version, captive core version, xdr version, etc.
thinking about that further - maybe two endpoints : one to retrieve "static" info, like versions and network passphrase and one for dynamic status such as last ledger num, early ledger num, etc.

[tsachiherman]

could you elaborate on the eta ? is that like a deadline ?

[paulbellamy]

getLedgers, I don't have a specific use case. But seemed in the spirit of a lower-level-but-more-powerful API. I don't think txclosemeta is a very internal data structure. It's in the stellar-xdr library, so anyone can parse it. That said, I'm not particularly attached to the getLedgers endpoint proposal.

[jcx120]

Open: Do we want to include getLedgers?