DOCSEARCHbyAlgolia
Submit Docs

Point Network Documentation

website·Indexed 32 days ago

https://docs.pointnetwork.io/

Developer and validator guides for Point Chain, featuring documentation on JSON-RPC methods, the pointd CLI, node setup, and validator security. Includes technical specifications for EVM interaction, state sync, chain upgrades, and keyring management.

Tokens
39.5K
Snippets
223
Records
335
Agent score
50%

What's inside Point Network

  1. Overview of Point Chain Multisig Accounts

    A multisig account on Point Chain is a special account that requires a threshold number of signatures from a set of specified public keys to authorize transactions. This is used to increase account security or ensure multi-party consent. To be valid, a transaction must be signed by at least the minimum threshold of the involved keys; otherwise, the resulting multisignature is invalid.

  2. Overview of Point Network environments

    Point Network provides three primary environments depending on the stage of development and deployment:

    • YNET: The default live environment for the Alpha version of Point Network.
    • e2e: An end-to-end environment used to simulate YNET on a single local developer machine for testing deployments and integrating new services.
    • zappdev: A lightweight development environment specifically optimized for building, testing, and deploying Zapps (applications that run on Point Network).

  3. Overview of Tendermint KMS for Point Chain

    Tendermint KMS (tmkms) is a Key Management Service that separates key management from Tendermint nodes. It provides improved security, risk management policies, a unified API for various Hardware Security Modules (HSMs), and double-signing protection. For maximum security, it is recommended to run the KMS service on a separate physical host from the validator node.

  4. Overview of Point Network

    Point Network is a holistic implementation of a decentralized internet (Web 3.0). It aims to provide a unifying infrastructure of main protocols for other Web 3.0 projects—such as social media, trading platforms, and streaming services—to build upon. The network is designed to be open, censorship-resistant, permissionless, and privacy-oriented, with integrated programmable money, intended to return data control from corporations and nation-states to the individual user.

  5. Overview of Point Network dapp development

    dApps on Point Network can be built as standard EVM-based applications or by using the Point SDK. Using the Point SDK is highly recommended for new dapps because it automatically proxies connections to the Point Node, simplifying the development process.

  7. Understand Point Chain's Architectural Foundation

    Point Chain is built using the Cosmos SDK to provide modularity and composability. It utilizes Tendermint Core's BFT (Byzantine Fault Tolerant) consensus engine to achieve fast-finality and Proof-of-Stake (PoS) functionality. The architecture separates the consensus process from the application state via the Application Blockchain Interface (ABCI), allowing Point Chain to function as an ABCI application that replaces Ethereum's Proof-of-Work (PoW) with Tendermint's consensus.

  8. Understand Point Chain upgrade categories

    Chain upgrades for Point Chain are categorized by their scheduling, impact on compatibility, and data requirements:

    • Planned vs. Unplanned: Planned upgrades are scheduled at a specific block height via proposals. Unplanned upgrades require validators to gracefully halt nodes at a coordinated point.
    • Breaking vs. Non-breaking: Based on Semver (vX.Y.Z). Major versions (X) are backward incompatible. Minor versions (Y) add features and may be state-breaking. Patch versions (Z) are backward compatible bug fixes.
    • Data Reset: Some upgrades (like rollbacks or hard forks) require a full reset of the blockchain state while retaining validator keys.
    • Automatic vs. Manual: Upgrades can be managed automatically using the cosmovisor process or performed manually by replacing the binary.

  10. Point Chain client interface overview

    The Point Chain provides multiple client interfaces to support both Cosmos and Ethereum-style transactions and queries. Each interface serves a specific purpose and operates on a default port.
    InterfaceDescriptionDefault Port
    Cosmos gRPCQuery or send Point Chain transactions using gRPC9090
    Cosmos RESTQuery or send Point Chain transactions using HTTP RESTful API (gRPC-Gateway)9091
    Ethereum JSON-RPCQuery Ethereum-formatted transactions/blocks or send Ethereum txs8545
    Ethereum WebsocketSubscribe to Ethereum logs and events emitted in smart contracts8586
    Tendermint RPCQuery transactions, blocks, consensus state, broadcast transactions, etc.26657
    Tendermint WebsocketSubscribe or unsubscribe to Tendermint ABCI events26657
    CLIQuery or send Point Chain transactions via terminalN/A

  11. Point Network Node Architecture Overview

    The Point Network Node prototype is composed of several key modules including an Application Loader, Context Manager, Logger, Process Manager, Configuration (Application and User), Storage (LevelDB, Encryption, Compression), Console, Network (DHT, Blockchain), ZProxy Server, Node Server, API Server, and Smart Contracts.

  12. Interact with Point Chain using JSON-RPC

    Point Chain provides a JSON-RPC server that allows developers to interact with the EVM, read Ethereum-formatted transactions, and send transactions to the network. It supports JSON-RPC over HTTP and WebSocket transports, which must be enabled via command-line flags or the app.toml configuration file.