Skip to content

Commit bff8d7f

Browse files
committed
Fix AC linting
1 parent eac940e commit bff8d7f

File tree

7 files changed

+27
-32
lines changed

7 files changed

+27
-32
lines changed

docs/aurora-cloud/01-welcome/01-introduction.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
# 💡 Welcome to Aurora
22

3-
**What is Aurora?**
3+
## What is Aurora?
44

55
Aurora is an **EVM** (Ethereum Virtual Machine) compatible blockchain layer 2 on top of **Near protocol**, combining the compatibility with the Ethereum ecosystem and the performance and scalability of Near.
66

7-
8-
**How is Aurora different from other Ethereum layer 2s?**
7+
## How is Aurora different from other Ethereum layer 2s?
98

109
Aurora is not a rollup or a side chain. It is implemented as a **smart contract** on the NEAR Protocol. This means that Aurora inherits most of the features from Near protocol such as:
1110

@@ -19,7 +18,7 @@ While providing ethereum compatibility:
1918
* Transaction fees (gas fees) in Aurora are paid in ETH and are constant ([gas price](https://dev.aurora.dev/posts/evm-gas-near-gas-on-aurora) is 0.07 GWei, which is around **$0.003 per transaction**).
2019
* Aurora supports all the Ethereum ecosystem tools — [MetaMask](https://metamask.io/), [Foundry](https://github.com/foundry-rs), [Truffle](https://www.trufflesuite.com/truffle), [Hardhat](https://hardhat.org/), [Remix](https://remix.ethereum.org/), etc...
2120

22-
**What are the TPS on Aurora?**
21+
## What are the TPS on Aurora?
2322

2423
Transactions Per Second is a common measure of performance for blockchains. Since Aurora inherits its characteristics from Near Protocol, the TPS are the same as on Near which are around **1k TPS.**
2524

@@ -29,14 +28,14 @@ Note that the TPS number depends a lot on the size of transactions (a simple tra
2928
* Thanks to the sharding technology of Near, TPS could go up to **100k** with the current shards
3029
* And theoretically it actually has **no limit** since sharding offers horizontal scaling
3130

32-
**What programming language do I need to know to deploy on Aurora?**
31+
## What programming language do I need to know to deploy on Aurora?
3332

3433
As an EVM compatible chain, smart contracts on Aurora are written in Solidity, exactly how it is done on Ethereum, Polygon, Arbitrum or any other EVM chain.  
3534

36-
**I already have a dapp on Polygon, can I migrate to Aurora?**
35+
## I already have a dapp on Polygon, can I migrate to Aurora?
3736

3837
Absolutely, since both chains are EVM compatible, you can simply redeploy your smart contracts on Aurora without additional development, and you will instantly benefit from the **high throughput** and **low transaction costs**.
3938

40-
**What are Virtual Chains?**
39+
## What are Virtual Chains?
4140

4241
Virtual Chains are dedicated instances of the Aurora Engine, customised to a specific application. Read more about Virtual Chains in the next section.
Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# 📄 About Virtual Chains
22

3-
#### **What are Virtual Chains?**
3+
## What are Virtual Chains?
44

55
Virtual Chains are a unique innovation from Aurora providing a **dedicated** and **customised** chain, or **appchain**. 
66

@@ -12,22 +12,18 @@ Each Virtual Chain is a copy of the **Aurora Engine** (the Aurora smart contract
1212

1313
![image5](/img/.gitbook/assets/image_(5).png)
1414

15-
#### **How are Virtual Chains different from other appchains (Arbitrum, Avalanche, Polygon) ?**
15+
## How are Virtual Chains different from other appchains (Arbitrum, Avalanche, Polygon)?
1616

1717
Usually, appchains are side chains or rollups, which are completely separate blockchains from the main settlement chain. This has several consequences:
1818

1919
* Each appchain needs to have its own **validators set**, which can be expensive to set up and run, and affects the decentralisation and security of the network. Typically, an appchain requires a minimum of 5 validators (which already comes at a cost) 
2020
* Appchains come empty, meaning the team will need to redevelop all the tools they might have wanted to use, such as onramps, oracles, indexers, etc... This involves third parties and can be extremely costly and time consuming.
2121

22-
2322
* **Instead, each Virtual Chain automatically gets all the 220 validators from Near**
2423
* Because Virtual Chains are smart contracts on Near, this allowed us to build tools and services that automatically support all new Virtual Chain, such as **onramp, centralised exchange support, Oracle**, etc... so that you don't have to start from scratch.
2524

26-
27-
**How do I get my own Virtual Chain?**
25+
## How do I get my own Virtual Chain?
2826

2927
Aurora has built a platform for this purpose: [**Aurora Cloud**](https://auroracloud.dev/).
3028

3129
Aurora Cloud proposes different plans to get your own chain, including **free transactions**, custom **professional services** and much more... in order to let you focus on **building your application**, not setting up infrastructure!
32-
33-

docs/aurora-cloud/02-run-your-own-virtual-chain/04-enable-gas-abstraction.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,14 @@ The Aurora Engine is paying gas in NEAR on the Near protocol, but inside the Vir
88

99
![frame827_3](/img/.gitbook/assets/Frame_827_(3).png)
1010

11-
**Defining the gas mechanics**
11+
## Defining the gas mechanics
1212

1313
Gas can be collected in different ways on a Virtual Chain:
1414

1515
* Usage based: This is the most common method. Gas is calculated based on the transaction size and charged in the base token of the network
1616
* Fixed fee: To simplify user interactions, gas could be charged as a fixed fee on the Virtual Chain. For instance, the base token could be $USDT and each transaction could cost 0.01 $USDT
1717

18-
**Advanced logic around free transactions**
18+
## Advanced logic around free transactions
1919

2020
Free transactions are a great way to simplify onboarding of new users or to incentivise certain behaviours. But this should not be a on or off setting, and Aurora Cloud lets you define advanced ways of attributing free transactions, so that you can use it at your advantage.
2121

docs/aurora-cloud/02-run-your-own-virtual-chain/05-on-offramp-to-your-chain.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ But onramp services can be expensive, with steep setup costs (sometimes up to $1
1414

1515
![frame827_0](/img/.gitbook/assets/Frame_827.jpg)
1616

17-
**How does it work?**
17+
## How does it work?
1818

1919
Since each Aurora Chain is a smart contract deployed on Near, they can seamlessly communicate with each other through the cross contract call technology (XCC).
2020

@@ -26,33 +26,33 @@ The result is an onramp solution that does not require technical development on
2626

2727
_Aurora partnered with Münzen to develop this solution._ [_Read more about Münzen_](https://munzen.io/ramp)
2828

29-
**Adding an onramp widget to your application**
29+
## Adding an onramp widget to your application
3030

3131
Aurora Cloud Onramp provides you with a widget that can be embedded in any application for the best user experience. The widget will open a popup powered by Münzen, and the customer will be required to go through the steps and abide by any regulatory requirements (such as passing KYC if needed).
3232

33-
**Main Benefits**
33+
## Main Benefits
3434

3535
* KYC-free transaction up to 100 EUR
3636
* 16 fiat currencies supported
3737
* Buy crypto in just two minutes
3838

39-
**What countries are supported?**
39+
## What countries are supported?
4040

4141
* Aurora Cloud Onramp supports 115 countries. The full list, including restricted countries, can be found [here](https://docs.google.com/spreadsheets/d/15geR5hByqh8XFhX6bHwq9C1g8LxH1Q1Ck0tfQEmoSzo/edit?usp=sharing). ([https://docs.google.com/spreadsheets/d/15geR5hByqh8XFhX6bHwq9C1g8LxH1Q1Ck0tfQEmoSzo/edit?usp=sharing](https://docs.google.com/spreadsheets/d/15geR5hByqh8XFhX6bHwq9C1g8LxH1Q1Ck0tfQEmoSzo/edit?usp=sharing))
4242

43-
**What payment methods are available?**
43+
## What payment methods are available?
4444

4545
* Debit/Credit card payment (Visa and Mastercard)
4646
* Bank Transfer
4747

48-
**What assets are supported?**
48+
## What assets are supported?
4949

5050
* At the moment, stablecoins USDT and USDC are supported by default and do not require any additional setup to enable.
5151

52-
**Can I list my own token?**
52+
## Can I list my own token?
5353

5454
* Yes, this will be subject to Münzen’s listing process and will incur a fee. Raise your interest to your Aurora Cloud Account Manager and they will introduce you to the Münzen team.
5555

56-
**Commercials**
56+
## Commercials
5757

5858
* An additional fee can be added on top of the base rate. Please get in touch with your account manager to set it up.

docs/aurora-cloud/02-run-your-own-virtual-chain/06-pyth-oracle.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,19 +6,19 @@ description: Access Pyth Oracle from any Virtual Chain
66

77
Aurora Cloud partnered with Pyth to propose an access to its Oracle from all Virtual Chains.
88

9-
**How does it work?**
9+
## How does it work?
1010

1111
Thanks to the communication between Virtual Chains, your Virtual Chain can call the Pyth Oracle deployed on Aurora Mainnet to retrieve price feeds required for your on-chain logic.
1212

1313
Pyth proposes more than x price feeds.
1414

1515
![frame827](/img/.gitbook/assets/Frame_827_(4).png)
1616

17-
**Technical Overview**
17+
## Technical Overview
1818

1919
Each Virtual Chain comes with the Cloud Oracle deployed on it. The Cloud Oracle proposes the same interface as the Pyth Oracle but leverages the cross contract call technology between your Virtual Chain and Aurora Mainnet to retrieve the price feed you need.
2020

21-
**Why is this important?**
21+
## Why is this important?
2222

2323
The Pyth Oracle strives for decentralisation where prices are collaboratively fed by the different actors in the network.
2424

@@ -28,7 +28,7 @@ Besides, you get access from your Virtual Chain to all the other price feeds fro
2828

2929
![image3](/img/.gitbook/assets/image_(3).png)
3030

31-
**Aurora Cloud addon**
31+
## Aurora Cloud addon
3232

3333
The Cloud Oracle is configurable from the Aurora Cloud Console and also supports price feeds from CoinGecko, to offer an easy and instant solution to your Oracle needs.
3434

docs/aurora-cloud/02-run-your-own-virtual-chain/07-connect-cexes-to-your-chain.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ The tool is currently available at [https://aurora.plus/forwarder](https://auror
1515

1616
![image1](/img/.gitbook/assets/image_(1).png)
1717

18-
**How does it work?**
18+
## How does it work?
1919

2020
The forwarder, as its name suggests, forwards any assets sent to its Near deposit address to the recipient Aurora address. 
2121

@@ -24,15 +24,15 @@ The forwarder, as its name suggests, forwards any assets sent to its Near deposi
2424
* This process is invisible for the user who simply receives their assets on their address on your Virtual Chain.
2525

2626

27-
**Technical overview**
27+
## Technical overview
2828

2929
The forwarder leverages the chain abstraction ability from Aurora and Near by routing assets to the target virtual chain.
3030

3131
In technical terms, the forwarder is a smart contract deployed on Near, and has the capacity to generate a unique Near address based on an Aurora address (one per Aurora network). When the contract receives tokens that are part of the curated token list, it will automatically send these assets to the address on the Aurora network selected.
3232

3333
![image2](/img/.gitbook/assets/image_(2).png)
3434

35-
**Supported assets**
35+
## Supported assets
3636

3737
These assets will be automatically forwarded to the destination address.
3838

docs/aurora-cloud/02-run-your-own-virtual-chain/08-bridge-assets-to-your-chain.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Each Virtual Chain is automatically supported by the Rainbow Bridge technology s
44

55
![frame827_6](/img/.gitbook/assets/Frame_827_(6).png)
66

7-
**Embeddable bridge**
7+
## Embeddable bridge
88

99
The bridge addon in Aurora Cloud allows you to configure your own bridge interface and embed it in your application.
1010

0 commit comments

Comments
 (0)