Skip to content

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

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

docs(specs): update OpenRPC specifications from Daikon [Bot]#1350
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 16:14
@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, 4:15 PM

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: cb1d18e00f

ℹ️ 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".

| [`zks_getTestnetPaymaster`](/docs/chains/zksync/zk-sync-api-endpoints/zks-get-testnet-paymaster) | [`zks_getTransactionDetails`](/docs/chains/zksync/zk-sync-api-endpoints/zks-get-transaction-details) |
| [`zks_L1BatchNumber`](/docs/chains/zksync/zk-sync-api-endpoints/zks-l-1-batch-number) | [`zks_L1ChainId`](/docs/chains/zksync/zk-sync-api-endpoints/zks-l-1-chain-id) |
| [`zks_sendRawTransactionWithDetailedOutput`](/docs/chains/zksync/zk-sync-api-endpoints/zks-send-raw-transaction-with-detailed-output) | |
| [`eth_accounts`](/docs/chains/zksync/z-ksync-api-endpoints/eth-accounts) | [`eth_blockNumber`](/docs/chains/zksync/z-ksync-api-endpoints/eth-block-number) |
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 Restore the canonical ZKsync endpoint slug

For users clicking the ZKsync overview links, these URLs now point at /docs/chains/zksync/z-ksync-api-endpoints/..., but the repo’s existing ZKsync redirects and legacy destinations still normalize the misspelled z-ksync-api-endpoints only under /docs/node/zksync to the canonical zk-sync-api-endpoints path (content/redirects.yml:1898), not under /docs/chains/zksync. This leaves the overview linking to the unredirected/generated-wrong chain path instead of the working zk-sync-api-endpoints pages.

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 Remove the active Tea API overview

In contexts where users reach the new /docs/tea/tea-api-overview slug directly, this page advertises active Tea methods even though the existing Tea deprecation notice says Alchemy has discontinued Tea support and the endpoint redirects send Tea API traffic to that notice. Because the current deprecation redirects only cover /docs/chains/tea/... and /docs/reference/tea-api-quickstart, this newly introduced slug re-exposes stale active-network docs instead of the deprecation notice.

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.

1 participant