📃
OmniOne Developer Site
  • Introduction
  • Manager console guide
    • To begin with...
      • Wallet Settings
      • Select an Account
      • The Issuer/SP account creation
      • Issue access token for the OmniOne Agent
    • Issuer Console
      • Claim
      • VC Type
      • VC Format
      • Issue the VC Information
      • My request list
    • SP Console
      • Service List
      • Token Transaction History
      • My service request
  • Server system construction
    • To begin with...
      • Server Wallet creation and Key settings
      • Collect the Issuer and SP's DID
      • application.properties settings
    • Server default environment configuration per IDE
      • Spring Tool Suite 4
      • IntelliJ IDEA
    • Building the Issuer system
      • Issuer server guide(JAVA)
    • Building the SP system
      • SP server guide (JAVA)
  • Checking Blockchain data
    • Check Agent API
      • bp
      • Committee
      • DID
      • executor
      • key
      • pDID
      • player
      • policy
      • txinfo
      • txissue
      • vc
      • version
      • response codes
  • SDK instruction guide
    • Core SDK Guide
      • Java Wallet
        • IWKeyManager
        • IWDIDManager
        • IWRecoveryManager
        • ZkpException
        • IWException
      • iOS Wallet
        • IWKeyManager
        • IWDidManager
        • IWClaimManager
        • IWRecoveryManager
        • IWErrorManager
        • Enum
    • Server SDK Guide
      • Java
        • ServerInfo
        • IssuerApi
        • SpApi
        • VcResult
        • VcInitParam
        • VCRegParam
        • VcVerifyParam
        • SpProfileParam
    • Omni App Link SDK
      • Server
      • Android
      • IOS
  • Node creation
    • Full Node creation
      • Full Node by using Docker
        • Docker Installation
        • Building Full Node
        • Full Node settings
      • Installation type Full Node
        • Full Node installation
    • BP Node creation
      • BP Node by using Docker
        • Docker Installation
        • Building BP Node
        • BP Node settings
          • keosd/BP Node executing simultaneously
      • Installation type BP
        • Node Installation
        • Executing Node
        • Node settings
        • BP Vote
Powered by GitBook
On this page
  • OmniOne Source download
  • Wallet and Key issuance
  • Issuing Wallet
  • opening the Wallet
  • Checking wallet list
  • Wallet unlock
  • Issuing Private Key
  • Adding Private Key
  • Executing keosd and nodeos
  • Executing keosd
  • Executing Node
  • Checking Node block data

Was this helpful?

  1. Node creation
  2. Full Node creation
  3. Installation type Full Node

Full Node installation

OmniOne Source download

It is required to have a source to build a node. Please open either terminal or Shell and enter the following command.

# Source clone
~# git clone --recursive [source URL]
~# cd eos

~# ./script/eosio_build.sh

After completing the build, set "eos/build/bin" folder as the environment variable.

Wallet and Key issuance

Issuing Wallet

Wallet is used to do a transaction signature by storing the private key to the encrypted file. Use the following command to create a wallet.

# [Local directory]/eos/build/bin/ Register the folder as environment variables to enter command simply.  
~# cleos wallet create --to-console

# in a case when the environment variable is not set, please use it as below.
# This command will be omited from the next step.
~# [local directory]/eos/build/bin/cleos wallet create --to-console

Log as below will be generated as the following command executes.

Creating wallet: default
Save password to use in the future to unlock this wallet.
Without password imported keys will not be retrievable.
"PW5KeERwdF3trFFpd....................t42S9XCw2"

Please store the password where it cannot be exposed.

opening the Wallet

When starting keosd instance, the wallet is locked in default. Execute the following command to Open the Wallet.

~# cleos wallet open

Checking wallet list

~# cleos wallet list

Wallets:
[
  "default"
]

Wallet unlock

Wallet my be open through "cleos wallet open" command but it is still at unlocked status. unlock by using the wallet password stored above.

~# cleos wallet unlock

when a message that indicates to enter a password appears, enter it then press enter.

Next, execute the following command.

~# cleos wallet list

Wallets:
[
  "default *"
]

Please check whether it has the asterisk behind default on the list. The asterisk indicates that the wallet is not locked.

Issuing Private Key

Private Key can be issued through cleos. Execute the following command to issue Private Key.

~# cleos create key --to-console -f passwd
Private key: 5JgVKptje2...W6nt1JeaH9yTBLqiNq8sF
Public key: EOS755TUwb...WzW92H7hBjVPorHKgRHSz

Adding Private Key

Private Key can be added by executing the following command in the wallet.

~# cleos wallet import

"[local directory]/eos/build/bin/keosd" launched
private key: 5KQwrPbwdL6PhXu...eyXtP79zkvFD3

Executing keosd and nodeos

Executing keosd

Use the following command to execute keosd.

~# keosd &

When error as below occurs, terminate keosd that is running on the background by using pkill keosd command then type keosd &.

Failed to lock access to wallet directory; is another keosd running?
    {}
    thread-0  wallet_manager.cpp:304 initialize_lock

message as below will be printed if it is executed normally.

info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/node/get_supported_apis
info  2020-07-16T02:49:20.505 thread-0  wallet_api_plugin.cpp:69      plugin_startup       ] starting wallet_api_plugin
info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/wallet/create
info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/wallet/create_key
info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/wallet/get_public_keys
info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/wallet/import_key
info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/wallet/list_keys
info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/wallet/list_wallets
info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/wallet/lock
info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/wallet/lock_all
info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/wallet/open
info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/wallet/remove_key
info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/wallet/set_timeout
info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/wallet/sign_digest
info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/wallet/sign_transaction
info  2020-07-16T02:49:20.505 thread-0  http_plugin.cpp:699           add_handler          ] add api url: /v1/wallet/unlock

Executing Node

Next, is a command that executes Node. When a command is executed it loads the default plug-in, sets the server address, uses CORS, adds contract partially, and records debugging and logs.

# Make this command to sh(Shell executing file) to execute easily.
~# nodeos -e -p eosio \
--plugin eosio::producer_plugin \
--plugin eosio::producer_api_plugin \
--plugin eosio::chain_api_plugin \
--plugin eosio::http_plugin \
--plugin eosio::history_plugin \
--plugin eosio::history_api_plugin \
--filter-on="*" \
--access-control-allow-origin='*' \
--contracts-console \
--http-validate-host=false \
--verbose-http-errors >> nodeos.log 2>&1 &

local directory can be skippable and stored in the root folder.

Checking Node block data

Execute the next command to check whether Nodeos is creating a block.

~# tail -f [local directory]nodeos.log

Press ctrl + c button to terminate the Log pritning screen

~# curl http://localhost:8888/v1/chain/get_info
PreviousInstallation type Full NodeNextBP Node creation

Last updated 4 years ago

Was this helpful?

Chekcing the node status