FAQ

What does it take to build a dApp with QSign?

The dApp team needs to integrate the QSign interface into their contracts to make appropriate calls, that will allow cross-chain messaging right away.

Can a single contract control several wallets within single or multiple networks?

Yes, a single contract can have as many wallets on supported chains as needed.

Can a user contract send multiple messages in a single go?

Generally it's possible, but currently that functionality is not supported.

How much time does it take for the message to be delivered from chain A to chain B?

This strongly depends on the chains involved. The main factor here is that before broadcasting the message to chain B, the Cross Chain Oracle (CCO) needs to make sure of its finality, so it needs to wait for a certain predetermined number of confirmations. Furthermore, higher transaction volume also can affect the processing time.

What is the current state of QSign development and integrations?

There is an MVP currently that successfully works for two EVM chains. The QSign team can easily integrate the network with the managed wallet, we also support CAIPs. It's also possible to integrate non-EVM chains on the controller side, and we will be happy to discuss that with potential clients.

How much does it cost to use QSign? Who pays transaction fees?

Sending a message from chain A to chain B involves the following fees:

1. The network fee for initiating the process on chain A
   The user pays it by default.

2. The network fee for the transaction on chain B
   This fee is paid from the managed public address on chain B.

3. The network fee for delivering the update on chain A
   The user pays it when the transaction is initiated.

4. QSign service fee
   Currently, there is a flat fee in gas tokens that the user pays together with the request to fund the subsequent transactions and cover the service fee.

How is the QSign service monetized?

There is a small QSign service fee involved. It is supplied as a part of the flat fee the user pays when calling the QSign contract.

Do you plan to open access to MPC directly via API?

Currently not. From the usage perspective, QSign targets the applications related to cross-chain communication between smart contracts. If you want to automatize the signing process and utilize role-based governance without smart contracts involved, check out our partner API.

Which chains are supported in the Technology Preview

QSign currently works on two EVM testnets: Sepolia and Mumbai.