-
Notifications
You must be signed in to change notification settings - Fork 39
Add agent configuration guide #451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite. This stack of pull requests is managed by Graphite. Learn more about stacking. |
2137234 to
4549720
Compare
4549720 to
4e9d3df
Compare
b159e7c to
4f8fc9b
Compare
4e9d3df to
9a8eb0f
Compare
9a8eb0f to
a2e048f
Compare
| 1. An agent built using our Node or Agent SDK | ||
| 2. A payer wallet that has been [funded through the XMTP Funding Portal](./fund-your-app.mdx) | ||
|
|
||
| ## Setup your Signer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| ## Setup your Signer | |
| ## Setup your Payer Wallet |
|
|
||
| ## Setup your Signer | ||
|
|
||
| When you create a client, you already specify a `Signer` that is used to link your XMTP identity to a wallet. You can choose to use the same `Signer` to pay for messages, or create a new one purely for this purpose. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| When you create a client, you already specify a `Signer` that is used to link your XMTP identity to a wallet. You can choose to use the same `Signer` to pay for messages, or create a new one purely for this purpose. | |
| When you create a client, you already specify a `Signer` that is used to link your XMTP identity to a wallet. You can choose to use the same `Signer` as your payer wallet, or create a new one purely for this purpose. In either case, it must be the same wallet you [funded through the XMTP Funding Portal](./fund-your-app.mdx) |
|
|
||
| When you create a client, you already specify a `Signer` that is used to link your XMTP identity to a wallet. You can choose to use the same `Signer` to pay for messages, or create a new one purely for this purpose. | ||
|
|
||
| This Signer must be of type `eoa`. The `messagePayer` may not be a smart contract wallet, since the signatures need to be able to be verified offchain. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| This Signer must be of type `eoa`. The `messagePayer` may not be a smart contract wallet, since the signatures need to be able to be verified offchain. | |
| This Signer must be of type `eoa`. The `messagePayer` may not be a smart contract wallet, since the signatures need to be able to be verified offchain. | |
| :::info | |
| You can fund your payer wallet from a smart contract wallet [using the XMTP Funding Portal](./fund-your-app.mdx). | |
| ::: |

Add XMTP agent configuration guide to document how to configure an agent to pay for messages in configure-agent.mdx
Add a new documentation page that outlines XMTP agent setup for message payments, including signer and payer requirements, RPC configuration, and a TypeScript example using
Agent.create.messagePayerAgent.createwithsigner,rpcUrls.xmtp,dbEncryptionKey,env, andmessagePayerin configure-agent.mdx📍Where to Start
Start with the new documentation content in configure-agent.mdx, focusing on the
Agent.createexample and the signer andmessagePayerrequirements section.📊 Macroscope summarized a2e048f. 0 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted
🗂️ Filtered Issues
No issues evaluated.
<!-- MACROSCOPE_FOOTER_END -->\<!-- Macroscope's pull request summary ends here -->