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
Aurora Chains are dedicated blockchains that go beyond mere Ethereum compatibility through a set of industry-first innovations like:
10
10
11
-
**custom token & fee mechanics* (e.g., gasless transactions; paying for gas with a custom token; some percentage of any transaction value to be stored in Aurora Chain Treasury, etc.);
12
-
**custom access control* (public vs private chain, who can transact, who can deploy contracts? e.g., NFT-based access to the blockchain, private chain can be built by using a private NEAR shard – [Calimero](https://www.calimero.network/));
13
-
**seamless interoperability* with Aurora, NEAR, and any other Aurora Chains: you can freely move your assets using Rainbow Bridge, call contracts via cross-contract calls, etc.; This is the main difference between Chains and other solutions (like Avalanche or Cosmos). There is no disjointness in between. You can call any smart contract in any other Chain or Near and interact with it freely.
14
-
**tremendous transaction throughput – *we can provide you with dozens of millions of transactions daily for your ecosystem.
11
+
**custom token & fee mechanics* (e.g., gasless transactions; paying for gas with a custom token; some percentage of any transaction value to be stored in Aurora Chain Treasury, etc.);
12
+
**custom access control* (public vs private chain, who can transact, who can deploy contracts? e.g., NFT-based access to the blockchain, private chain can be built by using a private NEAR shard – [Calimero](https://www.calimero.network/));
13
+
**seamless interoperability* with Aurora, NEAR, and any other Aurora Chains: you can freely move your assets using Rainbow Bridge, call contracts via cross-contract calls, etc.; This is the main difference between Chains and other solutions (like Avalanche or Cosmos). There is no disjointness in between. You can call any smart contract in any other Chain or Near and interact with it freely.
14
+
**tremendous transaction throughput – *we can provide you with dozens of millions of transactions daily for your ecosystem.
15
15
16
16
Every Aurora Chain is based upon the [Aurora smart contract.](https://github.com/aurora-is-near/aurora-engine/) Aurora Chain is just another instance of it that can be configured in way that will work in the best way possible to be aligned with your business model and goals. The Aurora Labs team will gladly help you maintain and support your chain.
Copy file name to clipboardExpand all lines: blog/aurora-cloud-borealis-business.md
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -32,15 +32,15 @@ Let’s see this setup process in more detail.
32
32
33
33
As previously discussed, Deals consist of rules. Therefore, when a business engages with Aurora's engineering team, two key aspects need to be established:
34
34
35
-
*Which smart contracts will be part of a deal?
36
-
*What is the business logic around free transactions for users?\
35
+
* Which smart contracts will be part of a deal?
36
+
* What is the business logic around free transactions for users?\
37
37
38
38
39
39
Typically, setting up a deal would initiate with specific parameters. These, however, are not strict boundaries but flexible starting points. Our adaptability allows us to fine-tune the operational rules by leveraging a wide range of resources. These could range from IP addresses and authentication tokens to the internal data embedded within each transaction. Nevertheless, right now, we propose using the following set of parameters:
40
40
41
-
***FROM:** This parameter specifies the originator of the transaction, and it can take values such as ***All***, meaning that the rule engine will not filter any transactions based on their origin address (i.e., all origin addresses are valid for this deal) or ***EOA*** in which case the rule engine will only pick up transactions coming from a specific list of addresses (EOAs). We refer to this list as the whitelist, which must be populated by the businesses.
42
-
***TO:** This parameter specifies the transaction's target, and it can take values such as an ***address*** so that the rule engine will pick up transactions directed to this specific contract address. If a transaction goes to another contract, it cannot be associated with this deal.
43
-
***DEAL**: This parameter specifies the number of transactions that the beneficiaries of this deal can get. It can be set to UNLIMITED or a specific number.
41
+
***FROM:** This parameter specifies the originator of the transaction, and it can take values such as ***All***, meaning that the rule engine will not filter any transactions based on their origin address (i.e., all origin addresses are valid for this deal) or ***EOA*** in which case the rule engine will only pick up transactions coming from a specific list of addresses (EOAs). We refer to this list as the whitelist, which must be populated by the businesses.
42
+
***TO:** This parameter specifies the transaction's target, and it can take values such as an ***address*** so that the rule engine will pick up transactions directed to this specific contract address. If a transaction goes to another contract, it cannot be associated with this deal.
43
+
***DEAL**: This parameter specifies the number of transactions that the beneficiaries of this deal can get. It can be set to UNLIMITED or a specific number.
44
44
45
45
Here are a few simple examples of Borealis Business deals:
46
46
@@ -60,9 +60,9 @@ Here is an image describing how the AuroraPass (AP) Deal works:
60
60
61
61
Businesses must define a list of approved addresses that can benefit from their deal. The whitelisted addresses are managed via a dedicated API to enable companies to:
62
62
63
-
*Add an address.
64
-
*Remove an address.
65
-
*Check if an address is on the whitelist.
63
+
* Add an address.
64
+
* Remove an address.
65
+
* Check if an address is on the whitelist.
66
66
67
67
The Aurora team will provide businesses with the credentials for this API as part of the Borealis deal setup process.
Copy file name to clipboardExpand all lines: blog/demystifying-transaction-failures.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -42,12 +42,12 @@ That is it. The task is solved. You can see in Aurora Helpers directly what this
42
42
43
43
Those `07 03` numbers correspond to the `status` field of the Aurora Engine's transaction. The First number indicates the[ Aurora Engine API version](https://github.com/aurora-is-near/aurora-engine/pull/299/files#diff-a0e4fe79c7aa101e4b4e969318e18bb3854f0f8607e4b56d5665e131f98fdfa8R116). And the second one corresponds to the [statuses](https://github.com/aurora-is-near/aurora-engine/blob/a00df8e7d83ae49c035348111cc89be28cb93dab/engine-types/src/parameters/engine.rs#L19-L26) which could transactions have inside the Engine after execution. Let's compile them into the list below:
44
44
45
-
*00 – Succeed: transaction has been executed successfully.
46
-
*01 – Revert: transaction has been reverted, most likely because of internal contract terms.
47
-
*02 – OutOfGas: execution ran out of gas.
48
-
*03 – OutOfFund: not enough funds to start the execution.
49
-
*04 –OutOfOffset: an opcode accesses external information, but the request exceeds the offset limit.
50
-
*05 – CallTooDeep: call stack is too deep.
45
+
* 00 – Succeed: transaction has been executed successfully.
46
+
* 01 – Revert: transaction has been reverted, most likely because of internal contract terms.
47
+
* 02 – OutOfGas: execution ran out of gas.
48
+
* 03 – OutOfFund: not enough funds to start the execution.
49
+
* 04 –OutOfOffset: an opcode accesses external information, but the request exceeds the offset limit.
50
+
* 05 – CallTooDeep: call stack is too deep.
51
51
52
52
We can create the enum map inside our code to convert easily between codes and error names:
Copy file name to clipboardExpand all lines: blog/getting-started-with-aurora.md
+22-22Lines changed: 22 additions & 22 deletions
Original file line number
Diff line number
Diff line change
@@ -95,11 +95,11 @@ To interact with the contract, you have to obtain some AuroraEth in the Aurora `
95
95
96
96
To directly obtain AuroraETH in the `testnet`, you can follow these steps:
97
97
98
-
*Go to the following link: [https://aurora.dev/faucet](https://aurora.dev/faucet)
99
-
*Select the Testnet.
100
-
*Connect to MetaMask. Click on "Connect to Aurora Testnet." This will likely open your MetaMask wallet and prompt you to perform a few simple instructions.
101
-
*Check the wallet address to which you have connected. If you have multiple accounts in MetaMask and it is not connected to the desired account, click on the MetaMask icon in your browser and select the account you want to connect to.
102
-
*Click on "Request 0.001 ETH from the faucet." This will initiate the process of receiving AuroraETH.
98
+
* Go to the following link: [https://aurora.dev/faucet](https://aurora.dev/faucet)
99
+
* Select the Testnet.
100
+
* Connect to MetaMask. Click on "Connect to Aurora Testnet." This will likely open your MetaMask wallet and prompt you to perform a few simple instructions.
101
+
* Check the wallet address to which you have connected. If you have multiple accounts in MetaMask and it is not connected to the desired account, click on the MetaMask icon in your browser and select the account you want to connect to.
102
+
* Click on "Request 0.001 ETH from the faucet." This will initiate the process of receiving AuroraETH.
103
103
104
104
Congratulations! You now have AuroraETH in your `testnet` wallet!
105
105
@@ -113,17 +113,17 @@ This method will take approximately 20 minutes. First, we will obtain ETH in Goe
113
113
114
114
Obtain the Eth in Goerli testnet in Ethereum:
115
115
116
-
*Go to the following link:[*https://goerli-faucet.pk910.de/*](https://goerli-faucet.pk910.de/). Of course, it is not the only option. But here, you can get the Eth without a daily limit.
117
-
*Enter the address where you want the Eth to be sent.
118
-
*Click “Start Mining” and wait…
119
-
*Finish the mining and receive Eth.
116
+
* Go to the following link:[*https://goerli-faucet.pk910.de/*](https://goerli-faucet.pk910.de/). Of course, it is not the only option. But here, you can get the Eth without a daily limit.
117
+
* Enter the address where you want the Eth to be sent.
118
+
* Click “Start Mining” and wait…
119
+
* Finish the mining and receive Eth.
120
120
121
121
Transfer the Eth to Aurora using the Rainbow Bridge:
Copy file name to clipboardExpand all lines: blog/hot-to-get-your-tokens-from-bastion-contract.md
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -12,9 +12,9 @@ To formulate the problem more precisely, a user has some `cUSDCcUSDTLP` tokens a
12
12
13
13
We will go through the next steps:
14
14
15
-
*What contracts should we call?
16
-
*What method should we call, and how?
17
-
*How to convert `cUSDC` and `cUSDT` into regular stables?
15
+
* What contracts should we call?
16
+
* What method should we call, and how?
17
+
* How to convert `cUSDC` and `cUSDT` into regular stables?
18
18
19
19
We will use the most convenient way for users to interact with smart contracts—the Explorer. However, devs can always write a script to perform the steps described in this article with Ethers or Web3.js.
20
20
@@ -66,8 +66,8 @@ We're unsure about the arguments here yet, so let's find out what values we shou
66
66
67
67
You can see what exactly has happened here during the execution in terms of the token transfers:
68
68
69
-
*`cUSDCcUSDTLP` tokens were burned
70
-
*`cUSDT` and `cUSDC` tokens were transferred to the caller
69
+
*`cUSDCcUSDTLP` tokens were burned
70
+
*`cUSDT` and `cUSDC` tokens were transferred to the caller
71
71
72
72
Now, let's scroll down a bit and click on "View details" link at the left bottom of the page, you will see the arguments of the method used there:
73
73
@@ -90,8 +90,8 @@ That is it! Now you got back your `cUSDC` and `cUSDT` tokens.
90
90
91
91
To do this, we will need to point our attention to these contracts:
Copy file name to clipboardExpand all lines: blog/how-to-get-usdc-tokens-on-aurora-testnet.md
+14-14Lines changed: 14 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -57,25 +57,25 @@ We have the Goerli Ethereum account and some GoerliETH. Let’s exchange some Et
57
57
58
58
**2. Connect to Goerli Network.** It can look like it doesn’t support testnet network, but it actually support it, just it is not clear from the web interface.
59
59
60
-
*Click the `Connect` button. Choose MetaMask and connect to your account.
60
+
* Click the `Connect` button. Choose MetaMask and connect to your account.
0 commit comments