Practical overview
When it fits
Use it when a Flow integration depends on protocol-level contracts or when researching how Flow handles functions such as staking, fees, scheduled transactions or random-beacon history.
Who it is for
- Flow node operators reviewing protocol contracts
- Builders integrating staking or delegation services
- Protocol researchers examining Flow contract behavior
- Cadence developers building integrations with Flow protocol contracts
Documented uses
- Review the contract logic behind FLOW token, staking, delegation and epochs.
- Find transaction examples for interacting with service-account, scheduler and other protocol contracts.
- Use the repository’s protocol contracts and templates as references when building Flow integrations.
Requirements & limits
The repository is public and identifies the Unlicense as its license.
- The contracts are written in Cadence, which the README describes as a resource-oriented language for Flow smart contracts.
- The README recommends completing Cadence tutorials before reading the repository.
- The repository lists contract addresses for Emulator, Testnet and Mainnet; confirm the relevant network and release when integrating.
- This is source code and developer reference material, not a hosted user-facing staking or wallet service.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Find FlowToken contract addresses and transaction templates
Identify the documented FlowToken contract address for a network and locate its related transaction templates.
Before you start
- Access to the flow-core-contracts repository README.
Steps
Open the repository README.
Find the FlowToken section and select the address listed for Emulator, Testnet, or Mainnet.
Use the README’s link to the
transactions/flowTokendirectory to review FlowToken transaction templates.
Expected outcome
You can identify the README-listed FlowToken address for a selected network and locate the related transaction templates.
Guide limitations
- The README identifies addresses and template locations but does not provide steps for executing transactions.
- No address is provided here for networks other than Emulator, Testnet, and Mainnet.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 9 October 2026
- Original website title
- onflow/flow-core-contracts · Official homepage title · retained in its source language

