Home

Alastria Wiki

Welcome to Alastria WIKI.

In this site, you will find the most relevant resources about Alastria Network and its infrastructure.

Permissioning

All nodes that will be installed in the Alastria Networks must be permissioned. To ask for permission you must enter your data in this electonic form and make a PR for the files that are modified in the installation process. If an associated will want to remove a node from the network, it is kindly appreciated that a a request must be notified through a PR. Other guides related with operation of Alastria Node are aviable in following documents:

• CONDICIONES DE OPERACIÓN DE LA RED T ALASTRIAPOR PARTE DE NODOS CRÍTICOS
• Políticas de Gobierno y Operación de la Red T Alastria

How to set up Alastria nodes

English installation guide Red T

• A regular node in Red T using Docker
• A validator node in Red T using Docker
• A bootnode in Red T using Docker

Spanish installation guide Red T

• A regular node in Red T using Docker
• A validator node in Red T using Docker
• A bootnode in Red T using Docker

Other resources

• Private Smart Contracts in Red T
• Guide to Deploy Smart Contracts in Red T

F.A.Q

"My node is out of sync with the alastria-t network"

As there are several ways to run the node, there are several parameter that should be tested. Alastria-T network it's a public-permisioned network, that uses Quorum (AKA GoQuorum, JPMorgan Quorum) as client. So, there's be running a "geth" process. Here a example of a geth process running as REGULAR (AKA "general") node:

geth --datadir /root/alastria/data --networkid 83584648538  
--identity REG_MemberNameInAlastria_T_2_4_00 --permissioned --port 21000  
--rpc --rpcaddr 0.0.0.0 --rpcapi admin,db,eth,debug,miner,net,shh,txpool,personal,web3,quorum,istanbul --rpcport 22000  
 --istanbul.requesttimeout 10000 --ethstats REG_MemberNameInAlastria_T_2_4_00:bb98a0b6442386d0cdf8a31b267892c1@netstats.telsius.alastria.io:80 --verbosity 3 --vmdebug --emitcheckpoints --targetgaslimit 8000000  
--syncmode full --gcmode full --vmodule consensus/istanbul/core/core.go=5 --nodiscover  
--metrics --metrics.influxdb --metrics.influxdb.endpoint http://geth-metrics.planisys.net:8086 --metrics.influxdb.database alastria  
--metrics.influxdb.username alastriausr --metrics.influxdb.password ala0str1AX1 --metrics.influxdb.host.tag=REG_MemberNameInAlastria_T_2_4_00

If there's no running process for geth

CORS:

• Es necesario arrancar el nodo con la opción "GLOBAL_ARGS=$GLOBAL_ARGS --rpccorsdomain "http://localhost:8080""

• English version

• Spanish version

3. Netstats and Block Explorers

• Monitors of the network (ethnetstats)
• Block explorers

Where to ask for help?

• Slack
• GitHub (uses and governance)

Development Status (Starting from 1 October 2018)

• Sprint 0
• Sprint 1
• Sprint 2
• Sprint 3
• [Sprint 4] Since January 21st, 2019 as the network was opened, the work has been done based on request

Nowadays, the following developments are in place or in backlog (any help/volunteers are welcomed):

• Netstats improvements, to allow this tool to handle a very big number of nodes.
• Validator nodes automatic round, to allow the network to make automatic change of the validator nodes without intervention of the humans administrators, in case of any fault/malfunctioning of the nodes
• HardFork to upgrade to the new EVM and the new Quorum version.
• HardFork to upgrade GetH binary to prepare for Gas implementation
• Faucet or Gas Distributor