Skip to content

Commit

Permalink
Update What is flare page FLR-515 (#263)
Browse files Browse the repository at this point in the history
Co-authored-by: Xavi Artigas <[email protected]>
  • Loading branch information
AnnemarieJ and segfaultxavi authored Sep 4, 2023
1 parent f0c8967 commit fae3cd4
Show file tree
Hide file tree
Showing 2 changed files with 51 additions and 17 deletions.
55 changes: 40 additions & 15 deletions docs/tech/flare.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,33 +3,58 @@
!!! image inline end ""
![Flare logo](logo-FLR.png){ loading=lazy .allow-zoom }

Flare is a layer-1 blockchain network aimed at working with decentralized data.
Flare is the blockchain for data.
It is a [layer 1](glossary.md#layer1), EVM smart contract platform designed to expand the utility of blockchain.

Flare is used just like Ethereum: even though the code is different, Flare offers the same API, supports the same smart contracts and the [EVM](glossary.md#evm) just like Ethereum.
As an example, Flare also supports [NFTs](glossary.md#nft).
Flare's aim is to provide data as a public good, meaning that data is not controlled by a centralized entity and is available to all.
The infrastructure providers, which perform doubly as [validators](../tech/validators.md) and [data providers](../infra/data/operating.md), enable two native oracles, the [FTSO](./ftso.md) and the [State Connector](./state-connector.md).
This native processing provides developers on Flare with efficient access to large amounts of data and data proofs at minimal cost.

Common blockchain tools like [wallets](../user/wallets/index.md) and [block explorers](../user/block-explorers/index.md) are fully available on Flare.
By giving developers trustless access to the broadest range of data, Flare can advance the development of more blockchain use cases where data is important, such as in DeFi, gaming, NFT, music, and social networks.

The native currency of the Flare network is the `$FLR` token, which is not an [ERC-20](https://ethereum.org/en/developers/docs/standards/tokens/erc-20/) token.
`$FLR` is handled the same way `$ETH` is handled on the Ethereum blockchain.
## Flare Protocols

## The Flare Protocols
Flare has the following native data acquisition protocols at these stages of development:

A number of protocols are actively being developed on the Flare network that provide on-chain decentralized data:
* The **[Flare Time-Series Oracle (FTSO)](./ftso.md)** provides continuous estimations of changing data, such as price pairs.
* The **[State Connector](./state-connector.md)** allows querying of verifiable, non-changing data from other chains and the internet.
* Flare **LayerCake** is being developed by Flare Labs to provide a decentralized, trustless bridging system between smart contract networks. For an overview of trustless bridges, see [LayerCake](https://flare.network/layercake/).

* The [Flare Time-Series Oracle (FTSO)](./ftso.md) provides continuous estimations for different types of data.
* The [State Connector](./state-connector.md) allows querying non-changing, verifiable information from outside the Flare network.
## Developing on Flare

## The Flare Networks
Flare developers can work in a familiar Ethereum-like environment.
It offers the same [API](../apis/index.md) and uses the Ethereum Virtual Machine ([EVM](glossary.md#evm)), so Ethereum's Solidity smart contracts can be used directly.
Like Ethereum, Flare supports other assets, such as [NFTs](glossary.md#nft).
See [Developer Docs](../dev/index.md).

The Flare native currency, `$FLR`, works the same as `$ETH` on the Ethereum blockchain.
For those contracts that can only work with [ERC-20](glossary.md#erc20) tokens, `$FLR` can be easily [wrapped](../user/wrapping-tokens.md) as `$WFLR`, which is an ERC-20 representation of `$FLR`.
Flare's [FTSO delegation](ftso.md#delegation) and Flare [governance](./governance.md) are examples of such apps.

Common blockchain tools like [wallets](../user/wallets/index.md), a [token management portal](https://portal.flare.network/), and [block explorers](../user/block-explorers/index.md) are available on Flare.

Flare is actively seeking developers eager to discover what new utility can be brought to the blockchain industry when acquiring data is possible in a decentralized way.
To start, since Flare is EVM-compatible, you can migrate Ethereum smart-contract dapps to Flare.
Then consider, for example, creating DeFi, gaming, NFT, music, or social network dapps.
See [Start Building](https://flare.network/start-building/), for more information.

## Flare Networks

Flare has 4 networks with different purposes:

* **Flare** is the [main network](glossary.md#main_network).
* **Songbird** is the [canary network](glossary.md#canary_network), used for testing features under "real fire" conditions, before deploying them on the main network.
* **Coston** is Songbird's public [test network](glossary.md#coston).
* **Coston2** is Flare's public [test network](glossary.md#coston).
* **Flare** is the [main network](glossary.md#main_network), where `$FLR` is the native currency.
* **Songbird** is the [canary network](glossary.md#canary_network), where `$SGB` is the native currency. Created with users in mind, it is meant for testing features under "real fire" conditions, before deploying them on the main network.
* **Coston** is Songbird's public [test network](glossary.md#coston), created with developers in mind.
* **Coston2** is Flare's public [test network](glossary.md#coston), created with developers in mind.

<figure markdown>
![The Flare networks](flare-network-types.png){ loading=lazy .allow-zoom width=500px }
<figcaption>General feature adoption flow.</figcaption>
</figure>

## Flare Chains

Flare uses two chains and is developing a built-in interoperability mechanism between them.

* **C-Chain:** The contract chain that is used for smart contracts. It is where the Ethereum Virtual Machine operates, and is the chain where the vast bulk of the community currently interact.
* **P-Chain:** The platform chain that accommodates [staking](../tech/validators.md) and provides rewards to its validators.
13 changes: 11 additions & 2 deletions docs/tech/glossary.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Cross-chain (or inter-ecosystem) interoperability { #cross_chain }
DAO { #dao }
: A Decentralized Autonomous Organization is an entity with no central authority. Its governance is mandated by rules encoded on a blockchain so it is tamper-proof.

dApp { #dapp }
Dapp { #dapp }
: A Decentralized Application is a computer program that makes use of blockchain technology and therefore the information it uses or stores has the same benefits (trustlessness, censorship resistance, geographical redundancy, etc). The dapp itself may or may not be hosted on a blockchain.

Data Provider { #data_provider }
Expand All @@ -51,6 +51,9 @@ DeFi { #defi }
Delegate { #delegate }
: To assign a duty to someone else, so they do it for you. On the Flare network, an address can delegate any fraction of the votes associated with the tokens it holds to another address, for the purpose of [FTSO](#ftso) weighting or governance participation. Note that no tokens are transferred.

ERC-20 { #erc20 }
: The Ethereum Request for Comments 20, proposed in November 2015, is an Ethereum token standard that implements an API for tokens within smart contracts. It is a standard for fungible (exchangeable) tokens, which have a property that makes each token exactly the same (in type and value) as another token. For example, an ERC-20 token acts just like Ethereum's ETH token, meaning that 1 token is and will always be equal to all the other tokens. [Read more...](https://ethereum.org/en/developers/docs/standards/tokens/erc-20/)

EVM { #evm }
: The Ethereum Virtual Machine allows executing smart contracts on the Ethereum network, regardless of the kind of computer that executes it. Multiple blockchain networks, including Flare, support EVM contracts. [Read more...](https://ethereum.org/en/developers/docs/evm/)

Expand Down Expand Up @@ -78,8 +81,14 @@ Governance { #governance }
Know Your Customer { #kyc }
: The process an entity completes to verify the identities of its users to comply with global requirements.

Layer 1 { #layer1 }
: An L1 is a blockchain in the classical sense, in that it comprises a network of nodes that exchange information to guarantee the integrity of a shared ledger and offer functionality like token exchange and programmability. Compare it to an L2, which is built on top of an existing L1.

Layer 2 { #layer2 }
: An L2 is a blockchain built on top of an existing L1 making use of its programmability. L2 chains add extra functionality to the L1, like scalability.

Ledger { #ledger }
: Historically, a book where financial transactions are recorded. In [blockchain](#blockchain) technology a ledger can contain any kind of information and it has multiple copies distributed among several computers, which are kept in sync by a [consensus](#consensus) algorithm.
: Historically, a book where financial transactions are recorded. In [blockchain](#blockchain) technology, a ledger can contain any kind of information, which has multiple copies distributed among several computers, kept in sync by a [consensus](#consensus) algorithm.

Light Client Relay { #light_client_relay }
: A simplified communication mechanism built for speed that only queries the header data of any transaction and therefore lacks the security that comes from querying a full node with full history (e.g. [SPV](https://en.wikipedia.org/wiki/Bitcoin_network#Payment_verification)).
Expand Down

0 comments on commit fae3cd4

Please sign in to comment.