Understand the project
Practical overview
When it fits
Use Cadence when the target application runs on Flow and its contracts benefit from resource semantics, compile-time type checking and capability-based access control. The browser Playground suits an initial language experiment, while Flow CLI, its emulator and the VS Code extension support a local development workflow.
Who it is for
- Developers building smart contracts on Flow
- Teams creating resource-oriented blockchain applications
- Developers implementing capability-based access control in contracts
- Tool builders creating parsers or analysis tools for Cadence code
Documented uses
- Develop and read Cadence smart contracts for Flow
- Model digital assets as non-copyable, movable resources
- Define scoped access using capabilities and entitlements
- Test and emulate Flow-oriented development workflows locally
- Build tools that parse or analyze Cadence source code
Before you choose
Requirements & limits
The repository is public and licensed under Apache-2.0. The project identifies a browser-based Cadence Playground and local development tools for Linux, macOS and Windows.
- Flow is the target network identified by the project, so network fit is a primary consideration.
- Resource-oriented programming and move semantics shape how assets are represented and transferred.
- Capability-based security and entitlements determine how access is expressed.
- Flow CLI is the documented primary build tool and includes an emulator for local network behavior.
- The VS Code extension is the documented editor tool for Cadence development, deployment and interaction.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Evidence and transparency
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 2 October 2026
- Original website title
- onflow/cadence · Official homepage title · retained in its source language