We changed our privacy policy. Read more.

Hot answers tagged

20

9732 is the default port for P2P connections, can be overridden with --net-addr=ADDR:PORT when starting the node 8732 is the default port for RPC connections, can be overridden with --rpc-addr=ADDR:PORT All networking uses TCP. If using iptables the below rules should suffice for tezos specifically. Be aware you will need to allow other non tezos network ...


12

@xtzbaker is spot on with the ports that the node uses. Preventing DDoS for the baking node is also one of the reasons that the most common setup for baking is to have a private baking node with trusted public nodes. Basically, we have a single node that the baker and endorser uses and it's configured to be on private mode. Private mode will disallow ...


10

It is possible to have a hot-standby signer albeit I would recommend against it. In order to have a hot-standby, you initialise a second ledger with the same seed as the first one. Then you need a strategy that describes in what cases the standby signer becomes active. The downside of a standby signer is that you lose the double-sign protection that the ...


8

CPU: nothing special, a couple of GHz will do, tezos supports multi-core well MEMORY: see my plot below. Seems like >4GB makes sense. 8GB should be enough. STORAGE: Random read and random write >150MB/s. This can easily become a bottleneck with embedded systems, a spinning disk is not recommended. Also flash cards could wear out quickly if they are not ...


7

The difference is in the default derivation path suggested by the cli. If you use /0'/0' in both (or nothing in both) you should get the same keys. The words are derived based on the hash of the root tz1 public key hash, and a list of adjectives and animals. The lists are sufficiently big that it's reasonably unlikely that you'd end up with two ledgers ...


7

Looks like a good start. Unless your (4G)-router has a battery consider an uninterruptible power source (UPS). A second laptop with signer and additional ledger on standby in a separate location close by will improve HA in case of hardware problems, fire/water damage or a prolonged power outage. Probably more important is your software setup. Does the ...


6

The docker builds are generally aimed at those individuals who are not comfortable with, or have no experience in compiling software. There is no advantage over running docker builds vs compile on your own; the code is the same. The docker builds are indeed supported by the core devs. With each new release of the core code, the docker images are also updated....


6

The the signer's firewall only allows connections to the signer port from the node VPS who's IP I whitelisted. Because of this, I didn't feel it was necessary to setup signer authentication. This is the main security concern I would have. In general, your setup is fairly secure, however, the main risks are: Because the signer has no authentication, anyone ...


6

8GB RAM is recommended1 for a node. Kiln recommends 10GB of RAM for example. The mainnet node in my Ubuntu 18.04 Baker/Node doesn't use up a lot of resources from the CPU. However, using an SSD is highly recommended. I at least have been getting a lot of "timed out" errors on the second node I run on an HDD. The mainnet node running on an SSD runs smooth.


5

To fully sync the entire chain from the start should take a little under 24 hours depending on the speed of your SSD. If you are using non-SSD it can take many days and is not recommended. New history modes have recently been added as it's not necessary to regenerate all of the context metadata from the beginning for most cases. Running in those modes will ...


5

You could also add an extra layer of security by having your node's internet connection go through a DDoS protected VPN, like OctoVPN https://octovpn.com


5

Hardware wallets like the Ledger Nano are good cold storage solutions. Offline-wallet creation in an air-gap device is also a good solution. Kukai wallet offers you the possibility to do offline-signing so your seed is never exposed to the online world when interacting with the network.


4

Of course the use of the Docker makes it easier to build a node, and it is useful for people with an initial level of knowledge of programming on Linux. The fact is that when you build a node for baking through the Docker, you may encounter errors that will not be easy enough to understand. I advise you to collect the node by the steps prescribed in this ...


4

Relationship is not explicit. fitness for a block is just total number of endorsements in the chain that block is extending. If you are well connected with endorsers and bakers, fitness is very likely high. Answer that you are looking for is empirical which requires logging number of peers connected vs fitness score of the baked block for each baker. ...


3

The performance of syncing an archive node depends on multiple factors including your hardware, network connectivity, number peers etc however one of the dominant one is the intensity of I/O operations not the number of computations by the CPU (see this question for instance). It is more likely that you would go faster by improving your storage from say hdd ...


3

npm i eztz wont work. Instead you can add eztz's git repo as a dependency in your package.json "dependencies": { "eztz": "git://github.com/TezTech/eztz.git#0c6b93ffdd774f7ed3c528058f854deb0649a61c" } After that you just run npm i or yarn to install the package. When you want to use the library you have to import it import { eztz } from 'eztz';...


3

We run our node on Digital Ocean. Our nodes are 2vCPU/2GB RAM/60GB SSD with 4GB swap. We have been running this configuration for 6+ months with no issues. We used to run with 1vCPU, but had lots of iowait. A second vCPU solved that. SSD is almost a must-have. Anything over >4GB RAM or >2 CPUs/Cores is just overkill at this time. Maybe in 1-2+ years when ...


3

The the signer's firewall only allows connections to the signer port from the node VPS who's IP I whitelisted. Because of this, I didn't feel it was necessary to setup signer authentication. I would flip this. Block all incoming connections to the signer and instead have the signer connect to the TF. That way you don't have to worry about a malicious node ...


3

First of all, when storing tezos using an HSM one still needs to connect to a node in order to perform operations like transactions or delegation. For this there is the choice between connecting to a local full node (see here or there) or wallet services that offer support for HSM, like Tezbox, Galleon (as of now Kukai does not support HSM I believe). One ...


3

Yes, you need a different data-dir, RPC port, and P2P port, like: --net-addr :10001 --rpc-addr :10002 --data-dir /some/path The tezos-node executables should be compiled from each respective branch mainnet / alphamet too.


3

You may need to input a public node to bootstrap in your peer list; https://zeronet.smartpy.io is available.


2

The ledger maintains a HWM (high watermark) for "double bake protection" - this means it will not sign more than 1 block at a certain height. I do not believe it is possible to maintain multiple HWMs with a single ledger (except for testing period chains), and so you might get in trouble if baker A signed a block for height X+1 just before baker B tries to ...


2

For the tezos-node service it is possible to remove the timestamp using a tezos-node configuration with the following additional parameter at the top level: "log": { "template": "$(section): $(message)" }, That results in log output like this: Mar 18 09:41:43 baker.example.com tezos-node[27537]: validator.chain(1): Pushed: 2019-03-18T14:41:43Z, Treated: ...


2

I figured it out. For some reason, I am running on Mac and had a .bash-profile and .bash_profile. I edited the wrong one. The sudo is for the increase maxfiles, unrelated to the disclaimer removal.


2

The most significant benefit of an on premise solution is the availability of devices like the Ledger Nano S which are a proven mechanism for securing your private keys. With a cloud provider like Azure you do not have such a straightforward means to secure your keys. In theory you can make use of their dedicated HSM but it is not as clearly documented/...


2

The main risk with using multiple ledger/bakers is the risk of double-baking/double-endorsing which will make you lose your bond. So technically the answer to your question is "yes" however to be proper it relies on your setup's ability to make sure that at any one time at most one baking node is able to talk to the network. There are various ways to ...


2

I recently wrote and ansible role to do all this on debian machines : you can check it out here : https://gitlab.com/abate/training-2020-deploy/-/tree/master/ansible I'm still working on the ssh tunnel that is not super reliable, but the rest seems working.


2

Here is a step by step updated guide on how to build a Tezos node from the sources on Ubuntu, also see my youtube video: https://www.youtube.com/watch?v=SAHoF-oO71U DOWNLOADS AND LINKS Ubuntu download: https://ubuntu.com/download/desktop Tezos node snapshot links: Available snapshots for main net? https://github.com/Phlogi/tezos-snapshots curl -s https://...


1

Calling tezos-admin-client p2p stat on node B will list among other things, all active connections. The connections to private node will have the word private near the end of the line. Here is an example in sandbox where 127.0.0.1:19732 plays the node A (private and trusted): $ tezos-admin-client p2p stat GLOBAL STATS ↗ 4.21 kiB (224 B/s) ↘ 1.70 kiB (89 ...


1

Tezos Alphanet is now called "Babylonnet". Future Testnets will get the name of the actual active (or future) protocol. Follow this guide to setup a Babylon Testnet node.


Only top voted, non community-wiki answers of a minimum length are eligible