Transaction memos and batch transactions activate on Arc Testnet
# node operators
# network upgrades
# hardfork
# Testnet
# Arc
# Indexers
# Infrastructure
The v0.7.2 hardfork activates on Arc Testnet June 18 at 14:00 UTC, bringing transaction memos and batch transactions to developers.
Tim Baker
Arc Testnet is upgrading to v0.7.2.
The hardfork activates on June 18, 2026 at 12:00 UTC. Testnet node operators must upgrade before activation or their nodes will desync from the network.
This is a testnet update. No mainnet timing or mainnet availability is implied.
Who needs to act
This post is primarily for Arc Testnet node operators.
If you operate a testnet node, upgrade to v0.7.2 before June 18 at 12:00 UTC. Earlier node versions are not supported after the hardfork activates.
The release also activates transaction memos and batch transactions on Arc Testnet, but the immediate operational requirement is the node upgrade.
What changes for node operators
The v0.7.2 breaking changes are mostly operational. Review the release notes and breaking changes before upgrading, especially if your node setup depends on custom RPC behavior, legacy transaction formats, large JSON-RPC batches, or mempool handling assumptions.
Key areas to check:
JSON-RPC gas cap default
Replay-unprotected transaction handling
JSON-RPC batch request limits
Invalid transaction list behavior
Operators with standard setups may not need to change much beyond the version upgrade, but any custom config should be reviewed against the breaking changes before activation.
Why this matters
Hardfork activations require coordination.
After the activation time, nodes running earlier versions will no longer follow the supported Arc Testnet path. For builders and partners depending on testnet infrastructure, that means node operators should upgrade early, validate configs, and make sure monitoring is clean before the activation window.
If you are running infra for an app, indexer, exchange workflow, validator environment, internal test setup, or partner integration, treat this as an operational deadline.
Start here
Upgrade to v0.7.2 before June 18, 2026 at 12:00 UTC.
