The APIS Docs
HookDiscordContact Us
  • ☺️Hello, Web3!
  • ↔️About The APIS
    • Introduction
    • Core Team
    • Our Partners
  • 🤖Roadmap
  • 🍦Products
    • 🔍Hook
      • Get Started
        • Explore
        • Calendar
        • Collections Trending
        • Watch List
      • Twitter RSS
      • Chatting /w Community
    • ❄️Data Lake
  • 🤓Academy
    • On-Chain Glossary
      • NFT
      • DeFi
  • ℹ️$API Token Info
    • 🅰️$API Smart Contract Address
    • 🪙Token Economics
      • $API Token Utility
      • $API Token Distribution
      • Dune Analysis
      • Investors
      • FAQs
        • What is API?
        • How do APIs work?
        • What is the API token?
        • Why does API stand out?
        • What does API mean for the crypto industry?
    • 📈Get $API Token
    • ⬆️Listed Exchanges
  • 🤝Get In Touch
    • 🥰Contact Us
    • 🥰Join Us
    • ❓FAQ
  • 📖Docs
    • 🔐Security
      • 📄Security Report by Certik
    • 📄Terms & Conditions
    • 📑Privacy Policy
    • ℹ️Disclaimer
  • 📃Whitepaper
    • Whitepaper
      • 1️⃣1⃣ Background
        • 1.1 Background
        • 1.2 Introduction
      • 2️⃣2⃣ Architecture
        • 2.1 Message Propagation Protocol
        • 2.2 Message Formatting Overview
        • 2.3 APIS Core Contracts
        • 2.4 Governance Contract (GC)
        • 2.5 Dispute Resolution Contract (DRC) Factory
        • 2.6 Optimistic Rollup Contract
      • 3️⃣3⃣ Applications
        • 3.1IDs
        • 3.2 API Token
        • 3.3 Token Distribution, Community Ownership
      • 4️⃣4⃣ Discussion
      • 5️⃣5⃣ Appendix
        • 5.1 REST History and Analysis
        • 5.2 REST APIs in Practice
        • 5.3 Strengths and Weaknesses of REST
        • 5.4 GraphQL History and Analysis
        • 5.5 GraphQL as a ‘Fetching Tree’
        • 5.6 Anatomy of a GraphQL Request
        • 5.7Note on GraphQL Resolvers:
        • 5.8 Direct Comparison
        • 5.9 Weaknesses of GraphQL
      • 6️⃣6⃣ Bibliography
Powered by GitBook
On this page
Edit on GitHub
  1. Whitepaper
  2. Whitepaper

3⃣ Applications

The Applications of the APIS network are twofold: to create better end-user experiences and to create better developer experiences. For end-users, APIS allows developers to seamless integrate features with guaranteed 100% uptime, censorship resistance, and near-zero platform risk. While the uptime and censorship resistance features of a decentralized network has been discussed thoroughly by the public blockchain community, we believe that platform risk remains under-discussed. Developers who utilize the APIS network for their decentralized applications will never be upcharged by a monopolistic, profit-seeking company, as protocols create markets, not monopolies [25]. The platform risk view can be further substantiated by Metamask’s recent change in open-source licensing, leaving developers to question whether a Metamask integration will require fees in the future [26]. APIS already supports all queries and indexes of Ethereum through the aggregation of APIS’s centralized competitors, and shortly thereafter will support IPFS and Filecoin due to its growing popularity. Additionally, any additional blockchains can be added to the APIS index and query protocol, should an ID for that blockchain be created by an APIS Gateway or Node.

Previous2.6 Optimistic Rollup ContractNext3.1IDs

Last updated 3 years ago

📃
3️⃣