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
  • Step 1: Deploying your node on Azure using the browser interface
  • Step 2: Wait for a 1.000 blocks
  • Optional: Deploying your node on Azure using the cmd-line interface
  1. Running a node
  2. Public node
  3. Cloud installation

Microsoft Azure

This page shows the 2 steps needed to get an LTO Network node up and running using Microsoft Azure, specifically Azure Container Instances (Not to be confused with Azure Kubernetes Services).

PreviousIBM CloudNextOKD (OpenShift)

Last updated 1 year ago

So you decided you want to be part of the LTO Network, awesome!

A great way to be part of the community is by actively participating as a node in the network.

Make sure to check out the Prepare: before continuing. The node setup pages assume you utilize a 2-wallet setup for extra safety.

Below the 2-step setup procedure using the browser there is an optional procedure for using the command-line interface.

Step 1: Deploying your node on Azure using the browser interface

LTO Public Node on Azure — Main screen

As mentioned before we’re configuring a Container instance using ACI. This is not to be confused with AKS, Azure Kubernetes Services. AKS can be used to setup a cluster for container orchestration. This is overkill for what we’re trying to achieve at this time.

Please type “container” (without an s) in the box and “Container instances” will appear. Click Container instances.

First step is to configure some basic settings for your new container instance. You can not really go wrong here. The subscription entry displayed will display on your Azure subscription. You might need to create a Resource group using create new. Please name your container, select a Region where you want to host your container and make sure to enter the image namecorrectly. Before going to the next step we need to change 1 more thing.

Let’s boost the memory a little from 1.5 GB default to 2 GB by clicking Change size. Now click on Next: Networking to go to the next step.

Wow, this one is easy. We don’t need to change anything here. Maybe you want to enter the DNS name label. It’s up to you. This is not a requirement. No ports need to be added at this point. You can leave it at default.

Please click Next: Advanced so we can start configuring our node.

Alright at this stage you want to configure your LTO_WALLET_SEED. This is an important step. This should be the seed of the wallet you use for staking. We configure the LTO_WALLET_PASSWORD to encrypt the seed. The LTO_NODE_NAME is the name your node will use to identify itself on the LTO Network.

A future update might include the usage of secrets to secure our configuration.

When you’re done putting in these variables click on Review + create.

If validation is successful click Create to create your container and wait for the deployment to finish.

The deployment might take 1–2 minutes to complete.

Your LTO Public Node is now running on Azure using Azure Container Instances. Not convinced? Let’s double check :) Please click on Go to resource.

Let’s click on Containers under Settings. Now click on Connect and select a bash shell to Connect. A terminal will open. Activate the terminal by clicking on the black screen.

Using the cd (change directory) command we will browse to the /lto/log directory. In this directory you’ll find our logfile called: lto.log.

Start a tail like in the above screenshot and follow the progress as your node downloads the blockchain or maybe is already adding MicroBlocks.

That’s it. You’ve successfully mastered setting up a LTO Network public node on Microsoft Azure. Awesome!

Step 2: Wait for a 1.000 blocks

Optional: Deploying your node on Azure using the cmd-line interface

Optionally you can start your container using the command-line interface. A big advantage of using the CMD is that you can automate everything.

Use the following commands to kick-off your LTO Network Public node using command line:

CONTAINER_RESOURCE_GROUP="lto-network-rg"
CONTAINER_LOCATION="westeurope"
CONTAINER_NAME="lto-network-node"
CONTAINER_NODE_NAME="YOUR NAME"
CONTAINER_WALLET_SEED="SEED1 SEED2 SEED3"
CONTAINER_WALLET_PASSWORD="PASSWORD"

az group create --name $CONTAINER_RESOURCE_GROUP --location $CONTAINER_LOCATION

az container create --resource-group $CONTAINER_RESOURCE_GROUP --name $CONTAINER_NAME \
 --image ltonetwork/public-node \
 --cpu 1 \
 --memory 2 \
 --os-type linux \
 --ports 80 \
 --restart-policy Always \
 --environment-variables "LTO_NODE_NAME"="$CONTAINER_NODE_NAME" \
 --secure-environment-variables "LTO_WALLET_SEED"="$CONTAINER_WALLET_SEED" "LTO_WALLET_PASSWORD"="$CONTAINER_WALLET_PASSWORD"

With just these two commands you have successfully launched your LTO Network Public node container application. Using the following command you can view your nodes progress:

az container logs --resource-group $CONTAINER_RESOURCE_GROUP --name $CONTAINER_NAME

You can double check your environment variable configuration using the following commands:

az container exec --resource-group $CONTAINER_RESOURCE_GROUP --name $CONTAINER_NAME --exec-command "/bin/bash"
$ echo $LTO_WALLET_SEED 
$ echo $LTO_WALLET_PASSWORD
LTO Public Node on Azure — No port / network changes required
LTO Public Node on Azure — Setup your environment variables
LTO Public Node on Azure — Deployment of Container instance is running
LTO Public Node on Azure — A successful deployment of your LTO Public Node container on Azure

You can find the LTO Network Explorer at It shows you the blocks generated, by who, when, how big they are and how many transactions are in the block.

After launching your node check the to see the number of the last block. Wait till another 1.000 blocks are generated and expect your node to be part of the LTO Network.

Utilize the available to get more insights into the network and your participation. Let's build a secure and useful network together!

Depending on your stake (the number of LTO tokens you have in the “2nd wallet”) it will take more or less time for you to start earning LTO. Be patient and be happy. Welcome to the amazing LTO Network community! Read more .

https://explorer.lto.network.
Explorer
Community Tech Tools
about community programs
Setup your wallet page
LTO Public Node on Azure — Base configuration
LTO Public Node on Azure — Configure memory
LTO Public Node on Azure — Validation passed — Your screen might look slightly different
LTO Public Node on Azure — Connected to the console
LTO Public Node on Azure — Tailing your Node’s logfile