Future Direction: Full vProgs

What it is

Full vProgs are the future network-composition model for independent apps on Kaspa.

This page is architectural context for app builders, not a separate current option. The core idea is that independent apps would be able to read or call one another directly across the network instead of having composition happen inside one managed app environment.

How it differs from Based Apps

Based Apps give you one managed app environment today, with a built-in account model and app-local composition inside that environment.

Full vProgs describe a future where composition is a network property between independent apps, not just something that happens inside one managed app environment.

What synchronous composition means

Synchronous composition means one app can read another app’s current state or call another app in the same flow, without waiting for a later settlement round, bridge step, or deferred action.

Why it matters

The point is to make direct app-to-app composition possible across the network.

That changes the design space for builders who eventually want an ecosystem of interoperable apps instead of a single managed app environment.

Current expectations

This is not the path to optimize for today. If you are building an app now, use Based Apps and treat Full vProgs as the future direction for richer app-to-app composition. Covenants and Inline ZK remain valid choices for asset rules and per-action verification.