Skip to content

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

Merged
dslovinsky merged 2 commits into
mainfrom
bot/daikon-specs-update
Sep 8, 2026
Merged

docs(specs): update OpenRPC specifications from Daikon [Bot]#1613
dslovinsky merged 2 commits into
mainfrom
bot/daikon-specs-update

Conversation

@gha-alchemyplatform-temporal

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

1 chain created or updated:

  • Arc

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.

@gha-alchemyplatform-temporal
gha-alchemyplatform-temporal Bot requested a review from a team as a code owner September 8, 2026 16:00
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown

🔗 Preview Mode

Name Status Preview Updated (UTC)
Alchemy Docs ✅ Ready 🔗 Visit Preview Sep 8, 2026, 5:06 PM

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

Copy link
Copy Markdown

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: 7350749be5

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

Comment thread src/openrpc/chains/arc/arc.yaml
The Daikon spec update PR added a `$ref` for `arc_getCertificate` in `src/openrpc/chains/arc/arc.yaml` but no matching entry exists in `_components/custom/methods.yaml`. This commit adds the definition so the reference resolves and the method renders under Arc's API reference.

Sourced from:
- circlefin/arc-node `crates/types/src/commit_http.rs` (`HttpCommitCertificate` struct: `height` u64, `round` i64, `block_hash` ValueId, `signatures` Vec<{address, base64 signature}>)
- circlefin/arc-node `crates/evm-node/src/rpc/openapi/openapi.yaml` (error mapping: -32004 Certificate not found, -32602 Invalid params)
- Live call against arc-testnet.g.alchemy.com/v2 confirming the wire shape and error semantics.

The height parameter accepts both a decimal integer (`7`) and a hex-encoded quantity string (`"0x7"`), matching the Arc v0.7.x CHANGELOG note.

Refs Daikon PR #1613

Requested-by: @dslovinsky
@alchemy-bot

Copy link
Copy Markdown
Contributor

Added the missing arc_getCertificate definition in _components/custom/methods.yaml on this branch: c4db709.

arc_getCertificate is a real method on Arc's custom arc JSON-RPC namespace, exposed by the Malachite BFT consensus layer per Circle's arc-node docs. Schema derived from the HttpCommitCertificate Rust struct and cross-checked with a live call against arc-testnet.g.alchemy.com/v2.

The example response value was captured from that same live call so the Try It default matches the actual server behavior.

Not adding arc_getVersion — it returns Unsupported method: arc_getVersion on ARC_TESTNET against Alchemy's Arc endpoint, so Daikon's omission is correct.

@dslovinsky
dslovinsky merged commit 3f66f36 into main Sep 8, 2026
15 checks passed
@dslovinsky
dslovinsky deleted the bot/daikon-specs-update branch September 8, 2026 17:08
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