Kagami will follow a path to decentralisation in three stages. It should be noted that Kagami never has custody of digital assets and thus its path to decentralisation is not as pressing in comparison to other projects. It is however acknowledged that decentralisation is important for the long term success of Kagami.
  1. 1.
    Kagami dApp uses a centralised backend for rapid development. Policy layer can be adapt quickly to community feedback and add extra features at warp speed. Whilst mainly centralised this stage includes on-chain risk records.
  2. 2.
    Kagami dApp integrates with policies located on-chain. Hybrid data model with private data (contact details, certain policy limits etc) remain on centralised backend. Centralised oracles watch for events emitted from policy smart contracts and trigger features such as notifications, MPC holds etc.
  3. 3.
    Centralised backend removed. Decentralised oracle network deployed (eg: Chainlink). Each entity using Kagami has sovereignty over their own data. dApp supports data retrieval on demand from various storage systems (local, cloud, IPFS) and supplies required information to smart contracts, oracles as required. Its noted any data written on-chain becomes public. Confidentiality of data is paramount and solutions to this data privacy problem are not yet fully formed.