88923673-6
Safe Queue Service Migration Deadline Set for Jan. 19, 2027
Safe gives developers until Jan. 19, 2027 to move four Transaction Service workflows to its multichain Queue Service, while existing keys and post-execution data access remain available.

Outputs
Jan. 19, 2027 is the migration deadline for four affected Transaction Service APIs.
Safe Queue Service uses one multichain API for pending transactions, signatures, off-chain messages and delegate management.
A single request can retrieve pending transactions for as many as 100 Safe address-and-chain pairs.
Each transaction proposal must include at least one valid signature.
Existing API keys remain usable, while executed history, balances and Safe details continue after the affected APIs close.
Safe has set Jan. 19, 2027 as the deadline for developers to migrate from four affected Transaction Service APIs, according to the company's Safe Queue Service announcement. The change covers transaction proposals, signature collection, off-chain messages and delegate management.
The announcement states: “Developers using the affected APIs must complete their migration by Jan. 19, 2027.” The date applies to integrations using the listed endpoints, rather than marking the end of every Transaction Service function.
What changes at the Jan. 19 deadline?
Safe will close the affected APIs after the migration deadline. Safe Queue Service, already operating in production, provides the replacement path through one multichain API.
In interface terms, four affected functions are being consolidated behind one multichain service. Its immediate operational focus is moving pending-workflow traffic away from the affected Transaction Service APIs while retaining the broader service.
Which operations move to the multichain API?
The migration covers four named workflows:
- Transaction proposals: proposals move to the unified Queue Service interface.
- Signature collection: signature-related processing moves from the affected Transaction Service API.
- Off-chain messages: off-chain message handling moves to the same production service.
- Delegate management: delegate-management requests move to the unified multichain interface.
Safe Queue Service already processes all four categories in production, and Safe{Wallet} already uses it. The cutoff therefore requires affected developers to change integrations rather than wait for a service scheduled for a future launch.
How large is a pending-transaction request?
A single request can retrieve pending transactions for as many as 100 Safe address-and-chain pairs. The stated ceiling concerns retrieval scope; Safe does not present the figure as a transaction-throughput or confirmation-speed metric.
That scale gives integrators one request path across multiple address-and-chain pairs. Each transaction proposal must still include at least one valid signature, so developers need to preserve that requirement as the unified interface takes over signature collection.
What remains available after closure?
After the affected APIs close, Transaction Service will continue to provide executed transaction history, balances and Safe details. Safe is therefore narrowing the closure to four queue-related functions while retaining completed-transaction and account-data services.
Developers can also keep their current credentials. The company stated: “Existing API keys remain usable.” Endpoint migration is therefore separate from key replacement under Safe's current plan.
What should developers verify before the cutoff?
Teams should audit integrations that call the affected APIs for proposals, signatures, off-chain messages or delegate management. They then need to route those calls through the Queue Service interface and test the signature condition: every transaction proposal requires at least one valid signature.
Existing-key testing should cover each affected integration rather than assume a credential migration alongside the endpoint change. Pending-transaction retrieval should also be checked against the service's stated capacity of as many as 100 address-and-chain pairs per request.
The retained Transaction Service functions require no relocation under the announcement. Teams can keep using that service for executed transaction history, balances and Safe details after the four affected endpoints close.
What is the next operational checkpoint?
The next hard checkpoint is Jan. 19, 2027. After that cutoff, the material market-structure change is an interface split: pending queue workflows move to Safe's unified multichain API, while executed transaction history, balances and Safe details remain available through Transaction Service.
via tokenpost.com (Source)
More from Tom Whitfield
Show full bio
News editor covering technology and product news in crypto and web3 industry at Mempool Brief.
1,440 articles