Prepare
git clone https://github.com/lab10-coop/tau1
cd tau1
./download_parity.sh
Run
./parity -c node.toml
Prepare
git clone https://github.com/lab10-coop/tau1`
cd tau1
./download_parity.sh
Add your mining key
- Copy the keyfile (json) of your mining key into
data/keys/tau1.artis(create directory if it doesn't exist yet). The filename doesn't matter. - Create a file
password.txtcontaining the password to unlock the keyfile.
Adapt the config
- Copy
trustnode.toml.exampletotrustnode.toml. - Open
trustnode.tomlwith your favourite editor and replace every<PLACEHOLDER>entry.
Run
./parity -c trustnode.toml
Keep running
A trustnode is supposed to be always on, thus running it in an interactive shell isn't the best option.
This repository includes a systemd template config you can use to make parity a system service.
The following steps require root privileges (sudo).
- Copy
artis-tau1-parity.service.exampleto/etc/systemd/system/artis-tau1-parity.service(if that directory doesn't exist, you're likely not using systemd and can't use this method). - Open the copied file and set User, Group, WorkingDirectory and ExecStart to the right values for your system
- Start the service:
systemctl start artis-tau1-parity - Flag service to be started on boot:
systemctl enable artis-tau1-parity
You can check the status of the service with systemctl status artis-tau1-parity.
There's a nice network status dashboard at http://status.tau1.artis.network/
It only lists nodes which want to be listed.
In order to be on the list, a dedicated status reporting application needs to run alongside parity.
If you run a trustnode, please get listed.
If you permanently run a normal node, a listing is also welcome!
Prepare
Check which version of nodejs you have installed (if any):
node --version
Anything newer than v6 should do.
If you don't have it installed, your options depend on the operating system.
Ubuntu 18.04:
apt install nodejs
Ubuntu 16.04:
curl -sL https://deb.nodesource.com/setup_10.x -o nodesource_setup.sh
sudo bash nodesource_setup.sh
sudo apt install nodejs
(Of course you can take a look into nodesource_setup.sh before executing it with root permissions.)
Install
Next, get the application:
git clone https://github.com/lab10-coop/node-status-reporter
cd node-status-reporter
npm install
Run
Now you could run it with
NODE_ENV=production INSTANCE_NAME=<your instance name here> WS_SERVER=http://status.tau1.artis.network WS_SECRET=ahZahhoth3engaem npm start
Keep running
If you installed a service for parity, you should do the same for this application.
- Copy
artis-tau1-statusreporter.service.exampleto/etc/systemd/system/artis-tau1-statusreporter.service. - Open the copied file and adapt it to your needs. Important: set something for INSTANCE_NAME and CONTACT_DETAILS and then uncomment both.
- Start the service:
systemctl start artis-tau1-statusreporter - Flag service to be started on boot:
systemctl enable artis-tau1-statusreporter
You can check the status of the service with systemctl status artis-tau1-statusreporter.
Metamask is a browser extension which implements an Ethereum wallet. It can be used with any Ethereum compatible network.
Once you have Metamask installed:
- Open and unlock Metamask
- Click the Networks dropdown and choose Custom RPC
- For RPC URL, enter "http://rpc.tau1.artis.network"
- (optional, but convenient) Click show advanced options, then enter "ATS" for Symbol and "ARTIS tau1" for Nickame
- Click SAVE
In order to transact with the network, you need ATS for tx fees.
There's a faucet for that: call
http://faucet.tau1.artis.network/addr/<ADDRESS_TO_BE_FUNDED>
(replace <ADDRESS_TO_BE_FUNDED> with the address of the account you want to get ATS for). Every call triggers a transfer of 1 ATS.
τ1 is an ARTIS testnet.
It makes use of several open source contributions of the fantastic Ethereum community, most importantly those of poa.network and Paritytech.
This directory includes a binary build of the parity-ethereum client (version 2.0.8) for convenience. Instructions for building from source can be found here.
Newer versions of Parity are expected to be compatible (able to sync with this chain), older ones are not!
