Synapse STIP Addendum

DAO Grant Programs STIP Bridge Addendum
1

Banner copy
Banner copy1920Ă—1080 83.3 KB

Synapse Protocol STIP ADDENDUM

Synapse Protocol was granted 2M DAO in the STIP Backfund proposal to increase bridge volume in the Arbitrum Ecosystem and launch Intent-based, slippage free bridging.

We delivered on both, bridging ~$3.8b (10x) during the program, and bootstrapping SynapseRFQ which provides slippage free bridging on up to $5m in under 15 seconds.

  1. Can you provide a link to your previous STIP proposal (round 1 or backfund)?
  1. How much, in the previous STIP proposal, did you request in ARB?

Amount requested: 2,000,000 ARB

  1. In which date did you start the incentive program for your users and in which date did it end?

STIP Back Fund distributions for Synapse started 26th of January 2024, and ended 29th of March 2023

  1. Could you provide the links to the bi-weekly STIP performance reports and Openblocks Dashboard?

Bi-Weekly Reports

Openblocks Dashboard

  1. Could you provide the KPI(s) that you deem relevant for your protocol, both in absolute terms and relative change, for the first of each month starting from October 2023 until April 2024, including the extremes? If you don’t know what KPI might be relevant for you or how to properly define them, please refer to the following document:

Attached is a Dune Dashboard that looks at bridging during the STIP program

Outside of KPIs

Bridge Volume

DATE 01/10/23 01/11/23 01/12/23 01/01/24 01/02/24 01/03/24
Volume ($M) 95.6M 113.4M 233.1M 210.5M 914.9M 2.88B
TVL % +18.5% +31% +56% -9% +334% +215%

MAU

DATE 01/10/23 01/11/23 01/12/23 01/01/24 01/02/24 01/03/24
MAU (K) 31k 42k 76k 50k 95k 112k
MAU % -25.6% +34% +80% -33% +89% +17%

[From the dune dashboard above]
STIP also helped to launch and scale RFQ, which brought bridge fees near zero and transactions that complete in < 30 seconds.

1322Ă—694 29.8 KB

The program also helped to incentivize > $3B in total volume.

1600Ă—359 56.3 KB

  1. [Optional] Any lessons learned from the previous STIP round?

A general lesson we learned was that incentives need to be updated quite frequently, and that incentive design can be carefully crafted to create organic volume and find more sticky users. Specifically, incentivizing certain routes and adjusting the size of those incentives helped to grow RFQ, and find users that converted from other bridging alternatives.

New Plans for STIP Bridge

  1. How much are you requesting for this STIP Bridge proposal?

    950,000 ARB (47.5%) of the original grant amount.

This is what Synapse thinks is necessary to achieve similar results and scale the intent base RFQ system.

  1. Do you plan to use the incentives in the same way* as highlighted in Section 3 of the STIP proposal?

Yes, incentives will be allocated as following:
62.5% to Bridge fee and gas rebates
37.5% to Relayer incentives

37.5% is being allocated to relayers to specifically encourage onboarding of new relayers that will make quotes even more competitive, and broaden the set of assets and chains supported. In the last round, incentives were distributed proportionately to the ($) amount each relayer bridged. This incentive structure rewards relayers with the best pricing, and best routes, and will be used again.

Also important to note that incentives are not used for any liquidity mining.

  1. [Only if answered “no” to the previous question] How will the incentive distribution change in term of mechanisms and products?

    N/A

  2. Could you provide the addresses involved in the STIP Bridge initiative (multisig to receive funds, contracts for distribution, and any other relevant contract involved), and highlight if they changed compared to the previous STIP proposal?
    The address will be:

Both Contracts remain the same

  1. Could you share any feedback or suggestion on what could be improved in future incentive programs, what were the pain points and what was your general evaluation of the experience?

    While the overall program experience was positive, I think a better way to streamline community feedback around incentives would help to create a positive flywheel around effective incentive spend. There was not as much forum activity around weekly updates as there could have been. In general I thought most of the process would’ve worked out quite well. I would have liked for OpenBlocks to be better incentivized so they could carry a heavier load on reporting and centralizing that info.

1 Like
2

Hello @moses ,

Thank you for your application! Your advisor will be SeedLatam Gov @SEEDGov

Please join the LTIPP discord and ping your advisor in the general chat so they can create a new channel and start communicating with you.

2 Likes
3

Hi @moses we are waiting for you in the discord!

1 Like
4

Wanted to add some clarity on some of the items our advisor pointed out.

Data Reporting:

In the initial STIP Backfund program, Synapse Labs created a bespoke data stream on Dune to track solely the incentivized routes and RFQ. While we relied on this as the source of truth internally, other data tools did not support this level of granularity at the time. Thus OpenBlocks and the Synapse Explorer only offered a small peak into the efficacy of the program. An example of this is the API exposed only returns volume “from” Arbitrum, when a majority of the incentivized routes were “to” Arbitrum. To solve this Labs is working with OBL to upgrade the data streams so they have sufficient tooling to do their job, and also go a step deeper.

Another goal for the program would be to get more granular with data reporting and track where dollars are going/what users are doing once they enter the ecosystem. Research for Synapse on Optimism shows that Synapse drove 25% of all high-value users to the chain. Tracking this activity on chain helps to make the impact from grants like this more obvious, and more data on user behavior, organic activity, and alignment with general Arbitrum ecosystem goals for growth help everyone to make more informed decisions.

Incentive Structure:

In the addendum we specifically outlined what relayer incentives look like. The initial relayer incentives were a success: in the last month, 90% of intra L2 volume has gone through SynapseRFQ. Relayers offer quotes that are more competitive than fee-less CCTP, and most aggregators, and have finality times < 20 seconds. The new incentives should drive more competition and diversity amongst relayers, as well as offer new routes and assets.

The majority of rebates are allocated towards fee and gas rebates. In LTIPP there were several concerns with direct fee rebates. In this scenario, fee-rebates look more like liquidity incentives for just-in-time liquidity. A large portion of fees go directly to relayers in return for assets on the desired chain. This is infinitely cheaper than incentivizing the existing Uni v2/v3 pools on synapse that over pay for liquidity and offer worse pricing. This subsidy for liquidity provision also encourages the proliferation of relayers, and competition that drives down price and speeds. Relayers already offer slippage-free, near instant bridging, and this direct subsidy for liquidity provision encourages more relayers to onboard.

** Synapse DAO employed several measures to prevent sybiling, these methods were not publicized to prevent abuse of these rules.

Summary of KPIs:

Expand SynapseRFQ specifically by encouraging relayer onboarding and increasing competition. This includes the nominal amount of relayers in the ecosystem, the routes, chains, and assets supported, and the resulting decrease in quote prices and bridge speeds.

Encourage new $$ into the Arbitrum ecosystem. With SynapseRFQ, bridging to Arbitrum will be slippage free from any chain. This should also be directed in a way that encourages participation in the larger arbitrum defi ecosystem (ie users should bridge to use partner protocols like GMX to truly onboard onto the chain).

One note is that Synapse did not and will not incentivize traditional liquidity pools using the grant. The goal of the initial stip program was to provide slippage free bridging, and this is most efficiently done through SynapseRFQ