Skip to content

Added docs for Scan-app /registry rate limits#1073

Open
pasindutennage-da wants to merge 1 commit into
mainfrom
pasindutennage-da/add/scan-registry-ratelimits
Open

Added docs for Scan-app /registry rate limits#1073
pasindutennage-da wants to merge 1 commit into
mainfrom
pasindutennage-da/add/scan-registry-ratelimits

Conversation

@pasindutennage-da

Copy link
Copy Markdown
Contributor

[ci]

Signed-off-by: pasindutennage-da <pasindu.tennage@digitalasset.com>

Signed-off-by: Pasindu Tennage <pasindu.tennage@digitalasset.com>
@mintlify

mintlify Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
cantonfoundation 🟢 Ready View Preview Jul 14, 2026, 3:35 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@mintlify

mintlify Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
cantonfoundation 🟡 Building Jul 14, 2026, 3:33 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.


### Rate-limiting Public Endpoints

Because the `/registry` endpoints must be publicly accessible, you must explicitly configure your Istio mesh to allow public traffic to these routes while rate-limiting them to prevent Denial of Service (DoS) attacks.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not everyone uses Istio. This should be more generic.

Because the `/registry` endpoints must be publicly accessible, you must explicitly configure your Istio mesh to allow public traffic to these routes while rate-limiting them to prevent Denial of Service (DoS) attacks.
We recommend configuring the following rate limits for the `/registry` endpoints using your preferred rate-limiting mechanism:

* **For Transfer Factory endpoints** (`/registry/transfer-instruction/v1/transfer-factory` and `/registry/transfer-instruction/v2/transfer-factory`):

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we sure that we want the concrete numbers public? Shouldn't they be in configs-private, and just referenced here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Tracking: Expose Scan::registry/token APIs publicly

2 participants