Wishlist and Fixlist

Klever Blockchain Feature Requests
1

Request queries for the Node API

  • List of all pools with the amounts
    This saves an incredible number of queries (has already been posted in Slack)

  • Query account with asset list
    Currently, you can only find out the account’s asset list via the Kleverchain proxy.

To fix:

Error in the description at Swagger UI

The description says: returns the reward available …

7 Likes
2

Noted bro, I’m adding on the pipe just now

2 Likes
3

Hello my friend @CryptoJaeger,

Since you tagged the last post, I think it’s appropriate to update you on this.

So, since we’ve deployed a new version of KVM on the testnet, we’ll focus on other things, like updating our proxy with many enhancements and improvements. Your suggestion will be considerate on the pipeline and is within the scope of this update.

We don’t yet have a timeframe for this update, but I believe it will be near the KVM launch.

1 Like
4

Hello @CryptoJaeger!

We’re getting closer and closer to implementing your suggestion, and to ensure we develop the best integration to meet your needs, I’d like to request some examples of what it should look like.

Important Note:

I noticed that you requested this on NodeAPI, but unfortunately, the node will not be performant for this type of operation. The node is strictly designed for performance and security, meaning its data structure is optimized for access in a specific way by the core consensus.

But don’t worry! The proxy was created exactly to fill this gap—providing support for advanced queries, complex listings, pagination, ordering, and more.

About the Examples

Could you provide examples like the following?

:one: List of all pools with their amounts

:small_blue_diamond: Request:

GET /path/to/list

:small_blue_diamond: Query Params:

  • filterA: Filter by asset ID (accepts a list of assets).
  • filterB: Filter by X and does Y.

:small_blue_diamond: What makes this new endpoint different from the existing /v1.0/assets/pool/list in proxy?

:small_blue_diamond: Expected Response:

{ example JSON response }

:two: Query an account with its asset list

:small_blue_diamond: Request:

GET /path/to/account

:small_blue_diamond: What makes this new endpoint different from the existing /v1.0/address/<address>/overview in proxy?

:small_blue_diamond: Expected Response:

{ example JSON response }

Let me know if you can provide these details—it will help us refine the implementation! :rocket:

2 Likes
5

I was primarily interested in the Node API. But since you don’t want to change anything for performance and security reasons, my wish list is actually obsolete.

Regarding the pool list, it makes no sense to me if I have to specify an owner. I want a list with all available pools.

Unbenannt
Unbenannt1455×634 44.5 KB

Just forget the wish list.

6

I really appreciate your feedback and understand your concerns. I want to clarify that it’s not about not wanting to change anything, but rather that the architecture is designed in a way where specific types of operations are best handled by the proxy for performance and security reasons.

Regarding the pool list, you don’t actually need to specify an owner—it’s just a filter. You can call the endpoint normally without providing it:
https://api.mainnet.klever.finance/v1.0/assets/pool/list

Also, if you have any requests that don’t involve metrics, listing, search, or queries, the node could be a candidate for that. The node is great for retrieving specific information but isn’t optimized for operations related to the above.

Let me know if this helps or if you’d like to discuss any alternatives!

1 Like