Use release 0.2.0 (#30)

xmtp · Feb 19, 2025 · 6c0cbc8 · 6c0cbc8
1 parent 579a3c5
commit 6c0cbc8
Show file tree

Hide file tree

Showing 3 changed files with 7 additions and 7 deletions.
diff --git a/helm/README.md b/helm/README.md
@@ -152,7 +152,6 @@ env:
   secret:
     XMTPD_DB_WRITER_CONNECTION_STRING: "postgres://<username>:<password>@<host-service>:<port>/<database>?sslmode=disable"
     XMTPD_SIGNER_PRIVATE_KEY: "<private-key>"
-    XMTPD_PAYER_PRIVATE_KEY: "<private-key>"
     XMTPD_CONTRACTS_RPC_URL: "https://xmtp-testnet.g.alchemy.com/v2/<apikey>"
     XMTPD_MLS_VALIDATION_GRPC_ADDRESS: "http://mls-validation-service.default.svc.cluster.local:50051"
     XMTPD_CONTRACTS_CHAIN_ID: "241320161"
@@ -215,8 +214,9 @@ The payer service does not depend on the XMTPD service, a database, or the MLS s
 It does require access to the public internet to read state from the blockchain.
 It also requires write access to all known XMTP nodes in the cluster.
 
-As of XMTPD docker image v0.1.1, all services require the same configuration options even though some might be unused.
-As such, you can reuse the same config that we described in [Step 4](#Step-4-Install-the-xmtpd-node).
+You can use the config defined in [Step 4](#Step-4-Install-the-xmtpd-node) as a starting point.
+Set `XMTPD_PAYER_PRIVATE_KEY` to a key to a wallet that has been funded and can be used to pay for
+blockchain messages and XMTP system messages.
 
 Install the helm chart
 ```bash

diff --git a/helm/xmtp-payer/Chart.yaml b/helm/xmtp-payer/Chart.yaml
@@ -4,5 +4,5 @@ description: A Helm chart for XMTP Payer
 type: application
 maintainers:
   - name: XMTPD
-version: 0.1.0
-appVersion: "v0.1.3"
+version: 0.2.0
+appVersion: "v0.2.0"
diff --git a/helm/xmtpd/Chart.yaml b/helm/xmtpd/Chart.yaml
@@ -4,5 +4,5 @@ description: A Helm chart for XMTPD
 type: application
 maintainers:
   - name: XMTPD
-version: 0.1.0
-appVersion: "v0.1.3"
+version: 0.2.0
+appVersion: "v0.2.0"