Futaba
TwitterBlog
  • 🌱Introduction
    • Introduction
    • Concept
    • Architecture
  • 🛠️Protocol
    • Gateway
      • Send
      • Receive
      • Estimate fee
      • Cache
    • Light Client
      • Request Query
      • Verify
      • Estimate fee
    • Relayer
    • Konoha
      • Chainlink Oracle
      • Herodotus
      • Lagrange
  • 💡Guide
    • Futaba Testnet
      • Balance query
      • Custom query
      • Access cache
      • Cross-chain voting
    • Quick Start
    • Customize Light Client
    • Example Apps
  • 📗References
    • FAQ
    • Contract addresses
    • Glossary
  • 🔗Links
    • Twitter
    • Blog
Powered by GitBook
On this page
  • What is Futaba?
  • What is Futaba used for?
  • What does it look like with Futaba integrated?
  • What are some usecases?

Was this helpful?

  1. Introduction

Introduction

NextConcept

Last updated 1 year ago

Was this helpful?

What is Futaba?

Futaba is a modular omnichain interface enabling communication between contracts, rollups and blockchain networks by querying and pulling data from a single source chain.

What is Futaba used for?

Futaba unifies liquidity, community of users, accounting and management of a dApp or an ecosystem

by enabling data to be pulled from one / many chains to one single source chain

What does it look like with Futaba integrated?

Aspects
without Futaba integrated (currently)
with Futaba integrated

Fees

dApp users spend large amounts of gas fees whenever interacting with dApps on Ethereum mainnet

dApp users can interact with dApps on Ethereum mainnet from dApps/contracts on rollups / L2s, paying only rollups / L2 gas fees

Security

To save on fees and time, dApp users bridge to rollups / L2s, at the risk of trusting 3rd party bridges / protocols (single point of failure).

Dev Costs

Whenever a new rollup / chain attracts a lot of liquidity, developers incur a new cost of developer hours and money, as they create a new set of contracts, just to capture market share and users.

Developers save money and developer hours, by integrating a new rollup/chain via Futaba

Dev Effort

Developers have more accounting to do, more data to be managed, and community that is more fragmented to interact with - as their dApp goes live on multiple chains (multi-chain)

Developers community, data and accounting are accessed and unified from a single source chain, yet accessing data across many chains (omni-chain).

What are some usecases?

Reduced transaction fees - Query and access yield/reward balances on Ethereum mainnet from rollups or Layer 2s at much lower fees, compared to withdrawing the yield balance from mainnet itself. Usecases / dapps: LST, Perp DEXes, Yield aggregators

Reduced developer hours to scale to other chains/rollups - With Futaba integrated, dapp users on chain/rollup X, Y, Z, can access balances on mainnet, instead of deploying another set of contracts and liquidity on another chain/rollup to scale every time. Usecases / dapps: AMMs, DEXes, Perp DEXes

while secured modularly by , which is made up of multiple validation / security modules that builders can choose to incorporate to optimize their validation method. If one of the modules are exploited, Futaba is still secured by Konoha and its other unaffected modules.

Futaba's ensures dApp users are secure even if one of the 3rd party validators/oracles ie , , zk light clients, are exploited.

Konoha
Konoha
Chainlink
Lagrange
🌱
Page cover image