feat: add privy server wallet provider by azf20 · Pull Request #242 · coinbase/agentkit

azf20 · 2025-02-02T13:44:27Z

What changed? Why?

Introduces a Privy Server Wallet Provider (extending EvmWalletProvider), extending the viem provider using @privy-io/server-auth (which has a createViemAccount method)
Follows the "configureWithWallet" pattern (similar to the cdp provider)
Wallet ID is required
Supports optional authorization private key

Qualified Impact

This is an incremental provider, however it does add @privy-io/server-auth as a dependency. An initial implementation was made using the REST API to minimize dependencies, but adding support for authorization keys and full transaction sending / signing support introduced sufficient complexity that the trade off shifted to adding the dependency - particularly to avoid or easily mitigate breaking changes in future (on either side). However - open to discussion!

cb-heimdall · 2025-02-02T13:44:33Z

✅ Heimdall Review Status

Requirement Status More Info

Reviews

✅ 2/1

Denominator calculation

Show calculation

1 if user is bot 0

1 if user is external 0

From .codeflow.yml 1

Additional review requirements

Show calculation

Max	0

0

From CODEOWNERS 0

Global minimum 0

Max 1

1

1 if commit is unverified 0

Sum 1

John-peterson-coinbase · 2025-02-05T19:09:40Z

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

+
+    const network = {
+      protocolFamily: "evm" as const,
+      networkId: config.networkId || "84532",


network ID for base sepolia is base-sepolia

thanks, fixed!

tsconfig.base.json

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

azf20 · 2025-02-05T19:49:00Z

thanks @John-peterson-coinbase, added fixes here f49f51d, including package-lock.json (though on reflection wasn't sure about the policy there). Let me know if there is anything else!

John-peterson-coinbase · 2025-02-07T18:28:56Z

Thanks @azf20 - please rebase and sign the commits following the commit signing instructions

azf20 · 2025-02-07T20:04:03Z

thanks so much, I rebased and verified, hope that looks right!

0xRAG · 2025-02-10T23:34:58Z

Hey @azf20 I tested this locally and it's working great! As a couple final asks, could you:

Add an examples/langchain-privy-chatbot – It can be a copy/paste of examples/langchain-cdp-chatbot swapping out CdpWalletProvider for PrivyWalletProvider
Add an export_wallet function (see: here) or otherwise document the best way to save and restore a Privy wallet

Thank you!

azf20 · 2025-02-11T22:54:51Z

OK great! I rebased and added an example - I added a comment explaining that Privy server wallets are embedded & controllable via the dashboard & API. Let me know if that makes sense or if you wanted that elsewhere

typescript/examples/langchain-privy-chatbot/README.md

0xRAG · 2025-02-11T23:08:01Z

OK great! I rebased and added an example - I added a comment explaining that Privy server wallets are embedded & controllable via the dashboard & API. Let me know if that makes sense or if you wanted that elsewhere

Nice, thanks! Two things:

Let's add the new example to the workspaces entry in the root package.json. Then remove the package-lock.json from the new example
Thanks for the brief comment explaining Privy Server wallets – I think it would be nice to include it in the example README as well

0xRAG · 2025-02-11T23:13:54Z

Also, what are your thoughts on this ask:

Add an export_wallet function (see: here) or otherwise document the best way to save and restore a Privy wallet

Is this simply saving off the wallet ID, then using that to query Privy?

azf20 · 2025-02-12T00:08:05Z

Added to workspaces entry & removed package.json
Added some more notes on Privy to the README
Added an "Export" function for the Wallet Provider which returns the input configuration (App ID, Secret, Wallet ID, Auth Key if applicable) - this isn't the private key, but it's the information required to make any changes on the Privy side
Fixed commit signing

Thanks!

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

typescript/examples/langchain-privy-chatbot/chatbot.ts

azf20 · 2025-02-13T23:18:36Z

Thanks so much! Rebased + updated README and Changelog

John-peterson-coinbase · 2025-02-13T23:30:19Z

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

+  /** The ID of the wallet to use */
+  walletId?: string;
+  /** Optional network ID to connect to */
+  networkId?: string;


@0xRAG @azf20 - This config should take chainId instead of networkId . Network ID is a CDP concept and will limit the Privy implementation to only support CDP supported networks. Privy does not have the same constraints as CdpWalletProvider and therefore should take chainId which will unblock usage of all EVM.

Good call! This is done now in ba189e3

cb-heimdall · 2025-02-13T23:31:28Z

Review Error for John-peterson-coinbase @ 2025-02-13 23:31:28 UTC
User failed mfa authentication, public email is not set on your github profile. see go/mfa-help

colfax23

Wow, this is great! Thanks for doing this. I'm Colfax from the Privy team, it's nice to meet you, this was enjoyable to review.

The core change that needs to be made is around how the authorization private key + ID is handled during wallet creation. Feel free to let me know if you have any questions!

colfax23 · 2025-02-14T04:13:28Z

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

+      networkId: config.networkId || "base-sepolia",
+    };
+
+    const chain = NETWORK_ID_TO_VIEM_CHAIN[network.networkId!];


As @John-peterson-coinbase mentioned above, Privy can support any EVM chain, so you can update the config to take in a chainId (eg 84532 for base sepolia). In order to resolve the viem chain object, here is a post I've found helpful.

done, thanks for the hint!

colfax23 · 2025-02-14T04:15:17Z

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

+    const walletId =
+      config.walletId ??
+      (
+        await privy.walletApi.create({


nit: this call returns the whole wallet object (including the address), so if you shift things around a bit you can save the second network hop below to getWallet

nice yes did that too

colfax23 · 2025-02-14T04:26:46Z

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

+      (
+        await privy.walletApi.create({
+          chaintype: "ethereum",
+          authorizationKeyIds: config.authorizationKey ? [config.authorizationKey] : undefined,


This actually takes as an input an authorizationKeyId which is an ID assigned by to an authorization key when it is registered with Privy server wallets. In order to use an authorization key with a wallet, you need to pre register it with Privy. We are actually working on supporting key registration during wallet creation, but it is not implemented yet.

I can see two paths forward here:

You can implement authorization key registration with Privy before wallet creation. We don't have support for it in server-auth but we do via our REST API (docs - see REST API tab). The developer would generate the p256 private + public keypair (instructions in above docs as well) and input them both as a config, then you would send the public key to privy, and you'll get back an ID which you'd use during wallet creation. The server-auth config above correctly takes in the private key.

You can take in an authorizationKeyId in the config, however that would require the developer to register the key with Privy themselves beforehand, which isn't an ideal experience.

Thanks for that context, sorry I had missed that you need to pass IDs for creation.

I tried 1., but hit an issue where the https://api.privy.io/v1/wallets endpoint was returning a 404 - see this branch on my project repository as a test case azf20/hello-world-computer@cd61b55

So I reverted to 2, but also found that an authorization key was required on new wallet creation, not sure if that is expected? Got the following when I didn't pass in an auth key:

⨯ Error: Missing `privy-authorization-signature` header.

So I updated the error handling and docs accordingly - not an ideal experience but I think ok for now

Good catch - I'll look into this on our end and I think option 2 + pointing folks to the Privy dashboard to create their key is a good approach for now.

colfax23 · 2025-02-14T04:28:56Z

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

+  /** Optional network ID to connect to */
+  networkId?: string;
+  /** Optional authorization key for the wallet API */
+  authorizationKey?: string;


nit: consider renaming this to authorizationPrivateKey so it is clear this is the private key, not the public key or ID, also to be parallel with the Privy config

good call, done

colfax23 · 2025-02-14T04:38:08Z

typescript/examples/langchain-privy-chatbot/README.md

+  - PRIVY_APP_ID=
+  - PRIVY_APP_SECRET=
+  - PRIVY_WALLET_ID=[optional, otherwise a new wallet will be created]
+  - PRIVY_WALLET_AUTHORIZATION_KEY=[optional, only if you are using authorization keys for your server wallets]


I think it is worth specifying that this is the authorization private key

colfax23 · 2025-02-14T04:44:21Z

typescript/examples/langchain-privy-chatbot/README.md

+
+This example demonstrates an agent setup as a self-aware terminal style chatbot with a [Privy server wallet](https://docs.privy.io/guide/server-wallets/).
+
+Privy wallets are embedded wallets - learn more at https://docs.privy.io/guide/server-wallets/. The Agentkit integration assumes you have a Privy server wallet ID which you want to use for your agent - creation and management of Privy wallets can be done via the Privy dashboard or API.


consider replacing "Privy wallets are embedded wallets" with "Privy's server wallets enable you to securely provision and manage cross-chain wallets via a flexible API"

cb-heimdall · 2025-02-14T04:56:41Z

Review Error for colfax23 @ 2025-02-14 04:56:41 UTC
User must have write permissions to review

azf20 · 2025-02-14T12:07:37Z

Thanks so much for taking a look @colfax23! I fixed and tested new wallet creation, see the approach taken here: #242 (comment). I encountered some issues which might be on the Privy side, so I went ahead with an approach that worked to create new server wallets in Privy:

Also updated to take any chainId (assuming it's supported by viem), as well as some docs / naming clarifications.

Appreciate the help!

azf20 · 2025-02-14T13:12:46Z

An update: @colfax23 shared a URL which will work for wallet creation, and I go that working locally, with the slight downside that it creates a new signing key (with the same public key) on every run. Would be good to clarify expected behaviour on ⨯ Error: Missingprivy-authorization-signature header., and whether we prefer the "specify the keyId" or "dynamically create the key" approach here. Thanks!

colfax23

Looks great! Left a few minor comments, but once addressed this looks good to go from my perspective.

colfax23 · 2025-02-14T13:13:52Z

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

+   *   appId: "your-app-id",
+   *   appSecret: "your-app-secret",
+   *   walletId: "wallet-id",
+   *   networkId: "base-sepolia"


nit: update to chainId: 84532

good catch!

colfax23 · 2025-02-14T13:21:09Z

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

+   * ```
+   */
+  public static async configureWithWallet(config: PrivyWalletConfig): Promise<PrivyWalletProvider> {
+    const privy = new PrivyClient(config.appId, config.appSecret, {


There is an edge case here where the authorizationPrivateKey is provided but not authorizationKeyId which will get things into a funky state. Can you do a check to enforce that either both or neither are provided before initializing the PrivyClient?

I think it's ok to initialise with just an authorizationPrivateKey if you're using an existing wallet, not creating a key?

Ah, you're right - if the user has an existing wallet that has a key attached to it, you need to specify authorizationPrivateKey and technically don't need to specify the ID. My bad! Fine to leave as is, good catch.

colfax23 · 2025-02-14T13:22:22Z

typescript/examples/langchain-privy-chatbot/README.md

+  - PRIVY_APP_ID=
+  - PRIVY_APP_SECRET=
+  - PRIVY_WALLET_ID=[optional, otherwise a new wallet will be created]
+  - PRIVY_WALLET_AUTHORIZATION_PRIVATE_KEY=[optional, only if you are using authorization keys for your server wallets]


Can you link the key creation docs and / or point folks to the Privy dashboard to create their key + register it with Privy to get their ID?

updating README

colfax23 · 2025-02-14T13:25:22Z

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

+      (
+        await privy.walletApi.create({
+          chaintype: "ethereum",
+          authorizationKeyIds: config.authorizationKey ? [config.authorizationKey] : undefined,


Good catch - I'll look into this on our end and I think option 2 + pointing folks to the Privy dashboard to create their key is a good approach for now.

cb-heimdall · 2025-02-14T13:26:16Z

Review Error for colfax23 @ 2025-02-14 13:26:16 UTC
User must have write permissions to review

azf20 · 2025-02-14T14:11:26Z

Thanks, sounds good - updated READMEs accordingly

John-peterson-coinbase

LGTM pending a few instances of networkID -> chainID remaining, a few documentation updates, and a small change to the example.

We can land this in today's EOW release if these are resolved.

@azf20

John-peterson-coinbase · 2025-02-14T14:46:31Z

typescript/agentkit/README.md

+const config = {
+    appId: "PRIVY_APP_ID",
+    appSecret: "PRIVY_APP_SECRET",
+    networkId: "base-sepolia",


please update to chainId as previously discussed

John-peterson-coinbase · 2025-02-14T14:49:35Z

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

+ * @param id - The chain ID
+ * @returns The chain
+ */
+function getChain(id: number) {


This function should be exported from https://github.com/coinbase/agentkit/blob/main/typescript/agentkit/src/network/network.ts

John-peterson-coinbase · 2025-02-14T14:51:48Z

typescript/agentkit/README.md

+#### Exporting Privy Wallet information
+
+The `PrivyWalletProvider` can export wallet information by calling the `exportWallet` method. 
+
+```typescript
+const walletData = await walletProvider.exportWallet();
+
+// walletData will be in the following format:
+{
+    walletId: string;
+    authorizationKey: string | undefined;
+    networkId: string;
+}
+```


please update to chainId as previously discussed

Also - should this return value be a named interface to make it more clear?

Let's also add an example of instantiating a PrivyWalletProvider from the exported object.

John-peterson-coinbase · 2025-02-14T14:54:11Z

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

+  appSecret: string;
+  /** The ID of the wallet to use, if not provided a new wallet will be created */
+  walletId?: string;
+  /** Optional network ID to connect to */


Suggested change

/** Optional network ID to connect to */

/** Optional chain ID to connect to */

John-peterson-coinbase · 2025-02-14T14:56:08Z

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

+  /** The ID of the wallet to use, if not provided a new wallet will be created */
+  walletId?: string;
+  /** Optional network ID to connect to */
+  chainId?: number;


Suggested change

chainId?: number;

chainId?: string;

Update type to conform with Network interface typing.

John-peterson-coinbase · 2025-02-14T15:00:11Z

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

+    networkId?: string;
+  } {
+    return {
+      walletId: this.#walletId,
+      authorizationPrivateKey: this.#authorizationPrivateKey,
+      networkId: this.getNetwork().networkId,


Suggested change

networkId?: string;

} {

return {

walletId: this.#walletId,

authorizationPrivateKey: this.#authorizationPrivateKey,

networkId: this.getNetwork().networkId,

chainId: string;

} {

return {

walletId: this.#walletId,

authorizationPrivateKey: this.#authorizationPrivateKey,

chainId: this.getNetwork().chainId,

Update to use chain ID as previously discussed.

This should return a named interface object for clarity.

John-peterson-coinbase · 2025-02-14T15:01:08Z

typescript/examples/langchain-privy-chatbot/chatbot.ts

+    const config = {
+      appId: process.env.PRIVY_APP_ID as string,
+      appSecret: process.env.PRIVY_APP_SECRET as string,
+      networkId: process.env.NETWORK_ID || "base-sepolia",


nit: use chain ID

John-peterson-coinbase · 2025-02-14T15:01:24Z

typescript/examples/langchain-privy-chatbot/chatbot.ts

+  // Warn about optional NETWORK_ID
+  if (!process.env.NETWORK_ID) {
+    console.warn("Warning: NETWORK_ID not set, defaulting to base-sepolia testnet");
+  }


nit: use chain ID

John-peterson-coinbase · 2025-02-14T15:04:06Z

typescript/examples/langchain-privy-chatbot/chatbot.ts

+    const exportedWallet = walletProvider.exportWallet();
+    fs.writeFileSync(WALLET_DATA_FILE, JSON.stringify(exportedWallet));


If WALLET_DATA_FILE already exists, the example should read the exported wallet data from the file and instantiate the existing wallet.

updated to do this

John-peterson-coinbase · 2025-02-14T15:05:16Z

typescript/agentkit/README.md

+
+#### Authorization Keys
+
+Privy offers the option to use authorization keys to secure your server wallets. When using authorization keys, you must provide the `authorizationPrivateKey` and `authorizationKeyId` parameters to the `configureWithWallet` method.


Please hyperlink to Privy documentation on Authorization Keys given this may be a new concept to AgentKit developers.

Shuffled it around to put the link to the docs before this 👍

azf20 · 2025-02-14T15:52:53Z

thanks so much for the thorough feedback, good catches! pushed changes

0xRAG · 2025-02-14T15:59:00Z

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

+      if (!config.authorizationPrivateKey) {
+        throw new Error("authorizationPrivateKey is required when creating a new wallet");
+      }
+      if (!config.authorizationKeyId) {
+        throw new Error(
+          "authorizationKeyId is required when creating a new wallet with an authorization key, this can be found in your Privy Dashboard",
+        );


It's my understanding that an authorization key is optional when creating a Privy server wallet, so can we relax the requirement here?

That was also my understanding, though when I tested the header was required - @colfax23 can you confirm if that's only in the case where an account has set up Authorization keys (which mine had)? If so we can update to helpfully handle the resulting error, rather than blocking here

Authorization keys are not required for wallet creation unless you've created one in the dashboard and have given in the permissions Can create and modify wallets. If you've done that, we require it for all wallet creation requests.

Two pieces of feedback we're taking from this & working on:

This UX of requiring it in all cases if a key is created is not intuitive, we're working on some updates here

The error message when you try to create a wallet without specifying the key, when it is required, is not very clear (it is Missing privy-authorization-signature header.)

For the next steps, I think we can relax this constraint, and @azf20 if you can handle the error gracefully if a key is required but not present that'd be great!

Also, @azf20 when you mention in the README about creating authorization keys in the Privy dashboard, can you add a note to uncheck Can create and modify wallets to help prevent people from getting into this state by mistake like you did? That way they can create a key that is intended for wallet transaction signing purposes only.

Got it, thanks for the clarification @colfax23!

thanks both! I added a more helpful error message for that specific case + updated the README

typescript/agentkit/README.md

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts

0xRAG

Amazing work, thanks for doing this @azf20!

@colfax23 thank you as well for your review!

LGTM, @John-peterson-coinbase can you take a final pass?

🚀

John-peterson-coinbase

🚀

azf20 marked this pull request as draft February 2, 2025 15:42

azf20 marked this pull request as ready for review February 2, 2025 20:37

John-peterson-coinbase reviewed Feb 5, 2025

View reviewed changes

azf20 force-pushed the privy-wallet-provider branch from bbb3359 to fca9cf3 Compare February 7, 2025 20:02

azf20 force-pushed the privy-wallet-provider branch from fca9cf3 to 452f2b0 Compare February 7, 2025 20:35

John-peterson-coinbase added wallet provider New wallet provider triaged needs review PR / issue needs review apple labels Feb 10, 2025

0xRAG removed the triaged label Feb 10, 2025

0xRAG added changes requested PR / Issue has changes requested and removed needs review PR / issue needs review labels Feb 11, 2025

azf20 force-pushed the privy-wallet-provider branch from 452f2b0 to 6d6eb39 Compare February 11, 2025 22:53

azf20 requested a review from murrlincoln as a code owner February 11, 2025 22:53

0xRAG reviewed Feb 11, 2025

View reviewed changes

typescript/examples/langchain-privy-chatbot/README.md Outdated Show resolved Hide resolved

azf20 force-pushed the privy-wallet-provider branch from 4b584eb to 73a8080 Compare February 12, 2025 00:05

0xRAG reviewed Feb 12, 2025

View reviewed changes

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts Outdated Show resolved Hide resolved

0xRAG reviewed Feb 12, 2025

View reviewed changes

typescript/examples/langchain-privy-chatbot/chatbot.ts Outdated Show resolved Hide resolved

0xRAG added in review PR / issue is in review typescript and removed changes requested PR / Issue has changes requested labels Feb 13, 2025

azf20 added 2 commits February 13, 2025 22:22

docs: update example for optional walletId

47c6477

docs: readme and changelog

0b67c61

azf20 force-pushed the privy-wallet-provider branch from 61d7a46 to 0b67c61 Compare February 13, 2025 23:18

John-peterson-coinbase requested changes Feb 13, 2025

View reviewed changes

colfax23 suggested changes Feb 14, 2025

View reviewed changes

feat: fix wallet creation, chainId

ba189e3

docs: example

aaf356c

colfax23 approved these changes Feb 14, 2025

View reviewed changes

docs: authorization keys

cfab8cf

John-peterson-coinbase requested changes Feb 14, 2025

View reviewed changes

fix: feedback

2f4e4b3

0xRAG reviewed Feb 14, 2025

View reviewed changes

typescript/agentkit/README.md Show resolved Hide resolved

azf20 added 2 commits February 14, 2025 16:21

fix: toc

72e88b4

fix: helpful error when using auth keys

356ed23

0xRAG reviewed Feb 14, 2025

View reviewed changes

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts Outdated Show resolved Hide resolved

0xRAG reviewed Feb 14, 2025

View reviewed changes

typescript/agentkit/src/wallet-providers/privyWalletProvider.ts Show resolved Hide resolved

fix: missing privateKey, conditional keyid

4d13dd2

0xRAG requested a review from John-peterson-coinbase February 14, 2025 19:40

0xRAG approved these changes Feb 14, 2025

View reviewed changes

John-peterson-coinbase approved these changes Feb 14, 2025

View reviewed changes

0xRAG merged commit aacf2e1 into coinbase:main Feb 14, 2025
8 checks passed


		This example demonstrates an agent setup as a self-aware terminal style chatbot with a [Privy server wallet](https://docs.privy.io/guide/server-wallets/).

		Privy wallets are embedded wallets - learn more at https://docs.privy.io/guide/server-wallets/. The Agentkit integration assumes you have a Privy server wallet ID which you want to use for your agent - creation and management of Privy wallets can be done via the Privy dashboard or API.

	/** Optional network ID to connect to */
	/** Optional chain ID to connect to */

		const exportedWallet = walletProvider.exportWallet();
		fs.writeFileSync(WALLET_DATA_FILE, JSON.stringify(exportedWallet));


		#### Authorization Keys

		Privy offers the option to use authorization keys to secure your server wallets. When using authorization keys, you must provide the `authorizationPrivateKey` and `authorizationKeyId` parameters to the `configureWithWallet` method.

Conversation

azf20 commented Feb 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What changed? Why?

Qualified Impact

Uh oh!

cb-heimdall commented Feb 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Heimdall Review Status

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

azf20 commented Feb 5, 2025

Uh oh!

John-peterson-coinbase commented Feb 7, 2025

Uh oh!

azf20 commented Feb 7, 2025

Uh oh!

0xRAG commented Feb 10, 2025

Uh oh!

azf20 commented Feb 11, 2025

Uh oh!

Uh oh!

0xRAG commented Feb 11, 2025

Uh oh!

0xRAG commented Feb 11, 2025

Uh oh!

azf20 commented Feb 12, 2025

Uh oh!

Uh oh!

Uh oh!

azf20 commented Feb 13, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cb-heimdall commented Feb 13, 2025

Uh oh!

colfax23 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cb-heimdall commented Feb 14, 2025

Uh oh!

azf20 commented Feb 14, 2025

Uh oh!

azf20 commented Feb 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

colfax23 left a comment

azf20 commented Feb 2, 2025 •

edited

Loading

cb-heimdall commented Feb 2, 2025 •

edited

Loading

azf20 commented Feb 14, 2025 •

edited

Loading