Amending the P2P Layer Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What determines the length of a cycle in Tezos?Network restrictions on Tezos baking?What does “stakeholders govern the protocol” exactly means?How many full nodes on the tezos network?How do I base58 encode the chain ID using Python?How does the tezos blockchain security model works?Block Withholding AttacksCan I use an RPC to switch the Tezos node to another protocol?
What does Turing mean by this statement?
Putting class ranking in CV, but against dept guidelines
Crossing US/Canada Border for less than 24 hours
How were pictures turned from film to a big picture in a picture frame before digital scanning?
What is an "asse" in Elizabethan English?
Dyck paths with extra diagonals from valleys (Laser construction)
Trademark violation for app?
Can you explain what "processes and tools" means in the first Agile principle?
Maximum summed subsequences with non-adjacent items
How did Fremen produce and carry enough thumpers to use Sandworms as de facto Ubers?
How to write capital alpha?
What initially awakened the Balrog?
Why is it faster to reheat something than it is to cook it?
How does the math work when buying airline miles?
How to pronounce 伝統色
Why does it sometimes sound good to play a grace note as a lead in to a note in a melody?
What is the difference between globalisation and imperialism?
Most bit efficient text communication method?
Is there public access to the Meteor Crater in Arizona?
Did any compiler fully use 80-bit floating point?
Why weren't discrete x86 CPUs ever used in game hardware?
Drawing spherical mirrors
The Nth Gryphon Number
Amount of permutations on an NxNxN Rubik's Cube
Amending the P2P Layer
Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?What determines the length of a cycle in Tezos?Network restrictions on Tezos baking?What does “stakeholders govern the protocol” exactly means?How many full nodes on the tezos network?How do I base58 encode the chain ID using Python?How does the tezos blockchain security model works?Block Withholding AttacksCan I use an RPC to switch the Tezos node to another protocol?
Is it possible to amend the P2P layer of Tezos? As far as I understand from here, the amendment process is only for the economic protocol.
If we wanted to suggest changes to how the P2P layer works through future research, how would we go about it? Through a hard fork?
protocol network
edited Apr 8 at 10:04
luchonacho
620519
asked Apr 3 at 3:48
ralexralex
936
add a comment |
Is it possible to amend the P2P layer of Tezos? As far as I understand from here, the amendment process is only for the economic protocol.
If we wanted to suggest changes to how the P2P layer works through future research, how would we go about it? Through a hard fork?
protocol network
edited Apr 8 at 10:04
luchonacho
620519
asked Apr 3 at 3:48
ralexralex
936
add a comment |
Is it possible to amend the P2P layer of Tezos? As far as I understand from here, the amendment process is only for the economic protocol.
If we wanted to suggest changes to how the P2P layer works through future research, how would we go about it? Through a hard fork?
protocol network
edited Apr 8 at 10:04
luchonacho
620519
asked Apr 3 at 3:48
ralexralex
936
Is it possible to amend the P2P layer of Tezos? As far as I understand from here, the amendment process is only for the economic protocol.
If we wanted to suggest changes to how the P2P layer works through future research, how would we go about it? Through a hard fork?
protocol network
protocol network
edited Apr 8 at 10:04
luchonacho
620519
asked Apr 3 at 3:48
ralexralex
936
edited Apr 8 at 10:04
luchonacho
620519
asked Apr 3 at 3:48
ralexralex
936
edited Apr 8 at 10:04
luchonacho
620519
edited Apr 8 at 10:04
luchonacho
620519
edited Apr 8 at 10:04
luchonacho
620519
620519
asked Apr 3 at 3:48
ralexralex
936
asked Apr 3 at 3:48
ralexralex
936
asked Apr 3 at 3:48
ralexralex
936
936
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The P2P layer is part of the shell and is not amended via the onchain governance. Improvements to the existing approach are always welcome by contributing to the gitlab.
People are also free to work on separate implementations of the shell and explore different approaches to optimization while still remaining compatible with the existing shell. And of course nothing stops anyone from deciding they want to be incompatible and attempt to fork.
There is already an implementation in Rust underway whose motivation is described as:
The Tezos ecosystem will benefit from an increase in the diversity of its nodes (multiple implementations across a range of different programing languages & operating systems). It allows us to verify that the protocol is unambiguous. It keeps the door open for innovation and secures the honesty of all participants.
For more details see here.
edited Apr 8 at 10:04
luchonacho
620519
answered Apr 3 at 6:37
cousinitcousinit
1,100314
You don't have to fork even if you make a different version of the protocol.
– Pierre Chambart
Apr 8 at 21:13
add a comment |
There is a version negotiation at the initialization of the connection. You can make an incompatible version of the P2P protocol as long as it has a different version name. For the network not to be split, you need at least one node that speaks both versions of the protocol.
answered Apr 8 at 21:11
Pierre ChambartPierre Chambart
1962
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%2f980%2famending-the-p2p-layer%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The P2P layer is part of the shell and is not amended via the onchain governance. Improvements to the existing approach are always welcome by contributing to the gitlab.
People are also free to work on separate implementations of the shell and explore different approaches to optimization while still remaining compatible with the existing shell. And of course nothing stops anyone from deciding they want to be incompatible and attempt to fork.
There is already an implementation in Rust underway whose motivation is described as:
The Tezos ecosystem will benefit from an increase in the diversity of its nodes (multiple implementations across a range of different programing languages & operating systems). It allows us to verify that the protocol is unambiguous. It keeps the door open for innovation and secures the honesty of all participants.
For more details see here.
edited Apr 8 at 10:04
luchonacho
620519
answered Apr 3 at 6:37
cousinitcousinit
1,100314
You don't have to fork even if you make a different version of the protocol.
– Pierre Chambart
Apr 8 at 21:13
add a comment |
The P2P layer is part of the shell and is not amended via the onchain governance. Improvements to the existing approach are always welcome by contributing to the gitlab.
People are also free to work on separate implementations of the shell and explore different approaches to optimization while still remaining compatible with the existing shell. And of course nothing stops anyone from deciding they want to be incompatible and attempt to fork.
There is already an implementation in Rust underway whose motivation is described as:
The Tezos ecosystem will benefit from an increase in the diversity of its nodes (multiple implementations across a range of different programing languages & operating systems). It allows us to verify that the protocol is unambiguous. It keeps the door open for innovation and secures the honesty of all participants.
For more details see here.
edited Apr 8 at 10:04
luchonacho
620519
answered Apr 3 at 6:37
cousinitcousinit
1,100314
You don't have to fork even if you make a different version of the protocol.
– Pierre Chambart
Apr 8 at 21:13
add a comment |
The P2P layer is part of the shell and is not amended via the onchain governance. Improvements to the existing approach are always welcome by contributing to the gitlab.
People are also free to work on separate implementations of the shell and explore different approaches to optimization while still remaining compatible with the existing shell. And of course nothing stops anyone from deciding they want to be incompatible and attempt to fork.
There is already an implementation in Rust underway whose motivation is described as:
The Tezos ecosystem will benefit from an increase in the diversity of its nodes (multiple implementations across a range of different programing languages & operating systems). It allows us to verify that the protocol is unambiguous. It keeps the door open for innovation and secures the honesty of all participants.
For more details see here.
edited Apr 8 at 10:04
luchonacho
620519
answered Apr 3 at 6:37
cousinitcousinit
1,100314
The P2P layer is part of the shell and is not amended via the onchain governance. Improvements to the existing approach are always welcome by contributing to the gitlab.
People are also free to work on separate implementations of the shell and explore different approaches to optimization while still remaining compatible with the existing shell. And of course nothing stops anyone from deciding they want to be incompatible and attempt to fork.
There is already an implementation in Rust underway whose motivation is described as:
The Tezos ecosystem will benefit from an increase in the diversity of its nodes (multiple implementations across a range of different programing languages & operating systems). It allows us to verify that the protocol is unambiguous. It keeps the door open for innovation and secures the honesty of all participants.
For more details see here.
edited Apr 8 at 10:04
luchonacho
620519
answered Apr 3 at 6:37
cousinitcousinit
1,100314
edited Apr 8 at 10:04
luchonacho
620519
edited Apr 8 at 10:04
luchonacho
620519
edited Apr 8 at 10:04
luchonacho
620519
620519
answered Apr 3 at 6:37
cousinitcousinit
1,100314
answered Apr 3 at 6:37
cousinitcousinit
1,100314
answered Apr 3 at 6:37
cousinitcousinit
1,100314
1,100314
You don't have to fork even if you make a different version of the protocol.
– Pierre Chambart
Apr 8 at 21:13
add a comment |
You don't have to fork even if you make a different version of the protocol.
– Pierre Chambart
Apr 8 at 21:13
You don't have to fork even if you make a different version of the protocol.
– Pierre Chambart
Apr 8 at 21:13
You don't have to fork even if you make a different version of the protocol.
– Pierre Chambart
Apr 8 at 21:13
add a comment |
There is a version negotiation at the initialization of the connection. You can make an incompatible version of the P2P protocol as long as it has a different version name. For the network not to be split, you need at least one node that speaks both versions of the protocol.
answered Apr 8 at 21:11
Pierre ChambartPierre Chambart
1962
add a comment |
There is a version negotiation at the initialization of the connection. You can make an incompatible version of the P2P protocol as long as it has a different version name. For the network not to be split, you need at least one node that speaks both versions of the protocol.
answered Apr 8 at 21:11
Pierre ChambartPierre Chambart
1962
add a comment |
There is a version negotiation at the initialization of the connection. You can make an incompatible version of the P2P protocol as long as it has a different version name. For the network not to be split, you need at least one node that speaks both versions of the protocol.
answered Apr 8 at 21:11
Pierre ChambartPierre Chambart
1962
There is a version negotiation at the initialization of the connection. You can make an incompatible version of the P2P protocol as long as it has a different version name. For the network not to be split, you need at least one node that speaks both versions of the protocol.
answered Apr 8 at 21:11
Pierre ChambartPierre Chambart
1962
answered Apr 8 at 21:11
Pierre ChambartPierre Chambart
1962
answered Apr 8 at 21:11
Pierre ChambartPierre Chambart
1962
answered Apr 8 at 21:11
Pierre ChambartPierre Chambart
1962
1962
add a comment |
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%2f980%2famending-the-p2p-layer%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
