Skip to content

Commit 33a5d40

Browse files
committed
s/Atom/Cosmos/g
1 parent 2090407 commit 33a5d40

File tree

5 files changed

+216
-219
lines changed

5 files changed

+216
-219
lines changed

FAQ.md

+76-71
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,13 @@ are their own silos with no good way to interoperate except via centralized
88
exchanges, or tricks like hashlocked transactions (like the Lightning Network),
99
which have their own benefits and drawbacks.
1010

11-
- **How does Atom do sharding?**
11+
- **How does Cosmos do sharding?**
1212

13-
Atom implements sharding using zones. It's a sharding solution that preserves
13+
Cosmos implements sharding using zones. It's a sharding solution that preserves
1414
the sovereignty of the shard as a self-governing and self-validating system.
15-
The Atom Hub doesn't care about the internal state of an Atom zone -- rather,
16-
all that matters to the Atom Hub is what the zone explicitly communicates to the
17-
Atom Hub via IBC packets.
15+
The Cosmos Hub doesn't care about the internal state of an Cosmos zone --
16+
rather, all that matters to the Cosmos Hub is what the zone explicitly
17+
communicates to the Cosmos Hub via IBC packets.
1818

1919
- **What's an IBC packet?**
2020

@@ -33,71 +33,75 @@ this data) can verify its integrity.
3333

3434
- **Isn't this just sidechains, like what Blockstream proposed?**
3535

36-
Yes. Exactly. Except in Atom, the hubs and zones are all powered by Tendermint
36+
Yes. Exactly. Except in Cosmos, the hubs and zones are all powered by Tendermint
3737
consensus. IBC on Tendermint is great because of all the reasons why
3838
light-client payment verification is great as compared to proof-of-work --
3939
superior speed, no need to download all the block headers, 1-block finality, and
40-
security via collateral. So Atom is a bit like Blockstream's sidechains
41-
proposal, except with the Atom Hub at the center instead of Bitcoin, which makes
42-
everything faster and simpler, and arguably more secure. Also the fact that the
43-
Atom Hub is a multiasset blockchain is a big advantage.
40+
security via collateral. So Cosmos is a bit like Blockstream's sidechains
41+
proposal, except with the Cosmos Hub at the center instead of Bitcoin, which
42+
makes everything faster and simpler, and arguably more secure. Also the fact
43+
that the Cosmos Hub is a multiasset blockchain is a big advantage.
4444

4545

46-
- **How does Atom compare to Ethereum sharding?**
46+
- **How does Cosmos compare to Ethereum sharding?**
4747

4848
Vitalik is working on sharding solutions for Ethereum, but the solutions I've
4949
seen assume that all the shards are running the same VM. The biggest difference
50-
between what Vitalik's latest sharding design and Atom is that the Atom Hub lets
51-
you plug in any zone, even for entirely different VMs or zones with no VMs at
52-
all (like Bitcoind). This works because the Atom Hub is about preserving the
53-
total number of tokens across zones/shards, whereas Vitalik's scaling solution
54-
is about sharding the general Ethereum state machine state. The zones of the
55-
Atom Hub don't care that other zones fail or crash, as long as the Atom Hub
56-
continues to function and preserves the total number of tokens across all the
57-
zones. Vitalik is trying to create a sharding solution where none of the shards
58-
may fail, because the internal state of those shards can mean anything at all.
59-
Vitalik is trying to solve a much more difficult problem. If we do our job
60-
right, we will be able to implement whatever he comes up within Atom.
50+
between what Vitalik's latest sharding design and Cosmos is that the Cosmos Hub
51+
lets you plug in any zone, even for entirely different VMs or zones with no VMs
52+
at all (like Bitcoind). This works because the Cosmos Hub is about preserving
53+
the total number of tokens across zones/shards, whereas Vitalik's scaling
54+
solution is about sharding the general Ethereum state machine state. The zones
55+
of the Cosmos Hub don't care that other zones fail or crash, as long as the
56+
Cosmos Hub continues to function and preserves the total number of tokens across
57+
all the zones. Vitalik is trying to create a sharding solution where none of
58+
the shards may fail, because the internal state of those shards can mean
59+
anything at all. Vitalik is trying to solve a much more difficult problem. If
60+
we do our job right, we will be able to implement whatever he comes up within
61+
Cosmos.
6162

6263
- **Why are shards called zones?**
6364

64-
Shards are called zones in Atom because they really are like sovereign economic
65-
zones. We've seen a taste of blockchain governance with the Ethereum hard-fork
66-
following TheDAO hack. In Atom, all zones are sovereign and can construct their
67-
own governance policies, and yet they can all interoperate on the Atom Hub.
68-
That's the benefit of the IBC abstraction, that it's about accountable and
69-
cryptographicaly verifiable communication.
65+
Shards are called zones in Cosmos because they really are like sovereign
66+
economic zones. We've seen a taste of blockchain governance with the Ethereum
67+
hard-fork following TheDAO hack. In Cosmos, all zones are sovereign and can
68+
construct their own governance policies, and yet they can all interoperate on
69+
the Cosmos Hub. That's the benefit of the IBC abstraction, that it's about
70+
accountable and cryptographicaly verifiable communication.
7071

7172
- **How does one exchange currencies in this system?**
7273

73-
For tokens outside the Atom system, they can only be introduced via pegged
74+
For tokens outside the Cosmos system, they can only be introduced via pegged
7475
derivatives (akin to what Blockstream's sidechains paper was suggesting). I
7576
suppose you could also use other means to track the value of some token inside
76-
the Atom network by involving prediction markets or betting, but I'm not an
77+
the Cosmos network by involving prediction markets or betting, but I'm not an
7778
expert on those. They can be supported too by other zones, but I won't go into
7879
them here.
7980

80-
In the Atom Hub, pegs will be tied to a specific zone; that is, a zone and its
81+
In the Cosmos Hub, pegs will be tied to a specific zone; that is, a zone and its
8182
validator sets are expected to also be involved in a m-of-n contract on the
82-
target chain, like Bitcoin or Ethereum.
83+
target chain, like Bitcoin or Ethereum.
8384

84-
``` _ peg smart contract / [ Ethereum ] <--> [ EtherAtom Peg Zone ] <-IBC-> [
85-
Atom Hub ] <-IBC-> (Bitcoin) [ PoW/Casper ] [ Tendermint ]
86-
[ Tendermint ] <-IBC-> (exchang) ```
85+
```
86+
_ peg smart contract
87+
/
88+
[ Ethereum ] <--> [ EtherCosmos Peg Zone ] <-IBC-> [ Cosmos Hub ] <-IBC-> (Bitcoin) [ PoW/Casper ]
89+
[ Tendermint ] [ Tendermint ] <-IBC-> (exchange)
90+
```
8791

8892
Once the tokens are in the hub, its must easier to exchange currencies. Either
89-
trade with another account directly in the Atom Hub (a Send transaction with two
90-
inputs and two outputs, with 2 different assets, swapped). But this requires
91-
both parties to the trade to be online. Instead, you can send your tokens to an
92-
exchange zone, to take advantage of an order-book.
93+
trade with another account directly in the Cosmos Hub (a Send transaction with
94+
two inputs and two outputs, with 2 different assets, swapped). But this
95+
requires both parties to the trade to be online. Instead, you can send your
96+
tokens to an exchange zone, to take advantage of an order-book.
9397

94-
- **So can I trade BTC for ETH using Atom?**
98+
- **So can I trade BTC for ETH using Cosmos?**
9599

96100
You can, if you trust the respective Ethereum and Bitcoin peg zones. If
97101
alternatives of Ethereum and Bitcoin (ie. same codebase, different network)
98-
launch on Atom, you can trade those directly.
102+
launch on Cosmos, you can trade those directly.
99103

100-
- **Does Atom involve escrow?**
104+
- **Does Cosmos involve escrow?**
101105

102106
Not really, though the hub may be thought of as an escrow agent mediating
103107
between two zones, but that's of course the point. However, the pegs in
@@ -112,19 +116,19 @@ of the zone, as well as the client. Ideally there will be a standard
112116
specification for constructing a transaction to move funds from one zone to
113117
another. So an EVM zone should be implemented such that it can process this
114118
universal transaction format that lets any simple user account send funds to
115-
another zone via the Atom Hub (or any other hub). This may be something to be
119+
another zone via the Cosmos Hub (or any other hub). This may be something to be
116120
defined as an IETF or W3C specification, but it's a bit too early for that, so
117121
we should forge ahead and document the spec for everyone to see.
118122

119123
There should be some specification for defining:
120124
- the destination zone
121-
- the intermediary zones (typically the Atom Hub)
125+
- the intermediary zones (typically the Cosmos Hub)
122126
- the assets and quantity
123127
- the destination account or smart contract
124128
- any other information
125129

126130
These are specified [here](
127-
https://github.com/gnuclear/atom-whitepaper/blob/master/WHITEPAPER.md#ibcpackettx).
131+
https://github.com/cosmos/cosmos/blob/master/WHITEPAPER.md#ibcpackettx).
128132

129133
There will also be way to navigate these zones, whereby nodes or validators of a
130134
zone can publish their IP endpoints or whatnot, voluntarily. So zone discovery
@@ -138,13 +142,13 @@ safety, like "don't send money to zones you don't know".
138142

139143
We can accomodate other PoS consensus mechanisms as long as they have a very
140144
clean and consise light-client verification protocol. Or, even Tendermint might
141-
upgrade to support additional features. It will be up to the Atom Foundation
142-
and the Atom governance to decide whether to support them. It isn't necessary
145+
upgrade to support additional features. It will be up to the Cosmos Foundation
146+
and the Cosmos governance to decide whether to support them. It isn't necessary
143147
if there can be adapter zones. That's what a Bitcoin peg zone is -- an adapter
144148
zone to sit between PoW and Tendermint.
145149

146150

147-
- **What is the maximum number of nodes in Atom? Does each zone or hub have
151+
- **What is the maximum number of nodes in Cosmos? Does each zone or hub have
148152
their own nodes?**
149153

150154
Yes. Each zone has its own nodes, we don't re-use public keys (yet, though we
@@ -163,13 +167,13 @@ No. Validators for a zone only validate transactions for their zone.
163167
zone to another." Can you talk about what exactly the asymmetric transfer is?**
164168

165169
It's maybe not the best term, but we coined it to refer to the kind of
166-
inter-zone token transfer that happens in the Atom Hub. The transfer of tokens
167-
was not via any bidirectional or bilateral exchange mechanism, or even through a
168-
peg. It's as if the token moved from one zone to another. The trick is that
169-
there is a common crypto "depository" -- the Atom Hub.
170+
inter-zone token transfer that happens in the Cosmos Hub. The transfer of
171+
tokens was not via any bidirectional or bilateral exchange mechanism, or even
172+
through a peg. It's as if the token moved from one zone to another. The trick
173+
is that there is a common crypto "depository" -- the Cosmos Hub.
170174

171175

172-
- **According to the whitepaper: "Atom reflects this position in that it makes
176+
- **According to the whitepaper: "Cosmos reflects this position in that it makes
173177
no distinction between hubs - there is no "top" hub, and the most popular or
174178
successful hub is a matter of adoption by zones. " In your view what will make
175179
hubs more successful and what will make them unsuccessful?**
@@ -185,11 +189,11 @@ partners), etc. One could also imagine a much slower, but more distributed
185189

186190
If a validator misbehaves on its own by double-signing at the same height &amp;
187191
round, then the evidence is very short and simple -- it's just the two
188-
conflicting votes. This evidence can be included in the the AtomHub as a Slash
189-
transaction, and the validator will immediately become inactive and slashed
190-
after the Slash transaction gets committed.
192+
conflicting votes. This evidence can be included in the the CosmosHub as a
193+
Slash transaction, and the validator will immediately become inactive and
194+
slashed after the Slash transaction gets committed.
191195

192-
If there is a zone fork, either of the Atom Hub or any of the zones, the two
196+
If there is a zone fork, either of the Cosmos Hub or any of the zones, the two
193197
conflicting commits also constitute evidence. This is a much more complicated
194198
data structure. It is guaranteed to slash at least 1/3 of the validators' atoms
195199
for that zone.
@@ -233,7 +237,7 @@ The 2/3 quorum of any votes to synchronize validators, a kind of virtual clock
233237
cycle, was also inspired by DLS's paper in the later sections (after section 5).
234238

235239

236-
- **Why is Atom's governance better than any other options out there?**
240+
- **Why is Cosmos's governance better than any other options out there?**
237241

238242
One is, the stakeholders are well defined, as is the prior social contract. ETH
239243
had a hard time with the fork because they had to ask the ether holders as well
@@ -242,29 +246,30 @@ to partake in governance, so no quorum could be reached in time. Asking the
242246
miners is necessary to ensure that the hard-fork will have support, but after a
243247
while they tend to simply follow the money and incentives.
244248

245-
Atom is different because instead of anonymous miners we have social contract
249+
Cosmos is different because instead of anonymous miners we have social contract
246250
bound validators and delegators who have stake, and, they have the obligation to
247251
partake in governance.
248252

249253
- **What use cases do you think are most compelling in the future?**
250254

251-
Atom allows everyone to benefit from the network effect of various interoperable
252-
tokens and zones. For example, if anyone creates a peg zone or a new token
253-
type, all the other zones can use them if they support the new token type.
255+
Cosmos allows everyone to benefit from the network effect of various
256+
interoperable tokens and zones. For example, if anyone creates a peg zone or a
257+
new token type, all the other zones can use them if they support the new token
258+
type.
254259

255-
So, the Atom Hub has a particular use-case that isn't filled by anything today.
256-
The best use-case for Atom Zones are for any token-based blockchain that benefit
257-
from the new interoperability, speed, and scalability properties. It may be a
258-
kind of distributed exchange.
260+
So, the Cosmos Hub has a particular use-case that isn't filled by anything
261+
today. The best use-case for Cosmos Zones are for any token-based blockchain
262+
that benefit from the new interoperability, speed, and scalability properties.
263+
It may be a kind of distributed exchange.
259264

260-
- **Do you feel Atom and Interledger are complimentary or are you directly
265+
- **Do you feel Cosmos and Interledger are complimentary or are you directly
261266
competing with it?**
262267

263268
They're more complementary than competing. For one, Interledger will be very
264-
useful for creating Atom zones that interface with the traditional financial
269+
useful for creating Cosmos zones that interface with the traditional financial
265270
system.
266271

267272
Interledger can also be used directly between blockchain zones. For this
268-
use-case, the Atom Hub may be a competitive option, as compared to other options
269-
for Interledger notary sets. The Atom Hub validators could also offer their
270-
services as an Interledger notary set.
273+
use-case, the Cosmos Hub may be a competitive option, as compared to other
274+
options for Interledger notary sets. The Cosmos Hub validators could also offer
275+
their services as an Interledger notary set.

OBJECTIVES.md

+8-8
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
1-
# Atom Foundation Objectives
1+
# Cosmos Foundation Objectives
22

3-
- Design and maintain the free & open-source Atom Network protocol and specifications, an architecture for an upgraded global financial system
3+
- Design and maintain the free & open-source Cosmos Network protocol and specifications, an architecture for an upgraded global financial system
44

5-
- Develop an open-source implementation of the core components of the Atom Network
5+
- Develop an open-source implementation of the core components of the Cosmos Network
66

7-
- Release the first live instance of the Atom Hub
7+
- Release the first live instance of the Cosmos Hub
88

9-
- Distribute the tokens associated with the Atom Hub via a crowdfunding event, and oversee management of the raised funds for fulfilling the other objectives
9+
- Distribute the tokens associated with the Cosmos Hub via a crowdfunding event, and oversee management of the raised funds for fulfilling the other objectives
1010

1111
- R&D in the field of cryptoeconomics; the intersection of cryptography, distributed consensus, and economics
1212

13-
- Education and outreach to increase global adoption of the Atom Network by individuals and organizations
13+
- Education and outreach to increase global adoption of the Cosmos Network by individuals and organizations
1414

15-
- Hold community driven events to discuss and motivate research and development in the Atom ecosystem
15+
- Hold community driven events to discuss and motivate research and development in the Cosmos ecosystem
1616

17-
- Encourage alternatives to the Atom Hub and competition within the Atom Network
17+
- Encourage alternatives to the Cosmos Hub and competition within the Cosmos Network
1818

1919

0 commit comments

Comments
 (0)