import DocCard from "@theme/DocCard"; import DocCardList from "@theme/DocCardList"; import { findSidebarItem } from "@site/src/sidebarUtils"; import DocCardSection from "@site/src/components/DocCardSection"; import HammerSvg from "@site/static/img/HammerGraphic.svg?react"; import OasisSvg from "@site/static/img/OasisGraphic.svg?react"; import SpeakerSvg from "@site/static/img/SpeakerGraphic.svg?react"; import CogSvg from "@site/static/img/CogGraphic.svg?react"; import CoreSvg from "@site/static/img/CoreGraphic.svg?react"; import BlocksSvg from "@site/static/img/BlocksGraphic.svg?react";
<DocCardSection title="Use Cases" path="/build/use-cases" itemPaths={[ "/build/use-cases/key-generation", "/build/use-cases/trustless-agent", "/build/use-cases/price-oracle", "/build/use-cases/tgbot", ]} svg={}
Use Oasis to build verifiable, auditable applications
powered by TEE running on a permissionless network of nodes. No censorship,
no hidden costs, no central authority!
Get your hands dirty quickly by reviewing [top use cases](/build/use-cases)
and considering one that fits your needs. Our tutorials will help you make
your app up and running in no time.
<DocCardSection title="Build on Oasis" path="/build/" itemPaths={[ "/build/rofl/", "/build/sapphire/", "/build/opl/", ]} svg={}
Our [Runtime Offchain Logic (ROFL)](/build/rofl/) enables you to build
secure applications running in a trusted environment (TEE). This is ideal
for trusted oracles, AI agents, verifiable compute tasks such as AI
training, or game servers.
ROFL can seamlessly communicate with [Oasis Sapphire](/build/sapphire/)—an
EVM-compatible L1 blockchain with built-in contract state and end-to-end
transaction encryption.
The Oasis team also prepared a set of libraries called the
[Oasis Privacy Layer](/build/opl/) to bridge existing dApps running
on other chains with the unique Sapphire's confidentiality and other
[tools](/build/tools/).
<DocCardSection title="Learn" path="/general/" itemPaths={[ "/general/oasis-network/", "/general/manage-tokens/", ]} svg={ }
Learn the fundamentals of Oasis architecture, wallets, and unique privacy features.
<DocCardSection title="Get Involved" path="/get-involved/" itemPaths={[ "/get-involved/", ]} svg={}
Connect with developers, run infrastructure, and contribute to the future of Oasis.
<DocCardSection title="Run Node" path="/node/" itemPaths={[ "/node/network/mainnet", "/node/network/testnet", "/node/run-your-node/", ]} svg={}
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.
<DocCardSection title="Develop Core" path="/core/" itemPaths={[ "/core/consensus/", "/core/runtime/", "/adrs", ]} svg={}
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.
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.