What incentive is there for baking on the test chain during voting period?2019 Community Moderator...
page split between longtable caption and table
If I delete my router's history can my ISP still provide it to my parents?
Why is working on the same position for more than 15 years not a red flag?
What is a good way to foreshadow that magic is actually very advanced technology?
How to acknowledge an embarrassing job interview, now that I work directly with the interviewer?
Why do members of Congress in committee hearings ask witnesses the same question multiple times?
How can I deal with a significant flaw I found in my previous supervisor’s paper?
name character vectors with same name of list
How to avoid being sexist when trying to employ someone to function in a very sexist environment?
what are the advantages of using makefile for small projects?
Program that converts a number to a letter of the alphabet
Unwarranted claim of higher degree of accuracy in zircon geochronology
Why zero tolerance on nudity in space?
Find minimum number of meeting periods to reach 2 degrees of separation for a group
Slow moving projectiles from a hand-held weapon - how do they reach the target?
It took me a lot of time to make this, pls like. (YouTube Comments #1)
Reference on complex cobordism
Recrystallisation of dibenzylideneacetone
Finding radius of circle
Is there a better way to make this?
Can you earn endless XP using a Flameskull and its self-revival feature?
Is it a fallacy if someone claims they need an explanation for every word of your argument to the point where they don't understand common terms?
Dilemma of explaining to interviewer that he is the reason for declining second interview
Every character has a name - does this lead to too many named characters?
What incentive is there for baking on the test chain during voting period?
2019 Community Moderator ElectionFor a baking server, is timesyncd good enough for clock resolution?Can I use multiple ledgers for baking?What is the penalty for double baking?What happens to deposits after a baking node has double-baked?Splitting Voting and Baking rightsWhat is the optimal frequency for delegating your excess proceeds as a solo baker?When is baking rewards counted to the staking balance?Docker vs local build for baking on mainnet?When does roll counts update for voting?RPC query for amendment status
It seems there is a reasonable amount of overhead (and some risk) for participating in the baking process on the 48 hour test chain during the voting period.
As far as I can tell there is no incentive for a baker to actually participate in the test chain baking outside of simply "it is good for the network", and there is also no downside, so long as a critical number of bakers participate.
I guess I see it as similar to the choice of whether to run the accuser or not, for an individual baker there is little need or incentive.
baking voting
asked 6 hours ago
xtzbakerxtzbaker
422215
add a comment |
It seems there is a reasonable amount of overhead (and some risk) for participating in the baking process on the 48 hour test chain during the voting period.
As far as I can tell there is no incentive for a baker to actually participate in the test chain baking outside of simply "it is good for the network", and there is also no downside, so long as a critical number of bakers participate.
I guess I see it as similar to the choice of whether to run the accuser or not, for an individual baker there is little need or incentive.
baking voting
asked 6 hours ago
xtzbakerxtzbaker
422215
add a comment |
It seems there is a reasonable amount of overhead (and some risk) for participating in the baking process on the 48 hour test chain during the voting period.
As far as I can tell there is no incentive for a baker to actually participate in the test chain baking outside of simply "it is good for the network", and there is also no downside, so long as a critical number of bakers participate.
I guess I see it as similar to the choice of whether to run the accuser or not, for an individual baker there is little need or incentive.
baking voting
asked 6 hours ago
xtzbakerxtzbaker
422215
It seems there is a reasonable amount of overhead (and some risk) for participating in the baking process on the 48 hour test chain during the voting period.
As far as I can tell there is no incentive for a baker to actually participate in the test chain baking outside of simply "it is good for the network", and there is also no downside, so long as a critical number of bakers participate.
I guess I see it as similar to the choice of whether to run the accuser or not, for an individual baker there is little need or incentive.
baking voting
baking voting
asked 6 hours ago
xtzbakerxtzbaker
422215
asked 6 hours ago
xtzbakerxtzbaker
422215
asked 6 hours ago
xtzbakerxtzbaker
422215
asked 6 hours ago
xtzbakerxtzbaker
422215
asked 6 hours ago
xtzbakerxtzbaker
422215
422215
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It is a good question. The answer relies on I believe the mistake you made in asserting that there is "no downside" to not participate in the test net.
For example: if a baker has rights just after the protocol updates then if the baker did not prepare his setup to adjust for the new protocol he has a risk of missing his first bakes under the new protocol.
It gives an incentive to "get prepared" and the testnet is the best way to do the transition smoothly
So in conclusion i would say in particular for professional bakers who have public performance metrics and delegators to answer to, that it is important for them to make sure their setup is prepared for the protocol update during the testnet phase
answered 5 hours ago
EzyEzy
2,357427
1
Ensuring you have up to date baking software is absolutely necessary for your baking operation, however that does not mean you need to participate in the test chain, by design the baker should flip to the new protocol for you after the successful test. I'll grant the "be prepared" incentive is there, however it seems equally as weak as the "good of the network" incentive considering you run an increased risk of losing rewards by participating in the test chain
– xtzbaker
5 hours ago
1
@xtzbaker i disagree. If you as a baker wait until the testing phase is finished to change your config you will have operational risk. If you discount this risk as 0 it is your choice of course. But as any risk it has a monetary cost.
– Ezy
5 hours ago
The question isn't about preparing your node for the new protocol, a baker can just as easily prepare themselves using zeronet or alphanet, and simply have the appropriate versions of the software running on mainnet prior to the new protocol being adopted. The question is specifically about taking part in the baking process on the test chain. There appears to be very weak incentives for bakers to participate in the baking process on the test chain.
– xtzbaker
24 mins ago
@xtzbaker i respectfully disagree one more time: it has everything to do with preparing for the new protocol. zeronet is not guaranteed to be the exact same thing as the mainnet. Testnet is. There is 0 downside in testing in testnet instead of zeronet if the baker is willing to do some testing at all.
– Ezy
22 mins ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "698"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftezos.stackexchange.com%2fquestions%2f652%2fwhat-incentive-is-there-for-baking-on-the-test-chain-during-voting-period%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It is a good question. The answer relies on I believe the mistake you made in asserting that there is "no downside" to not participate in the test net.
For example: if a baker has rights just after the protocol updates then if the baker did not prepare his setup to adjust for the new protocol he has a risk of missing his first bakes under the new protocol.
It gives an incentive to "get prepared" and the testnet is the best way to do the transition smoothly
So in conclusion i would say in particular for professional bakers who have public performance metrics and delegators to answer to, that it is important for them to make sure their setup is prepared for the protocol update during the testnet phase
answered 5 hours ago
EzyEzy
2,357427
1
Ensuring you have up to date baking software is absolutely necessary for your baking operation, however that does not mean you need to participate in the test chain, by design the baker should flip to the new protocol for you after the successful test. I'll grant the "be prepared" incentive is there, however it seems equally as weak as the "good of the network" incentive considering you run an increased risk of losing rewards by participating in the test chain
– xtzbaker
5 hours ago
1
@xtzbaker i disagree. If you as a baker wait until the testing phase is finished to change your config you will have operational risk. If you discount this risk as 0 it is your choice of course. But as any risk it has a monetary cost.
– Ezy
5 hours ago
The question isn't about preparing your node for the new protocol, a baker can just as easily prepare themselves using zeronet or alphanet, and simply have the appropriate versions of the software running on mainnet prior to the new protocol being adopted. The question is specifically about taking part in the baking process on the test chain. There appears to be very weak incentives for bakers to participate in the baking process on the test chain.
– xtzbaker
24 mins ago
@xtzbaker i respectfully disagree one more time: it has everything to do with preparing for the new protocol. zeronet is not guaranteed to be the exact same thing as the mainnet. Testnet is. There is 0 downside in testing in testnet instead of zeronet if the baker is willing to do some testing at all.
– Ezy
22 mins ago
add a comment |
It is a good question. The answer relies on I believe the mistake you made in asserting that there is "no downside" to not participate in the test net.
For example: if a baker has rights just after the protocol updates then if the baker did not prepare his setup to adjust for the new protocol he has a risk of missing his first bakes under the new protocol.
It gives an incentive to "get prepared" and the testnet is the best way to do the transition smoothly
So in conclusion i would say in particular for professional bakers who have public performance metrics and delegators to answer to, that it is important for them to make sure their setup is prepared for the protocol update during the testnet phase
answered 5 hours ago
EzyEzy
2,357427
1
Ensuring you have up to date baking software is absolutely necessary for your baking operation, however that does not mean you need to participate in the test chain, by design the baker should flip to the new protocol for you after the successful test. I'll grant the "be prepared" incentive is there, however it seems equally as weak as the "good of the network" incentive considering you run an increased risk of losing rewards by participating in the test chain
– xtzbaker
5 hours ago
1
@xtzbaker i disagree. If you as a baker wait until the testing phase is finished to change your config you will have operational risk. If you discount this risk as 0 it is your choice of course. But as any risk it has a monetary cost.
– Ezy
5 hours ago
The question isn't about preparing your node for the new protocol, a baker can just as easily prepare themselves using zeronet or alphanet, and simply have the appropriate versions of the software running on mainnet prior to the new protocol being adopted. The question is specifically about taking part in the baking process on the test chain. There appears to be very weak incentives for bakers to participate in the baking process on the test chain.
– xtzbaker
24 mins ago
@xtzbaker i respectfully disagree one more time: it has everything to do with preparing for the new protocol. zeronet is not guaranteed to be the exact same thing as the mainnet. Testnet is. There is 0 downside in testing in testnet instead of zeronet if the baker is willing to do some testing at all.
– Ezy
22 mins ago
add a comment |
It is a good question. The answer relies on I believe the mistake you made in asserting that there is "no downside" to not participate in the test net.
For example: if a baker has rights just after the protocol updates then if the baker did not prepare his setup to adjust for the new protocol he has a risk of missing his first bakes under the new protocol.
It gives an incentive to "get prepared" and the testnet is the best way to do the transition smoothly
So in conclusion i would say in particular for professional bakers who have public performance metrics and delegators to answer to, that it is important for them to make sure their setup is prepared for the protocol update during the testnet phase
answered 5 hours ago
EzyEzy
2,357427
It is a good question. The answer relies on I believe the mistake you made in asserting that there is "no downside" to not participate in the test net.
For example: if a baker has rights just after the protocol updates then if the baker did not prepare his setup to adjust for the new protocol he has a risk of missing his first bakes under the new protocol.
It gives an incentive to "get prepared" and the testnet is the best way to do the transition smoothly
So in conclusion i would say in particular for professional bakers who have public performance metrics and delegators to answer to, that it is important for them to make sure their setup is prepared for the protocol update during the testnet phase
answered 5 hours ago
EzyEzy
2,357427
answered 5 hours ago
EzyEzy
2,357427
answered 5 hours ago
EzyEzy
2,357427
answered 5 hours ago
EzyEzy
2,357427
2,357427
1
Ensuring you have up to date baking software is absolutely necessary for your baking operation, however that does not mean you need to participate in the test chain, by design the baker should flip to the new protocol for you after the successful test. I'll grant the "be prepared" incentive is there, however it seems equally as weak as the "good of the network" incentive considering you run an increased risk of losing rewards by participating in the test chain
– xtzbaker
5 hours ago
1
@xtzbaker i disagree. If you as a baker wait until the testing phase is finished to change your config you will have operational risk. If you discount this risk as 0 it is your choice of course. But as any risk it has a monetary cost.
– Ezy
5 hours ago
The question isn't about preparing your node for the new protocol, a baker can just as easily prepare themselves using zeronet or alphanet, and simply have the appropriate versions of the software running on mainnet prior to the new protocol being adopted. The question is specifically about taking part in the baking process on the test chain. There appears to be very weak incentives for bakers to participate in the baking process on the test chain.
– xtzbaker
24 mins ago
@xtzbaker i respectfully disagree one more time: it has everything to do with preparing for the new protocol. zeronet is not guaranteed to be the exact same thing as the mainnet. Testnet is. There is 0 downside in testing in testnet instead of zeronet if the baker is willing to do some testing at all.
– Ezy
22 mins ago
add a comment |
1
Ensuring you have up to date baking software is absolutely necessary for your baking operation, however that does not mean you need to participate in the test chain, by design the baker should flip to the new protocol for you after the successful test. I'll grant the "be prepared" incentive is there, however it seems equally as weak as the "good of the network" incentive considering you run an increased risk of losing rewards by participating in the test chain
– xtzbaker
5 hours ago
1
@xtzbaker i disagree. If you as a baker wait until the testing phase is finished to change your config you will have operational risk. If you discount this risk as 0 it is your choice of course. But as any risk it has a monetary cost.
– Ezy
5 hours ago
The question isn't about preparing your node for the new protocol, a baker can just as easily prepare themselves using zeronet or alphanet, and simply have the appropriate versions of the software running on mainnet prior to the new protocol being adopted. The question is specifically about taking part in the baking process on the test chain. There appears to be very weak incentives for bakers to participate in the baking process on the test chain.
– xtzbaker
24 mins ago
@xtzbaker i respectfully disagree one more time: it has everything to do with preparing for the new protocol. zeronet is not guaranteed to be the exact same thing as the mainnet. Testnet is. There is 0 downside in testing in testnet instead of zeronet if the baker is willing to do some testing at all.
– Ezy
22 mins ago
1
1
Ensuring you have up to date baking software is absolutely necessary for your baking operation, however that does not mean you need to participate in the test chain, by design the baker should flip to the new protocol for you after the successful test. I'll grant the "be prepared" incentive is there, however it seems equally as weak as the "good of the network" incentive considering you run an increased risk of losing rewards by participating in the test chain
– xtzbaker
5 hours ago
Ensuring you have up to date baking software is absolutely necessary for your baking operation, however that does not mean you need to participate in the test chain, by design the baker should flip to the new protocol for you after the successful test. I'll grant the "be prepared" incentive is there, however it seems equally as weak as the "good of the network" incentive considering you run an increased risk of losing rewards by participating in the test chain
– xtzbaker
5 hours ago
1
1
@xtzbaker i disagree. If you as a baker wait until the testing phase is finished to change your config you will have operational risk. If you discount this risk as 0 it is your choice of course. But as any risk it has a monetary cost.
– Ezy
5 hours ago
@xtzbaker i disagree. If you as a baker wait until the testing phase is finished to change your config you will have operational risk. If you discount this risk as 0 it is your choice of course. But as any risk it has a monetary cost.
– Ezy
5 hours ago
The question isn't about preparing your node for the new protocol, a baker can just as easily prepare themselves using zeronet or alphanet, and simply have the appropriate versions of the software running on mainnet prior to the new protocol being adopted. The question is specifically about taking part in the baking process on the test chain. There appears to be very weak incentives for bakers to participate in the baking process on the test chain.
– xtzbaker
24 mins ago
The question isn't about preparing your node for the new protocol, a baker can just as easily prepare themselves using zeronet or alphanet, and simply have the appropriate versions of the software running on mainnet prior to the new protocol being adopted. The question is specifically about taking part in the baking process on the test chain. There appears to be very weak incentives for bakers to participate in the baking process on the test chain.
– xtzbaker
24 mins ago
@xtzbaker i respectfully disagree one more time: it has everything to do with preparing for the new protocol. zeronet is not guaranteed to be the exact same thing as the mainnet. Testnet is. There is 0 downside in testing in testnet instead of zeronet if the baker is willing to do some testing at all.
– Ezy
22 mins ago
@xtzbaker i respectfully disagree one more time: it has everything to do with preparing for the new protocol. zeronet is not guaranteed to be the exact same thing as the mainnet. Testnet is. There is 0 downside in testing in testnet instead of zeronet if the baker is willing to do some testing at all.
– Ezy
22 mins ago
add a comment |
Thanks for contributing an answer to Tezos Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftezos.stackexchange.com%2fquestions%2f652%2fwhat-incentive-is-there-for-baking-on-the-test-chain-during-voting-period%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
