Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update(readme): various enhancements #92

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions FAQs.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# FAQ

## AtomOne vs Gaia

AtomOne is designed as an alternative fork of Gaia with a distinct focus on
minimalism in its ICS & Token IBC hub. This results in a leaner, more efficient
architecture. In terms of governance, AtomOne introduces a higher consensus
threshold (Constitutional Majority) and emphasizes decentralized
decision-making. In terms of software, AtomOne will start as a fork of
"cosmoshub4".
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"cosmoshub4".
"cosmoshub-4".

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also done in other places. But the correct chain ID has a dash
https://github.com/cosmos/chain-registry/blob/master/cosmoshub/chain.json


## AtomOne vs Gno.land

Gno.land will be a hub for GnoVM based smart contracts. It may benefit from
ICS1.5 in the future, but we will first offer GnoVM scaling on the AtomOne ICS
economic zone. Gno.land will not connect to Gaia and other external chains for
the purpose of token pegging except indirectly through AtomOne, or its minimal
successor (how a hub is meant to be used).

Gno.land will run its own separate validator set but the Gno VM will be made
available for hosting on AtomOne ICS and its successors.
50 changes: 50 additions & 0 deletions MILESTONES.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
# Milestones
salmad3 marked this conversation as resolved.
Show resolved Hide resolved

There are largely four phases to this plan.

## AtomOne Phase 1: Pre-IBC

1. Define Constitution
2. Governance Fixes
3. Launch Governance-Only Chain
4. Implement IBC

## AtomOne Phase 2: Post-IBC

1. $PHOTON with Auto-Staking
2. Fix Validator Incentives
3. Implement ICS1.5
4. Prototypes with SubDAOs (including GNO)

## AtomOne Phase 3: ICS1.5 scaling

1. Migrate $PHOTON to ICS
2. Promote Smart Contract Use Cases
3. Develop Scalable Validator Infrastructure
4. Develop Recovery Procedures

## AtomOne Phase 4: Maintenance

1. Create OnChain Education Curriculum
2. Promote Good Forks and Projects
3. Promote Other Common Goods
4. Finalize the Software

Finalization should not be seen as a thing to avoid, but rather a necessity for
preserving immutability and thus providing real security benefits.

Everyone who wants something different is given a way to create their own
variation to compete and cooperate with the AtomOne hub. We should all be
familiar with this concept, as it is how AtomOne itself was born--by exodus
from Gaia.

It is possible that what we arrive at is not sufficient in the long run, and
that is still OK; the ultimate goal is to be a standard reference, in the very
least in relation to an improved fork; a reference that will last a thousand
years or more.

In short, the goal is nothing more than to create timeless code, even knowing
that in the end even AtomOne will be phased out, but never forgotten; the
template will have split into a million different forks and conquered the
world. AtomOne Eschatology will be well documented and planned, for a time when
nobody was around for these early beginnings.
Loading