Takeaways

#
  • Saraniecki described composability as allowing separate applications to complete a transaction together or fail together.
  • Canton’s design had to preserve control over financial information even when assets moved across applications.
  • He argued that application builders and other participants bringing activity to a network should share in its rewards.
  • Sykes separated the question of network usefulness from how that usefulness could reach a token holder.

Moving an asset onto a blockchain does not, by itself, resolve the work involved in a financial transaction. Different institutions still need to coordinate, decide who can see the information and establish whether every part of the transaction will complete.

That was the problem Eric Saraniecki described in his interview with Louis Sykes on the February 5, 2026 edition of Crypto After Dark. The Digital Asset co-founder presented Canton's design as an attempt to connect financial applications while preserving the controls their users require. Sykes had recorded the interview the previous day, then aired it during a sharp crypto selloff.

What composability was supposed to solve

Saraniecki began with composability: the ability for independently operated applications and assets to participate in one coordinated transaction. In his explanation, all the required steps would settle together or the transaction would fail together.

That matters when neither participant wants to move first. Separate transfers can leave one institution waiting for another, with reconciliation and handoffs between them. Saraniecki used cross-border banking to illustrate how the coordination problem grows as more intermediaries become involved.

He saw the opportunity extending beyond stablecoin payments. Cash balances, money-market funds and Treasury holdings could become components in a connected system, allowing users to move between cash and yield-bearing assets. Repo transactions conducted intraday or outside conventional market hours were another example he raised.

Privacy had to survive the transaction

An institution's willingness to participate depended on more than faster settlement. Saraniecki emphasized control over assets and control over information. A financial institution might accept a shared network without accepting that competitors could inspect its balances, customer activity or cash movements.

The privacy requirement also extended across applications. His example was a medical payment: the doctor should not learn the patient's total wealth, and the bank should not learn the reason for the appointment. Protecting a balance while exposing the context of its use would leave part of the problem unresolved.

Sykes made the same point with an everyday purchase. Paying for a loaf of bread should not require disclosing the contents of a bank account. Both examples helped explain why the interview treated privacy as a condition of useful financial infrastructure, rather than an optional feature added after the transaction system was built.

Saraniecki described a difficult balance. Applications needed their own information and asset controls, but those controls could not eliminate the ability to transact together. Otherwise, he argued, the new system would recreate the separate processes it was meant to improve.

Who should receive the network rewards?

The interview then moved from the technology to its economics. Saraniecki questioned token systems that direct their rewards primarily to the operators of infrastructure.

He considered that structure understandable for Bitcoin's relatively focused purpose and emphasis on decentralization. For a smart-contract ecosystem, however, he argued that applications, assets, wallets and user acquisition also create value. Rewarding only the people running the infrastructure would leave those contributions undercompensated.

His comparison was a credit-card network. The rails receive compensation, but other participants who bring merchants, users and activity into the system share in its economics. He described Canton's rewards as favoring participants according to the activity they bring to the network.

He did not present the design as finished or perfect. He said the community was learning from its operation and adjusting it.

Sykes's investment question was separate

Outside the interview, Sykes used the selloff to examine the connection between a crypto network's use and the value of its token. He was interested in whether a functioning business generated activity and whether the token had a mechanism to participate in that activity's economics. Canton and Hyperliquid were his examples of projects he was following.

He also said he had started buying Bitcoin, while allowing for more downside, and rejected the suggestion that he was using leverage on the decline. His market view remained distinct from Saraniecki's account of financial infrastructure. A useful application, a well-designed incentive system and an attractive investment price each required their own assessment.

Questions and answers

#

Questions answered in the original 2026-02-05 episode.

What did composability mean in this interview?

Saraniecki used the term for a transaction spanning independently operated applications in which all required steps settle together or none do. He contrasted it with coordinating separate transfers and reconciling them afterward.

Link to this answer

Why was privacy central to the discussion?

Financial users may need shared settlement without exposing balances, customer relationships or the purpose of a transaction. The interview considered privacy across connected applications as well as within a single account.

Link to this answer

Did Saraniecki describe Canton’s incentive model as complete?

No. He explained its intended rewards for participants who bring activity to the ecosystem, but said the community was still learning and adjusting the system.

Link to this answer

Adapted by Stock Market TV Editorial from the original video. Source date: . Article published: .