[Ethereum] Spark Liquidity Layer - Add USAT and USDT transferAsset Rate Limits to Anchorage - March 16, 2026

Spark's Operational Facilitator has placed a proposal into the voting system on behalf of nested contributor Phoenix Labs.

Review

The Spark community can hereby express support or opposition to the following changes, as described by the author of the proposals:

[Ethereum] Spark Liquidity Layer - Add USAT transferAsset Rate Limit to Anchorage

Anchorage is the issuer of Tether’s onshore, GENIUS compliant stablecoin USAT. It is expected that swaps and liquidity facilities between USDT and USAT will be available on the Anchorage platform in the near future. Enabling transferAsset rate limits for both USDT and USAT from SLL into Anchorage will allow Spark to rebalance liquidity efficiently between the two stablecoins and source initial USAT liquidity needed to bootstrap the proposed USAT/USDS Uniswap v4 pool noted below. We are proposing a relatively high daily throughput (slope) based on anticipated liquidity needs to manage USDT vs USAT inventory that could potentially stretch into mid to high nine figure levels.

Change summary:

• transferAsset (USAT)
  • Address: 0x49506C3Aa028693458d6eE816b2EC28522946872
  • maxAmount: 5 million
  • slope: 250 million

[Ethereum] Spark Liquidity Layer - Add USDT transferAsset Rate Limit to Anchorage

Similar to above, we propose adding a USDT transferAsset rate limit to enable rebalancing liquidity between USDT and USAT, and sourcing initial USAT liquidity needed to support the planned Uniswap v4 deployment.

Change summary:

• transferAsset (USDT)
  • Address: 0x49506C3Aa028693458d6eE816b2EC28522946872
  • maxAmount: 5 million
  • slope: 250 million

The proposed Spark Artifact changes can be found in the following pull request: https://github.com/sky-ecosystem/next-gen-atlas/pull/204

Outcomes

• If "For" receives the most votes, the proposal will be approved. The associated pull request will be merged into Spark's artifact. When required, the listed changes will proceed to implementation by the relevant actors.
• If "Against" receives the most votes, the proposal will be rejected. No changes will be implemented.