Blockchain network deployment — Apla Blockchain Platform Guide documentation (2024)

Table of Contents
Example deployment¶ Deployment stages¶ Backend deployment¶ Deploying the first node¶ Deploying additional nodes¶ Frontend deployment¶ Software prerequisites¶ Building Molis App¶ Blockchain network configuration¶ Creating the founder’s account¶ Importing apps, roles, and templates¶ Adding first node to the list of nodes¶ Adding extra validating nodes¶ Adding a member to Consensus role¶ Creating the node owner’s account¶ Adding node owner to Validator role¶ Adding the validating node via voting¶ FAQs

This guide demonstrates how to deploy your own blockchain network.

Note

  • If you want to try the Apla blockchain network instead, check out Apla Testnet.
  • If you want to deploy a local testing environment quickly, consider using Apla quickstart which is based on Docker images.

Example deployment

This guide deploys the example blockchain network of three nodes.

The network has three nodes:

  • Node 1 is the first node in the blockchain network. It can generate new blocks and send transactions from the clients connected to it.
  • Node 2 is an extra validating node. It can generate new blocks and send transactions from the clients connected to it.
  • Node 3 is an extra node. It cannot generate new blocks but can send transactions from the clients connected to it.

Nodes are deployed in this configuration:

  • Each node will use its own instance of PostgreSQL database system.
  • Each node will use its own instance of Centrifugo service.
  • The go-apla services will be deployed on the same host with other backend components.

Addresses and ports used by nodes are described in the following table:

NodeComponentIP and Port
1PostgreSQL127.0.0.1:5432
1Centrifugo10.10.99.1:8000
1go-apla (TCP-server)10.10.99.1:7078
1go-apla (API-server)10.10.99.1:7079
2PostgreSQL127.0.0.1:5432
2Centrifugo10.10.99.2:8000
2go-apla (TCP-server)10.10.99.2:7078
2go-apla (API-server)10.10.99.2:7079
3PostgreSQL127.0.0.1:5432
3Centrifugo10.10.99.3:8000
3go-apla (TCP-server)10.10.99.3:7078
3go-apla (API-server)10.10.99.3:7079

Deployment stages

Your own blockchain network must be deployed in several stages:

  1. Backend deployment

    1. Deploying the first node
    2. Deploying additional nodes

  2. Frontend deployment

  3. Blockchain network configuration

    1. Creating the founder’s account
    2. Importing apps, roles, and templates
    3. Adding first node to the list of nodes

  4. Adding extra validating nodes

    1. Adding a member to Consensus role
    2. Creating the node owner’s account
    3. Adding node owner to Validators role
    4. Adding the validating node via voting

Backend deployment

Deploying the first node

First node is a special node because it must be used to start the blockchain network. First block of the blockchain is generated by the first node and all other nodes download the blockchain from it. The owner of the first node becomes the platform founder.

Dependencies and environment setup

sudo

All commands for Debian 9 must be run as a non-root user. But some system commands need superuser privileges to be executed. By default, sudo is not installed on Debian 9, and you must install it first.

  1. Become the root superuser.
su -
  1. Upgrade your system.
apt update -y && apt upgrade -y && apt dist-upgrade -y
  1. Install sudo.
apt install sudo -y
  1. Add your user to the sudo group.
usermod -a -G sudo user
  1. After the reboot, the changes take effect.
Go language

Install Go as described in the official documentation.

  1. Download the latest stable version of Go (> 1.10.x) from the Golang official site or via the command line:
wget https://dl.google.com/go/go1.11.2.linux-amd64.tar.gz
  1. Extract the package to /usr/local.
tar -C /usr/local -xzf go1.11.2.linux-amd64.tar.gz
  1. Add /usr/local/go/bin to the PATH environment variable (either to /etc/profile or $HOME/.profile).
export PATH=$PATH:/usr/local/go/bin
  1. For changes to take effect, source this file. For example:
source $HOME/.profile
  1. Remove the temporary file:
rm go1.11.2.linux-amd64.tar.gz
PostgreSQL
  1. Install PostgreSQL (> v.10) and psql:
sudo apt install -y postgresql
Centrifugo
  1. Download Centrifugo version 1.8.0 from GitHub or via command line:
wget https://github.com/centrifugal/centrifugo/releases/download/v1.8.0/centrifugo-1.8.0-linux-amd64.zip \&& unzip centrifugo-1.8.0-linux-amd64.zip \&& mkdir centrifugo \&& mv centrifugo-1.8.0-linux-amd64/* centrifugo/
See Also
Buy ENS Domain - Where to Buy ETH DomainsThe Developer’s Guide to Blockchain DevelopmentETH RegistrarThe importance for brands to secure .ETH domain names.  | Disruptive
  1. Remove temporary files:
rm -R centrifugo-1.8.0-linux-amd64 \&& rm centrifugo-1.8.0-linux-amd64.zip
Directories

For Debian 9 OS, it is recommended to store all software used by the blockchain platform in a separate directory.

This guide uses the /opt/apla directory, but you can use any directory. In this case, change all commands and configuration files accordingly.

  1. Make a directory for the blockchain platform:
sudo mkdir /opt/apla
  1. Make your user the owner of this directory:
sudo chown user /opt/apla/
  1. Make subdirectories for Centrifugo, go-apla, and node data. In this guide, all node data is stored in the directories with nodeX name, where X is the node number. Depending on which node you are deploying, this will be node1 for node 1, node2 for node 2, and so on.
mkdir /opt/apla/go-apla \mkdir /opt/apla/go-apla/node1 \mkdir /opt/apla/centrifugo \

Creating the database

  1. Change user’s password postgres to Apla’s default password. You can set your own password, but then you must change it in the node configuration file config.toml.
sudo -u postgres psql -c "ALTER USER postgres WITH PASSWORD 'apla'"
  1. Create a node current state database, for example ‘apladb’:
sudo -u postgres psql -c "CREATE DATABASE apladb"

Configuring Centrifugo

  1. Create Centrifugo configuration file:
echo '{"secret":"CENT_SECRET"}' > /opt/apla/centrifugo/config.json

You can set your own “secret”, but then you also must change it in the node configuration file config.toml.

Installing go-apla

  1. Download and build the latest release of go-apla from GitHub:
go get -v github.com/AplaProject/go-apla
  1. Copy the go-apla binary to the /opt/apla/go-apla directory. If you use the default Go workspace then the binary is located in the $HOME/go/bin directory:
cp $HOME/go/bin/go-apla /opt/apla/go-apla

Configuring the first node

  1. Create the node 1 configuration file:
/opt/apla/go-apla/go-apla config \ --dataDir=/opt/apla/go-apla/node1 \ --dbName=apladb \ --centSecret="CENT_SECRET" --centUrl=http://10.10.99.1:8000 \ --httpHost=10.10.99.1 \ --httpPort=7079 \ --tcpHost=10.10.99.1 \ --tcpPort=7078
  1. Generate node 1 keys:
/opt/apla/go-apla/go-apla generateKeys \ --config=/opt/apla/go-apla/node1/config.toml
  1. Generate the first block:

Note

If you are creating your own blockchain network. you must use the --test=true option. Otherwise you will not be able to create new accounts.

/opt/apla/go-apla/go-apla generateFirstBlock \ --config=/opt/apla/go-apla/node1/config.toml \ --test=true
  1. Initialize the database:
/opt/apla/go-apla/go-apla initDatabase \ --config=/opt/apla/go-apla/node1/config.toml

Starting the first node backend

To start the first node backend, you must start two services:

  • centrifugo
  • go-apla

If you did not create these as services, you can just execute binary files from their directories in different consoles.

  1. Run centrifugo:
/opt/apla/centrifugo/centrifugo \ -a 10.10.99.1 -p 8000 \ --config /opt/apla/centrifugo/config.json
  1. Run go-apla:
/opt/apla/go-apla/go-apla start \ --config=/opt/apla/go-apla/node1/config.toml

Deploying additional nodes

All other nodes (Node 2 and Node 3) are deployed like the first node with three differences:

  • You do not need to generate the first block. Instead, it must be copied to the node data directory from node 1.
  • The node must be configured to download blocks from node 1 via --nodesAddr option.
  • The node must be configured to use its own addresses and ports.

Node 2

Follow this sequence of actions:

  1. Dependencies and environment setup

  2. Creating the database

  3. Configuring Centrifugo

  4. Installing go-apla

  5. Create the node 2 configuration file:

    /opt/apla/go-apla/go-apla config \ --dataDir=/opt/apla/go-apla/node2 \ --dbName=apladb \ --centSecret="CENT_SECRET" --centUrl=http://10.10.99.2:8000 \ --httpHost=10.10.99.2 \ --httpPort=7079 \ --tcpHost=10.10.99.2 \ --tcpPort=7078 \ --nodesAddr=10.10.99.1

  6. Copy the first block file to Node 2. For example, you can do it via scp on Node 2:

    scp user@10.10.99.1:/opt/apla/go-apla/node1/1block /opt/apla/go-apla/node2/

  7. Generate node 2 keys:

    /opt/apla/go-apla/go-apla generateKeys \ --config=/opt/apla/go-apla/node2/config.toml

  8. Initialize the database:

    See Also
    The Costs of Implementing Blockchain: What You Need to Know - Rejolut

    ./go-apla initDatabase --config=node2/config.toml

  9. Run centrifugo:

    /opt/apla/centrifugo/centrifugo \ -a 10.10.99.2 -p 8000 \ --config /opt/apla/centrifugo/config.json

  10. Run go-apla:

    /opt/apla/go-apla/go-apla start \ --config=/opt/apla/go-apla/node2/config.toml

As a result, the node will download the blocks from the first node. This node is not the validating node, so it cannot generate new blocks. Node 2 will be added to the list of validating nodes later in this guide.

Node 3

Follow this sequence of actions:

  1. Dependencies and environment setup

  2. Creating the database

  3. Configuring Centrifugo

  4. Installing go-apla

  5. Create the node 3 configuration file:

    /opt/apla/go-apla/go-apla config \ --dataDir=/opt/apla/go-apla/node3 \ --dbName=apladb \ --centSecret="CENT_SECRET" --centUrl=http://10.10.99.3:8000 \ --httpHost=10.10.99.3 \ --httpPort=7079 \ --tcpHost=10.10.99.3 \ --tcpPort=7078 \ --nodesAddr=10.10.99.1

  6. Copy the first block file to Node 3. For example, you can do it via scp on Node 3:

    scp user@10.10.99.1:/opt/apla/go-apla/node1/1block /opt/apla/go-apla/node3/

  7. Generate node 3 keys:

    /opt/apla/go-apla/go-apla generateKeys \ --config=/opt/apla/go-apla/node3/config.toml

  8. Initialize the database:

    ./go-apla initDatabase --config=node3/config.toml

  9. Run centrifugo:

    /opt/apla/centrifugo/centrifugo \ -a 10.10.99.3 -p 8000 \ --config /opt/apla/centrifugo/config.json

  10. Run go-apla:

    /opt/apla/go-apla/go-apla start \ --config=/opt/apla/go-apla/node3/config.toml

As a result, the node will download the blocks from the first node. This node is not the validating node, so it cannot generate new blocks. Сlients can connect to this node and it can send transactions to the network.

Frontend deployment

Molis client can be build by the yarn package manager only on Debian 9 (Stretch) 64-bit official distributive with installed GNOME GUI.

Software prerequisites

Node.js

  1. Download Node.js LTS version 8.11 from the Node.js official site or via the command line:
curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash
  1. Install Node.js:
sudo apt install -y nodejs

Yarn

  1. Download Yarn version 1.7.0 from yarn GitHub repository or via command line:
cd /opt/apla \&& wget https://github.com/yarnpkg/yarn/releases/download/v1.7.0/yarn_1.7.0_all.deb
  1. Install Yarn:
sudo dpkg -i yarn_1.7.0_all.deb && rm yarn_1.7.0_all.deb

Building Molis App

  1. Download latest release of Molis from Molis GitHub repository via git:
cd /opt/apla \&& git clone https://github.com/AplaProject/apla-front.git
  1. Install Molis dependencies via Yarn:
cd /opt/apla/apla-front/ \&& yarn install

Adding the blockchain network configuration

  1. Create settings.json file that contains connections information about full nodes:
cp /opt/apla/apla-front/public/settings.json.dist \ /opt/apla/apla-front/public/public/settings.json
  1. Edit settings.json file in any text editor and add required settings in this format:
http://Node_IP-address:Node_HTTP-Port

Example settings.json file for three nodes:

{ "fullNodes": [ "http://10.10.99.1:7079", "http://10.10.99.2:7079", "http://10.10.99.3:7079" ]}

Building as Molis Desktop App

  1. Build the desktop app with Yarn:
cd /opt/apla/apla-front \&& yarn build-desktop
  1. The desktop app must be packed to the AppImage:
yarn release --publish never -l

After that, your application will be ready to use, but its connection settings cannot be changed in the future. If these settings will change, you must build a new version of the application.

Building as Molis Web App

  1. Build the web app:
cd /opt/apla/apla-front/ \&& yarn build

After building, redistributable files will be placed to the ‘/build’ directory. You can serve it with any web-server of your choice. Settings.json file must be also placed there. Note that you do not need to build your application again if your connection settings will change. Instead, edit the settings.json file and restart web-server.

  1. For development or testing purposes, you can build Yarn’s web-server:
sudo yarn global add serve \&& serve -s build

After this, your Molis Web App will be available at: http://localhost:5000

Blockchain network configuration

Creating the founder’s account

Create an account for the first node owner. This account is the founder of the new blockchain platform and will have administrator access rights.

  1. Run Molis (frontend).

  2. Import an existing account using the following data:

    • Backup payload is the node owner’s private key located in the /opt/apla/go-apla/node1/PrivateKey file.

      Note

      There are two private key files in this directory. PrivateKey file is for node owner’s account. It is used to create the node owner’s account. NodePrivateKey is the private key of the node itself and must be kept secret.

  3. Login under this new account. Because roles haven’t been created at this moment, use the Without role login option.

Importing apps, roles, and templates

At this moment, the blockchain platform is in the blank state. You can configure it by adding the framework of roles, templates and apps that support the basic ecosystem functions.

  1. Clone the applications repository.
cd /opt/apla \&& git clone https://github.com/AplaProject/apps.git

  1. In Molis, navigate to Developer > Import.

  2. Import apps in this order:

    1. /opt/apla/apps/system.json
    2. /opt/apla/apps/lang_res.json
    3. /opt/apla/apps/basic.json
    4. /opt/apla/apps/conditions.json

  3. Navigate to Admin > Roles and click Install default roles.

  4. Sign out of the system via the profile menu.

  5. Log into the system under the Admin role.

  6. Navigate to Home > Votings > Templates list and click Install default templates.

Adding first node to the list of nodes

  1. Navigate to Admin > Platform parameters and click the cogwheel icon for the full_nodes parameter.
  2. Specify the parameters for the first blockchain network node. Node’s public key is located in the /opt/apla/go-apla/node1/NodePublicKey file. Node owner’s key identifier is located in the /opt/apla/go-apla/node1/KeyID file.
{"api_address":"http://10.10.99.1:7079","key_id":"%node_owner_key_id%","public_key":"%node_public_key%","tcp_address":"10.10.99.1:7078"}

Adding extra validating nodes

Adding a member to Consensus role

By default, only members of the Consensus role (Apla Consensus asbl) can participate in votings required for adding extra validating nodes. It means that a member of the ecosystem must be appointed to this role before new validating nodes can be added.

In this guide, the founder’s account will be appointed as a sole member of the Consensus. In a production environment, this role must be assigned to members that perform platform governance.

  1. As an ecosystem founder, navigate to Home > Roles and click the Consensus role (Apla Consensus asbl).
  2. Click Assign and assign founder’s account to this role.

Creating the node owner’s account

  1. Run Molis (frontend)

  2. Import an existing account using the following data:

    • Backup payload is the node owner’s private key located in the /opt/apla/go-apla/node2/PrivateKey file.

  3. Login under this new account. Because a role hasn’t been assigned to this account, use the Without role login option.

  4. Navigate to Home > Profile and click on the new profile name.

  5. Add account details (profile name, description, etc.)

Adding node owner to Validator role

  1. As a new node owner:

    1. Navigate to Home > Candidates for the validators.
    2. Click Create request and fill the Candidates for the validators request form.
    3. Click Send request.

  2. As a founder:

    1. Login under the Consensus role (Apla Consensus asbl).
    2. Navigate to Home > Candidates for the validators.
    3. Start the voting for by clicking the “play” icon by the candidate’s request.
    4. Navigate to Home > Votings and click Update votings statuses.
    5. Click the voting name and vote for the node owner (click Vote).

As a result, node owner’s account will be assigned the Validator role.

Adding the validating node via voting

  1. As a founder, login under the Consensus role (Apla Consensus asbl).

  2. Navigate to Admin > Platform parameters and click the cogwheel icon for the full_nodes parameter.

  3. Specify the node 2 parameters:

    • TCP address is 10.10.99.2:7078.
    • API address is http://10.10.99.2:7079.
    • Key ID of the node founder is located in the /opt/apla/go-apla/node2/KeyID file.
    • Node’s public key is located in the /opt/apla/go-apla/node2/NodePublicKey file.

  4. Click Vote.

  5. Navigate to Home > Votings and click Update votings statuses.

  6. Click the “Voting for System param value” voting and vote for the system parameter change (Click Accept).

As a result, a new node will be added to the list of validating nodes.

Blockchain network deployment — Apla Blockchain Platform Guide documentation (2024)

FAQs

How to deploy a blockchain network? ›

  1. Step one: Decide on your network configuration. The structure of a blockchain network will be dictated by the use case it's serving. ...
  2. Step two: Set up a cluster for your resources. ...
  3. Step three: Set up your CAs. ...
  4. Step four: Use the CA to create identities and MSPs. ...
  5. Step five: Deploy peers and ordering nodes.

Read On ›
How is blockchain deployed? ›

Deploying the first node. First node is a special node because it must be used to start the blockchain network. First block of the blockchain is generated by the first node and all other nodes download the blockchain from it. The owner of the first node becomes the platform founder.

Discover More Details ›
Which blockchain network is best for DApps? ›

Top Blockchains
#NameTransactions
1BNB Chain BNB5.27M +0.85%
2Ethereum ETH1.49M -15.11%
3Polygon MATIC12.8M -1.15%
4TRON TRX45.61k -11.07%
21 more rows

Continue Reading ›
Is IBM blockchain free? ›

Simply follow instructions to deploy the blockchain console to get started. The free trial version is fully functional, meaning the product features available in the free trial version are identical to the paid version.

See Details ›
How to deploy blockchain on cloud? ›

Choose your deployment process

From your IBM Cloud account, you can deploy the IBM Blockchain Platform service from either the IBM Cloud Catalog or the Red Hat Marketplace. IBM Cloud Catalog Use the IBM Cloud Catalog to deploy blockchain to an IBM Kubernetes service or OpenShift cluster in IBM Cloud.

Find Out More ›
How to deploy a blockchain node? ›

📘 Info:
  1. Once you have logged on to the web app, click the Deploy a Node button in the middle of the Overview screen.
  2. The Deploy a Node area is your blockchain storefront. Here, you will find a full suite of Blockdaemon-hosted protocols.

Tell Me More ›
How does blockchain work step by step? ›

How does blockchain work?
  1. Step 1 – Record the transaction. A blockchain transaction shows the movement of physical or digital assets from one party to another in the blockchain network. ...
  2. Step 2 – Gain consensus. ...
  3. Step 3 – Link the blocks. ...
  4. Step 4 – Share the ledger.

Show Me More ›
How does a blockchain platform work? ›

Blockchain is a method of recording information that makes it impossible or difficult for the system to be changed, hacked, or manipulated. A blockchain is a distributed ledger that duplicates and distributes transactions across the network of computers participating in the blockchain.

Explore More ›
How to create a blockchain platform? ›

Steps to Develop a Blockchain Solution from Scratch
  1. Step 1: Identify a Problem to Solve. ...
  2. Step 2: Draft Your Business Requirements. ...
  3. Step 3: Identify a Consensus Mechanism. ...
  4. Step 4: Choose the Best Blockchain Platform. ...
  5. Step 5: Design Your Blockchain Nodes. ...
  6. Step 6: Plan Your Blockchain Configuration. ...
  7. Step 7: Build Your APIs.

Continue Reading ›
What is the difference between DApps and blockchain? ›

Decentralized applications, or dApps, are software programs that run on a blockchain or peer-to-peer (P2P) network of computers instead of on a single computer. Rather than operating under the control of a single authority, dApps are spread across the network to be collectively controlled by its users.

Show Me More ›

What is the most secure blockchain network? ›

Introduced in 2013, Ethereum is one of the oldest and most established blockchain platforms. It provides a truly decentralized blockchain that is comparable to the Bitcoin blockchain network. Manders said its key strength is that it enables true decentralization with support for smart contracts.

Read The Full Story ›
Which cloud is best for blockchain? ›

Top 10 blockchain cloud data providers
  • AWS Bitquery. ...
  • Amazon Managed Blockchain. ...
  • BigQuery. ...
  • 14 Best Crypto API & Blockchain APIs for Developers. ...
  • IBM Blockchain Platform. ...
  • Oracle Blockchain Platform Cloud Service.
Dec 1, 2023

See Details ›
How much does it cost to run a blockchain? ›

Private blockchains require infrastructure setup and maintenance costs. This may involve hosting on cloud platforms, setting up dedicated servers, and other related expenses. The approximate cost for a private blockchain is around $1500 per month.

Get More Info Here ›
How much does a blockchain server cost? ›

Industry Averages & Best Guesses (based on company size and complexity) in Dollars: Family: In-house server: $10,000-$50,000 setup, $2,000-$5,000/month maintenance. Tribe: Hosted server: $5,000-$20,000/month, L2 blockchain: Development costs $20,000-$50,000, gas fees variable.

Continue Reading ›
What is AWS blockchain? ›

AWS Blockchain services

Multiple parties can transact with one another without having to know or trust each other. Each party, known as a member, owns a peer node in the network. AWS Blockchain Partners. AWS marketplace provides 70+ validated blockchain and distributed ledger technology solutions from our partners.

View More ›
How to deploy a private blockchain? ›

How to Build a Private Blockchain Platform?
  1. Define the Purpose. ...
  2. Select the Consensus Algorithm. ...
  3. Set Up the Network. ...
  4. Choose the Blockchain Platform. ...
  5. Design the Smart Contracts. ...
  6. Implement Data Encryption and Test the Blockchain. ...
  7. Deploy and Maintain the Network. ...
  8. Enhanced Security.
Jan 10, 2024

View Details ›
How do I create a simple blockchain network? ›

The code starts by creating an instance of the class Blockchain. This class stores information about the blockchain, including the previous block and proof. The code then uses the Proof of Work function to create a new block. The new block has a proof and hash that are based on the previous block and proof.

See More ›
How do I create a local blockchain network? ›

How to Create Your Own Blockchain From Scratch
  1. 4 Steps to Creating a Blockchain. Create a block. Add the data (header and body) to the block. Hash the block. Chain the blocks together. ...
  2. 5 Key Concepts in the Blockchain Ecosystem. Cryptographic hash and digital signature. Immutable ledger. P2P network.
Feb 7, 2023

Learn More ›
How do you deploy Ethereum network? ›

You need to deploy your smart contract for it to be available to users of an Ethereum network. To deploy a smart contract, you merely send an Ethereum transaction containing the compiled code of the smart contract without specifying any recipient.

Discover More Details ›
Top Articles
August 2016 Goals and Financial Updates - Retire by 40
Sea Salt Beet Fries with Garlic Cashew Cream Dipping Sauce - Dishing Up the Dirt
Canary im Test: Ein All-in-One Überwachungssystem? - HouseControllers
How To Be A Reseller: Heather Hooks Is Hooked On Pickin’ - Seeking Connection: Life Is Like A Crossword Puzzle
Polyhaven Hdri
Jonathan Freeman : "Double homicide in Rowan County leads to arrest" - Bgrnd Search
Emmalangevin Fanhouse Leak
Wal-Mart 140 Supercenter Products
Tribune Seymour
Midway Antique Mall Consignor Access
House Share: What we learned living with strangers
Xm Tennis Channel
Gina's Pizza Port Charlotte Fl
Find your energy supplier
Top Hat Trailer Wiring Diagram
Nyuonsite
Sonic Fan Games Hq
1v1.LOL - Play Free Online | Spatial
Vigoro Mulch Safe For Dogs
Orange Pill 44 291
Masterkyngmash
Glover Park Community Garden
Brbl Barber Shop
R Baldurs Gate 3
Giantbodybuilder.com
Shiny Flower Belinda
How rich were the McCallisters in 'Home Alone'? Family's income unveiled
Publix Daily Soup Menu
Does Circle K Sell Elf Bars
Nsu Occupational Therapy Prerequisites
RUB MASSAGE AUSTIN
Marine Forecast Sandy Hook To Manasquan Inlet
Selfservice Bright Lending
11 Pm Pst
Chs.mywork
Jefferson Parish Dump Wall Blvd
Msnl Seeds
National Insider Threat Awareness Month - 2024 DCSA Conference For Insider Threat Virtual Registration Still Available
craigslist | michigan
Fapello.clm
manhattan cars & trucks - by owner - craigslist
Exam With A Social Studies Section Crossword
Pike County Buy Sale And Trade
Perc H965I With Rear Load Bracket
Cvs Coit And Alpha
Understanding & Applying Carroll's Pyramid of Corporate Social Responsibility
Deshuesadero El Pulpo
Spongebob Meme Pic
Cheryl Mchenry Retirement
Unity Webgl Extreme Race
Latest Posts
Scholarship Secrets: How to Avoid Student Loans and go to College for Free! - Amyl Jaylen
Os 5 ETFs ligados a commodities negociados na Bolsa | B³
Article information

Author: Twana Towne Ret

Last Updated:

Views: 6269

Rating: 4.3 / 5 (64 voted)

Reviews: 95% of readers found this page helpful

Author information

Name: Twana Towne Ret

Birthday: 1994-03-19

Address: Apt. 990 97439 Corwin Motorway, Port Eliseoburgh, NM 99144-2618

Phone: +5958753152963

Job: National Specialist

Hobby: Kayaking, Photography, Skydiving, Embroidery, Leather crafting, Orienteering, Cooking

Introduction: My name is Twana Towne Ret, I am a famous, talented, joyous, perfect, powerful, inquisitive, lovely person who loves writing and wants to share my knowledge and understanding with you.