Skip to main content

Try it Live

Run Hardfork examples in the interactive playground

    Chronological Ordering

    Hardforks are ordered chronologically by deployment date:
    Comparison uses array index lookup, making it O(1) constant time.

    Usage Patterns

    Feature Gating

    Check minimum version requirements:

    Network Configuration

    Validate network compatibility:

    Transaction Type Selection

    Select appropriate transaction format:

    EIP References

    Common minimum version checks:

    Performance

    Time Complexity: O(1) - Array index comparison Typical Time: ~10-20ns per call

    See Also

    • isBefore - Check if strictly less than
    • isAfter - Check if strictly greater than
    • compare - Three-way comparison
    • gte - Alias for isAtLeast