xmtp

Come build the most secure and private messaging network in the world—owned by the people who build it and use it.

Trying to assess if my bot (which uses @xmtp/xmtp-js v12.1.0) is ready for the XMTP v3 upgrade. I see there's a v13.0.4 update available, but I *also* see that there's a new @xmtp/node-sdk that seems to be a successor - but *that* library is also in alpha and described as unstable.

How do I know if my bot is ready for V3? It sounds like it'll be blocked from the network Q2 of this year if it's not?

@jrh3k5.ethh - thank you for this question. xmtp-node is now in beta and ready for you to build in production. APIs may change based on feedback. 🫡  If you have any other questions as you upgrade to V3, please feel free to open an issue in the relevant repo. For example: https://github.com/xmtp/xmtp-js/issues. If helpful, here are more details about the XMTP V2 deprecation plan:

* higher rank in Tae Kwon Do than Vladimir Putin
* hobbies include finding new lows of dad jokes
* opinions are my own and I will DMCA anyone who copies them

@jrh3k5.ethh - thank you for this question. xmtp-node is now in beta and ready for you to build in production. APIs may change based on feedback. 🫡  If you have any other questions as you upgrade to V3, please feel free to open an issue in the relevant repo. For example: https://github.com/xmtp/xmtp-js/issues. If helpful, here are more details about the XMTP V2 deprecation plan: https://community.xmtp.org/t/xip-53-xmtp-v2-deprecation-plan/867

Is there a timeline of when the new APIs will be stable? Trying to minimize the amount of work for a hobby project to convert.

Yep! We're very close -- targeting March 1.