AMA : ArweaveNews X Ecclesia
Over which blockchains is Ecclesia built?
Currently we are only building Ecclesia on the Arweave blockchain, however we have been looking more extensively at including some cross-chain compatibility. This isn’t an issue we are currently very concerned with, as it will likely come down to regulatory reasons if we have to build a multi-chain dApp. Regardless of what happens, Arweave will certainly be used as the layer one.
Where does Ecclesia use Arweave Blockchain?
Ecclesia is planning on using Arweave at almost every step of the process. All user posts and interactions will be stored on the blockchain. We plan on using Argo to host the app on Arweave. The main instances in which Ecclesia may incorporate off chain elements are in using a fiat to crypto onramp, and in gateway hosting to allow for better loading times for users.
Ecclesia is a scalable protocol? Can it be extended / enhanced by community contributions?
We are currently taking a fairly conservative approach to the scalability of Ecclesia as a platform. On the one hand, we are looking for as much community input as possible, and in the coming weeks are looking to incorporate more of the community in creating the platform. We really want anyone who is interested in getting involved to reach out, because a diversity of expertise is what will make Ecclesia truly unique. On the other hand, we are looking to keep Ecclesia as a “closed” platform, and treating the operability of it as similar to a Web 2.0 app. We are aware of the $QUAD protocol and the amazing value it provides for those who use it. However, we have made the decision to build our own separate protocol for two main reasons. First, having our own protocol allows us to have control over how we reach compliance with various legal systems. Blockchains and DAO’s fall into a lot of grey areas, and so by controlling our own protocol, we can ensure that we expose ourself minimally to legal regulations. Second, protocols such as $QUAD are targeted for a very particular intended audience, and simply put, it is not in line with our target audience. Our target audience largely doesn’t care to be given ownership when they interact with a platform; they just want an immutable social platform. For these two reasons, we are limiting the interoperability that could be offered when building on the Arweave blockchain.
Will the project issue its own token? If yes… where will it be created (network)?
Ecclesia is not planning on issuing our own token to interact with the platform. We are planning on creating a profit sharing community in which PSTs will be issued to the platform’s creators, but for user interactions we are just planning on using AR.
Is Ecclesia open source? If not, what are reasons to keep it closed source?
Ecclesia will be almost entirely open source. The only aspects that may have to be closed source are gateway operations and the crypto on-ramp.
Goals? And why a normal user would use your platform?
Our main goal is to create a user-friendly enough experience that it gains adoption from a Web 2.0 audience. Most dApps require the user to be at least familiar with what blockchain is. We are hoping to remove this knowledge barrier, so that the numerous benefits that are provided by blockchain based applications can be accessed by a blockchain unaware audience.
Do you think that people will take the time to understand crypto in order to use your app?
I don’t think most users will take the time to understand crypto, and I don’t think they will need to. In the same way that most internet users don’t understand SSL certificates, users should not need to understand crypto in order to reap the benefits of it.
Who is your target audience?
Our target audience is somewhat two-fold, and is actually an area of our business model that we are trying to redefine. Currently, our target audience is people who have something to say, people who want to hear it, and who are being prevented from spreading that message. On the other hand, we are designing an influence weighted system that enables users to collectively mobilize to make their interactions with leaders more meaningful. We are currently trying to focus our user experience and branding more towards the latter audience, because we believe that it makes for a more unique and viable business model.
Who do you envision to be the main user/s of your platform?
Similar to the last question, we envision the main users to be somewhat two-fold. Our ideal user would be somebody who is interested in moving the public discourse forward, and who believes that everybody deserves a seat at the table when taking part in public discourse.
Ecclesia Twitter : https://twitter.com/EcclesiaSpeech?s=09
