Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
Contributions
=============

TODO
See [Provide Feedback on a Page](https://github.com/canton-network/cf-docs#provide-feedback-on-a-page).
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
Copyright (c) 2025 Digital Asset (Switzerland) GmbH and/or its affiliates. All rights reserved.
Copyright (c) 2026 Digital Asset (Switzerland) GmbH and/or its affiliates. All rights reserved.
SPDX-License-Identifier: Apache-2.0 AND CC-BY-4.0

docs
Expand Down
11 changes: 0 additions & 11 deletions docs-main/global-synchronizer/deployment/prerequisites.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,14 +3,6 @@ title: "Prerequisites"
description: "System requirements for running a validator on the Canton Network"
---

{/* COPIED_START source="splice:docs/src/validator_operator/validator_hardware_requirements.rst" hash="22640d55" */}

<Warning title="Pre-reviewed Content - Do Not Modify">
This section was copied from existing reviewed documentation.
**Source:** `docs/src/validator_operator/validator_hardware_requirements.rst`
Reviewers: Skip this section. Remove markers after final approval.
</Warning>

This section describes hardware requirements for running a validator. Note that these are reference values. Actual requirements can vary based on usage of your validator. We recommend monitoring your production validator nodes with respect to CPU and memory usage of all components and disk usage of the database, and adjust the resourcing as needed.

The requirements include both the validator and participant container.
Expand All @@ -26,6 +18,3 @@ These requirements are largely identical between the docker-compose based deploy
## Database Latency

Components are relatively sensitive to database latency. If you use a managed database offering like GCP CloudSQL, it is recommended that you allocate it in the same region and zone that your cluster runs in.


{/* COPIED_END */}