💠Federated & Decentralised by Design

Overview (What to aim for)

Avoid centralisation. Allow for federated databases/systems where possible that are each reusable & accessible by the individual (multiple functional identities, modes of payments, sources of data etc.). This prevents creation of honey pots (cybersecurity risk) and over-aggregation of information into unwieldy large central databases (a privacy risk).

In today’s world, it is perfectly possible to connect various systems via common protocols and standards and still achieve unification without centralisation.

A lot of people think that having a central system with high security is actually better than having multiple decentralised systems that are interconnected. However, this has proven to be false. Simply put, any central system or storage becomes a honeypot that is the repeated target of multiple cyber attacks. Decentralised systems function as lower value targets and strengthened by the best principles and practices of DPI, they become highly secure with very low chances of large scale data leaks or privacy concerns.

Technical Tools (How to achieve it)

• ”Wrapper” APIs above disparate existing systems rather than new large centralised databases.

Societal Outcomes (Why it matters)

• Autonomy of Institutions

• Cybersecurity

• Individual Privacy

• Resilience - avoid overdependence on any one system