Amending the P2P LayerWhat 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?
How can bays and straits be determined in a procedurally generated map?
LaTeX: Why are digits allowed in environments, but forbidden in commands?
How much RAM could one put in a typical 80386 setup?
Could an aircraft fly or hover using only jets of compressed air?
Why doesn't Newton's third law mean a person bounces back to where they started when they hit the ground?
What's that red-plus icon near a text?
What defenses are there against being summoned by the Gate spell?
Is it possible to do 50 km distance without any previous training?
How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?
Accidentally leaked the solution to an assignment, what to do now? (I'm the prof)
What does the "remote control" for a QF-4 look like?
Do other languages have an "irreversible aspect"?
What are the disadvantages of having a left skewed distribution?
Can an x86 CPU running in real mode be considered to be basically an 8086 CPU?
Is it unprofessional to ask if a job posting on GlassDoor is real?
Can a monk's single staff be considered dual wielded, as per the Dual Wielder feat?
NMaximize is not converging to a solution
Convert two switches to a dual stack, and add outlet - possible here?
Languages that we cannot (dis)prove to be Context-Free
I'm flying to France today and my passport expires in less than 2 months
Paid for article while in US on F-1 visa?
Was any UN Security Council vote triple-vetoed?
How do I deal with an unproductive colleague in a small company?
Maximum likelihood parameters deviate from posterior distributions
Amending the P2P Layer
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 (http://tezos.gitlab.io/mainnet/whitedoc/the_big_picture.html), 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
add a comment |
Is it possible to amend the P2P layer of Tezos? As far as I understand from (http://tezos.gitlab.io/mainnet/whitedoc/the_big_picture.html), 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
add a comment |
Is it possible to amend the P2P layer of Tezos? As far as I understand from (http://tezos.gitlab.io/mainnet/whitedoc/the_big_picture.html), 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
Is it possible to amend the P2P layer of Tezos? As far as I understand from (http://tezos.gitlab.io/mainnet/whitedoc/the_big_picture.html), 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
asked 2 days ago
ralexralex
936
936
add a comment |
add a comment |
1 Answer
1
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
https://medium.com/altcoin-magazine/why-we-are-writing-a-tezos-node-shell-in-rust-with-demo-aa03813e48d8
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
1 Answer
1
active
oldest
votes
1 Answer
1
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
https://medium.com/altcoin-magazine/why-we-are-writing-a-tezos-node-shell-in-rust-with-demo-aa03813e48d8
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
https://medium.com/altcoin-magazine/why-we-are-writing-a-tezos-node-shell-in-rust-with-demo-aa03813e48d8
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
https://medium.com/altcoin-magazine/why-we-are-writing-a-tezos-node-shell-in-rust-with-demo-aa03813e48d8
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
https://medium.com/altcoin-magazine/why-we-are-writing-a-tezos-node-shell-in-rust-with-demo-aa03813e48d8
edited 2 days ago
answered 2 days ago
cousinitcousinit
1,060314
1,060314
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