|mistakia ff83f34a7e fix: telemetry import ephemeral port bug||1 month ago|
|api||1 month ago|
|build||1 month ago|
|common||1 month ago|
|db||1 month ago|
|docs||1 month ago|
|importer||3 months ago|
|internals/webpack||2 months ago|
|resources||1 month ago|
|scripts||1 month ago|
|server||1 month ago|
|src||1 month ago|
|tags||1 month ago|
|.eslintrc.js||1 month ago|
|.gitignore||2 months ago|
|.prettierignore||3 months ago|
|.prettierrc.js||3 months ago|
|CONTRIBUTING.md||2 months ago|
|LICENSE||2 months ago|
|README.md||2 months ago|
|babel.config.js||2 months ago|
|config.sample.js||1 month ago|
|constants.js||1 month ago|
|ecosystem.config.js||3 months ago|
|package.json||1 month ago|
|server.js||3 months ago|
|yarn.lock||1 month ago|
Vision & Purpose
Nano.Community aims to be a portal to Nano’s growing community by maintaining docs, guides, and conventions to improve community communication & onboarding.
This project will serve as both a knowledge hub and an overlay / gateway to the greater Nano community & ecosystem.
A set of community maintained documents made up of guides and wiki-style documents helping to onboard new community members & developers.
|-- design | |-- attack-vectors.md | |-- basics.md | |-- challenges.md | |-- glossary.md | |-- roadmap.md | `-- security.md |-- getting-started-devs | |-- tutorials | | `-- overview.md | |-- documentation.md | |-- getting-started.md | |-- integrations.md | |-- protocol-reference.md | `-- running-a-node.md |-- getting-started-users | |-- storing | | |-- basics.md | | `-- setup.md | |-- acquiring.md | |-- basics.md | |-- best-practices.md | |-- privacy.md | `-- using.md |-- history | |-- community | | `-- nano-trade.md | `-- overview.md |-- introduction | |-- advantages.md | |-- basics.md | |-- how-it-works.md | |-- investment-thesis.md | |-- misconceptions.md | `-- why-it-matters.md |-- community.md |-- contributing.md |-- faqs.md |-- network.md `-- support.md
<summary>Content Aggregation & Categorization</summary>
Automatic content aggregation, indexing, categorization and chronicling.
Content can be tagged to a topic to allow for members to easily explore past discussions around a certain topic. Each topic will have a neutral, concise, and high-level summary along with supporting & opposing arguments, and links to all past comments. Topics exist to easily point new members to past conversations as new members will naturally think of things already discussed by past members.
|-- spam | |-- ledger-spam.md | | `-- minimum-account-balances.md | `-- congestion-spam.md |-- tx-prioritization | |-- dpow.md | |-- fee.md | `-- taac-pos4qos.md |-- attack-vectors.md |-- consensus.md |-- economics.md |-- finality.md |-- governance.md |-- micropayments.md |-- privacy.md |-- scalability.md |-- security.md `-- wallets.md
<summary>Nano Based Accounts & Voting</summary>
Nano.Community accounts are a generated key-pair where the public key is signed by the private key pertaining to a nano account. This will allow associating a user’s activity to an account on the nano network. The signing process will take place within a wallet (or on the commandline) and will not increase the risk/attack surface for a nano private key. This feature can be used to automate moderation of contributions as well as measuring support for or against certain proposals.
<summary>Onboarding / Contribution Guides</summary>
Community conventions will set forth best practices on how to format/structure posts across various platforms in the nano community.
<summary>Nano Improvement Proposals (i.e. RFC)</summary>
[needs more research]
See Zach’s comments here
Nano.Community aims to be a community run project and welcomes anyone to contribute.
Start by reading the contribution guidelines.