# Competitive Edge

## Scope

StarkPay as an all-in-one solution is piling up potential competitors. As a B2C service, StarkPay is both [a bridge and a privacy solution](../product/bridge-and-privacy-solution). As a B2B service, StarkPay is also [a payment provider](../product/all-in-one-solution). This is the first reason why StarkPay stands out from other Web3 solutions. From lambda users to businesses, StarkPay is the ultimate DeFi protocol.

## Bridge Demarcation

StarkPay stands out from other bridges by using STARKs technology and a Layer-2 engine, which ensures low transaction costs and optimal scalability, without any risk of congestion.

In addition, StarkPay's zero-knowlegde proof-of-validity technology guarantees data integrity and total user confidentiality, positioning it as a more secure and private solution than current bridges.

Finally, StarkPay clearly differentiates itself from bridge solution by offering a truly [self-sovereign (self-custodial) solution](../technology/self-custody).

## Why STARKs rather than SNARKs?

Both STARKs and SNARKs are cryptographic proof systems that can be used by bridges. Many of them have made the mistake of using SNARKs, but not StarkPay. Here's why:

* Larger Proofs: While STARK proofs are larger than SNARK proofs, the important metric to compare when considering a scaling solution is the amortized gas cost per transaction. STARKs operating rollup allows to validate batches of transactions in one proof, further reducing the amortized gas cost per transaction.
* Safer Cryptographic Assumptions: STARKs are provably secure and rely on well tested theoretic principles. STARKs are also post-quantum secure.
* No Trusted Setup: Many SNARK constructions require a trusted setup. Moreover, the size of the setup key grows linearly with the size of the computation being performed. STARKs require no trusted setup whatsoever – making their use easier and safer.

## Privacy Solution Demarcation

<figure><img src="https://741004475-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtaNYKgjGUgShacuHUc8g%2Fuploads%2FoG2kIW4KZVYnlESYrA9E%2Fprivacy-solution-demarcation.png?alt=media&#x26;token=691eb92b-c2a0-4fef-8141-e42fffa5ec36" alt=""><figcaption></figcaption></figure>

## Payment Providers Demarcation

<figure><img src="https://741004475-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtaNYKgjGUgShacuHUc8g%2Fuploads%2FKr2Xxe26b6rtaWaOmWj0%2Fpayment-provider-demarcation-1.png?alt=media&#x26;token=d11958e7-8048-4909-b3fb-73713fcf3003" alt=""><figcaption></figcaption></figure>

<figure><img src="https://741004475-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtaNYKgjGUgShacuHUc8g%2Fuploads%2F6trMVPYzC78JCkKLu5YQ%2Fpayment-provider-demarcation-2.png?alt=media&#x26;token=f41b9153-0121-45eb-bf35-e1f9dca8f606" alt=""><figcaption></figcaption></figure>

## Mass Adoption

Most Web3 protocols presenting themselves as crypto payment providers are in reality just a UI / UX for applications, offering them only a dashboard for tracking on-chain transactions and sometimes a management API or SDK.

StarkPay not only offers these features, but also stands out for its[ chain abstraction solution](../../technology/keystone#chain-abstraction). Whether for the end user, or for the applications themselves, chain abstraction is what will enable true mass adoption, enabling Web2 applications to adapt to Web3.
