Skip to content

docs: name Zakura as a supported validator and cite the RPC spec - #6

Merged
elicbarbieri merged 1 commit into
mainfrom
docs/zakura-support
Nov 6, 2026
Merged

elicbarbieri merged 1 commit into
mainfrom
docs/zakura-support

Conversation

@zancas

@zancas zancas commented Nov 6, 2026

Copy link
Copy Markdown
Member

Fixes: no issue. Issues are disabled on this repository.

What this PR changes

The docs named Zebra as the only validator. Zingod also works with Zakura, a Zebra fork. This PR names Zakura beside Zebra in seven files.

  • README.md names Zakura in the introduction and in the quick start.
  • docs/running.md lists Zebra and Zakura in the Requirements section, with the URLs of the Zakura repository, website and image.
  • CONTRIBUTING.md, docs/example_configs/zingod.toml, packages/zingod-source/usage.md and .changeset/1-zingod-1.0.0.md name Zakura where they named Zebra alone.
  • docs/architecture.md adds zakurad to the validators that answer -32601 to checkadmission.

The RPC specification

Zingod reads a validator through the Zcash JSON-RPC interface. The Requirements section now cites the specification by its full URL: https://zcash.github.io/rpc/.

The section lists the ten methods that Zingod calls. Each method has the URL of its page in the specification. The method names come from packages/zingod-source/src/legacy_rpc.rs.

Zakura 1.8.4 lists all ten methods in two OpenRPC documents:

One limit: validator_client = "grpc"

The support covers validator_client = "legacy_rpc", which is the default.

Zakura 1.8.4 serves GetBlockRange on its indexer gRPC. Its stream carries BlockAndHeight messages. Zingod reads BlockAndHash messages. Field 1 has a different wire type in the two messages. The Validator client section tells a Zakura operator to use legacy_rpc, and it links the Zakura proto file.

A maintainer must confirm this statement. The comparison used the two proto files only. No run of the gRPC client against zakurad supports it.

Verification

  • Each cited URL answers with status 200.
  • The example config has new comment text only. Its keys and values are unchanged.
  • No test ran Zingod against zakurad for this PR. The live suite tests against zebrad 6.2.3 only, and the running guide says so.
  • The title of the 1.0.0 change file still reads "trusted Zebra validators".

🤖 Generated with Claude Code

Zingod reads a validator through the Zcash JSON-RPC interface, and Zakura
(https://github.com/zakura-core/zakura), a Zebra fork, serves that
interface. The docs named Zebra alone. They now name Zakura beside Zebra
in the README, the running guide, the contributing guide, the example
config, the zingod-source guide and the 1.0.0 change file.

The Requirements section of docs/running.md cites the specification by its
full URL, https://zcash.github.io/rpc/, and lists the ten methods Zingod
calls, each with the URL of its page. It also links the two OpenRPC
documents of Zakura 1.8.4, which list all ten methods for the authenticated
listener and for the restricted one.

The support covers validator_client = "legacy_rpc". Zakura 1.8.4's indexer
GetBlockRange streams BlockAndHeight, and Zingod's grpc client reads
BlockAndHash. The Validator client section tells a Zakura operator to use
legacy_rpc for that reason. The architecture guide adds zakurad to the
validators that answer -32601 to checkadmission.

No test ran Zingod against zakurad for this change. The live suite still
tests against zebrad 6.2.3 only, and the running guide says so.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@zancas
zancas requested a review from elicbarbieri November 6, 2026 21:34

@elicbarbieri elicbarbieri left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Looks good

@elicbarbieri
elicbarbieri merged commit 19abe48 into main Nov 6, 2026
3 checks passed
@elicbarbieri
elicbarbieri deleted the docs/zakura-support branch November 6, 2026 22:39
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