Skip to content

docs(specs): update OpenRPC specifications from Daikon [Bot]#1349

Closed
alchemy-bot wants to merge 7 commits into
mainfrom
bot/daikon-specs-update
Closed

docs(specs): update OpenRPC specifications from Daikon [Bot]#1349
alchemy-bot wants to merge 7 commits into
mainfrom
bot/daikon-specs-update

Conversation

@alchemy-bot
Copy link
Copy Markdown
Contributor

🤖 Automated update of OpenRPC specs

This PR updates JSON-RPC method references based on the latest Daikon config. See this comprehensive guide

2 chains created or updated:

  • Dogecoin
  • Robinhood Chain

This workflow run:

  • Uses references to shared components for methods
  • Creates new OpenRPC specs and updates existing ones
  • For new chains, adds them to docs navigation
  • Respects x-bot-ignore arrays to exclude specific methods from automation

Something look wrong? If you are an Alchemy employee please open a PR with changes in Daikon. If you are a member of the public please reach out to our team.

@alchemy-bot alchemy-bot requested a review from a team as a code owner June 4, 2026 15:57
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 4, 2026

🔗 Preview Mode

Name Status Preview Updated (UTC)
Alchemy Docs ✅ Ready 🔗 Visit Preview Jun 4, 2026, 3:58 PM

@dslovinsky
Copy link
Copy Markdown
Collaborator

test

@dslovinsky dslovinsky closed this Jun 4, 2026
@dslovinsky dslovinsky deleted the bot/daikon-specs-update branch June 4, 2026 15:58
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bf30391b5a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

title: Bitcoin Cash API Overview
description: Overview of available Bitcoin Cash API methods
subtitle: Comprehensive list of Bitcoin Cash JSON-RPC methods
slug: docs/bitcoin-cash/bitcoin-cash-api-overview
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Generate the Bitcoin Cash overview under bitcoincash

This publishes a second Bitcoin Cash overview at the hyphenated bitcoin-cash route, but the existing section in content/docs.yml and the current quickstart/endpoints use bitcoincash (/docs/reference/bitcoincash-api-quickstart and /docs/chains/bitcoincash/...). A repo-wide search finds the new hyphenated quickstart and endpoint targets only in this added file, so users who reach this page get 404s for every API link instead of the existing Bitcoin Cash docs.

Useful? React with 👍 / 👎.

title: Tea API Overview
description: Overview of available Tea API methods
subtitle: Comprehensive list of Tea JSON-RPC methods
slug: docs/tea/tea-api-overview
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep Tea routed to the deprecation notice

Tea is already deprecated in this docs set: content/docs.yml lists only tea-deprecation-notice.mdx for the Tea section, and content/redirects.yml redirects /docs/chains/tea/tea-api-* and /docs/reference/tea-api-quickstart to that notice. Adding this live overview reintroduces a deprecated API page whose quickstart and endpoint links immediately route users to the deprecation notice, which undermines the intended deprecation flow.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants