ACADEMY

v2

MODULE 15

LESSON 3

Tick Timing & Integration Flow

When a user calls a Procedure, it is included in a transaction and scheduled for a future tick.

When that tick arrives, Computors execute the contract code and update on-chain state.

Integrations (wallets, dApps, or backends) must therefore wait for the scheduled tick to confirm state changes, instead of expecting instant results.

For read-only Functions, integrations may call them at any time to retrieve the latest state without waiting.

More info can be found here:

https://docs.qubic.org/api/rpc#6-transaction-anatomy

https://docs.qubic.org/api/...

Back

Back

Next Lesson →

Next Lesson →

Learn

Performance Test

Qubic in the Press

Developers

Incubation Program

Ecosystem

Community

Ambassador Program

Legal

Terms of Service

© 2025 Qubic.

Qubic is a decentralized, open-source network for experimental technology. Nothing on this site should be construed as investment, legal, or financial advice. Qubic does not offer securities, and participation in the network may involve risks. Users are responsible for complying with local regulations. Please consult legal and financial professionals before engaging with the platform.

© 2025 Qubic.

Qubic is a decentralized, open-source network for experimental technology. Nothing on this site should be construed as investment, legal, or financial advice. Qubic does not offer securities, and participation in the network may involve risks. Users are responsible for complying with local regulations. Please consult legal and financial professionals before engaging with the platform.