Skip to content
ENTITY PROFILE / KNOWLEDGE GRAPH

Hoodi’s Glamsterdam test

RSS

Ethereum scheduled Hoodi’s Glamsterdam activation for October 26 at 17:42:48 UTC. All Hoodi operators must update their execution client to Besu 26.10.0 before activation. All Hoodi operators must update their execution client to Ethrex 30.0.0-rc.2 before activation. All Hoodi operators must update their execution client to Nethermind 2.2.0 before activation. All Hoodi operators must update their consensus client to Lodestar 1.50.0 before activation. All Hoodi operators must update their consensus client to Nimbus 26.10.1 before activation. All Hoodi operators must update their consensus client to Prysm v7.3.0 before activation. All Hoodi operators must update their consensus client to Teku 26.10.1 before activation. GLM-5 (Baseten) matches Claude Sonnet 4.6 on core agent tasks. MiniMax M2.7 (OpenRouter) matches Claude Sonnet 4.6 on core agent tasks. GLM-5 (Baseten) has a latency of 0.65 seconds, compared to 2.56 seconds for Claude Sonnet 4.6. Claude Sonnet 4.6 has a latency of 2.56 seconds, compared to 0.65 seconds for MiniMax M2.7 (OpenRouter). GLM-5 (Baseten) has a throughput of 70 tokens per second, compared to 34 tokens per second for Claude Sonnet 4.6. Claude Sonnet 4.6 has a throughput of 34 tokens per second, compared to 70 tokens per second for MiniMax M2.7 (OpenRouter). GLM-5 (Baseten) charges $0.95 per million tokens for input, compared to $3.00 for Claude Sonnet 4.6. MiniMax M2.7 (OpenRouter) charges $0.30 per million tokens for input, compared to $3.00 for Claude Sonnet 4.6. GLM-5 (Baseten) charges $3.15 per million tokens for output, compared to $15.00 for Claude Sonnet 4.6. MiniMax M2.7 (OpenRouter) charges $1.20 per million tokens for output, compared to $15.00 for Claude Sonnet 4.6. Glamsterdam upgrade was scheduled to run on the Hoodi testnet Ethereum suspended the planned 200 million gas limit increase on the Hoodi testnet· Entity summary generated by Graphiti

RELATIONS
20Relations
CURRENT
18Current
EVENTS
2Events
REPORTS
3Source reports
KNOWLEDGE ATLAS0 entities · 0 relations
No public neighbors yet
Explore all published links of a node; previously discovered relations remain visible.

Relation timeline

BY VALID-FROM DATE
  1. EthereumSCHEDULED ACTIVATION FORHoodi’s Glamsterdam test

    Ethereum scheduled Hoodi’s Glamsterdam activation for October 26 at 17:42:48 UTC.

    Current1 sourceEthereum
  2. EthereumSUSPENDED PLANNED GAS LIMITHoodi’s Glamsterdam test

    Ethereum suspended the planned 200 million gas limit increase on the Hoodi testnet

    Current1 sourceEthereum
  3. Glamsterdam upgradeSCHEDULED ONHoodi’s Glamsterdam test

    Glamsterdam upgrade was scheduled to run on the Hoodi testnet

    Ended 2026-10-231 sourceGlamsterdam upgrade
  4. Hoodi’s Glamsterdam testREQUIRES CONSENSUS CLIENTPrysm v7.3.0

    All Hoodi operators must update their consensus client to Prysm v7.3.0 before activation.

    Ended 2026-10-221 sourcePrysm v7.3.0
  5. Hoodi’s Glamsterdam testREQUIRES CONSENSUS CLIENTNimbus 26.10.1

    All Hoodi operators must update their consensus client to Nimbus 26.10.1 before activation.

    Current1 sourceNimbus 26.10.1
  6. Hoodi’s Glamsterdam testREQUIRES CLIENTBesu 26.10.0

    All Hoodi operators must update their execution client to Besu 26.10.0 before activation.

    Current1 sourceBesu 26.10.0
  7. Hoodi’s Glamsterdam testREQUIRES CONSENSUS CLIENTTeku 26.10.1

    All Hoodi operators must update their consensus client to Teku 26.10.1 before activation.

    Current1 sourceTeku 26.10.1
  8. Hoodi’s Glamsterdam testREQUIRES CLIENTNethermind 2.2.0

    All Hoodi operators must update their execution client to Nethermind 2.2.0 before activation.

    Current1 sourceNethermind 2.2.0
  9. Hoodi’s Glamsterdam testREQUIRES CLIENTEthrex 30.0.0-rc.2

    All Hoodi operators must update their execution client to Ethrex 30.0.0-rc.2 before activation.

    Current1 sourceEthrex 30.0.0-rc.2
  10. Hoodi’s Glamsterdam testREQUIRES CONSENSUS CLIENTLodestar 1.50.0

    All Hoodi operators must update their consensus client to Lodestar 1.50.0 before activation.

    Current1 sourceLodestar 1.50.0
  11. Hoodi’s Glamsterdam testHAS LATENCYMiniMax M2.7 (OpenRouter)

    Claude Sonnet 4.6 has a latency of 2.56 seconds, compared to 0.65 seconds for MiniMax M2.7 (OpenRouter).

  12. GLM-5 (Baseten)HAS INPUT PRICEHoodi’s Glamsterdam test

    GLM-5 (Baseten) charges $0.95 per million tokens for input, compared to $3.00 for Claude Sonnet 4.6.

    Current1 sourceGLM-5 (Baseten)
  13. GLM-5 (Baseten)HAS LATENCYHoodi’s Glamsterdam test

    GLM-5 (Baseten) has a latency of 0.65 seconds, compared to 2.56 seconds for Claude Sonnet 4.6.

    Current1 sourceGLM-5 (Baseten)
  14. MiniMax M2.7 (OpenRouter)MATCHESHoodi’s Glamsterdam test

    MiniMax M2.7 (OpenRouter) matches Claude Sonnet 4.6 on core agent tasks.

  15. MiniMax M2.7 (OpenRouter)HAS INPUT PRICEHoodi’s Glamsterdam test

    MiniMax M2.7 (OpenRouter) charges $0.30 per million tokens for input, compared to $3.00 for Claude Sonnet 4.6.

  16. GLM-5 (Baseten)MATCHESHoodi’s Glamsterdam test

    GLM-5 (Baseten) matches Claude Sonnet 4.6 on core agent tasks.

    Current1 sourceGLM-5 (Baseten)
  17. GLM-5 (Baseten)HAS OUTPUT PRICEHoodi’s Glamsterdam test

    GLM-5 (Baseten) charges $3.15 per million tokens for output, compared to $15.00 for Claude Sonnet 4.6.

    Current1 sourceGLM-5 (Baseten)
  18. Hoodi’s Glamsterdam testHAS THROUGHPUTMiniMax M2.7 (OpenRouter)

    Claude Sonnet 4.6 has a throughput of 34 tokens per second, compared to 70 tokens per second for MiniMax M2.7 (OpenRouter).

  19. MiniMax M2.7 (OpenRouter)HAS OUTPUT PRICEHoodi’s Glamsterdam test

    MiniMax M2.7 (OpenRouter) charges $1.20 per million tokens for output, compared to $15.00 for Claude Sonnet 4.6.

  20. GLM-5 (Baseten)HAS THROUGHPUTHoodi’s Glamsterdam test

    GLM-5 (Baseten) has a throughput of 70 tokens per second, compared to 34 tokens per second for Claude Sonnet 4.6.

    Current1 sourceGLM-5 (Baseten)

Relations are facts Graphiti extracted from reports, not verbatim quotes. An end date means later reporting showed the relation no longer holds.