Vince Chain Documentation
  • Vince Chain x Users
    • Getting Started
      • What is Vince Chain?
      • Vince Chain dApps
      • Vince Chain Features and Offerings.
    • Connecting Wallet
      • Blithe Wallet
        • Install Blithe Wallet
        • Set up Blithe Wallet account
        • Secure Blithe Wallet.
      • Metamask
        • Install Metamask
        • Set up Metamask account
        • Adding Vince Chain account manually on Metamask
        • Importing wallet on Metamask
        • Resetting Account​
        • Downloading Account State​
        • Registering for Vince Chain Domains​
      • Keplr
      • Ledger
      • Transferring Tokens on Vince Chain
      • View Balances
      • Vince Chain Onramp
      • Sending and receiving assets on Vince Chain
      • Deposit and Withdraw Assets across Chains​
    • Using dApp on Vince Chain
      • Queries and Transactions​
      • Vince Chain dApps
        • Staking​
        • Governance​
    • Frequently Asked Questions (FAQs)
  • 2. Vince Chain x Developers
    • Overview
      • Why build on Vince Chain?
      • Building dApps on Vince Chain
      • Contributing to Vince Chain Ecosystem
    • Building DApps & Smart Contracts
      • Deploying EVM Smart Contracts on Vince Chain
      • What are EVM Smart Contracts?
      • Smart Contracts & Solidity​
      • Smart Contracts & EVM Extensions
      • Smart Contracts & Oracles
      • Smart Contracts & JSON-RPC
      • Vince Explorers
      • Contract Verification
      • Post-project features on Vince Chain
    • Building a dApp front-end
      • Indexers
      • Wallet Integration
    • Building a dApp backend
    • Testnet
      • Security Audits
    • Mainnet
      • Deployment
      • Token distribution
      • Revenue
      • Vince Chain Community
    • Developer Kit
      • Block Explorers
      • Oracles
        • Oracle features
        • How do oracles work?
        • Vince Chain oracles
        • DIA
        • SEDA Network
        • Adrastia
      • Vince Client Integrations
        • Ethereum Client Integrations​
      • Contract Verification
      • Tools x Plugins x IDE
      • Indexers
        • Covalent: Indexer
    • Tools
      • Vince Chain Explorers
      • Oracles
      • Contract Verification
      • Tools & Plugins
      • Indexers
      • Vince Chain Client Integrations
    • API
      • Networks
      • Vince Clients
      • Ethereum JSON-RPC
      • Cosmos gRPC and REST Routes
      • Tendermint RPC
      • Snapshots & Archive Nodes
    • Frequently Asked Questions
  • 3. Vince Chain Protocols
    • Technical Architecture
      • Cosmos SDK
      • What is CometBFT?
      • Is Vince Chain compatible with EVM?
      • Contributing to Vince Chain
    • Vince Chain CLI
      • Configuration
      • Working with Docker
      • Single Node
      • Multi Node
      • CLI Commands
    • Concepts
      • Accounts
      • Vince Chain Accounts
        • Addresses and Public Keys
        • Address conversion
        • Key output
      • Querying an Account
        • Cosmos gRPC and REST
        • JSON-RPC
      • Chain ID
      • Vince Chain’s Identifiers
      • The Chain ID
      • Vince Chain ID Structure/Format
      • Encoding
        • Ethereum’s Recursive-Length Prefix (RLP) Encoding
        • Cosmos SDK Encoding
      • IBC Relayers
        • IBC layers
        • Restore & Manage Keys
      • Restore & Manage Keys
      • Keyring
        • Operating Systems (OS) Backends
        • File
        • Password Store
        • KDE Wallet Manager​
      • Transactions
        • Ethereum transactions
        • Cosmos Transactions
        • Vince Chain Transaction
      • Tokens
        • Overview
        • Vince Chain (VCE)
        • Ethereum (ETH)
        • Cosmos (ATOM)
      • Gas and Fees
        • What is Gas?
        • Why transaction fees are important.
        • Calculating Network Gas
        • Are Gas also fees? —What’s the relationship?
    • Modules
    • Module Accounts
    • Bugs
    • IBC Channels
    • Security
    • Metrics
    • Frequently Asked Questions
  • 4. Technical Documentation
    • Quick Start
    • Vince Tokenomics
    • Staking/Delegation
    • Set Up Validators
    • Keys and Wallets
    • JSON RPC & WebSockets
    • Node Requirements
    • Vince Chain Validators
      • Disk Space Optimization
      • Rewards Management
      • Validator Concepts
      • FAQ
    • Vince Chain Governance
    • Grants & Bounties
    • Resources
Powered by GitBook
On this page
  1. 2. Vince Chain x Developers

Building a dApp backend

A backend is where the rough work is mostly done. However, decentralized protocols may not necessarily need a backend. It is just as it is for CMS platforms where the backends are precompiled or readily available. A dApp used for basic transactions and protocols may not necessarily need a backend; However, its frontend must be compatible with the underlying blockchain or host on which its smart contracts run. Developers may use our standard libraries, such as VinceJs and ether.js, as backends for their dApps. Using our library and resources as backend has benefits:

  • Security. No matter how good you are at dApp development, you cannot deny the essential place of security. Our backend libraries are tamper-proof and free of bugs, making them a haven for your dApp to thrive.

  • Speed. Uptime is another quality feature every blockchain must have. Surprisingly, many blockchains are still lacking in this area. This is where we come into the picture. You can count on Vince Chain to build fast dApps and protocols.

  • Transparency. Decentralized finance (DeFi) should be built on transparency, which is the prayer of every DeFi enthusiast. Our on-chain activities are public, allowing everyone to track and monitor our activities in real-time.

  • Turing completeness. Our libraries are built to withstand extreme conditions regardless of the condition or environment

  • Isolation. Limitations emanating from badly written contracts cannot hamper the activities of our network due to our isolation property.

  • Decentralization. Vince Chain is as decentralized as “decentralization” itself.

If a dApp must need a backend, then the dev team must ensure it is hosted on a protocol that possesses the above-listed attributes. Nevertheless, regardless of whether a backend is needed for a dApp, the dev team must still consider the above features for both front-end and back-end development. This will help the project or dApp stand the test of time.

PreviousWallet IntegrationNextTestnet

Last updated 2 years ago