Skip to main content
Google Cloud Storage is an alternative to Amazon S3 for publishing signed checkpoints. You can use it with either supported KMS signer. Agent keys

Create a bucket

Use a dedicated bucket for Validator output. The bucket must allow public object reads so Relayers can fetch checkpoints. If your organization enforces public access prevention, use a checkpoint bucket in an environment that permits those reads. Google Cloud public access prevention Replace the project ID and bucket name, and choose a location for the bucket.

Grant access

Set SERVICE_ACCOUNT_EMAIL to your Validator’s Google Cloud service account. Give it bucket-scoped access to read and write objects. Grant public read access for Relayers. Google Cloud bucket IAM

Configure the Validator

Make the service account available to the Validator through Application Default Credentials. On GKE, use Workload Identity Federation. Application Default Credentials Add this block to your agent config and replace the bucket name. If you use a folder, set it to a single path segment. The Relayer expects that format in the announced storage location.
If you use a service account key file, omit useApplicationDefault and set checkpointSyncer.serviceAccountKey to its path inside the Validator process. Start the agent and verify checkpoint publication. Run Validators