Skip to main content

Add limit for RU for exact node

CloudBilling and payment

To protect the entire account from RU leaks, we would like to apply usage limits per node.
For example, I would like to limit my TRON node to 5M RUs. If the TRON node exceeds this limit, it should start responding with an “insufficient RUs” error.

Posted by Mykhailo Hordin ·
4 comments

Log in to comment and vote

Comments4

  • Mykhailo Hordin

    •

    Dec 18, 2025

    Hi, @Alexandr Redikultsev

    Thanks for the clarification!

    From our perspective, node-based RU limits look like the most flexible and practical option. In this case, there is no need to create a separate project per node just to apply restrictions, which keeps the setup much simpler and cleaner.

    Regarding default behavior, we believe there should be no RU limit by default, and limits should be configured explicitly only when needed.

    As some additional context and inspiration: in certain blockchains, the number of requests we generate depends heavily on overall network activity. We want to avoid a scenario where, due to such fluctuations, a single node suddenly consumes all available RUs on the account, causing instability or downtime for all other blockchains whose nodes are hosted under the same account.

    For this reason, for nodes of such blockchains, we would like to set a monthly RU cap to contain the issue and prevent it from propagating to other nodes.

    • Alexandr Redikultsev

      Team•

      Dec 18, 2025

      Hi @Mykhailo Hordin ,

      Thank you for getting back to be and providing a lot of details, really appreciate it.

      So basically, for your use case the following would be a good fit:

      1. RU Limit per node per month.
      2.No default limit, configure it whenever needed
      3.Possibility to reset the limit when the fluctuation is gone.

      Regarding the fluctuations you mentioned, how realistic for you is to avoid it let’s say with the daily/weekly limit? Just trying to grab some more context here :)

      • Mykhailo Hordin

        •

        Dec 19, 2025


        @Alexandr Redikultsev , Thanks for the summary - let me clarify one important point, as I think I may not have explained it clearly enough.

        In our case, the primary goal is to configure a persistent monthly RU cap per node, rather than a temporary limit used only during fluctuations.
        Ideally, we would configure a node once — for example, allocate 20M RUs per month to a specific node - and keep this configuration in place permanently.

        If the node exceeds this monthly limit, it should start returning an “insufficient RUs” error, and pay-as-you-go should not be triggered automatically. The idea is to have a strict upper bound to fully isolate the impact of a single node and protect the rest of the account.

        Because of that, daily or weekly limits would not fully solve our problem. Even a short-term spike within a day or a week can still consume a significant portion of the account’s total RUs and affect other nodes. A fixed monthly per-node cap gives us predictable cost control and strong isolation by design.

  • Alexandr Redikultsev

    Team•

    Dec 17, 2025

    Hi @Mykhailo Hordin , thank you for the idea! Let me clarify some details.

    Are you interested in node-based RU limitations or e.g. per project limitation may also come in handy?

    Let’s assume that RU limitation is available per project and per node, what do you think the default limitation should be for your specific case? Unlimited and you change it to some limit or some limit by default and you adjust it if needed?