VeChain Docs
  • Welcome to VeChain
  • Blockchain Basics
    • Introduction to blockchain
    • Introduction to digital property
    • The evolution of the internet
  • Introduction to VeChain
    • About the VeChain blockchain
      • Consensus Deep Dive
      • Governance
    • Dual-Token Economic Model
      • VeChain (VET)
      • VeThor (VTHO)
    • Acquire VeChain Assets
    • Sustainability
  • Core Concepts
    • Networks
      • Thor Solo Node
      • Testnet
      • Mainnet
    • Nodes
      • Node Rewards Programme
    • Blocks
      • Block Model
    • Transactions
      • Transaction Model
      • Transaction Fees
      • Transaction Calculation
      • Meta Transaction Features
        • Transaction Uniqueness
        • Controllable Transaction Lifecycle
        • Clauses (Multi-Task Transaction)
        • Fee Delegation
          • Multi-Party Payment (MPP)
          • Designated Gas Payer (VIP-191)
        • Transaction Dependency
    • Block Explorers
    • Wallets
      • VeWorld
        • User Guide
          • Setup
          • Wallet
          • Signing
          • Activities
          • Settings
        • FAQ
      • Sync2
        • User Guide
          • Setup
          • Wallet
          • Signing
          • Activities
          • Settings
        • FAQ
      • Sync
        • User Guide
          • Wallet
          • Ledger Device
          • Browser dApps and web
          • Interact with dApps
          • Activities
          • Settings
          • Report an Issue
          • Contributing
        • FAQ
    • EVM Compatibility
      • VeChain Modifications
      • Methodology
      • Test Coverage
        • Gas model
        • Raw transaction
        • hardhat specific
          • Ganache failures
          • evm_increaseTime
        • Failures in constructor
        • eth_sign
        • Contract address prediction
        • BadBeacon proxy address at 0x1
      • How to Recreate
      • Additional Information
        • Using Governance Contracts
        • ERC1820/ERC777 Testnet
        • Delegate Options
    • Account Abstraction
      • UserOperation
      • Bundler
      • EntryPoint Contract
      • Account Factory Contract
      • Paymaster Contract
    • Token Bound Accounts
  • How to run a node
    • Nodes
    • How to run a Thor Solo Node
    • Custom Network
    • Connect Sync2 to a Thor Solo Node
  • Developer Resources
    • Getting Started
    • How to build on VeChain
      • Connect to the Network
      • Read Data
        • Read Blocks
        • Read Transactions
        • Read Accounts
        • States & Views
        • Events & Logs
        • VET Transfers
      • Write Data
        • Transactions
        • Fee Delegation
      • Listen to Changes
        • Events
        • VET Transfers
        • Transactions
        • Blocks
        • Beats
      • Build with Hardhat
      • Utilities
        • BigInt and Unit-Handling
        • Name Service Lookups
    • Example dApps
      • Buy me a Coffee
      • Token Bound Accounts
      • PWA with Privy and Account Abstraction
    • EVM Compatibility for Developers
      • Key Architectural Differences and Optimizations
      • Practical Implications for Developers: Key Considerations
      • RPC Methods (Detailed Breakdown)
      • Frequently Asked Questions (FAQs)
      • VeChain Blockchain Specifications
      • Key Differences Between VeChain and Ethereum (Summary)
      • Best Practices for Developing on VeChainThor
    • How to verify Address-Ownership
      • Next.js Session Verification
    • Debug Reverted Transactions
    • Account Abstraction
    • VIP-191: Designated Gas Payer
      • How to Integrate VIP-191 (I)
      • How to Integrate VIP-191 (II)
      • How to Integrate VIP-191 (III)
    • Index with Graph Node
      • Setup with Docker
      • Index with OpenZeppelin
        • Create Subgraph Project
        • Configure Contracts
        • Deploy Subgraph and start Indexing
        • Track Subgraph Indexing
        • Access Subgraph
        • Update Subgraph
    • SDKs & Providers
      • SDK
        • Architecture
        • Accounts
        • Bloom Filter
        • Certificates
        • Contracts
        • Cryptography
        • Debug
        • Encoding
        • Polls
        • Subscriptions
        • Thor Client
        • Transactions
      • Thor DevKit
        • Installation
        • Usage
          • Cryptography
          • Accounts
          • Encoding
          • Transactions
          • Certificates
          • Bloom Filter
      • DApp Kit
        • v2
          • Installation
          • React
            • Installation
            • Usage
          • Vanilla JS
            • Installation
            • Usage
          • Core
            • Installation
            • Usage
          • Theme Variables
          • i18n
        • v1
          • Installation
          • React
            • Installation
            • Usage
          • Vanilla JS
            • Installation
            • Usage
          • Core
            • Installation
            • Usage
          • Theme Variables
          • i18n
          • Node Polyfills
          • V0 to V1
        • v0
          • Installation
          • Usage
          • React
            • Installation
            • Usage
          • Vanilla (UI)
            • Installation
            • Usage
          • Styles (UI)
          • i18n
      • DevPal
      • Web3-Providers-Connex
        • Installation
        • Usage
      • Connex
        • Installation
        • API Specification
    • Frameworks & IDEs
      • Hardhat
      • Remix
    • Built-in Contracts
    • VORJ
    • Useful Links
  • How to contribute
Powered by GitBook
On this page
  • Key Features
  • Online Functionality
  • License

Was this helpful?

  1. Developer Resources
  2. SDKs & Providers

Web3-Providers-Connex

PreviousDevPalNextInstallation

Last updated 1 year ago

Was this helpful?

The web3-providers-connex library implements the JSON-RPC provider defined in for the VeChainThor blockchain. The provider is compatible with and , allowing developers to use both libraries to interact with the VeChainThor blockchain, via Connex.

Available on GitHub .

Key Features

The web3-providers-connex library offers a wide range of functionalities related to the VeChainThor blockchain and dApp development. Some of the key features include:

  1. web3.js support: web3-providers-connex enables developers to interact with the VeChainThor blockchain with the familiar web3.js library.

  2. ethers.js support: web3-providers-connex enables developers to interact with the VeChainThor blockchain with the familiar ethers.js library.

  3. Supports all of the key features of Connex:

    1. Blocks and node status: The library enables developers to interact with and retrieve information about blocks on the VeChainThor blockchain. This includes accessing block data and querying the status of connected VeChain nodes.

    2. Accounts: Facilitates interactions with Externally Owned Accounts (EOAs), allowing developers to manage and transact with individual user accounts on the VeChainThor blockchain. This includes sending VET tokens and interacting with VTHO (VeThor) tokens.

    3. Smart Contracts: Developers can interact with and manage smart contracts deployed on the VeChainThor blockchain. This includes deploying smart contracts, invoking their functions, and retrieving contract data.

    4. Transactions: Create and broadcast transactions on the VeChainThor blockchain. Developers can initiate various transactions, such as token transfers, contract interactions, and asset management.

    5. Certificates: Manage certificates and certificate-related operations on the blockchain. Certificates are often used for identity verification and access control in dApps.

    6. Queries: Efficiently query the VeChainThor blockchain. This includes querying transaction details, contract state, and other relevant blockchain information for dApp development.

Online Functionality

web3-providers-connex serves as an "online" library, primarily used for dApp development and blockchain-related operations that can be performed online. For example, users can use web3-providers-connex to create, sign and broadcast transactions to the VeChainThor blockchain network.

License

The GNU Lesser General Public License v3.0 is an open-source license that grants users the freedom to use, modify, and distribute the software under certain conditions. It ensures that users have access to the source code, can make improvements, and distribute their modifications while also preserving the rights of the original authors.

web3-providers-connex is licensed under the GNU Lesser General Public License v3.0 (LGPL-3.0). The full text of the license can be found in the LICENSE file included in the .

For more details about the GNU Lesser General Public License v3.0, please visit the .

EIP-1193
web3.js
ethers.js
here
repository
GNU website