> ## Documentation Index
> Fetch the complete documentation index at: https://docs.notareum.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Community

# Community

Notareum is built in the open. Every repository, discussion, and protocol decision is public. This page lists the channels where contributors, integrators, validator operators, and end users coordinate.

## Channels

| Channel     | Link                                                       | Purpose                                    |
| ----------- | ---------------------------------------------------------- | ------------------------------------------ |
| GitHub      | [https://github.com/notareum](https://github.com/notareum) | Code, issues, pull requests, releases      |
| Discord     | [https://discord.gg/notareum](https://discord.gg/notareum) | Real-time contributor and operator chat    |
| X (Twitter) | [https://x.com/notareum](https://x.com/notareum)           | Protocol announcements                     |
| Forum       | [https://forum.notareum.org](https://forum.notareum.org)   | Long-form discussion, governance proposals |
| Mirror blog | [https://notareum.mirror.xyz](https://notareum.mirror.xyz) | Engineering and research posts             |

## GitHub

The GitHub organization hosts every protocol repository:

* `protocol`: versioned protocol specification.
* `contracts`: Solidity smart contracts, Hardhat config, deployment scripts.
* `notareum-ts-sdk`: TypeScript SDK (`@notareum/sdk`).
* `notareum-py-sdk`: Python SDK (`notareum`).
* `notareum-rs-sdk`: Rust SDK (crate `notareum`).
* `dapp`: Reference dApp (Next.js, wagmi v2).
* `whitepaper`: LaTeX whitepaper sources.
* `docs`: Documentation site (this content).
* `brand-assets`: Official logos, colors, templates.
* `audits`: Published audit reports.

Every repository welcomes issues and pull requests. Maintainers triage weekly.

### Filing a good issue

1. Check for existing issues first.
2. Include the SDK version, network, and relevant addresses.
3. Provide a minimal reproduction (code snippet or failing test).
4. For contract issues, include the transaction hash and decoded revert reason where available.
5. For SDK issues, include the full error object and stack trace.

### Opening a pull request

1. Discuss non-trivial changes in an issue first.
2. Branch from `main`; target `main` for the PR.
3. Follow the repository's code style (enforced by pre-commit hooks).
4. Add tests for new behavior; maintain the existing test count floor per SDK.
5. Update the changelog under the `Unreleased` section.
6. Link related issues and reviewers.

See each repository's `CONTRIBUTING.md` for project-specific details.

## Discord

The Discord server is the primary real-time venue. Channels are grouped by focus area:

* `#general`: project-wide discussion.
* `#dev-typescript`, `#dev-python`, `#dev-rust`: per-SDK help.
* `#dev-contracts`: smart contract development.
* `#validator-operators`: validator node operation and tuning.
* `#integrations`: wallet, exchange, and dapp integration Q\&A.
* `#governance`: proposal discussion and coordination.
* `#support`: user-facing questions.

Moderation is community-driven with a small rotating moderator group. The Code of Conduct below applies in all channels.

## Forum

The forum (`forum.notareum.org`) hosts long-form technical proposals, governance discussion, and retrospectives. Before submitting an on-chain governance proposal, drafts go through the forum for community review.

Forum categories:

* **Governance proposals**: drafts and active proposals.
* **Protocol design**: spec-level discussion (schema, canonical serialization, attestation primitives).
* **Economics**: fee, reward, and slashing parameter analysis.
* **Integrations**: integration retrospectives and best practices.
* **Research**: cryptographic and adversarial research.

Forum accounts are free and do not require a wallet connection, though linking a wallet is supported for vote-weight visibility.

## Governance

Governance lives on-chain via veNOTA voting through `NotareumGovernor`, with `AccessManager` timelocks enforcing delays. Process:

1. Draft the proposal on the forum.
2. Gather feedback for at least the minimum review window (typically 7 days).
3. Submit on-chain via the `Governor` contract.
4. Voting window runs for the configured period.
5. On success, the operation is scheduled in `AccessManager`.
6. After the delay elapses, anyone can execute the scheduled operation.

See [AccessManager](../smart-contracts/access-manager.md) for role and delay details.

## Validator operator community

Validators coordinate in `#validator-operators` on Discord and in the forum's validator category. Typical activity:

* Shared monitoring dashboards (Grafana, Prometheus configs).
* Node version coordination and upgrade scheduling.
* Reference configurations for running a validator node across cloud providers.
* Incident post-mortems and performance tuning.

Validator economics, tier progression, and slashing risk are covered in [ValidatorStaking](../smart-contracts/validator-staking.md) and [SlashingManager](../smart-contracts/slashing-manager.md).

### Validator onboarding checklist

1. Read [ValidatorStaking](../smart-contracts/validator-staking.md) end-to-end.
2. Acquire at least 10,000 NOTA.
3. Stand up a node following the operator guide (tracked at `contracts/ops`).
4. Stake via `ValidatorStaking.stake`.
5. Join `#validator-operators` and share your validator address.
6. Verify live attestation flow on testnet before committing mainnet stake.

## Code of Conduct

All channels operate under a shared Code of Conduct aligned with Contributor Covenant v2.1. Summary:

* Be respectful. Disagreement is welcome; personal attacks are not.
* No harassment, discrimination, or hate speech.
* Keep discussion on-topic. Spam and off-topic promotion are grounds for removal.
* No private solicitation of community members for undisclosed paid work.
* Report violations to `conduct@notareum.org` or to any Discord moderator.

Enforcement actions range from a warning, to temporary timeout, to permanent ban. Decisions are reviewed by the moderator group; appeals go to `conduct@notareum.org`.

Full Code of Conduct text: `github.com/notareum/.github/blob/main/CODE_OF_CONDUCT.md`.

## Contribution pathways

Ways to contribute beyond code:

* **Documentation.** Fix typos, clarify guides, add examples. This docs site is the `docs` repository.
* **Translations.** Translate the introduction and core docs into additional languages.
* **Tooling.** Build explorer plugins, wallet integrations, IDE extensions.
* **Research.** Publish analysis, attack scenarios, economic simulations on the forum.
* **Education.** Write tutorials, record videos, speak at meetups.
* **Validator operation.** Run a validator node, help others stand theirs up.
* **Governance.** Participate in proposals, even if only by voting.

## Staying up to date

* Follow `@notareum` on X for protocol announcements.
* Subscribe to the Mirror blog for engineering and research posts.
* Watch the `docs` and `contracts` repositories on GitHub for release notifications.
* Join Discord and opt into the `#announcements` role for zero-noise updates.

## Related pages

* [Whitepaper](whitepaper.md)
* [Security Disclosure](security-disclosure.md)
* [Brand Assets](brand-assets.md)
* [Changelog](../reference/changelog.md)