diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index caff4e2..67b9427 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -11,7 +11,7 @@ rewrites. ## Choose the right path - Ask usage and architecture questions in - [GitHub Discussions](https://github.com/orgs/ipicoin/discussions). + [GitHub Discussions](https://github.com/ipicoin/.github/discussions). - Report a reproducible bug in the repository where it occurs. - Suggest a bounded enhancement with the feature request template. - Use an [IPI Improvement Proposal](ipi/README.md) for protocol behavior, diff --git a/MAINTAINERS.md b/MAINTAINERS.md index 1213173..7f22f7f 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -61,6 +61,6 @@ team permissions are the authoritative record. Each active repository should add a public maintainer section or CODEOWNERS file once at least two responsible reviewers have accepted the role. -General coordination: [GitHub Discussions](https://github.com/orgs/ipicoin/discussions) +General coordination: [GitHub Discussions](https://github.com/ipicoin/.github/discussions) Private security or access concern: [hello@ipi.io](mailto:hello@ipi.io) diff --git a/SUPPORT.md b/SUPPORT.md index 0fba59a..6dfd9be 100644 --- a/SUPPORT.md +++ b/SUPPORT.md @@ -8,7 +8,7 @@ support agreement. | Need | Channel | | --- | --- | -| Usage or architecture question | [GitHub Discussions](https://github.com/orgs/ipicoin/discussions) | +| Usage or architecture question | [GitHub Discussions](https://github.com/ipicoin/.github/discussions) | | Reproducible software defect | Issue in the affected repository | | Protocol or governance change | [IPI Improvement Proposal](ipi/README.md) | | Security vulnerability | Private process in [SECURITY.md](SECURITY.md) | diff --git a/ipi/IPI-0000.md b/ipi/IPI-0000.md index 0a22760..c90d1f7 100644 --- a/ipi/IPI-0000.md +++ b/ipi/IPI-0000.md @@ -3,7 +3,7 @@ ipi: 0000 title: IPI Improvement Proposal Process description: Lifecycle and editorial requirements for IPI protocol and governance proposals author: IPI contributors -discussions-to: https://github.com/orgs/ipicoin/discussions +discussions-to: https://github.com/ipicoin/.github/discussions status: Active (bootstrap) type: Process created: 2026-07-15 diff --git a/ipi/IPI-0001.md b/ipi/IPI-0001.md index f5a9ce4..4df0698 100644 --- a/ipi/IPI-0001.md +++ b/ipi/IPI-0001.md @@ -3,7 +3,7 @@ ipi: 0001 title: Verifiable Independence description: Evidence model for systems that claim to be independently operable and verifiable author: IPI contributors -discussions-to: https://github.com/orgs/ipicoin/discussions +discussions-to: https://github.com/ipicoin/.github/discussions status: Draft type: Standards Track / Core created: 2026-07-15 diff --git a/ipi/README.md b/ipi/README.md index 4e27c5c..ac543f2 100644 --- a/ipi/README.md +++ b/ipi/README.md @@ -38,7 +38,7 @@ accepted proposal. ## Contributing a proposal 1. Start a focused - [GitHub Discussion](https://github.com/orgs/ipicoin/discussions) describing + [GitHub Discussion](https://github.com/ipicoin/.github/discussions) describing the problem, constraints, and alternatives. 2. Establish that an IPI is the right level of change and identify affected maintainers. diff --git a/profile/README.md b/profile/README.md index c96d844..191ce94 100644 --- a/profile/README.md +++ b/profile/README.md @@ -67,7 +67,7 @@ The first specification of this model is - Propose a protocol change through the [IPI process](/ipicoin/.github/tree/main/ipi). - Join an architectural or product conversation in - [GitHub Discussions](https://github.com/orgs/ipicoin/discussions). + [GitHub Discussions](https://github.com/ipicoin/.github/discussions). - Find issues marked [good first issue](https://github.com/search?q=org%3Aipicoin+label%3A%22good+first+issue%22+is%3Aopen&type=issues) or [help wanted](https://github.com/search?q=org%3Aipicoin+label%3A%22help+wanted%22+is%3Aopen&type=issues). @@ -98,7 +98,7 @@ operate independently. Architecture and governance changes are discussed before they are standardized. [Website](https://ipi.io) · -[Discussions](https://github.com/orgs/ipicoin/discussions) · +[Discussions](https://github.com/ipicoin/.github/discussions) · [Governance](/ipicoin/.github/blob/main/GOVERNANCE.md) · [IPI proposals](/ipicoin/.github/tree/main/ipi) · [Licensing](/ipicoin/.github/blob/main/LICENSING.md) · diff --git a/statements/TERMS_OF_SALES.md b/statements/TERMS_OF_SALES.md index 7db87de..9c1415f 100644 --- a/statements/TERMS_OF_SALES.md +++ b/statements/TERMS_OF_SALES.md @@ -11,7 +11,12 @@ IPI Coin is issued and managed by IPI.IO LLC, located at Suite 100, Erie, PA 165 #### 3. Nature of IPI Coin -IPI Coin is a cryptocurrency native to the IPI blockchain, utilizing a Proof of Network consensus mechanism. It is designed for high scalability, supporting unlimited transactions per second (TPS) and WASM-based smart contracts, enabling development in multiple programming languages. +At the time this historical document was drafted, IPI Coin was described as a +cryptocurrency for a proposed IPI blockchain with WebAssembly smart-contract +support. This preserved description is not evidence of a current network, +consensus implementation, throughput level, legal status, or production +service. Current technical claims require reproducible public evidence and a +reviewed specification. #### 4. Coin Supply and Distribution @@ -65,4 +70,4 @@ IPI.IO LLC reserves the right to update or modify these Terms at any time. Chang For questions or support regarding IPI Coin, please contact IPI.IO LLC using the contact form on the official website. -These Terms are based on the information provided on the official IPI Coin website. For the most current and detailed terms, always refer to the latest documentation and official announcements from IPI.IO LLC. \ No newline at end of file +These Terms are based on the information provided on the official IPI Coin website. For the most current and detailed terms, always refer to the latest documentation and official announcements from IPI.IO LLC.