Please describe your proposed solution.
<u>The protocol</u>
The dBranch news and information protocol will standardize publication and versioning of raw data, sources, citations, articles, opinions, reviews and fact checks. Each will be published using content addressing from IPFS which will enable permanent, immutable referencing that enhance transparency and audit-ability of content and minimizes link rot (links that break over time).
IPFS alone does not create an audit-able history, for that we need a blockchain. As sources are published, their IPFS addresses (CIDs) are written to the blockchain. This gives us a record of who published what, when. As content is updated the CID representing the new version will also be added to the blockchain which gives us the ability to audit the version history.
<u>The dBranch node</u>
The dBranch node (github) has everything needed to publish and curate content: the cardano node, db-sync and wallet, an ipfs node and the dBranch backend. An author can use the desktop application to draft and publish content and then use the node to submit the CID to the cardano blockchain. The backend uses transaction metadata to add the CID and article name to the blockchain. Currently, the wallet sends ADA to itself, it is a moot transaction that exists solely to announce the existence of the article. The transaction in the future will be used to send a small amount of ADA to a development team for a sustainable product.
The dBranch node can be used to curate articles. It will follow the blockchain and download, store and host (via IPFS) articles from authors or topics the curator is interested in. This approach will allow the growth of cooperative networks that pool resources to expand each actor's bandwidth and availability.
<u>A public goods non-compete protocol</u>
For the web's data to be truly interoperable there must be a non compete layer that standardizes information exchange. The dBranch protocol will be agnostic to the economic model of all participants, this allows dBranch to plug into any social media app centralized or not, any crowd funding platform centralized or not, any blockchain, any currency, anything, anywhere.
<u>A public goods company</u>
Development of the protocol and open source software implementation will be sustained by a public goods company. The business will be sustained by running a cloud hosted service which makes publishing as simple as using a traditional blogging platform. Because the protocol is open, users may migrate their content to another host or self host at any time. The records will be still be on the blockchain but they must host their content themselves. For those who run their own node, the source code will automatically (unless disabled) send a small fee to the company wallet when publishing an article.
<u>A new economic model</u>
The dBranch whitepaper breaks journalism up into several branches: contributors (journalists), researchers (investigative journalists), reviewers, studios, curators and audience. Legacy institutions combine many (if not all) of these branches into one company with aligned financial incentives. The dBranch protocol will enable these actors to separate their financial interest; for example if a reviewer is independent from a news outlet their incentive is not to maximize the reach of a news article so they can be as honest as they like.
While the protocol will be agnostic to economic funding, the long term goal of dBranch will eventually create (but not enforce) tools for crowd funding. Current crowd funding for journalism is limited to funding individuals or small outlets, but if successful, a small outlet will grow into a large one that recreates the problems they set out to solve. dBranch aims to alleviate this by separating financial incentives (and assets) into the aforementioned branches which separates power. dBranch consumers will have the ability to fund an entire ecosystem as easily as existing crowd funding platforms, however, under the hood they are funding potentially separate entities with separate financial motivations designed to limit the negative incentives of each (read this article for more information on the different branches).
The user experience section below will explain this with examples.
<u>User experience</u>
The neutrality of this protocol creates protections for all participants in the news ecosystem.
For the reader
Readers will be able to read their news in a platform that is external from the publisher which means that the publisher will have to follow the protocol in order to reach an audience. Node operators and curators will use the blockchain as their news wire. Only content published with immutable history will be available in neutral platforms. This limits an author's ability to manipulate history because each version of an article or source will be verifiable.
Additionally, because the protocol standardizes citations of things like transcripts and press releases, when an author quotes a source, the protocol will be referencing the source's IPFS content ID. This prevents cherry picking and misrepresentation because the article itself will not actually contain the quoted text, it will will reference the source by content ID and the user interface will load the external citation and put the quote inline. The user won't notice the difference but they will be able to hover their mouse over the quote and load the full, original source to determine for themselves the accuracy of the representation. By making it easier to audit we make it more difficult to get away with misrepresentation.
For the journalist
Trust is a two-way street. An author who uses a transparent system is likely to be viewed as more trustworthy. Ethical journalists need not be afraid of immutable history. We all make mistakes, and audit-ability will help separate authors who make mistakes from those who manipulate history.
The long term goal of dBranch is to support full decentralization as well as have a centralized version for those without the skills (or desire) to run their own node. It will be as easy as using any existing blogging platform but robust enough to deploy your own node and fully customize the software for a particular implementation. Local news outlets will be able to reduce their IT infrastructure costs by migrating to a free and open source framework for journalism. Independents will be able to migrate their work from the centralized service to another service or self hosted node at any time.
Journalists will also be a part of the internet information revolution. A link's half life is estimated to be about two years, meaning half of all links on the internet break after about two years. This is not acceptable for a robust information system, the internet itself needs a Dewey decimal system type of revolution and dBranch aims to build that!
For a news source
News sources such as government agencies, private companies, or any newsworthy individual will gain an advantage from dBranch as well. Official sources will be cryptographically signed on the Cardano blockchain which creates trust assumptions. Raw data, press releases, transcripts, etc will all be published raw, and journalists will cite the sources directly via content id rather than copy and paste quotes and share a link to the source that will break in 2 years. Additionally by verifying wallet addresses, neutral interfaces can give sources who are cited the ability to rebut claims in news articles directly with links that are out of the authors' control.
Note: You may read the dBranch whitepaper here which has more information, but it is outdated. The general vision is the same but details and execution will change. Notably, I am shifting from running the development team as a DAO to a public goods company.
Please describe how your proposed solution will address the Challenge that you have submitted it in.
Category: Dapps, Products & Integrations
This solution integrates an external protocol with the Cardano blockchain. It fits into several of the subcategories mentioned. It could be considered a marketplace for journalism, it will eventually integrate with social media, and nation states could use it for official statements that when combined with social media can help prevent the spread of misinformation. And journalism itself fits into the miscellaneous category.
To be clear, the protocol and software is a prototype and not fully developed so the funding would cover protocol development and its first integration with any blockchain. See below for more specifics.
What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?
I can think of two potential risks. Right now I am the sole developer of this project that does not have much of a following. The first risk is that I may not succeed in building the large team necessary for the full scope of this project and the second is that it may not get enough traction to have a large user base.
To solve for the first problem the scope of this proposal is designed to take the project from the current prototype to a beta project ready for a larger scale investment. Part of the grant would go to my salary to enable me to develop the feature set of the product. And another part would go to consultation with others who have managed large scale development teams to help form a detailed, sustainable plan to present for a larger funding round.
The second problem is intrinsically linked to the first, part of building a successful team includes creating marketing and outreach to spread the word. Some of the funding I am requesting will go to consultation with others who have built teams in the past.