-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Launch initiative to educate users about the DAO #56
Comments
@m52go Great summary!!!! I agree to all just want to add a few small things... From our Q&A DAO session (I forgot to record it ;-() I saw that there are 2 main problems of understanding the DAO.
I think boths topics are not covered sufficiently in the existing docs and it would be great to get those described in an easy to understand way. As you mentioned already @arunasurya , I think it would be a good idea that a few people with good communication skills partizipate in that effort. Neiman (I dont know his GH handle) would be also a good candidate and he will present the DAO at FOSDEM conference in February. He helped a lot on the conceptual side and he is working with another developer on the new trade protocol. |
@ManfredKarrer great! Yes, those are the exact 2 points I didn't fully understand myself until that call cleared them up. Those will be top priorities to get right. I'll see how we can work on gathering more communicators. Maybe we can try Twitter, etc. |
@m52go thank you for taking initiative! I like your ideas and would love to start working together on defining key concepts, including the ones @ManfredKarrer mentioned. I think it is important that we all understand these concepts well and agree on their definitions before presenting them to the rest of the world. I am open to discussing this in greater detail on slack and have a video call. |
The plan here sounds great. I'm going to riff below on a topic I think will be important in the education effort. It'll require more discussion and thought than what I'm putting together here, but I'd like to get the ball rolling in any case. One thing that's missing from existing documentation, and that smart people will scrutinize, is why BSQ would ever have any value beyond its underlying BTC value. It's important that we avoid accidentally promoting (or believing ourselves) the fallacy that a utility token's value is somehow tied to the value of the project. Potential users of BSQ don't care about the value of the project per se. They care that the BSQ they buy today at a given price is going to be worth the same or more tomorrow, i.e. that it will have the same or better transaction fee purchasing power in the future. For it to do so, there has to be sufficient demand by other users to hold the token so as to keep its value at or above that level. Mere transactional demand isn't enough; there also has to be sufficient reserve demand, i.e. the desire or need to hold the token for longer than it takes just to pay the fees for the next trade. I see several sources of reserve demand in the BSQ economy as we've envisioned it so far:
Of these three, I believe (2) is the most important because it involves potentially large amounts of BSQ being locked away for significant periods of time. The more users are doing this, the more BSQ there is tied up over time, creating potentially significant reserve demand. With that said, off-chain trading is something that will come online some time after the initial launch of the Bisq DAO, so it is only a potential future source of reservation demand, not one that we can count on in the beginning. (1) could become significant as well, but users won't bulk buy in any significant amounts until they trust the token retains its value, so I don't think we should expect much from it in the beginning. (3) will only become a significant source of reservation demand if users believe that (1) and (2) will generate reservation demand on their own. So it's nothing we have direct control over and I believe should basically be disregarded. We certainly don't want to 'pump' BSQ in any way, i.e. intentionally promote the idea that people should speculate on it. Some will do this on their own, assuming they believe in the project. Our job is to make a credible case for the core economics of BSQ, provide a sound implementation of the system and then let the market do the rest. I did not include contributor bonding in the list above, because I don't see this as reservation demand in the classical sense. It does reduce the overall amount of BSQ in circulation, but it is not on its own a source of "demand" for BSQ. What's important is that real users—not just contributors—see BSQ as a valuable resource they want to hold and use. I also have not included in the list above the idea of current BSQ stakeholders forcing a price floor on BSQ by refusing to sell it below a given price (e.g. $1 USD per BSQ). Ultimately, if the market does not see BSQ as being worth $1 per unit, they will bid it down and certain stakeholders will sell at that price, or BSQ will fail altogether because would-be buyers never find willing sellers. As a stakeholder, I think it's good to have a price in mind below which you would not sell, but I think it's also important to accept that we are ultimately at the mercy of our users, and that the process of discovering BSQ's price over time probably will not look like whatever pretty picture we have in our heads. I believe we should be humble as we roll this out, that we should listen closely to the market, and if we're finding the price to be lower than our expectations, to respond by adjusting incentives rather than just doggedly holding out and refusing to sell. Again, this is just a quick summary of my thoughts on this important topic, and it bears further discussion (probably in some venue other than this proposal). I just want to get the conversation started here, so that as we put together these educational materials we're sure to include in them a coherent and hopefully compelling story about BSQ valuation. |
@cbeams thanks for that feedback, very thoughtful, and valuation is certainly an important missing element. I hadn't considered (2) before, will investigate. |
@cbeams Thanks for the summary and discussion. The investment motivation is probably the strongest driver and very hard to estimate. Due legal risks we need to avoid to bring that up actively from our side. So I would leave that to the users to figure out themself if it might be an interesting investment opportunity or not. The fee part is for sure the most important. As we are getting close to break even already I think we should not be too worried that those who understand the whole model are doubting that buying a bit more BSQ as needed. Buying BSQ has also fee costs so to buy just for the next trade would not be very reasonable. Another part will be the asset listing fee. Currently we have over 100 coins (which are not traded). Fees will be low initially but I expect that they will get increased by voting soon after the launch. I think a listing fee of 500-1000 USD is reasonable and that would lead with 100 coins to a significant amount of BSQ. There is also the burn fee feature which might be used to convert back BTC to BSQ in case the fee payment in BTC stays too high. Maybe that will be used for other features (reputation) as well, but that is not clear enough atm. The most important is that our users and core followers really understand the model. As I saw in many discussions that is not easy to achieve as there is much resistance against any tokens and many make too quickly assumptions in direction ICO, etc. And of course it carries some complexity and requires some technical understanding. So I think we really need to be sure that the majority of our core users understand the model. Many of those are using Bisq despite disadvantages regarding convenience and trade fees, motivated because they want to support such a project. If they understand BSQ they will likely support it by buying BSQ as well. |
Excellent overview. To help with this, I think we need to have a specific target audience (profiles of the readers) for the blog posts. It will help determine the structure of the 3-5 posts and what to include in each one. Should they be progressive, gaining in complexity as a 5 blog post series? Should they stand alone? Determining who exactly we think the target reader is and why they are reading it will be important and will help us quickly decide all that, and eliminate wasted time and indecision. From a marketing perspective this will help determine where to share the posts etc. as well. Goals are another key item- I fully support the goal of revamping the email list. However, that should have a few more goals attached to it as far as reach and purpose. A monthly email keeping subscribers updated on Bisq is good, but there are other outcomes that could be important to Bisq which could be helped by a robust email list. For example, driving some viewers to the blog would be good, particularly for new email list subscribers as they may not know much about Bisq and want to learn more. An initial drip of these blog posts via email to new members of the Bisq community could go a long way in making sure those new members and curious people are educated on the platform and don't just fade off into the ether because they just didn't understand it. Thats why we're writing the blog posts and we can use that tool (the blog post explainers) to address that issue. We should also consider having some moderate goals around how many people we want the monthly email to reach and what is the result we want to have with those emails. In my example in the prior paragraph it's clear we want to help new users find the blog posts which can explain Bisq and answer many questions they might have, but thats one example. Having updates delivered via email is great, but there will be other goals that come up in the future that are important to Bisq that can be met by the email list. Used appropriately, the email list will be an excellent way to have important calls to action seen by the right people. You may have some important calls to action right now i'm not aware of and the email list would be a good distribution method to have those items accomplished. Additionally It would be good to prompt people to subscribe to the email list in a few different places (website etc.) as well because that will be important to Bisq later when marketing becomes more of a priority. If a non marketing goal is to preserve the leadership team's time by preventing DRY (don't repeat yourself) with media outlets, a media specific kit might be a good option. That kit should likely be updated periodically with roadmap updates, big wins, stats on the growing user base etc. The media is a different consumer of information than a prospective Bisq user, and as such will have different goals for reading it based on what they plan on doing with the information. They of course will need to understand how Bisq works, but they will likely be interested in the future of the project, perhaps the team, and certainly number of users and volume. So a static blog article can only achieve one of those goals-- explaining how it all works and what it's purpose is. It would fail at the goal of providing user statistics etc which the media may be interested in, and they would still reach out to the Bisq team for time/comment as it doesn't hit those goals. |
also-- i'm "OrphanedBlock" @m52go |
@Emzy any advice for using the email server? I'd like to send an email out by Wednesday to announce the new release. At the very least I'd like to have this functionality for DAO stuff in this proposal by the middle of December. @simonmanka thanks for the feedback! You made several points I want to discuss more...I'll follow up with you on Slack. |
@m52go unfortunately I think the main problem is not technical. The problem is the European GDPR law. Here some more info to mailing lists and the GDPR: |
@Emzy understood. I think it would be a good idea to prune the existing list anyway since we haven't used it for so long. Would you be against using your server to send people that initial message to join the new list? If you'd rather not, that's fine too...we can find another way. |
@m52go sorry, but you have to find another way to send the initial message. |
There is a solid open source software called Mautic that would be excellent for managing email announcements and campaigns. I've white-labeled a version, I've white labeled a version of it, I'd recommend it. @m52go |
This isn't a typical proposal, but I figured it worth writing to convey the initiative and its significance, garner feedback, and perhaps invite some more talent to execute it.
The DAO, BSQ token, and related concepts are intriguing, but they're not intuitive. The DAO—no matter how technically and conceptually robust―won't work if people don't buy BSQ to put it in motion (perhaps even worse, that they're driven away from the project from a misguided notion that Bisq is releasing its own scam token, etc).
Therefore it is critical that we do all we can to explain the DAO as clearly as possible before it launches.
I've been in touch with folks in and out of the project this week to discuss a good approach for doing this. What follows is a proposal that includes the insights I gained to launch a multi-pronged approach at explaining the DAO.
Note that I approach this proposal with the primary mission of educating, not marketing. With that said, we don't want to take time doing all this work and not maximize the number of people who consume it, so some little amount of marketing perspective would be nice.
If you've got experience with content strategy or video production or infographic design or anything else that might be helpful to complete the items below it would be great to hear your perspectives.
I propose we take the following measures to launch an educational initiative for the DAO, in (roughly) descending order of importance:
3-5 part blog series on bisq.network/blog
Re-establish email list
Give talks
Infographic / DAO visualization on website
User-facing DAO documentation
Explainers in software
Medium/personal blog offshoots
The text was updated successfully, but these errors were encountered: