Improvements and suggestions

[ark-kirill]

Hi everyone!

I’d like to suggest using this discussion as a central place for any proposals related to Chain.Love — whether it’s the overall product, the Toolbox, internal modules, the database structure, providers, UX improvements, integrations, or any other related topics.

If you have ideas, feedback, feature suggestions, structural improvements, or questions — please share them here.

The goal is to keep all proposals in one transparent thread so we can review, discuss, prioritize, and iterate together.

Looking forward to your contributions 🚀

[alongoni]

Hey there! How do I filter by programming language in SDK?

[ark-kirill]

For now you can’t =/

[ark-kirill]

What if we make all fields filterable?

[alongoni]

Amazing, thnx

[Dacomis]

Hey,

Is there a way to see all my subscriptions?

[Igor2698]

To view all your subscriptions on filecoin.chain.love, you’ll need to open your dashboard and make sure you’re signed in.

1. Click Connect Account (subscriptions won’t show until you’re logged in)

2. Open the Subscriptions tab in your dashboard

There you’ll see all your subscriptions and their statuses, and you can open details or manage them (pay/cancel, depending on the status)

If you don’t see anything in Subscriptions, double-check that you’re logged into the same account that created the plan/subscription.

[ArseniiPetrovich]

However, if you are asking about whether it is possible to see it across all installations - it is not yet possible, although we will add this to our roadmap, thank you!

[machdevking-hash]

Is there (or can we have) an MCP server for Chain.Love? Would honestly help us a lot on the AI side.

[nkorn1lov]

We have it planned on our roadmap already, will keep you updated on the progress!

[potven]

Maybe add a small “AI-focused” badge on relevant providers? Feels useful.

[ArseniiPetrovich]

Yeah. According to #434 we thought to make it as a separate category, but maybe having this as a label in other categories would actually make sense given that AI is nearly everywhere

[ivel13]

I started to use a load balancer as a service recently. Can I somehow set different timeouts for different providers? My main provider seems to keep hitting the time limit, so I would need to increase that. Generally, a bit more advanced configuration of the LB would be neat...

[dumikau]

Hey, you actually can!

To set a custom timeout for a provider:

1. Go to the Providers tab.
2. Find the card of the provider you want to modify.
3. Click Edit (top-right corner of the card).

In the Edit provider modal (as shown in the screenshot):

4. Enable Set custom timeout (toggle switch).
5. Enter the desired value in Timeout (ms).
6. Click Save.

The custom timeout will now override the default (5000 ms) for that provider.

[ElvisKrop]

On RPCs side - can we somehow limit the specific methods that are allowed for certain keys? security purposes

[eugene17kotov]

Currently, we do not have a direct feature to restrict specific RPC methods for a single key.
However, this is already on our product roadmap and will be implemented in future updates to provide more granular security control.

In the meantime, you can indirectly manage access to expensive or high-resource methods by configuring Credits Limits. Since different RPC methods consume different amounts of credits, setting a strict credit quota per unit of time can prevent the key from being overused for heavy operations.

How to configure limits for your key:

Step 1: Endpoint Selection. Choose the required endpoint. For your convenience, use the filters to narrow down the options:

• Network (mainnet, testnet etc.)
• Protocol (HTTPS/WSS)

Step 2: Key Configuration. In this section, you can set several security and usage parameters:

• Rate Limit: Set the maximum number of requests per minute/hour.
• Credits Limit: (Recommended for your case) Define the maximum credit consumption per unit of time. The default value is 100,000 credits per minute. You can lower this value to indirectly restrict access to 'heavy' methods.
• Additional Options: For enhanced security, use Allowed IP Address or Allowed Domains to ensure the key is only used from your trusted environments.

We will notify our users as soon as the method-specific filtering becomes available!

[matejdrazic]

Wow, I’ve seen you guys adding a per-provider pages on your Toolbox! Cool! Can we have them ecosystem-agnostic. Like, gonna be great to see if the provider is available on all the chains I’m looking at.

[vasylkivt]

Good point, we’re planning to add ecosystem-agnostic provider pages to our roadmap.

In the meantime, you can check provider availability across chains with our AI assistant here: link

[fosgate29]

Hi. I’ve seen it started to display verifiyed uptime metrics for some of the providers. How is it being calculated? Is there a way for me to see a history of those reports?

[ArseniiPetrovich]

Hey-hey :)
Yeah, that's a wonderful question. We actually currently utilize EigenLayer as a source for the financially-motivated operators, who are looking to perform some work to get a reward for the operators. Each of them serves like an independent fisherman that verifies availability of the RPC providers and report that on-chain. We have developed smart contracts that periodically runs a majority consensus mechanism to figure out if the provider was up or down at a certain period of time.
In details, the process is described in our Whitepaper: https://chain-love.gitbook.io/chain-love-docs/whitepaper#id-2.-performance-module, but the quick schema would look like that:

On top of that we have a "passive scoring" mode, meaning that the real users that utilize our monitoring/lb services are actually counting towards the general scoring system, that combines EigenLayer operators decision with what we see from our users and results in a single number that represents the uptime of the operator.

[leylahawn]

I’m using contributor to contribute to the database. Some of the entries are obsolete. Can we have in Contributor a way to delete them, not only to add? Thx