Skip to content

Timestamp units #98

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
badgersrus merged 1 commit into from
Dec 11, 2025
Merged

Timestamp units #98

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/3-smart-contract-features/4-transaction-timestamp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ sidebar_position: 4
# Precise transaction timestamp

Real-time games require users to make quick decisions, and the outcomes depend on the precise moment in time when the action was made.
This doesn't work well on-chain because latencies are not low enough.
This doesn't work well on-chain because latencies are not low enough. **The timestamp is provided in milliseconds**.

### Option 1 - External Timestamp oracle

Expand Down Expand Up @@ -42,7 +42,7 @@ interface ITimestamp {

```solidity

// TEN provides a system contract that returns the precise timestamp of the calling transaction
// TEN provides a system contract that returns the precise timestamp in milliseconds of the calling transaction
interface ITimestamp {
function getTransactionTimestamp() external returns (uint256);
}
Expand Down