Behind the Scenes: Tangem’s Day-One Arc Integration

This article is available in the following languages:

Author logo
Denis Polozov
•
Post image

This content is for general information and education only and does not constitute investment advice, a financial promotion, or a recommendation to buy, sell, hold, or otherwise deal in any cryptoasset or to use any specific third‑party service. Cryptoassets are high‑risk, can be very volatile, and you could lose all the money you invest. You will not have access to UK compensation or ombudsman schemes in relation to cryptoassets. If you are unsure whether any activity is suitable for you, you should seek independent financial advice. Take 2 mins to learn more.

 

When the Arc mainnet launched on September 16, Tangem users could access the network through our hardware wallet from day one. Normally, we schedule support for a blockchain when the work is ready, but Arc came with a date we couldn’t move, on a network we couldn’t fully test before it went live.

 

Our usual process gives each team the time it needs. Analysis clarifies requirements, Development implements them, QA tests the behavior, Product Ownership balances priorities, and the Release team coordinates delivery. If something needs another pass, the timeline can be adjusted. But this time, the work had to fit the date instead.

 

We're especially grateful to the Arc team for working closely with us throughout this process. Their active involvement and support made the integration much smoother than it would have been otherwise. This was especially important because a network approaching mainnet cannot be tested in quite the same way as one already running in production.

 

The challenges

Testing was one of the hardest parts of the integration. We could check basic transaction flows and expected behavior in the available environments, but we couldn't verify everything under live mainnet conditions.

 

Explorer access was limited, too, which made some checks less straightforward. Analysis and Development had to distinguish what was confirmed from what remained an assumption. QA focused on the scenarios that could be tested reliably and made the remaining uncertainty visible rather than treating it as resolved.

 

The deadline also introduced a separate problem: keeping a structured release process intact when the schedule was set externally. Moving quickly didn’t mean skipping steps. It meant being more precise about which steps were essential before launch, where work could proceed in parallel, and which open questions had to stay visible across teams.

 

Development, Analysis, and QA needed a shared understanding of the limits of pre-launch validation. The Release team needed an accurate picture of readiness, while Product Ownership kept the scope aligned with what users would need on September 16.

 

There were also competing priorities. Supporting Arc on day one required time from people working on other commitments. The teams had to identify which tasks directly affected a safe, usable launch and which could wait for a later release. Some tasks were deferred. The goal was to deliver the essentials without stretching the teams too thin.

 

The outcome

By September 16, Arc support was available in the wallet. For users, the benefit was simple: they could start using the new network immediately, with the wallet and security model they already knew.

 

For us, this experience reinforced the importance of a deliberate, readiness-driven process, while also showing how it could be adapted to a fixed deadline. The lessons learned will help us prepare for future network launches with similar constraints.

Author logo
Author Denis Polozov

Blockchain analyst.

Author logo
Reviewed by Egor Breus

Copy Editor at Tangem.