Open willjgriff opened 3 years ago
I played with it a bit, removed some phrases here and there, tell me what you think.
I like it, I think the simplifications make sense, and I like the use cases at the end a bit better, and it sort of roles into the 1hive use case as well.
I started conceptualising the video based on this script and need your thoughts on this. If we want to make video more engaging for wide range of crypto users, we need to present it in understandable way, currently it all seems like a wall of information. So it would be awesome if we can divide our script in sections like so:
Celeste enables the creation of decentralized applications for new use cases including:
It's okay if we go above 60sec a little.
Another stab at it.
Acceptable actions will not be challenged and will be processed at the end of a delay.
I think the previous version was more accurate. When reading this i interpret that as long as my action is acceptable (follows 1hive covenant guidelines), the action won't be challenged which is not 100% true
I think maybe something like Actions that are not challenged will be processed at the end of a delay.
Also with delay
are we referring to the voting period/ conviction estimated time ?
If so what do you think of Actions that are not challenged will be processed at the end of their corresponding period duration.
Suggestions (take from them what you will :)
...
Any user can perform an action, for example requesting request payment for work or creating create a vote, by locking a deposit.
Actions can be challenged for some window of time.
If an action isn't challenged, it will be executed. Acceptable actions will not be challenged and will be processed at the end of a delay.
If an action is challenged, a committee is randomly selected who to vote on whether it should be allowed or removed.
Anyone can escalate the dispute to a larger committee, but eventually a final decision will be made. The vote can be escalated to larger committees but eventually it will be finalised.
Those voting inline with the plurality majority make money, while those voting against the plurality majority lose money.
After a decision has been made the action is either executed can then be processed or it is or removed.
Celeste enables applications for use cases including can be used for:
....
Improving token-based governance
And it will be used to secure the 1Hive Protocol from whales (by allowing anyone to challenge proposals that aren’t in line with the values of the community)
Learn more here...
Ah i think that we should remove the wording questions and answers since we change it for disputes in celeste
@fabriziovigevani I can see the first point, that's fair.
As for the second point I think it need's to be as concise as possible because the current version isn't very clear when spoken with the video. I think using the term "delay", or perhaps some other word someone can think of instead of 3 words, is better to keep it short and understandable.
Ah i think that we should remove the wording questions and answers since we change it for disputes in celeste
@rperez89 Do you (or anyone) have any suggestions for how we can reword these 3 points with the above in mind?
Ah i think that we should remove the wording questions and answers since we change it for disputes in celeste
@rperez89 Do you (or anyone) have any suggestions for how we can reword these 3 points with the above in mind?
- Capturing answers to questions in a decentralised way is hard.
- Our application wants to know the answer to a question, for example, has a user completed some work? Or is a pending vote malicious?
- With Celeste we can answer these questions without a centralised authority.
mmmhh maybe:
Next version:
OR
^^^ Please make other suggestions for the first 3 points. I'm struggling to think of something for the dispute narrative. ^^^
I think it reads pretty well :)
Just one minor suggestion to make it even tighter:
With Celeste we can answer these questions without a centralised authority.
==> With Celeste we can provide an answer without a central authority.
After a decision has been made the action can be processed or it is removed.
I still think this is awkward..
Regarding the disputes vs questions debate, it’s not so much resolving a dispute that’s hard, but correctly answering subjective questions (disputes are a consequence of this really). So I’m not in favour of changing the narrative unless we somehow get this point across.
I think it reads pretty well :)
Just one minor suggestion to make it even tighter:
With Celeste we can answer these questions without a centralised authority.
==> With Celeste we can provide an answer without a central authority.
After a decision has been made the action can be processed or it is removed.
I still think this is awkward..
Regarding the disputes vs questions debate, it’s not so much resolving a dispute that’s hard, but correctly answering subjective questions (disputes are a consequence of this really). So I’m not in favour of changing the narrative unless we somehow get this point across.
The thing is that all is named as disputes in celeste, so what is kind of awkward is to call them in a different way in the presentation video i think.
@rperez89 right. But the disputes arise over the answer to a subjective question, do they not? If so, i don't think it's inconsistent.
In the interest of time lets stick with questions for the first bit. Final draft below. Feel free to make suggestions but we should get someone reading this and get it synced up with the video.
Inspo: https://twitter.com/aaveaave/status/1351504986698616832?s=21