|
1 | | -import DocCard from '@theme/DocCard'; |
2 | | -import DocCardList from '@theme/DocCardList'; |
3 | | -import {findSidebarItem} from '@site/src/sidebarUtils'; |
| 1 | +import DocCard from "@theme/DocCard"; |
| 2 | +import DocCardList from "@theme/DocCardList"; |
| 3 | +import { findSidebarItem } from "@site/src/sidebarUtils"; |
| 4 | +import DocCardSection from "@site/src/components/DocCardSection"; |
| 5 | +import OasisSvg from "@site/static/img/OasisGraphic.svg?react"; |
| 6 | +import GetInvolvedSvg from "@site/static/img/GetInvolvedGraphic.svg?react"; |
| 7 | +import BuildSvg from "@site/static/img/BuildGraphic.svg?react"; |
| 8 | +import DevelopCoreSvg from "@site/static/img/DevelopCoreGraphic.svg?react"; |
| 9 | +import NodeseSvg from "@site/static/img/NodesGraphic.svg?react"; |
4 | 10 |
|
5 | 11 | # Getting Started |
6 | 12 |
|
7 | | -## Use Oasis |
8 | | - |
9 | | -This introductory part contains general overview of the Oasis Network such as |
10 | | -the distinction between the consensus layer and different ParaTimes. It |
11 | | -also covers wallets and other tools for managing your assets across the Oasis |
12 | | -chains and how to use unique Oasis features. |
13 | | - |
14 | | -<DocCardList items={[ |
15 | | - findSidebarItem('/general/oasis-network/'), |
16 | | - findSidebarItem('/general/manage-tokens/'), |
17 | | - findSidebarItem('/general/manage-tokens/cli/'), |
18 | | -]} /> |
19 | | - |
20 | | -## Build on Oasis |
21 | | - |
22 | | -Contains learning material for the smart contract developers. Since the Oasis |
23 | | -platform is best known for confidentiality, the most notable ParaTime is |
24 | | -[Oasis Sapphire], an **EVM-compatible** ParaTime with **built-in contract state |
25 | | -encryption**. The Oasis team also prepared a set of libraries called the |
26 | | -[Oasis Privacy Layer] to **bridge existing dApps running on other chains** to |
27 | | -use the unique Sapphire's confidentiality. |
28 | | - |
29 | | -Our [Runtime OFfchain Logic (ROFL)][ROFL] enables you to **build secure applications running |
30 | | -offchain** in a trusted environment (TEE) and that seamlessly communicate with |
31 | | -Oasis Sapphire. This is ideal for trusted oracles, compute-expensive tasks |
32 | | -in AI or as a backend for interactive games. |
33 | | - |
34 | | -<DocCardList items={[ |
35 | | - findSidebarItem('/build/sapphire/'), |
36 | | - findSidebarItem('/build/opl/'), |
37 | | - findSidebarItem('/build/rofl/'), |
38 | | - findSidebarItem('/build/tools/'), |
39 | | -]} /> |
40 | | - |
41 | | -[Oasis Sapphire]: ./build/sapphire/README.mdx |
42 | | -[Oasis Privacy Layer]: ./build/opl/README.mdx |
43 | | -[ROFL]: ./build/rofl/README.mdx |
44 | | - |
45 | | -## Get Involved |
46 | | - |
47 | | -Contains information on official channels to get in touch with the Oasis Network |
48 | | -developers and how to contribute to the network. |
49 | | - |
50 | | -<DocCardList items={[ |
51 | | - findSidebarItem('/get-involved/'), |
52 | | - findSidebarItem('https://oasisrose.garden'), |
53 | | - findSidebarItem('/get-involved/run-node'), |
54 | | - findSidebarItem('/get-involved/oasis-core'), |
55 | | -]} /> |
56 | | - |
57 | | -## Run Node |
58 | | - |
59 | | -If you want to run your own Oasis node, this part will provide you |
60 | | -with guides on the current Mainnet and Testnet network parameters and how to |
61 | | -set up your node, let it be a validator node, perhaps running a ParaTime or |
62 | | -just a simple client node for your server to submit transactions and perform |
63 | | -queries on the network. |
64 | | - |
65 | | -<DocCardList items={[ |
66 | | - findSidebarItem('/node/'), |
67 | | - findSidebarItem('/node/mainnet/'), |
68 | | - findSidebarItem('/node/testnet/'), |
69 | | - findSidebarItem('/node/run-your-node/'), |
70 | | -]} /> |
71 | | - |
72 | | -## Build ParaTimes |
73 | | - |
74 | | -Apart from the Sapphire, Emerald, Cipher and the Key manager ParaTimes, |
75 | | -you can also write, compile, sign and deploy your own ParaTime on the Oasis |
76 | | -Network. This part describes the knobs you need to use to do so. |
77 | | - |
78 | | -<DocCard item={findSidebarItem('/build/tools/build-paratime/')} /> |
79 | | - |
80 | | -## Develop Core |
81 | | - |
82 | | -Whether you want to contribute your code to the core components of the Oasis |
83 | | -Network or just learn more about the Oasis consensus layer and other core |
84 | | -components, this is the part for you. |
85 | | - |
86 | | -<DocCard item={ findSidebarItem('/core/') } /> |
87 | | - |
88 | | -Additions or changes to the interoperable Oasis network components are always |
89 | | -made with consensus. Similar to the Ethereum's ERC/EIP mechanism Oasis follows |
90 | | -formal Architectural Decision Records (ADRs) which are first proposed, voted on |
91 | | -and finally implemented, if accepted. |
92 | | - |
93 | | -<DocCard item={ findSidebarItem('/adrs') } /> |
| 13 | +<div className='homepage-container'> |
| 14 | + <DocCardSection |
| 15 | + title="Use Oasis" |
| 16 | + path="/general/" |
| 17 | + description="This introductory part contains general overview of the Oasis Network such as |
| 18 | + the distinction between the consensus layer and different ParaTimes. It |
| 19 | + also covers wallets and other tools for managing your assets across the Oasis |
| 20 | + chains and how to use unique Oasis features." |
| 21 | + itemPaths={[ |
| 22 | + "/general/oasis-network/", |
| 23 | + "/general/manage-tokens/", |
| 24 | + "/general/manage-tokens/cli/", |
| 25 | + ]} |
| 26 | + svg={ |
| 27 | + <OasisSvg className="animatedSvg" /> |
| 28 | + } |
| 29 | +/> |
| 30 | + |
| 31 | +<DocCardSection |
| 32 | + title="Get Involved" |
| 33 | + path="/get-involved/" |
| 34 | + description="Contains information on official channels to get in touch with the Oasis Network developers and how to contribute to the network." |
| 35 | + itemPaths={[ |
| 36 | + "/get-involved/", |
| 37 | + "https://oasisrose.garden", |
| 38 | + "/get-involved/run-node", |
| 39 | + "/get-involved/oasis-core", |
| 40 | + ]} |
| 41 | + svg={<GetInvolvedSvg className="animatedSvg" />} |
| 42 | +/> |
| 43 | + |
| 44 | +<DocCardSection |
| 45 | + title="Build on Oasis" |
| 46 | + path="/build/" |
| 47 | + description={ |
| 48 | + <> |
| 49 | + Contains learning material for the smart contract developers. Since the |
| 50 | + Oasis platform is best known for confidentiality, the most notable |
| 51 | + ParaTime is <a href="/build/sapphire/">Oasis Sapphire</a>, an |
| 52 | + EVM-compatible ParaTime with built-in contract state encryption. The Oasis |
| 53 | + team also prepared a set of libraries called the |
| 54 | + <a href="/build/opl/">Oasis Privacy Layer</a> to bridge existing dApps running |
| 55 | + on other chains and use the unique Sapphire's confidentiality. |
| 56 | + <br /> |
| 57 | + <br /> |
| 58 | + Our <a href="/build/rofl/">Runtime Offchain Logic (ROFL)</a> enables you |
| 59 | + to build secure applications running offchain in a trusted environment |
| 60 | + (TEE) that seamlessly communicate with Oasis Sapphire. This is ideal for |
| 61 | + trusted oracles, compute-expensive tasks in AI, or as a backend for |
| 62 | + interactive games. |
| 63 | + </> |
| 64 | + } |
| 65 | + fullWidth |
| 66 | + itemPaths={[ |
| 67 | + "/build/sapphire/", |
| 68 | + "/build/opl/", |
| 69 | + "/build/rofl/", |
| 70 | + "/build/tools/", |
| 71 | + ]} |
| 72 | + svg={<BuildSvg className="animatedSvg" />} |
| 73 | +/> |
| 74 | + |
| 75 | +<DocCardSection |
| 76 | + title="Run Node" |
| 77 | + path="/node/" |
| 78 | + description="If you want to run your own Oasis node, this part will provide you with guides on the current Mainnet and Testnet network parameters and how to set up your node, let it be a validator node, perhaps running a ParaTime or just a simple client node for your server to submit transactions and perform queries on the network." |
| 79 | + itemPaths={[ |
| 80 | + "/node/", |
| 81 | + "/node/mainnet/", |
| 82 | + "/node/testnet/", |
| 83 | + "/node/run-your-node/", |
| 84 | + ]} |
| 85 | + svg={<NodeseSvg className="animatedSvg" />} |
| 86 | +/> |
| 87 | + |
| 88 | +<DocCardSection |
| 89 | + title="Develop Core" |
| 90 | + path="/core/" |
| 91 | + description={ |
| 92 | + <> |
| 93 | + Whether you want to contribute your code to the core components of the Oasis Network or just learn more about the Oasis consensus layer and other core components, this is the part for you. |
| 94 | + <br/> |
| 95 | + <br/> |
| 96 | + Additions or changes to the interoperable Oasis network components are always made with consensus. Similar to the Ethereum's ERC/EIP mechanism Oasis follows formal Architectural Decision Records (ADRs) which are first proposed, voted on and finally implemented, if accepted. |
| 97 | + </> |
| 98 | + } |
| 99 | + itemPaths={[ |
| 100 | + "/core/", |
| 101 | + "/adrs", |
| 102 | + ]} |
| 103 | + svg={<DevelopCoreSvg className="animatedSvg" />} |
| 104 | +/> |
| 105 | +</div> |
0 commit comments