17
In terms of resolution, it's not an issue. Even a few seconds off wouldn't affect your participation in the consensus given the comparatively large block time of 60 seconds.
In terms of security, you may not want to run any clock synchronization service though. A compromise of the ntp servers could allow an attacker to drift your clock.
Manually syncing ...
13
Regarding the security deposit/bond requirement, it is explained on the tezos official documentation:
Security deposits¶ The cost of a security deposit is
BLOCK_SECURITY_DEPOSIT = 512 XTZ per block created and
ENDORSEMENT_SECURITY_DEPOSIT = 64 XTZ per endorsement. Each delegate
key has an associated security deposit account. When a delegate bakes
...
12
Fundamentally a cycle is a set of block heights for which the baking en endorsement rights are determined by a single random seed.
The reason to have many blocks in a cycle is that it lowers the incentive to try and manipulate the random seed (since most seeds will produce similar distributions on average). The reason not to have too many blocks in a cycle ...
12
Currently, as of protocol 003, double baking(or endorsing) is penalized with losing all of one's rewards and bonds for that cycle in which the double bake(or endorse) occurred. The rewards are completely burnt. Bonds are half burnt and half rewarded to the baker that baked the block that includes the accuse operation.
If double bake occurs, the baker should ...
12
In principle the node doesn't need to be updated, it is capable of receiving a new protocol 004, compile it and use it to validate blocks produced by protocol 004. In practice it is a good idea to update to the latest release because there are always useful improvements. For example the snapshots introduced in Mainnet May allow for a much faster validation ...
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 ...
10
The endorser and accuser don't need to run on the same system as a node. They can run on a completely separate system, or on the same system (your choice), and only require communication with the Tezos node over RPC (to port 8732 by default).
The baker, however, does require local access to the data files that the node creates. The Tezos blockchain data is ...
10
From a purely theoretical perspective, when you are a baker who is capable to reaching 100% target of its priority 0 baking rights, the optimal situation in terms of your capital is to have all of it blocked as security deposit because it means that all your capital is working. In such situation as soon as some bond is unlocked it would get relocked again by ...
9
Whether it is a good idea to solo-bake with 10k XTZ depends on your goals and what you are willing to contribute.
If it is simply an experiment and you would like to get the experience and fun out of running a baker then go ahead. If this baking operation is critical towards your livelyhood and you cannot tolerate down-time or potential safety faults I ...
9
If a delegate doesn’t show any sign of activity for preserved_cycles it is marked inactive and its rights are removed. This mechanism is important to remove inactive delegates and reallocate their rights to the active ones so that the network is always working smoothly. Normally even a baker with one single roll should perform enough operations during 5 ...
8
https://kukai.app (not for mobile)
You can use the kukai wallet to do multi-send operations. It was a feature-request from a baker and now multiple bakers are using it.
8
There is no need to identity who submitted the evidence, because it is the baker who includes the evidence who receives the rewards.
8
There are only a couple known non-malicious causes of double baking or endorsing.
The first is running two bakers and/or two endorsers with the same wallet at the same time. Some bakers build their infrastructure to be highly available and have multiple bakers and/or endorsers running. There had been a couple cases where a switch over had caused double ...
8
How to Delegate Tezos XTZ with Tezos Client and Running Your Own Node (Betanet) - with Mac OS
https://medium.com/cryptium/how-to-delegate-tezos-xtz-with-tezos-client-and-running-your-own-node-betanet-cea6960cf45
Build a Betanet node on Debian 9
https://github.com/tezoscommunity/FAQ/wiki/Build-a-Betanet-node-on-Debian-9
Tezos Baking Economics — Guide
https:/...
8
You will not incur any penalties as long as you don't double bake so you can just stop running your nodes.
The key thing when shutting down is to remember that you have earned future baking rights 7 cycles in advance. So if you want to make full use of the rights and earn all of your rewards you need to leave your baker running with enough funds to cover ...
8
We also maintain a list of bakers on tzscan :
https://tzscan.io/delegation-services
When you click on the baker you’ll get all the information that you will need.
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
Just asked that question at riot.
The answer from our very wise Adrian Brink:
7
Let me try to take your questions one by one:
How can I tell that I registered my baker correctly?
After the delegation operation happens, if you check tzscan.io with your baker address, you should see (in the right hand side) "Delegate Status: Active" and the Manager and Delegate address should be the same as your baker address (assuming you are not ...
7
In short the answer has to do with
1) what is called counterparty risk
2) and how much is at risk.
In Tezos, regular delegation does not put your capital at risk because your xtz never leave your wallet while you allow the baker to vote on your behalf and get baking rights thanks to your delegation. The baker collects the baking rewards and then ...
7
Am I understanding correctly, that I can store for example my rental
contract as a Smart Contract and then it is made official with baking
it with bakers?
Like in all open blockchain systems, you can run a full node, which downloads all blockchain data. Once it has been synced, it can propagate new transactions and blocks to network, can validate new ...
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
I have done it by following these steps:
Calculate the maximum amount of stake you will need to leave in the account to cover rewards you are already eligible for. Basically the sum the upcoming rewards for the next 7 cycles
Delegate the remainder of your balance to your chosen baker leaving the amount you calculated in step 1
This should leave you with a ...
7
GET ../<block_id>/helpers/baking_rights?(level=<block_level>)*&(cycle=<block_cycle>)*&(delegate=<pkh>)*&[max_priority=<int>]&[all]
Retrieves the list of delegates allowed to bake a block. By default,
it gives the best baking priorities for bakers that have at least one
opportunity below the 64th priority ...
7
Frozen deposits are part of the staking balance (otherwise, your staking balance would decrease during baking);
Frozen rewards are not part of the staking balance. They are taken into account only when they are unfrozen.
If you look at:
https://gitlab.com/tezos/tezos/blob/master/src/proto_alpha/lib_protocol/src/delegate_storage.ml#L445
You will see that ...
7
Fundamentally, nonces are used by the blockchain to create randomness, such as choosing the snapshot for a cycle. Nonces are created by bakers and all the nonces for the cycle are combined to create a random seed. When baking blocks, you may be required to reveal a nonce in the next cycle. This nonce requirement is determinstic and happens every 32 blocks. ...
7
$ ./tezos-client show voting period
Current period: "testing_vote"
Blocks remaining until end of period: 32678
Current proposal: Pt24m4xiPbLDhVgVfABUjirbmda3yohdN82Sp9FeuAXJ4eV9otd
Ballots: { "yay": 2716, "nay": 0, "pass": 0 }
Current participation 5.09%, necessary quorum 80.00%
Current in favor 2716, needed supermajority 2172
$ ./tezos-client submit ballot ...
7
tezos-signer supports --require-authentication, --magic-bytes, and --check-high-watermark options. You should understand these.
$ tezos-signer man -v 3
...
-A --require-authentication: Require a signature from the caller to sign.
...
-M --magic-bytes <0xHH,0xHH,...>: values allowed for the magic bytes, defaults to any
-W --check-high-...
6
Nothing happens until the double-baking activity has been denounced
Once denounced the deposit is slashed and if the baker continues to bake in the same cycle his other deposits can be slashed as well. For this reason bakers who happened to double bake during a cycle should stop all activity for the rest of the cycle asap.
More info is available here (...
Only top voted, non community-wiki answers of a minimum length are eligible
