This is a temporary document designed to provide a collection of initiatives of the early stages of AtomOne. Its purpose is multi-fold:
- Index of Activities: Catalog ongoing issues, discussions, and key themes as the project develops.
- Accessible Reference: Act as a central, accessible point of reference for all users.
- Initiative Tracking: Offer a simple framework for tracking and updating initiatives.
| Issue | Issue Creator | Summary |
|---|---|---|
| #7: Decentralists Party and AtomOne Hub Governance | jaekwon | Discussion on distinct governance for the Decentralists party and AtomOne hub. Suggestions for limiting Decentralists' control. |
| #8: Defining "Foster Diversity and Alignment" | moul | Need for a clear definition of fostering diversity and alignment. Emphasis on open dialogue among competing groups. |
| #10: Money as Tokenized Trust | irreverentsimplicity | Money as a medium of social cooperation and trust. Concept of soft forks and trust as primary value in monetary systems. |
| #12: ATOM vs ATONE Integration & Genesis Distribution | jaekwon | Strategic approach to integration and distribution between ATOM and ATONE. Models for effective integration. |
| #13: Include stATOM Holders in ATONE | asalzmann | Proposal to include stATOM holders in ATONE genesis or airdrop. Discussion on the treatment of stATOM holders. |
| #16: Fix Cosmos Hub Failures | COverS8 | Addressing centralization of voting power in Cosmos Hub. Proposal for snapshot and distribution for AtomOne airdrop. |
| #14: Brand Identity and Twitter Handle | wnmnsr | Discussion on the brand identity and @_atomone Twitter handle. Proposal for a new symbol representative of an atom. |
| #17: Choosing the Genesis Software Target | moul | Discussion on starting with Tendermint 2 or forking from Cosmos Hub 4. Trade-offs between early start and required work. |
| #18: Choose Snapshot Attributes | moul | Debate on specific block for snapshot. Consideration of other proposals beyond proposal 848. |
| #19: Fix Cosmos Ecosystem Power Dynamics | andergri | Reducing political complexities and promoting inclusivity in the Cosmos Ecosystem. Proposal of a primary chain to support all teams. |
| #20: Official Cosmos ATOM-ONE NFT | COverS8 | Proposal for an official AtomOne NFT at genesis. Discussion on its potential as a community-building tool. |
| #21: ATOM-ONE Secure Communications for Users | COverS8 | Need for secure communication alternatives to Telegram and Discord. Proposal for a secure app for official governance communications. |
| #22: Link with Tendermint Atom One | moul | Questions about the connection between the AtomOne repository and Tendermint Atom One. Suggestions for a constitution and clarity on PHOTON design. |
| #23: Issues/PRs Moderation | moul | Challenge of selecting a responsible party for moderation. Proposal of an operations committee for moderation decisions. |
| #24: Setup Weekly Report | moul | Idea of initiating a weekly report. Use tools like ChatGPT to compile the list, with human intervention for fine-tuning. |
| #25: Should AiB Hire Dedicated Resources for Atomone? | moul | Proposal to create a job for overseeing AtomOne at AiB. Its role is to facilitate progress and act as a bridge between the community and AiB. |
| #26: Decentralists and Governance Structure | moul | Discussion on the role of Decentralists in AtomOne. Emphasis on defining their influence and control within the project's governance. |
| #27: Establishing and Monitoring Conditions for ICS | moul | Hardcoded conditions for becoming an ICS consumer. Discussion on governance approval, dApp virtualization, and financial commitments. |
| #29: Use GitHub Projects as a "Layer" System | moul | Proposal for using GitHub Projects for issue categorization. Suggesting Kanban-style labels and category tags. |
| #30: Create an Open Member List | moul | Establishing a list for interested contributors. Focusing on transparency and public engagement. |
| #31: Efficient Governance | qvuv05 | Discussing inflation rate reduction in ATOM and alternative governance models. |
| #32: Community Pool Financial Model | cryptulien | Proposing new funding approaches for the Community Pool. The suggestion of a linear financing model. |
| #33: Airdrops and Unstaking Emotional Impact | MasterFrenchie | Addressing emotional distress from halving, supporting creators, and considering KYC for distribution. |
| #36: Understand AtomOne | caillom | Metaphorical discussion to understand AtomOne's vision. A parallel is drawn between stranded community managing resources and AtomOne's governance. |
| #39: Limit AI/ChatGPT from AtomOne Core | jaekwon | Debate on the role and limitations of AI in AtomOne. Discussion on potential risks and benefits of AI integration in blockchain technology. |
| #40: Governance & Community Pool Thoughts | clockworkgr | Discussions on improving governance and community pool design in AtomOne. Suggestions include separating staking and governance and overhauling community pool funding. |
| #41: $PHOTON Token Design | giunatale | Delving into the design and functionality of the $PHOTON token. Topics include governance rights, auto-staking mechanisms, and tokenomics. |
Issue #7 discusses the governance structures of the Decentralists party and the AtomOne hub.
- Distinction between Decentralists (democratic) and AtomOne (proof-of-stake).
- Decentralist involvement requires on-chain worth, not just token ownership.
- Proposals to cap Decentralists' control in AtomOne for balanced governance.
- Discussions about linking voting power to token ownership and stake duration.
- Suggestion for strict voting conditions and specialized Decentralist roles.
Issue #31 discusses the need for effective governance in AtomOne, using the example of proposal #848.
- Impact of proposal #848 on inflation and staking.
- Need for informed governance and alternative models.
Issue #39 proposes restricting AI, like ChatGPT, in AtomOne core.
- Concerns about AI in blockchain and limiting its use.
- Community feedback and voting on AI restrictions.
- Proposals for limited AI use and perspectives on AI use.
- AI as a tool vs. AGI as a potential threat.
Issue #40 discusses the improvement of governance and community pool design for AtomOne.
- Adopting Decentralists' DAO governance suggestions, separating stakeholder and governance.
- Proposal for stakers to delegate voting on proposals, potentially using a specific module.
- Introduction of a tagging system for proposals in different domains like marketing or architecture.
- Community pool overhaul suggestions, including limits on funding per proposal and denominating proposals in fiat equivalent.
- Gradual release of funds for proposals, with possible rescinding based on future approval.
Issue #10 explores money as tokenized trust, examining its role in social cooperation and value perception.
- Money aligns varied perceptions of value, transitioning from a mental concept to a material, tokenized form.
- Tokenization simplifies value perceptions, facilitating social exchanges.
- Material representation of money can influence value perception.
- Collective trust in money's tokenized form impacts its value and community trust.
- Discussions include soft forking in financial ecosystems and trust's role in governance.
Issue #12 aims to address integrating ATOM and ATONE, focusing on distribution and slashing mechanisms for ATONE.
- Slashing in ATONE is necessary to enhance security decision-making intelligence.
- Debates on penalizing or rewarding ATOM holders based on proposal voting.
- Various methods for ATONE distribution and integration are considered.
- Trust and governance vulnerability in tokenized money reliance.
Issue #13 considers including stATOM holders in the ATONE genesis file or airdrop.
- Potential inclusion of stATOM holders in ATONE genesis or airdrop.
- Debate on the treatment of stATOM holders about governance participation.
- Distribution methods for ATONE to stATOM holders.
Issue #32 addresses the management of the Community Pool funds in the Cosmos ecosystem.
- Problems with current Community Pool management.
- Proposed focus areas for preserving and expanding the Community Pool.
- Governance and decision-making suggestions.
- Tax and reward structure considerations.
Issue #41 delves into the design and functionality of the $PHOTON token system.
- Discussion on PHOTON not providing governance rights, except for specific PHOTON-related proposals.
- Auto-staking of underlying ATONEs linked to PHOTON and challenges in rebalancing voting power.
- Proposal for a tax mechanism on auto-staked ATONEs and auto-compounding of underlying assets.
- The total supply cap for PHOTON is set at 1 Billion, with specific conversion formulae for bonding and unbonding.
- Examination of bonding dynamics, including incentives and impacts of slashing events.
- Need for defining a practical redemption mechanism for PHOTON, considering various dynamics of the dual-token model.
Issue #16 aims to adopt successful elements from the Cosmos Hub and address its shortcomings for AtomOne.
- Centralized voting power issues in the Cosmos Hub.
- Proposals for staking limits and validator identity disclosure.
- Assessment of validators' voting history in Cosmos Hub for AtomOne selection.
- Proposal for maximum staking limits with a single validator.
- Proposal for evaluating validators based on their voting history.
- Approach to airdrop mechanism, potentially excluding participants against AtomOne's vision.
- Learning from Cosmos Hub's tokenomics.
- Proposal for a community-driven treasury oversight committee.
Issue #17 discusses the initial software choice for AtomOne.
- Starting with Tendermint 2 (tm2) requires additional development.
- Starting with a Cosmos Hub 4 Fork allows for an early start but involves complex migration to tm2.
Issue #18 focuses on selecting the appropriate block for a snapshot in AtomOne.
- Debate on using specific blocks for the snapshot.
- Consideration of other proposals in snapshot attribute determination.
Link with Tendermint AtomOne Repository
Issue #22 seeks to clarify the relationship between AtomOne Hub's GitHub repository and the Tendermint repository.
- Discussion on the relationship between AtomOne Hub's and Tendermint's repositories.
- Need for a constitution and clarity on PHOTON design.
Issue #26 explores AtomOne's potential role as an ICS consumer.
- Debate on AtomOne being an ICS consumer.
- Alternatives and security considerations for ICS consumer status.
Issue #27 explores hardcoded conditions for AtomOne becoming an ICS consumer.
- Proposal for specific, hardcoded conditions for ICS consumers.
- Governance approval and virtualization of dApps discussed.
Issue #28 focuses on incorporating security standards into proposal evaluations for AtomOne.
- Proposals to include verifiable security standards, potentially marked by a 'security coverage' badge.
- Risk, security, and financial score integration for robust proposal assessment.
- Community-led review and feedback mechanism for proposals, with support for specialized security groups.
- Emphasis on balanced decision-making, combining strict security measures with adaptability for urgent proposals.
Issue #14 focuses on developing AtomOne's brand identity and Twitter handle (@_atomone).
- Proposal for AtomOne’s brand identity and Twitter handle reservation.
- Move towards natural element motifs, focusing on the Hydrogen molecule.
- Significance of Hydrogen in symbolizing fundamental properties.
- Design proposals with community feedback and development suggestions.
Issue #21 highlights the need for secure communication alternatives for AtomOne users.
- Need for end-to-end encrypted communication channels.
- An official, secure app or platform for governance communication is proposed.
Issue #19 addresses the power dynamics within the Cosmos Ecosystem.
- Need for a primary chain supporting all entities in Cosmos, reducing political complexity.
- Proposal for an inclusive and equitable ecosystem.
Issue #33 focuses on supporting users who unstaked ATOM due to recent proposals.
- Support for creators and Atom1 supporters who left the network.
- Concerns about governance direction and proposals.
- Challenges and solutions for rewarding supporters.
- Rewarding contributors and creators within the AtomOne ecosystem.
Issue #20 explores creating an official AtomOne NFT.
- NFT as recognition for early AtomOne project supporters.
- Potential future benefits and use cases for the NFT.
Issue #8 clarifies "fostering diversity and alignment" within the AtomOne and Decentralists framework. It emphasizes creating an ecosystem supporting diversity through self-aligned groups while maintaining alignment through shared values and goals.
- Diversity promotes competing and innovative ideas; alignment focuses on shared core values and principles.
- Distinction is needed between diversity in experimentation and alignment with the project’s constitution and principles.
- Clarity is essential in defining these concepts to prevent biased judgments and conflicting priorities.
Issue #30 discusses creating an open member list for AtomOne.
- Setting up a list of interested contributors.
- Mechanism for organization and participation.
- Proposed method for member listing.
- Importance of transparency and public engagement.
Issue #36 presents a metaphorical narrative to understand AtomOne.
- AtomOne compared to essential water and its inflation to a water source.
- Authority and regulation by the Decentralists.
- Inflation and tokenized trust implications.
- Alternative analogies and sustaining inflation.
Issue #23 discusses effective moderation of issues and PRs in AtomOne's GitHub repository.
- Debate on who should lead in moderating the GitHub repository.
- Proposed structures for moderation and the use of tools like ChatGPT.
Issue #24 proposes creating a weekly report for the AtomOne project.
- The report summarizes recent changes and assists in moderation.
- Methodology for report compilation with AI tools and human intervention.
Issue #25 discusses hiring a dedicated individual for AtomOne project management at AiB.
- Creating a position for overseeing the AtomOne project within AiB.
- Emphasis on transparency and community involvement.
Issue #29 discusses using GitHub Projects for categorizing issues in AtomOne.
- Categorization and labelling system proposals.
- Permission is required to create projects or assign issues.
- Suggestions for category tags and maintenance.