web3 Architecture

design decisions

Local first

Decentralized apps should provide means to work offline as much as possible. CRDT mechanics to ensure your local node is synched with the data you need to work offline

references:

• https://www.inkandswitch.com/local-first/

Linux first

The tech-stack should run on all linux distros first, then bridge to macOS, then bridge to other operating systems as required

Desktop first

All web3/DLT tools will be designed first for desktop hardware with maximum potential and features.. Later versions for smaller screens and limited hardware will be created

Portal / micro-frontend architecture

multiple ways to visualise / experience the same networks dataset or by combining network datasets

Modular Composibility

decentralized apps are composed of modular blocks, which in turn are composed of functional building blocks both UI and domain dataset.

Mutual sovereignty

The option to leave the network or create a new one with the existing public data

Agent centricity

The ability for each agent to decide what and with whom to share their data. Also the choice to revoke access to personal data and request the expiry of data already shared via DID claims.