The vote is not about whether the feature itself should be implemented, but rather about setting the activation epoch. Typically, each new feature deployed on the mainnet has an activation epoch. For DNS V2, we initially set this to a very high number, which was agreed upon by everyone.
Why choose such a “late” activation epoch initially? Activating this kind of feature without a fully prepared platform would make it impractical for 95% of users. It would primarily benefit those who can code or are willing to learn to interact with the MultiversX technical stack programmatically, which isn’t fair to the other majority of users.
P.S. I usually don’t have much time for Twitter, so bringing these things to my attention is helpful. Thanks!
bnistor4
•
Nov 12, 2024
Thank you for the time in responding and for the clarification.
Indeed it could have transpired that it was related to the “time” at the time.
Totally agree to obviously make the feature available to everyone and not to those who know how to interact with the blockchain programmatically.
I guess this new vote is related to the fact that the old deadline for activation is missed so a new one is needed?
Forgive me but I still struggle to understand the real need for a new vote rather than just activation when you feel it is good.
Mihai Alexandru Schiopu
Team•
Nov 12, 2024
The vote is not going to be for DNS specifically but for other changes that are coming together with DNS together with Barnard release.
No, we did not miss the activation epoch, I believe it is set to become active somewhere in year 10.000 atm. So all that we have to do is to set it to a more 2025-ish year.
bnistor4
•
Nov 12, 2024
I understood that the vote is also for other things, that was pretty clear. I am not questioning the other things.
What I don't understand then is why this point about DNS was included now in Barnard.
The only reason I can think of is because when it was proposed with Sirius the activation was put far away on purpose so that there would be time both to implement the functionality as best as possible.
So now because we may need to get the activation closer. (Here the need for the vote and thus the inclusion of the point related to DNS)
However, I find the process a bit odd in that I find the flow a bit nonlinear.
In any case. Thank you in the meantime for the answers and I will wait for more news in the future.
Thank you!
Mihai Alexandru Schiopu
Team•
Nov 12, 2024
I want for you to have a clear understanding of the situation.
I answered in the first reply that yes, on purpose it was set to a late activation epoch because the integration with platforms supporting the feature was not complete (not the feature itself) which would have not been fair for the 95% of users of Multiversx.
When you vote, you vote on a commit hash, that would cover also the fix of the DNS activation epoch, so implicitly also the DNS feature itself, I don’t see anything nonlinear about it.
Why do you feel that it is nonlinear?
bnistor4
•
Nov 12, 2024
I don't want to take up any more of your time than I already have. :D so feel free to move on.
In any case, I don't find this process linear.
1 year almost we voted pretty much “commitment” of DNS v2 development and its activation of course. (but we were perhaps not aware of its future-distant activation).
Time passed, and the activation remained pending despite the fact that the feature was ready (I assume) and we had decided to accept the new integration.
Now it turns out that we have to make a vote that ALSO acts as an activation for DNS v2.
This is what I find strange. What I say is, if we had already decided at the time (with Sirius) to implement the feature and activate it (implied as a thing) what is the point of going through a vote now? At this point just activate it when you feel everything is ready for everyone.
To be very clear:
I understand the motivation for putting a very distant activation date.
I understand making the feature available to anyone.
I understand the complexity and impact of such a launch.
But at this point in history, is it really necessary to wait for Barnard and have this activation go through a vote?
Sorry for repetition.
B.
•
Jun 26, 2024
It was released with Sirius 1.6, in January. When will be live to be used?
Mihai Alexandru Schiopu
Team•
Oct 15, 2024
We finalized the UI/UX changes and it will probably be launched in the next weeks.
Log in to comment and vote
Comments9
B.
Nov 12, 2024
Hi @Mihai Alexandru Schiopu
One thing that makes me puzzled about this task.
https://x.com/bnistor4/status/1856259531971424765
Do you have any comments on that?
Mihai Alexandru Schiopu
Nov 12, 2024
Hi B,
Thanks for reaching out.
The vote is not about whether the feature itself should be implemented, but rather about setting the activation epoch. Typically, each new feature deployed on the mainnet has an activation epoch. For DNS V2, we initially set this to a very high number, which was agreed upon by everyone.
Why choose such a “late” activation epoch initially? Activating this kind of feature without a fully prepared platform would make it impractical for 95% of users. It would primarily benefit those who can code or are willing to learn to interact with the MultiversX technical stack programmatically, which isn’t fair to the other majority of users.
P.S. I usually don’t have much time for Twitter, so bringing these things to my attention is helpful. Thanks!
bnistor4
Nov 12, 2024
Thank you for the time in responding and for the clarification.
Indeed it could have transpired that it was related to the “time” at the time.
Totally agree to obviously make the feature available to everyone and not to those who know how to interact with the blockchain programmatically.
I guess this new vote is related to the fact that the old deadline for activation is missed so a new one is needed?
Forgive me but I still struggle to understand the real need for a new vote rather than just activation when you feel it is good.
Mihai Alexandru Schiopu
Nov 12, 2024
The vote is not going to be for DNS specifically but for other changes that are coming together with DNS together with Barnard release.
No, we did not miss the activation epoch, I believe it is set to become active somewhere in year 10.000 atm. So all that we have to do is to set it to a more 2025-ish year.
bnistor4
Nov 12, 2024
I understood that the vote is also for other things, that was pretty clear. I am not questioning the other things.
What I don't understand then is why this point about DNS was included now in Barnard.
The only reason I can think of is because when it was proposed with Sirius the activation was put far away on purpose so that there would be time both to implement the functionality as best as possible.
So now because we may need to get the activation closer. (Here the need for the vote and thus the inclusion of the point related to DNS)
However, I find the process a bit odd in that I find the flow a bit nonlinear.
In any case. Thank you in the meantime for the answers and I will wait for more news in the future.
Thank you!
Mihai Alexandru Schiopu
Nov 12, 2024
I want for you to have a clear understanding of the situation.
I answered in the first reply that yes, on purpose it was set to a late activation epoch because the integration with platforms supporting the feature was not complete (not the feature itself) which would have not been fair for the 95% of users of Multiversx.
When you vote, you vote on a commit hash, that would cover also the fix of the DNS activation epoch, so implicitly also the DNS feature itself, I don’t see anything nonlinear about it.
Why do you feel that it is nonlinear?
bnistor4
Nov 12, 2024
I don't want to take up any more of your time than I already have. :D so feel free to move on.
In any case, I don't find this process linear.
1 year almost we voted pretty much “commitment” of DNS v2 development and its activation of course. (but we were perhaps not aware of its future-distant activation).
Time passed, and the activation remained pending despite the fact that the feature was ready (I assume) and we had decided to accept the new integration.
Now it turns out that we have to make a vote that ALSO acts as an activation for DNS v2.
This is what I find strange.
What I say is, if we had already decided at the time (with Sirius) to implement the feature and activate it (implied as a thing) what is the point of going through a vote now?
At this point just activate it when you feel everything is ready for everyone.
To be very clear:
I understand the motivation for putting a very distant activation date.
I understand making the feature available to anyone.
I understand the complexity and impact of such a launch.
But at this point in history, is it really necessary to wait for Barnard and have this activation go through a vote?
Sorry for repetition.
B.
Jun 26, 2024
It was released with Sirius 1.6, in January.
When will be live to be used?
Mihai Alexandru Schiopu
Oct 15, 2024
We finalized the UI/UX changes and it will probably be launched in the next weeks.