8

If you key starts with edsk: do this tezos-client import secret key my_account unencrypted:edsk...


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

There is an app specifically created for baking by Obsidian Systems. You can install it through Ledger Live (you might still need to enable developer mode in Ledger Live). Instructions here. You can read more about the baking app and wallet app here.


7

Apr 15 05:23:46 - client.baking: No slot found at level 395863 (max_priority = 64) This message is normal when you are not given any rights, so it's perfectly fine. There is no concern there. Going into the details how you can check whether or not you are set up correctly on chain. The easiest way is to check on the "Delegate" status shown on tzscan, ...


7

when you bake and endorse your funds will get locked up as a deposit for an amount of time. then you will receive your baking/endorsement rewards and you'll receive your deposit back.


6

I don't know about bakechain, but I can say your tezos-client command is incorrect. It needs to look like: ./tezos-client import secret key my_account encrypted:edesk1XXXX where encrypted:edesk1XXXX is the encrypted version of your key.


6

You should use as many peers as you can, for a more secure approach you can use a private node that connects to your public nodes instead. List with nodes: Tzscan Network Script to add peers: addPeers


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.


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 ...


5

It makes totally sense, to delegate the "excess XTZ". Just full rolls bake for you. Every undelegated XTZ (considering the fee) above a full roll are wasted rewards. The calculation is looking good to me. You just need to have an eye on the "Next Roll Goal" (7 cycles before). So you can delegate back to yourself.


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

From a Tezos protocol perspective the answer is you don't have to wait at all and there is no grace period. This is a common misunderstanding, but you need to think in cycles which are made up of 4096 blocks. Every cycle there are 16 snapshots taken, eventually one of these snapshots will be randomly selected to represent the "delegation and staking ...


3

As explained here https://medium.com/tezos/liquid-proof-of-stake-aec2f7ef1da7 The minimum staking balance for baking is 1 roll which includes the baker plus delegated funds. So the answer to your question is: yes To further the minimum capital the baker need to have in order to operate on normal conditions under the current protocol (003) is the ...


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

You can now download both the Ledger Tezos Baker and Ledger Tezos wallet directly within Ledger Live, bypassing a lot of the CLI work necessary before this existed.


2

This question was originally asked on r/Tezos where I replied with the following: Unfortunately this is a fact of life for bakers (endorsers) from time to time. In general, there are a number of possible causes for something like this happening, including, but not limited to: Your node's clock is wrong so even though it thinks it endorsed at the correct ...


2

Posting the reddit answer by BakeTzForMe: Unfortunately this is a fact of life for bakers (endorsers) from time to time. In general, there are a number of possible causes for something like this happening, including, but not limited to: Your node's clock is wrong so even though it thinks it endorsed at the correct time, it was too late or too ...


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

Baking and endorsing rights are allocated at random, proportionally to the delegate's stake, using a PRNG and a random seed derived from on-chain data (nonces committed by bakers and revealed later). For more details, see the doc. To see the distribution of baking/endorsing rights, use these RPCs: https://tezos.gitlab.io/api/rpc.html#get-block-id-helpers-...


2

Kiln is currently the easiest approach to running your own baker in the Tezos ecosystem. It is early in it's development and iterating quickly. But the focus clearly is to help people bake for themselves; as such there is no real need to automate baker payouts to others. If you are using Kiln to run your own delegation service you will likely need to find ...


1

For a smaller baker with only a few rolls, a couple factors need to be considered. This includes the hardware costs and costs from the time spent to learn and maintain the software. The hardware costs are generally low, it's not zero. Just for reference, some people claim to be baking on a raspberry pi (I have my doubts for a long term setup). If Tezos is to ...


1

Sorry to hear that! There are many different reasons why block or endorsement could be missed, such as internet connectivity etc - however we can rule out many of those in this case because we see your baker identified the baking opportunity, attempted to bake, but it seems it wasn't not able to find your Ledger device. This may be of no fault of your own, ...


1

I've been running a baker on a raspberry pi with 4CPU's and 4 gigs of ram for no issues. Also running a node on vultr(cloud provider) for testnet, 2 cpu with 4 gigs of ram, no issues at all running a baker on testnet there as well.


1

A lot of us bakers old timers depend on the work done by etomknudsen called "Tezos Node CPR". Main repo has systemd scripts to let systemd manage and log the tezos binaries. Systemd does a great job keeping services up as it's battle tested in enterprise level services, it handles process dependencies and restarting of services on errors. The Tezos Node ...


1

We are or hire system architects who design a HA (high availability) infrastructure for our bakers 😉 You can see some discussions here. SSH is definately one tool in the toolbelt here, but if you want a serious HA architecture you need to find skilled people to build and operate it 👍


1

In general the optimum behaviour is to transfer the excess tezos after every cycle as long as the expected rewards from delegating exceed the transaction fee, and leave the excess tezos in your account when the expected returns from delegating do not exceed the transaction fee. However there is one case where this is not the optimal behaviour, it is very ...


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