**Project Name:** Redot**Description:** Polkadot Re-Staking Layer.**Milestones:** A total of 3 milestones, currently applying for the 1st milestone**Total Amount:** 45,200 USD (DOT 6655.868)*converted to DOT at ema7 price: 6.791 USD/DOT as of January 31, 2024***ETD:** 10 to 12 weeks## Its Use1. **Allows Polkadot to have 1,000 parallel chains in another way.**2. **Makes Bitcoin L2 and Ethereum L2 dependent on Polkadot.**## Brief Description1. Redot is a re-staking layer for Polkadot.2. Redot is neutral, allowing for the addition of different types of tasks.3. We initially support the data availability layer and neutrally support various data availability networks.4. Validators only need to run a light client, making better use of the idle resources of validators.5. Redot is designed to approximate the security level of the Polkadot consensus layer.6. Essentially, Redot is an adapter for the Polkadot consensus layer, endowing it with various capabilities.7. Capabilities:8. Securely and inexpensively synchronize data availability to other L1s.9. Data availability persistence, enabling Inscription, Bitcoin L2 to support smart contracts 1. Bringing an alternative mechanism to Polkadot outside the parachain model, using DOT as Gas    10. Parachains securely acquire DA capabilities.11. Introducing innovative use cases of other models.12. Generating additional income for validators.A common analogy: We can understand the DA layer as a computer's memory, Polkadot as the CPU, and Redot as the motherboard connecting them.## BackgroundWhile Rollup technology claims to inherit L1 security, the truth is otherwise, with issues arising in how the DA layer is used.Optimistic Rollups need to ensure data availability, otherwise malicious nodes by hiding data render fraud proofs effectively moot. ZkRollups also require data availability for robustness. Especially in the Bitcoin ecosystem, Rollups, due to limitations of Bitcoin Script and even with ZK, still need interactive fraud proofs.However, Bitcoin lacks DA capability, and Ethereum lacks the ability to verify third-party DA layers. Rollup projects introduce data availability to L1 via bridges, but then the security of the Rollup depends on the bridge, not inheriting L1, losing its core advantage.Is there an absolutely secure way to use the DA layer? Imagine if Polkadot could securely ensure data availability, then synchronize it to other L1s via a BEEFY-based cross-chain mechanism. In terms of market value, validator size, technology, and history, Polkadot's security is far superior to other bridges, offering a strong guarantee.We come to the core issue, Polkadot's relay chain lacks DA capability and sampling ability. It should not possess these capabilities but should focus more on consensus layer security.### References1. Celestia uses Blobstream to synchronize data availability, essentially a small-scale validator bridge. [Celestia Blobstream Orchestrator](<https://docs.celestia.org/nodes/blobstream-orchestrator>)2. Avail uses various bridges, essentially requiring trust in Avail's validators.

hello

Problem Statement:
- Lack of transparency and accountability in decision-making processes within the Polkadot ecosystem.

Significance:
- This problem affects the entire Polkadot community and hinders the growth and development of the ecosystem.

Proposed Solution:
- Create a platform called Polkassembly that allows community members to discuss and vote on proposals, increasing transparency and accountability.

Expected Outcomes:
- Increased community engagement and participation in decision-making processes, leading to better governance and decision outcomes.

#1 hello

No Active Proposals