Radiant Enhancement Proposals (REPs) are design documents providing information to the Radiant community, or describing a new feature for Radiant or its processes or environment. REPs are the primary mechanism for proposing major new features, collecting community input on issues, and documenting design decisions.
| REP | Title | Author | Status | Type |
|---|---|---|---|---|
| 1 | DNS Seeder Infrastructure for Network Discovery | Radiant Core Contributors | 📝 Draft | Standard |
| 2 | PSRT Client-Side Order Expiration | Radiant Core Contributors | 📝 Draft | Standard |
| 3 | Asynchronous JSON-RPC Server | Radiant Core Contributors | 📝 Draft | Standard |
| 4 | P2P Encryption (BIP324) Implementation | Radiant Core Contributors | 📝 Draft | Standard |
| 5 | OP_CHECKTEMPLATEVERIFY (CTV) Implementation | Radiant Core Contributors | 📝 Draft | Standard |
| 1001 | Radiant Architecture Overview | Radiant Core Contributors | 📝 Draft | Informational |
| 1002 | Radiant Security Best Practices | Radiant Core Contributors | 📝 Draft | Informational |
| 2001 | REP Process Definition | Radiant Core Contributors | 🔄 Active | Process |
Legend: 📝 Draft | 🔄 Active | ✅ Final | ❌ Rejected | 🚫 Withdrawn
- REP-2001 - REP Process Definition (start here)
- REP Template - Template for creating new REPs
- Active REPs - Currently under consideration
- Final REPs - Accepted and implemented
- All REPs - Complete list by category
Protocol changes that affect most or all Radiant implementations:
- Consensus rule changes
- P2P network protocol changes
- New opcodes or transaction types
- Block validation changes
- RPC interface changes
Design issues, guidelines, and informational content:
- Architecture overviews
- Security best practices
- Mining guidelines
- Wallet integration standards
Process changes and governance:
- REP process changes
- Release processes
- Security disclosure processes
- Governance guidelines
- 📝 Draft: Initial proposal, being discussed
- 🔄 Active: Under consideration, implementation may begin
- ✅ Final: Accepted and implemented
- ❌ Rejected: Considered and rejected
- 🚫 Withdrawn: Author withdrew the proposal
| REP | Title | Author | Status | Description |
|---|---|---|---|---|
| 1 | DNS Seeder Infrastructure for Network Discovery | Radiant Core Contributors [email protected] | 📝 Draft | Implements DNS-based peer discovery to improve network resilience and reduce reliance on hard-coded seed nodes |
| 2 | PSRT Client-Side Order Expiration | Radiant Core Contributors [email protected] | 📝 Draft | Adds optional max_age filtering to PSRT RPC methods to reduce stale order clutter and improve swap protocol efficiency |
| 3 | Asynchronous JSON-RPC Server | Radiant Core Contributors [email protected] | 📝 Draft | Refactors JSON-RPC server for async processing to improve throughput and enable concurrent request handling |
| 4 | P2P Encryption (BIP324) Implementation | Radiant Core Contributors [email protected] | 📝 Draft | Implements BIP324 encrypted P2P transport to enhance network privacy and security against surveillance |
| 5 | OP_CHECKTEMPLATEVERIFY (CTV) Implementation | Radiant Core Contributors [email protected] | 📝 Draft | Implements BIP119 CTV opcode to enable trustless transaction covenants for vaults, congestion control, and batched payments |
| REP | Title | Author | Status | Description |
|---|---|---|---|---|
| 1001 | Radiant Architecture Overview | Radiant Core Contributors [email protected] | 📝 Draft | Comprehensive overview of Radiant blockchain architecture, components, and design principles for developers and researchers |
| 1002 | Radiant Security Best Practices | Radiant Core Contributors [email protected] | 📝 Draft | Security guidelines for node operators, developers, and users covering operational security, development practices, and user protection |
| REP | Title | Author | Status | Description |
|---|---|---|---|---|
| 2001 | REP Process Definition | Radiant Core Contributors [email protected] | 🔄 Active | Defines the REP process, format, and guidelines for submitting and managing Radiant Enhancement Proposals |
- Discuss First: Talk about your idea on community channels
- Use Template: Copy rep-template.md
- Create PR: Submit as a pull request to this repository
- Community Review: Participate in the review process
- Implementation: Develop reference implementation (for Standard Track)
- Discussions: GitHub Discussions
- Issues: GitHub Issues
- Core Repository: Radiant-Core/Radiant-Core
REP/
├── README.md # This file
├── REP-2001.md # REP Process Definition
├── rep-template.md # Template for new REPs
├── active/ # Active REPs
├── final/ # Final REPs
├── rejected/ # Rejected REPs
├── withdrawn/ # Withdrawn REPs
└── draft/ # Draft REPs (PRs)
All REPs are licensed under the MIT License unless otherwise specified in the individual REP.
Inspired by Bitcoin Improvement Proposals (BIPs), Ethereum Improvement Proposals (EIPs), and Python Enhancement Proposals (PEPs).