Skip to content

Commit dd0744b

Browse files
authored
Add alchemy step to helm along with correct contracts (#26)
1 parent b1d5514 commit dd0744b

File tree

1 file changed

+14
-6
lines changed

1 file changed

+14
-6
lines changed

helm/README.md

Lines changed: 14 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,14 @@ To add the XMTPD charts to your local helm repository, clone this repository loc
1313

1414
Eventually XMTP will provide a public Helm Charts release.
1515

16+
## 0) Alchemy Account
17+
18+
To run a node, you will need to have an [Alchemy Account](https://www.alchemy.com/).
19+
You can follow their docs on the [API Key Creation](https://docs.alchemy.com/docs/alchemy-quickstart-guide#1key-create-an-alchemy-api-key).
20+
21+
Once logged in, you can find and enable the [XMTP Chain](https://dashboard.alchemy.com/chains/xmtp).
22+
Find and copy the XMTP app HTTP endpoint along with its API key. It should be in the format `https://xmtp-testnet.g.alchemy.com/v2/<apikey>`
23+
1624
## 1) Dependencies
1725

1826
XMTPD needs a Postgres database to be running accessible from the cluster.
@@ -44,12 +52,12 @@ env:
4452
XMTPD_DB_WRITER_CONNECTION_STRING: "<postgres://postgres:[email protected]:5432/postgres?sslmode=disable>"
4553
XMTPD_SIGNER_PRIVATE_KEY: "<private-key>"
4654
XMTPD_PAYER_PRIVATE_KEY: "<private-key>"
47-
XMTPD_CONTRACTS_RPC_URL: "<https://rpc-testnet-staging-88dqtxdinc.t.conduit.xyz/>"
55+
XMTPD_CONTRACTS_RPC_URL: "https://xmtp-testnet.g.alchemy.com/v2/<apikey>"
4856
XMTPD_MLS_VALIDATION_GRPC_ADDRESS: "<http://mls-validation-service.default.svc.cluster.local:50051>"
49-
XMTPD_CONTRACTS_CHAIN_ID: "34498"
50-
XMTPD_CONTRACTS_NODES_ADDRESS: "<nodes-address>"
51-
XMTPD_CONTRACTS_MESSAGES_ADDRESS: "<messages-address>"
52-
XMTPD_CONTRACTS_IDENTITY_UPDATES_ADDRESS: "<identity-address>"
57+
XMTPD_CONTRACTS_CHAIN_ID: "241320161"
58+
XMTPD_CONTRACTS_NODES_ADDRESS: "<0x390D339A6C0Aa432876B5C898b16287Cacde2A0A>"
59+
XMTPD_CONTRACTS_MESSAGES_ADDRESS: "<0x162f2d4d96565437F47bfB7a0BF8AC4FF481Bbf6>"
60+
XMTPD_CONTRACTS_IDENTITY_UPDATES_ADDRESS: "<0x00e92e15AB0D7d3aA5c76bceCcE675DcAf311189>"
5361
XMTPD_METRICS_ENABLE: "true"
5462
XMTPD_REFLECTION_ENABLE: "true"
5563
XMTPD_LOG_LEVEL: "debug"
@@ -139,4 +147,4 @@ ingress:
139147
secretName: <tls-certs>
140148
```
141149

142-
For a comprehensive guide on how to terminate TLS in GKE, you can read our [GKE+Let'Encrypt+NGINX Howto](../doc/nginx-cert-gke.md)
150+
For a comprehensive guide on how to terminate TLS in GKE, you can read our [GKE+Let'Encrypt+NGINX Howto](../doc/nginx-cert-gke.md)

0 commit comments

Comments
 (0)