❓FAQ

1.Is ZAP Open Source?

Our smart contracts are open source, but our API is not. This is our competitive advantage, and we're handling it and aligning our strategy with the big DEX aggregators like 1inch and Paraswap, who also keep their API closed source.

2. How do we decide which bridge to implement next?

We move forward in a three-step way:

1. Assess existing bridges on their capabilities (which chains are supported) and security.

2. Check if all existing chains in our system are least supported by the two bridges we've implemented. That way, we make sure that there is a fallback solution should liquidity be empty or if we have to turn a bridge off due to a hack or something else.

3. Either implement a bridge that backs up another or a bridge that expands our capabilities to bridge toward new chains.

3. How do we decide which bridge to use?

Each bridge is graded manually and automatically based on qualitative and quantitative factors. Qualitative factors are, for example, trust assumptions and attack vectors. Quantitative factors like speed, fees, gas costs, and reliability can be measured. Our algorithm adjusts its decision-making based on these factors and generally acts after our default prioritization pattern, which says security > speed > costs. We believe that this pattern provides the most responsible and sustainable user experience. Anyone implementing our bridge aggregation protocol or SDK can adjust the prioritization pattern.

4. Can our backend algorithm / API be influenced?

Yes, we support whitelisting and blacklisting certain bridges. We also allow for prioritizing one bridge over the other, and we allow for a change of the default prioritization pattern. That way, we allow you to act biased. For example, you might like a certain bridge protocol or DEX aggregator because you don't trust certain others.

5. Do bridges cooperate with you?

Yes, over 50% of all bridge developers have invested in us. We're very close to them as we bring them more volume.