Clarify Alchemy Signer signup sunset#1388
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
🔗 Preview Mode
|
Richard-Dang
approved these changes
Jun 16, 2026
SahilAujla
approved these changes
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Clarifies that Alchemy Signer APIs are being sunset and no longer support new user signups as of June 16, 2026.
Related Issues
None.
Changes Made
/signupendpoint deprecated and updated JWT auth docs to avoid implying wallet pregeneration is still supported.Testing
ruby -e 'require "yaml"; YAML.load_file("src/openapi/accounts/accounts.yaml"); puts "accounts.yaml parsed"'pnpm run validate:restcould not run becausenode_modulesis missing and the workspace shell is using Node 18 instead of the repo-required Node 22.pnpm run validate)