Hot answers tagged

13

Here is how it works: Just to keep things simple, let's say that the chain (all the blocks included up to now) has a fitness of 100. In other words, 100 total endorsements were included on all the blocks in the chain. Your baker now has priority 0 rights to bake the next block (block #5), and you have 30 endorsements in your mempool for the previous block (...


11

The shell currently ignores a new head if it is less fit than the hypothetical next head -- baked with all the endorsements in the mempool. This hypothetical next fitness is called context_fitness in the code there. This means that if your baked block includes fewer endorsements than endorsers see in their mempool, they will ignore your block and wait for ...


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


9

There are about 50k rolls right now, and 4096 blocks per cycle. Based on this, you can work out using the following: probableBakesPerCycle = (2/49997) * 4096; About 0.16 bakes per cycle, or 1 bake every 6.1 cycles. https://tzscan.io currently shows the number of rolls as well


8

Assuming there are N rolls, you have 2 chances out of N to be selected to bake at level X with priority Y N = 2, you will be selected with probability 1, N = 4, you will be selected with probability 1/2, N = 49941 (which is the number of rolls for cycle 80), you'll be selected with probability 0,000040047 (for each priority of each level) This means that ...


8

Most likely poor connection to peers, or at least the ones that mattered at the point in time (the endorsers for your block, and baker of the next). Endorsers will endorse the block with the higher fitness, but they can't double endorse. That means if they saw your block and endorsed it, they can't change their mind when the p1 block came along (even if it ...


6

When you launch the docker node with ./mainnet.sh start, you can add extra arguments such as --private-mode --peer AAA.BBB.CCC.DDD:PORT (you probably need to specify --peer to connect your private node to your public node).


6

I figured out that you can use the --dry-run option in the transfer statement so that node will send transaction to remote-signer to sign, and you can check the remote-signer logs to see if everything is working fine or not. --dry-run will not actually send the transaction to the network.


6

The is no negative impact on delegators tokens when a baker gets hacked. When you delegate your tokens in Tezos they are not locked up and they remain in your custody and control. Note that this assumes you have control of your tokens in the first place; if you keep your tokens on an exchange then you aren't in custody and all your assets on the exchange ...


5

You also need to take into account the (evaluated) balance of the baker on the tz1 address, which also generates rewards, but which are not stated under the rewards tab. Under the rewards tab, only the KT1 addresses of the delegators are shown. It is not uncommon for a baker to own 40% of the total stake, so I don't think there is anything suspicious here. ...


4

There are approx 450 bakers at the moment. If you assume each is running an average desktop which runs at 100W (this is almost certainly too high but if you are looking for an upper bound it's probably good enough) then the energy consumed in a given day to secure the network is 450 * 24 * 100 / 1000 = 1,080 kilowatt hours. Bitcoin by comparison uses about ...


4

While this does not directly answer your question, Kiln has a feature that can notify you when your Private Node loses connections. When you configure Kiln to monitor the Private Node, include a 'minimum number of peers' in the UI. If your Private Node's peers drop below that number, you'll receive a notification. https://gitlab.com/obsidian.systems/tezos-...


4

Update 3/21/19 Core developers had pushed out a fix as of 366f64f3df266cf02a06412d6760f73626d0a2bf commit on the mainnet branch that addresses this issue that I described below. In the setting where you have a node in --private-mode (to bake) that connects itself to front (public) nodes, you must explicitly set your front nodes to trust your private ...


4

I just prefer to do this...it's a direct request to sign data without any possibility of forgetting to add the --dry-run flag. tezos-client sign bytes 0x03 for <tz alias or tz address> Here 0x03 is just any old random number. You could put any hex value here. If the remote signer is working you'll get back a message like: Signature: ...


4

The delegators have nothing to do with the validity of the transactions signed by their delegate/baker. The delegated funds are never at risk and that is why it is always safe to delegate your tokens. The example you gave of a baker including a "bad" transaction in its block is handled by the endorsers. They will not endorse this block and the bad baker won'...


4

I am Axel, the developer behind bakersperformanceindex.com and I hope this tool can help you in reviewing the baking services you're using. The basic idea behind it was: delegate the same amount of xtz to baking services, in our case 10xtz delegate at the very same cycle, in our case at cycle 34 collect and display data in a simple and raw manner So I ...


4

It is nothing harmful, this message just makes visible a peer disconnection that was formerly only printed in debug mode, and will probably be only visible in debug mode in the future. And it's normal to be disconnected from peers on a regular basis. It is part of the "connection diversification" process: sometimes a node choose to accept a new incoming ...


4

As far as I know, exchanges do not payout if you delegate to them. They don't act like normal bakers that takes delegations. Their advertised fees and payouts are for if and only if you keep your funds inside their exchange. They don't even advertise the address they use to bake, community members figured it out using some detective work. In short, by ...


3

Although there are a couple of scripts that will allow bakers to do auto payments, I would recommend you to try TAPS (Tezos Automatic Payment System). It is a web based solution with a complete GUI, allowing you to set up a scheduled task that will fetch tzScan.io each hour to detect a cycle change, by which it will loop through your delegators, calculate ...


3

Assignment of baking rights in a cycle are independent choices. So the probability for you to get at least one baking right with prio 0 in a cycle is: (1-((50000-2)/50000)^4096) = 15.1%


3

1) You become a baker by running a Tezos node and registering as a delegate. The financial requirement is currently 10.000 XTZ (although this might get lowered to 8.000 XTZ if the current Athens A proposal is ratified). Hardware requirements are minimum 1 medium sized server with quite a bit of disk space and preferrable a SSD disk (tezos is quite disk I/O ...


3

Solution: My initial problem was that I used the external IP in the tunnel configuration. The following solves the problem Reference to documentation on PuTTY tunnels: 1) Set "Source Port" for the port on your local machine: 8000. 2) Set "Destination" to your internal IP address on the remote machine including port 8000 as highlighted in the screenshot ...


3

There are a few issues here. What is double baking/endorsement? It is important to understand that the doubling penalty has little to do with injection. The crime is signing two different blocks or endorsements, with different hashes, at the same level. Injection is just one way for your crime to be discovered. You can safely inject a single block or ...


3

That's correct - this constructs an operation, much the same as when you use client to set delegate for ... or withdraw delegate from .... If the key_hash is not a baker, it will produce "Unregistered delegate" error (unless it's self-delegation to register a new baker or to activate a inactive baker). It is currently not possible to de-register a baker. If ...


3

You only need the equivalent of 2 CPU cores to bake/endorse with Tezos, and about 4 GB of RAM. Any more will remain idle. Yes, SSD due to poor database implementation, unfortunately. You should run this command before starting the baker and endorser: export TEZOS_LOG='* -> debug' That will give you much more output so you have an idea of what is ...


2

The lockup for rewards is the same - i.e. rewards are released when the security deposits are.


2

The error logs clearly suggest that the ENOTTY error for the "auth" key is your problem. You cannot directly use an encrypted key to authenticate the docker daemons to a remote signer, because you cannot type the password in. (As FLF OCP notes, "the ENOTTY error is coming from an attempt to ask the key password on a terminal, but there is no such terminal")....


2

If the proposal passes the "Testing Vote Period" the chain is forked into two chains for the "Testing Period". Bakers are encouraged to run another baker and endorser for this test chain (setting a different PROTOCOL parameter - instructions will be provided) 👍 My understanding is transactions are processed on both chains - users of mainnet does not have to ...


2

There are really two votes here. Voting on which proposal which actually be voted on. There might be several proposals, but only one proposal can win per proposal period. After a proposal has been selected there are two votes on the winning proposal. The first vote during the exploration period, and the second vote during the promotion period. For more ...


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


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