I wouldn't call that a lie, maybe just a bad choice of words. What they are doing is something I've been saying for years; namely self-awareness. They're applying the pillar of blockchain tech to the code itself. I truly believe in time this will become the norm.. only private and government blockchains will retain their own governance.I just looked at their website and the first thing I read was a lie. Tezos is the first and only blockchain with decentralised governance.
Here is where Arthur Breitman describes how Tezos can become any ledger and any coin.I thought Tezos uses it's own ledger? - but most definitely, if they had a node incentive programme, I'd be all over it.
https://www.youtube.com/watch?v=3mgaDpuMSc0&feature=youtu.be&t=1930
"They're applying the pillar of blockchain tech to the codeitself" - what does that mean?I wouldn't call that a lie, maybe just a bad choice of words. What they are doing is something I've been saying for years; namely self-awareness. They're applying the pillar of blockchain tech to the code itself. I truly believe in time this will become the norm.. only private and government blockchains will retain their own governance.
"They're applying the pillar of blockchain tech to the codeitself" - what does that mean?
Honestly, I looked at the website and I don't really get what Tezos actually is, someone ELI5. If I don't understand it and it can't be explained clearly in laymen terms then a.) it's too complicated for the average Joe and b.) I can't make an informed decision on if it's needed - which is why I voted other.
If it's governance for Dash then Dash already has that - and so far, I like Dash's governance model.
How exactly would this benefit Dash?
If you care so much about average joe, then why you deal with cryptocurrencies? Average joe cannot understand cryptocurrencies at all. Average joe cannot use internet. Average joe cannot even read or calculate. Those things are too complicated for him.a.) it's too complicated for the average Joe.
You pay a lot of money from the budget in things that are bullshits. You pay for advertising, for videos, for online stores and communities, for feasts. Just pay a small amount of money also for research. It wont hurt you, trust me.If it's governance for Dash then Dash already has that - and so far, I like Dash's governance model.
How exactly would this benefit Dash?
Dash voted for 2mb blocksit means that they vote for the software updates, using blockchain.
and reached consensus within 24 hours.Dash voted for 2mb blocks
When people talk about the wonders of blockchain, they will often tell you it's great for voting and also to verify supply chains... yet so far all blockchain projects do not apply these principles to their own projects... hence you get projects like ethereum that are happy to unconditionally fork to infinity. A blockchain that behaves like gold today might magically behave like silver tomorrow... in which case it's a bit disingenuous to call them blockchain "assets". The way I understand, Tezos hopes to apply some lock down to the code such that a few elite geeks are no longer masters of the universe... thus granting stability to the little people."They're applying the pillar of blockchain tech to the codeitself" - what does that mean?
The consensus model of Tezos reflects also to the code itself. It is not just a budget consensus. The vote has immediate result to the runtime code.and reached consensus within 24 hours.
I also do not see the clear advantage for Dash here. It looks like Tezos (just like Dash) developed a blockchain supported consensus model, where stakeholders in their coin will have voting power.
Only they chose a pure Proof of Stake model and are supporting Turing complete smart contracts, security-wise that immediately raises red flags for me.
Just tell us in simple words why Dash would benefit from instantiation on their platform ?
My understanding is that sentinel will allow MNs to vote on 'objects' which will include variables embedded in the code.When people talk about the wonders of blockchain, they will often tell you it's great for voting and also to verify supply chains... yet so far all blockchain projects do not apply these principles to their own projects... hence you get projects like ethereum that are happy to unconditionally fork to infinity. A blockchain that behaves like gold today might magically behave like silver tomorrow... in which case it's a bit disingenuous to call them blockchain "assets". The way I understand, Tezos hopes to apply some lock down to the code such that a few elite geeks are no longer masters of the universe... thus granting stability to the little people.
My understanding is that sentinel will allow MNs to vote on 'objects' which will include variables embedded in the code.
I could be wrong but my interpretation of Evans comments are that MN will be able to vote on sprok variables etc.
Which in essence what u are talking about.
Poll:Should 10% budget be a constant number for the present and the future?(yes/no/other)Because something is generated by a protocol, this does not mean that it is not a tax. It is a protocol generated tax.
What I mainly argue is that 10% is a hardcoded number, thus a wrong number. This is not correct, it should be a number that fits to the will of the active members of the community. If you have a theory explaining why 10% is the correct number for the community of today, then it is ok. But you have not. So in the case a number has no theory, then this number should vary in order to fit best into the community's current needs (and vary again in order to fit to the future needs of course).
And who is about to decide the change of that number? It is either Evan, or the core team, or the MN owners, or the miners, or the wallet owners. I am in favor of the third or fourth option. I dont think the fifth option (wallet owners) is appropriate, because wallet owners get benefits from the budget (for example they hope the basic income to be written in the budget).
So lets inspect the decision tree to be voted, and how polls are dependant eachother. More dependent polls could occur of course, this is just the simpliest decision tree example about this subject.
Poll:Should 10% budget be a constant number for the present and the future?(yes/no/other)
---Voted yes/other---> end
---Voted no-------------> Poll:Should Evan decide the change of this number? (yes/no/other)
And who is allowed to vote into this decision tree? Evan and the core team currently.Poll:Should core team decide the change of this number?(yes/no/other)
Poll:Should MN owners decide the change of this number?(yes/no/other)
------ Voted no/other--->end
-------Voted yes -----------> Poll: Should MN owners decide that change by voting with numbers? (yes/no/other)
Poll:Should miners decide the change of this number?(yes/no/other)
Poll:Should wallet owners decide the change of this number?(yes/no/other)
But I claim that at least MN owners should also be allowed to vote on it. Not by voting a simple yes or no for a proposed budget percentage, but by voting with a number, a number between 0% and 100%. And then the poll result should be the average of all the number votes.
as with all systems of governance. Some things are fixed, some are variable. I think most people can live with that.Poll:Should 10% budget be a constant number for the present and the future?(yes/no/other)
---Voted yes/other---> end
---Voted no-------------> Poll:Should Evan decide the change of this number? (yes/no/other)
Poll:Should core team decide the change of this number?(yes/no/other)
Poll:Should MN owners decide the change of this number?(yes/no/other)
------ Voted no/other--->end
-------Voted yes -----------> Poll: Should MN owners decide that change by voting with numbers? (yes/no/other)
-------Voted yes -----------> Poll:Should MN ownes decide the change by voting yes/no on a proposal of the core team? (yes/no/other)
Poll:Should miners decide the change of this number?(yes/no/other)
Poll:Should wallet owners decide the change of this number?(yes/no/other)
So in the decision tree, sentinel stands in the position marked as bold. Interesting...
as with all systems of governance. Some things are fixed, some are variable. I think most people can live with that.
I look forward to hearing more about it. But I'm still not convinced about smart contracts. We still haven't cracked simple payments or currency exchange. Never mind turning on your toaster using your alarm clock.Well in that case, and if the 10% fixed number of the budget system cannot change with sentinel, then this is exactly what tezos port may offer (among many other things) to dash.
You will not hear more about it, unless you change your vote to yes and you convince also others to vote yes, in order to be legitimate for someone to contact the tezos team and ask them to port dash into their platfom.I look forward to hearing more about it. But I'm still not convinced about smart contracts. We still haven't cracked simple payments or currency exchange. Never mind turning on your toaster using your alarm clock.
Poll:Should 10% budget be a constant number for the present and the future?(yes/no/other)
---Voted yes/other---> end
---Voted no-------------> Poll:Should Evan decide the change of this number? (yes/no/other)
Poll:Should core team decide the change of this number?(yes/no/other)
Poll:Should MN owners decide the change of this number?(yes/no/other)
------ Voted no/other--->end
-------Voted yes -----------> Poll: Should MN owners decide that change by voting with numbers? (yes/no/other)
-------Voted yes -----------> Poll:Should MN owners decide that change by voting yes/no on a proposal of the core team? (yes/no/other)
Poll:Should miners decide the change of this number?(yes/no/other)
Poll:Should wallet owners decide the change of this number?(yes/no/other)
So in the decision tree, sentinel stands in the position marked as bold? Interesting...
https://www.youtube.com/watch?v=3mgaDpuMSc0&feature=youtu.be&t=2054
No, because dash core will continue to "upgrade" with or without the consent of MNs.. AFAIK Tezos is putting control into the hands of it's users... if you want to modify against the will of the users then you'll have to fork... which makes a bloody change because right now crypto devs are the new bankers, constantly moving the goal posts and telling everyone else to fork off.My understanding is that sentinel will allow MNs to vote on 'objects' which will include variables embedded in the code.
I could be wrong but my interpretation of Evans comments are that MN will be able to vote on sprok variables etc.
Which in essence what u are talking about.
Below Arthur Breitman explains the tezos contract model.Nobody was asked about the protocol, the core team decided about it. And all of us had just one choice, either accept it and become members of dash, or reject it and leave dash. This is not correct. Protocols should not give only the accept and the reject choice.
At the begining the core team should put into a vote all initial values of their protocol. And in a second version, all inital decisions of the protocol should also become a subject to vote.
This is can be done by using reflective programming. The protocol should follow the reflective programming principles, and the core team must learn how to write in a reflective way. In computer science, reflection is the ability of a computer program to examine, introspect, and modify its own structure and behavior at runtime.
https://www.youtube.com/watch?v=pNerM72f0Pk&feature=youtu.be&t=1681
If it is succesful for others, maybe it will be too late for Dash.perhaps we should wait and see if it is successful for others before funding anything.