State Connector

Proposals

Where isolation ends and integration begins.

Blockchains have undoubtedly revolutionised our approach to data, trust, and decentralisation. But in their quest for security and autonomy, they've also become isolated fortresses.

These isolated entities face difficulties in achieving seamless communication with other blockchains or accessing external data from the open internet.

This limitation restricts the potential of decentralised applications that could thrive on interconnected data sources.

Let's take a look at how Flare's State Connector looks to solve this problem.

Why the State Connector?

Whilst recognising the challenges that emerge from these isolated blockchains, the State Connector aims to offer a decentralised solution to help simplify the flow of data. Here's how:

  • Decentralised Consensus: Unlike other bridging solutions that might rely on centralised parties, the State Connector takes a decentralised approach to achieve consensus on external data, whether it's from another blockchain or the open internet.
  • Broad Compatibility: The State Connector doesn't force other blockchains to adapt to its standards. Instead, it's designed to be flexible, integrating with a multitude of blockchain protocols without requiring them to alter their core code.
  • Trustworthiness: By utilising a robust attestation mechanism, the State Connector ensures that the data it integrates is accurate, reliable, and has been validated by independent entities.
  • Enhanced Data Flow: The State Connector facilitates the flow of data across chains, enabling smart contracts on Flare to access real-time data from other chains or the wider internet. This capability opens the door to a myriad of applications that can leverage these data sources.
Attestation providers

The State Connector relies on specific entities, known as attestation providers, to vouch for the accuracy and integrity of this data. These providers act as intermediaries that verify and attest to the correctness of external data before it is integrated into Flare.

How it works
1. Request

The attestation process initiates with a request. This request could come from a user, a smart contract, or any part of the Flare network that requires data from an external source.

2. Retrieve

Upon receiving the request, attestation providers spring into action to retrieve the required data, from third party sources.

3. Attest

Once the data has been retrieved, the attestation providers each provide their data to the State Connector smart contract, in what is called a commit-and-reveal method. This is done to ensure that each provider sources their own data and is not influenced by the data from other providers.

4. Consensus

With multiple attestation providers in the ecosystem, it's essential to have a unanimous agreement on the data's validity. If more than half of the attestation providers submit the same information to the smart contract, then it is made public. If a consensus is not reached then the attestation has failed and would need to be re-submitted, if needed.

"The answers are stored in the State Connector smart contract for a week, where anybody can read them, including the original requester."
Use cases

By bridging the gap between isolated blockchains and the broader internet, the State Connector unlocks a plethora of innovative use cases for decentralised applications (DApps). Some examples could include:

  • Cross-chain Financial Operations: DApps can facilitate seamless financial transactions across multiple blockchains, enabling users to easily swap, lend, or borrow assets without relying on centralised exchanges or intermediaries.
  • Real-time Data Access: DApps involved in sectors like finance, agriculture, or logistics can access real-time data from the broader internet, enabling functionalities like price feeds, weather updates, or shipment tracking within the decentralised framework.
  • Interoperable Gaming: Imagine a decentralised gaming platform where assets and achievements from one game can be used or showcased in another. The State Connector can make such cross-game interoperability a reality.
  • Decentralized Identity Verification: DApps offering services that require identity verification can use the State Connector to access and validate user data from different blockchains, all while ensuring data privacy and security.
  • Supply Chain Management: DApps in the supply chain sector can trace products across multiple stages and blockchains, ensuring authenticity and transparency from production to delivery.

By harnessing the power of the State Connector, DApps can transcend the limitations of single blockchains and offer users a richer, more integrated experience, all while maintaining the core principles of decentralisation and trust.

More information

Select category
Role

A data provider's role is to gather information from real-world sources and submit it to the FTSO.

​If the FTSO deems this information accurate, in relation to other submissions, then the provider is rewarded, along with any token holders who have delegated votes to them.

Data sourcing

Data providers can obtain the required data from any source they wish. With regards to crypto price data, typical sources would be exchanges, price aggregators and other oracles.​

It's important to have access to many different sources, as the data obtained may differ considerably.

Infrastructure

Building out reliable and resilient infrastructure is critical to the success of any data provider. 

​Often providers choose to run their infrastructure using a cloud based solution, such as AWS, or Google Cloud.​

A typical provider setup can include dedicated nodes, a price submitter tool, a database to organise and an application to process the data.

Algorithms

Once data has been gathered, it needs to be analysed and processed in some way before being submitted to the FTSO.​

The data needs to validated and checks made to ensure any 'bad' data is excluded. This can all be done automatically, based on pre-defined conditions.​

Each provider should create their own unique algorithms, that process the data in a way that ensures the final output represents what they themselves deem to be accurate.

Algorithms

Once data has been gathered, it needs to be analysed and processed in some way before being submitted to the FTSO.​

The data needs to validated and checks made to ensure any 'bad' data is excluded. This can all be done automatically, of course, based on pre-defined conditions.​

Each provider should create their own unique algorithms, that process the data in a way that ensures the final output represents what they themselves deem to be accurate.

Delegations

Accurate submissions lead to more rewards, which in turn should lead to a provider gaining more vote power.​

There is a cap on the maximum vote power any one provider can obtain, before the rewards their delegators receive are diluted.

​Some providers also offer other incentives to gain additional vote power. This includes building useful tools for the community and NFT giveaways, amongst other things. 

Service fees

Data providers charge a fee for the service they offer. It's how they are able to fund the operation of their service.

​The FTSO system gives a provider the freedom to set any fee they choose; however the higher the fee they charge, the less rewards their delegators will receive, which could drive them to delegate to a alternative provider.