FAQ

This is the documentation FAQ. Topic-specific questions belong on the relevant page so users and AI retrievers find answers in context.

How do I search the docs?

Use the site search first. For exact technical strings, search the repository with rg from the docs root:

rg "setpqhdpolicy" content

For node behavior, search the Core repository as well:

rg "setpqhdpolicy" ../tidecoin

Which Tidecoin Core version do these docs target?

These docs target the current Tidecoin Core v1.x / Bitcoin Core v30-based code line unless a page says otherwise. Consensus status pages, release notes, and activation pages should be checked before making operational decisions.

How do I suggest a correction?

Open a docs issue or pull request in the docs repository. Include:

• the page URL or file path;
• the incorrect text;
• the corrected text;
• the source that supports the correction.

For source-backed technical changes, prefer links to the Tidecoin Core source, whitepaper, release notes, or primary standards.

Why is some content not in this FAQ?

Because most answers should live where the user needs them. Examples:

Why do some pages cite source paths?

The docs often point to repo-relative source paths such as ../tidecoin/src/kernel/chainparams.cpp. That keeps technical claims auditable without hardcoding a local absolute path.

What should not be changed casually?

Do not casually change:

• activation status;
• chain parameters;
• signature sizes and scheme prefixes;
• address prefixes and HRPs;
• RPC names and argument order;
• release status;
• wallet availability claims.

Those facts must stay source-backed.

See also: Glossary, Introduction, Developers / Contributing.