Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Research and choose between the hedera app throttle and the MN throttle mechanism #10378

Open
bilyana-gospodinova opened this issue Feb 13, 2025 · 0 comments
Labels
enhancement Type: New feature web3 Area: Web3 API

Comments

@bilyana-gospodinova
Copy link
Contributor

Problem

Currently there are two throttles: the mirror node one with the mono code and the services one that comes from the hedera app dependency. Right now both mechanisms execute on every transaction with the modularizedServices flag. We need only one of them but for this case we need to research and choose.

Solution

We need to choose one of them. For this case we will need to research which way is better.

Alternatives

No response

@bilyana-gospodinova bilyana-gospodinova added enhancement Type: New feature web3 Area: Web3 API labels Feb 13, 2025
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Mirror Node Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Type: New feature web3 Area: Web3 API
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant