LTO Network
  • Getting started
  • What is LTO Network?
  • Tutorials
    • Buying and staking LTO
      • Exchanges
        • Binance
        • AscendEX (Bitmax)
        • Uniswap
        • PancakeSwap
        • Other exchanges
      • Creating your LTO web wallet
      • Using the LTO token bridge
      • Staking LTO tokens
    • Mining
      • Setup your node wallets
      • Node management
      • Public community nodes
    • Anchoring
      • Hashing
    • LetsFlow
  • Wallets
    • LTO Web Wallet
      • Using Ledger
    • Universal Wallet
    • LTO CLI
    • Third-Party Wallets
      • Stakely.io wallet
        • Web wallet
        • Commandline
    • ERC20 Token Swap
  • Running a node
    • Public node
      • Installation Guide
        • Mainnet & Testnet
        • Requirements
        • Configuration
        • (Virtual) Machine
        • Nginx reverse proxy (optional)
        • Troubleshooting FAQ
      • Cloud installation
        • Alibaba Cloud
        • AWS Elastic Beanstalk
        • Google Cloud
        • IBM Cloud
        • Microsoft Azure
        • OKD (OpenShift)
        • Raspberry Pi (Expert)
        • Ubuntu Linux with Container
        • Windows with Container
      • REST API
        • Address
        • Wallet
        • Lease Transactions
        • Peers
        • Blocks
        • Utils
        • FAQ
      • Security Notes
      • FAQ
      • Exchange integration guide
    • Anchor node
      • Installation Guide
        • Linux
        • MacOS
        • Windows
      • REST API
    • Identity node
      • Installation guide
        • Linux
        • MacOs
        • Windows
      • Configuration
        • Trust network
      • REST API
    • Workflow node
      • Installation Guide
        • MacOS
        • Windows
        • Ubuntu Linux
      • REST API
  • Ownables
    • What are Ownables?
    • Making your first ownable
    • Ownables SDK
      • Prerequisites
      • Setup
    • Ownables Architecture
      • Smart Contract
      • Widget
    • Ownables Bridge
  • Libraries
    • JavaScript
      • Accounts
      • Transactions
      • Event chain
      • Messages
      • Identities
      • HTTP Authentication
    • Python
      • Accounts
      • Public layer
    • PHP
      • Accounts
      • Identities
      • Public layer
      • Private layer
      • HTTP Authentication
      • Commandline scripts
    • Java
  • Protocol
    • Cryptography
    • Accounts
      • ED25519
      • secp256k1
      • secp256r1
    • Identities
      • Decentralized identifiers (DID)
      • Trust network
      • Verifiable credentials
    • Public layer
      • Transactions
        • Transfer
        • Lease
        • Cancel Lease
        • Mass Transfer
        • Set Script
        • Data
        • Anchor
        • Association
        • Revoke Association
        • Sponsorship
        • Cancel Sponsorship
        • Register
        • Burn
        • Mapped Anchor
        • Statement
      • Transaction fees
      • Consensus protocol
      • Activation Protocol
      • Data Structures
    • Private layer
      • Event chain
        • Event
      • Messaging
        • Sending messages
Powered by GitBook
On this page
  • Becoming a public community node
  • Prerequisites
  • Information disclosure
  • Web wallet listing/lease tab
  1. Tutorials
  2. Mining

Public community nodes

A step-by-step tutorial on becoming a public community node.

PreviousNode managementNextAnchoring

Last updated 3 years ago

Becoming a public community node

Anyone can become a public node on the LTO network as long as all prerequisites are met, the necessary contact info has been made available to the community, and basic git proficiency is part of your repertoire.

Prerequisites

To take your node public you obviously need to set up your own node first. If you haven't done so feel free to refer to our tutorials in this regard:

Furthermore, it helps a lot if you already demonstrated your ability to do payouts, e.g., through the community-provided payout script. Refer to the Node management tutorial for more information.

Information disclosure

The team keeps track of the public community nodes in a . To get listed there you need to provide with the following info:

  • Node LTO Address

  • Your Telegram Name

  • Node Name

  • Node Website / Telegram Channel

  • The Payout schedule

Web wallet listing/lease tab

The last step is getting listed in the official web wallet. You will require a github account and you will need to create a pull request with your node as part of the lease tab list.

Now you should have your local fork of the LTO UI project in your own github. To include your node in the community nodes leasing tab you will need to edit the communityNodes.json. Input your node data at the end of the list, same as the other nodes. The list is randomized before being displayed in the web wallet lease tab, so the position in the web wallet is different each time.

First things first, head over to github, and if you don't have an account already create one. Once you're done go to the and fork the project.

All that's left is for you to create a pull request with the . That's it, you're done. As soon as the pull request is granted by the LTO team your node will be part of the leasing tab the next time there is a new build. Congratulations!

Setup your node wallets
Public node
Node management
separate document
Christian Zhang
LTO UI project page
original LTO UI project
The lease tab lists public community nodes.
Fork the LTO UI project to edit the necessary file.
Edit the communityNodes.json with a text editor of your choice and you're good to go.
Create a pull request after editing the communityNodes.json file.