You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-18Lines changed: 16 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,15 @@
1
1
# Cyclone
2
2
3
-
Cyclone is a non-custodial Coin and ERC20 privacy-preserving protocol based on zkSNARKs, which is based on the implementation and trust-setup of [tornado.cash](https://tornado.cash/). It improves transaction privacy by breaking the on-chain link between the recipient and destination addresses. It uses a smart contract that accepts Coins deposits that can be withdrawn by a different address. Whenever Coins are withdrawn by the new address, there is no way to link the withdrawal to the deposit, ensuring complete privacy.
3
+
Cyclone is a multi-chain, non-custodial, privacy-preserving protocol. Cyclone applies zkSNARKs to enable transactional privacy by breaking the on-chain link between depositor and recipient addresses. It uses a smart contract that accepts coins/tokens deposits, which can be withdrawn by a different address. Whenever an asset is withdrawn from Cyclone, there is no way to link the withdrawal to the deposit for absolute privacy.
4
4
5
-
Tornado works great on Ethereum but
6
-
- The degree of privacy it provides is proportional to the anonymity set in each of its pools, the size of which are stagnated, unfortunately;
7
-
- Decentralized governance is missing to evolve this utility to evolve.
5
+
Cyclone's zkSNARKs is based on the trusted code and implementation of tornado.cash, which works great on Ethereum except:
6
+
- The degree of privacy it provides is proportional to the anonymity set in each of its pools, the size of which are stagnated without a properly designed incentive mechanism;
7
+
- It only supports Ethereum and no other blockchains;
8
+
- Decentralized governance is missing to evolve the protocol itself.
8
9
9
-
Cyclone is built to address these two problems, which aims to provide 100x privacy with self-evolving-ness based on the built-in crypto-economic incentives - which encourages liquidity to be added to the anonymity pool and best ideas get implemented/deployed via decentralized governance.
10
-
11
-
Cyclone is firstly launched on [IoTeX](https://iotex.io) as it is a decentralized, fast, and feature-rich blockchain with a healthy and great community!
10
+
Cyclone is built to address these problems and aims to provide enhanced economic incentives, multi-chain capability and decentralized governance via the $CYC token -- the core parts of its token economics are mint-n-burn, anonymity mining, and liquidity mining.
12
11
12
+
Cyclone is launching first on [IoTeX](https://iotex.io) as it is a fast and feature-rich blockchain with necessary ecosystem components and a healthy community. After that, Cyclone will launch on Ethereum, Polkadot and other mainstream public blockchains. $CYC will be the unified token for all instances of Cyclone Protocol.
13
13
14
14
15
15
## Why it is privacy-preserving?
@@ -27,22 +27,20 @@ You can read more about [tornado-cash](https://tornado.cash/)'s medium article a
27
27
28
28
## How $CYC works?
29
29
$CYC is the token used to incentivize participants (liquidity providers for anonymity and trading as well as community participants) into Cyclone.
30
-
- Total supply of $CYC is unlimited
31
-
-**Anonymity mining**
32
-
-- For each deposit of Coin or ERC20 to the anonymity pool, N $CYC is minted to the sender
33
-
-- For each withdraws of Coin or ERC20 from the anonymity pool, M $CYC needs to be sent to the contract and burned
34
-
-**Liquidity mining** - Coin-CYC pool tokens from mimo can be staked to mine a total of 1000 Coin per day
35
-
-**Decentralized governance** to continuously tune the token economics, grow anonymity pools, add new assets, and go beyond.
30
+
- Total supply of $CYC is limited by the max num of deposits for each pools
31
+
- Initial Supply: 2,021 for the community
32
+
- Mint-n-Burn
33
+
- Everyone can mint CYC tokens if deposits coins/tokens to anonymity pools
34
+
- CYC tokens are burned when one withdraws coins/tokens from anonymity pools
35
+
- Anonymity Mining: Coins/tokens are rewarded to ones who deposit coins/tokens into anonymity pools and keep them there for a while
36
+
- Liquidity Mining: CYC is rewarded to users who provides liquidity for CYC on DEX (Decentralized Exchanges) such as mimo
37
+
- Decentralized Governance will be enforced after launch, CYC will be used to govern the Cyclone Protocol.
36
38
37
39
## Fair and safe launch
38
-
We advocate "fair launch" meaning no $CYC tokens were pre-mined or pre-allocated, and this asset was not given a valuation. To activate the community and bootstrap the liquidity [mimo](https://mimo.finance), 50,000 $CYC tokens are minted during the launch where 40,000 $CYC tokens are sent to [mimo](https://mimo.finance) for AMM and 10,000 tokens are airdropped to the IoTeX community!
40
+
We advocate "fair launch" meaning **no $CYC tokens were pre-mined or pre-allocated**, and this asset was not given an initial valuation. To activate the community and bootstrap the liquidity [mimo](https://mimo.finance), 2,021 $CYC tokens are minted during the launch and are airdropped to the community!
39
41
40
42
We value "safe launch" too - therefore, we use the exact zkSNARKs part from Tornado's [implementation](https://github.com/tornadocash/tornado-core/releases/tag/v2.1) which has been [audited](https://tornado.cash/Tornado_circuit_audit.pdf) by [authorities](https://tornado.cash/Tornado_solidity_audit.pdf). In addition, we directly use the result from Tornado's `Trusted Setup MPC` which is [successful](https://ceremony.tornado.cash/) and running [great](https://medium.com/@tornado.cash/the-biggest-trusted-setup-ceremony-in-the-world-3c6ab9c8fffa#43d9) on [Ethereum](https://medium.com/@tornado.cash/tornado-cash-trusted-setup-ceremony-b846e1e00be1).
41
43
42
-
## Development
43
-
44
-
Please read DEV.md for the detailed development guide.
0 commit comments