From 8f5b699071583107e3a9cf20eae51cb4750c463a Mon Sep 17 00:00:00 2001 From: Golo Roden Date: Sat, 26 Sep 2026 13:09:18 +0200 Subject: [PATCH] fix: Describe the signing key of the test container as what it is. The README said that the signing key can be used when configuring the container to sign outgoing events, which the SDK does not offer. It is the private key EventSourcingDB signs events with. Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_01VVZx93wLHrp5dyCWKjUAfd --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 14485ae..30bfdab 100644 --- a/README.md +++ b/README.md @@ -663,7 +663,7 @@ signing_key = container.get_signing_key() verification_key = container.get_verification_key() ``` -The `signing_key` can be used when configuring the container to sign outgoing events. The `verification_key` can be passed to `verify_signature` when verifying events read from the database. +The `signing_key` is the private key EventSourcingDB signs events with. The `verification_key` can be passed to `verify_signature` when verifying events read from the database. #### Configuring the Client Manually