# Composable Architecture

### The problem with upgrading

Adding new features to a live blockchain typically requires a consensus-breaking change that involves a coordinated governance action.&#x20;

**This upgrade process introduces major friction to the blockchain development lifecycle and can greatly limit the speed of protocol reform and enhancements.**

{% hint style="warning" %}
How would you upgrade on other stacks? Re-build? Multi-layer governance? Social coordination?
{% endhint %}

### Frictionless additions&#x20;

👉 _Rather than growing on a single chain..._

* Canopy chains can transform into an application-specific ecosystem without any governance action.&#x20;
* This is a simple process of activating security features and cloning the Canopy blockchain for their new use cases.&#x20;
* This process distributes workloads and lessens the reliance on single validator groups.

### Sharding as a feature

* Canopy chains can quickly scale by adding interoperable sibling chains&#x20;
* Horizontal clones enable a distribution of workload, lessening the reliance on single validator groups

<figure><img src="https://2343293880-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLrZDX2RTu3ClIHkvyP7T%2Fuploads%2FJ0QUXD9T82oBtIgGrekB%2FCore%20features%20-Composable%20Architecture-%201.png?alt=media&#x26;token=c703f335-da34-4917-a9bf-9eedd745f858" alt=""><figcaption></figcaption></figure>

\
