This repository was archived by the owner on Jul 23, 2026. It is now read-only.
docs: add Chaintable security policy and contributing guide - #18
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
What
Replaces the community docs inherited from upstream with Chaintable-specific ones. Both documents follow the structure piloted and merged in Chaintable/go-ethereum#53:
1. Lead with the fork dichotomy — this repo is a fork (upstream client + the Chaintable pipeline tracer), so the first thing each document does is split the world in two:
2. "Our process" follows the shared Chaintable doc structure (Supported Versions / Reporting / Response Process / Disclosure / Scope; Getting Started / Development Workflow / Local Checks / Code Guidelines / Testing / Pull Requests / Commit Guidelines / Releases / License), adapted to this repo's toolchain, build targets, release stream, and license files.
Where the upstream copy of
CONTRIBUTING.mdlives under.github/, it is removed in the same commit: GitHub resolves community health files with.github/taking precedence over the repository root, so keeping it would shadow the new root file.Upstream's own policies are referenced by link rather than copied: security contact info (PGP keys, bounty scope) goes stale in a snapshot, the canonical upstream links are always current, and the original files remain available in git history.
Why
The inherited community files pointed all reports and contributions at upstream's process — misrouting anything about the pipeline layer, and saying nothing about where chain-level issues should go. Upstream issues follow upstream's logic; pipeline issues follow ours.
Part of the org-wide rollout across Chaintable public write-node forks.