[AIP-55] CEXs Liquidity Task Force with cede.store

Ryan aka @MrBobbie, BizDev lead a Cede Labs, a french startup backed by GSR, Stake Capital, and DoraHack.

This proposal introduces cede.store, a Chrome extension serving as an on-ramp solution to bring liquidity from centralized exchanges (CEXs) to Aura Finance. It enables users to seamlessly transfer assets from CEXs into on-chain wallets and invest them in the Aura Finance dApp. The goals are to improve user onboarding, leverage CeFi assets, and increase Aura’s TVL as well as AURA token trading volume.


This proposal is essential for the protocol as it outlines the establishment of a Liquidity Task Force (LTF) focused on expanding Aura’s liquidity, increasing TVL, and onboarding new users. It emphasizes strategies to incentivize users to invest in Aura Finance by providing a superior user experience, particularly by reducing frictions associated with transferring CEX assets to a DeFi wallet.


Cede.store is a browser extension with a non-custodial MetaMask-style interface focused on enabling users to manage off-chain assets across major CEXs like Kucoin or Bitget.

The proposal suggests integrating a ‘Transfer From CEXs’ option into Aura Finance’s Bridge, allowing users to seamlessly transfer their off-chain assets to on-chain wallets (e.g., SubWallet, Rabby, Phantom) and invest in the Aura Finance dApp with a few clicks.

Anticipated benefits of integrating cede.store include:

  • Aura Users: Access a new method to transfer funds to on-chain wallets, facilitating the use of Aura services such as the Bridge or Lock.

  • Aura dApp: Integration removes onboarding frictions for both existing and new users, leveraging their CeFi assets while remaining within the dApp. Users can efficiently send AURA tokens from KuCoin or BitGet to their on-chain wallet, then lock them into the Aura Finance dApp, potentially increasing TVL.

Our documentation: Integrate Withdrawal Features – cede.store
Our demo: https://www.youtube.com/watch?v=CDP_k7oxzcg

Regarding the concerns you may have on the security/tech side:

cede.store allows users to connect their API key and Access key (OAuth) from CEXs to manage and track their off-chain assets. Our solution is a non-custodial Chrome extension with the same DeFi UX (we want to uphold DeFi values). Therefore, we don’t store the API keys; they are stored client-side, not server-side.

We employ the same battle-tested encryption model as Metamask and recently underwent an audit by Hacken, receiving a perfect 10/10 score. They made the announcement recently.

Additionally, we are working with Ledger’s Former CTO and Co-founder to integrate API keys in a hardware wallet, making it even more secure for users.

So, we don’t store any CEX credentials. The user maintains ownership of these.

This proposal will remain open before the next Snapshot.

I appreciate and encourage an open discussion on the subject should there be any concerns or questions.

This vote will be a single-choice vote. You may vote “For” or “Against” this proposal or choose to abstain from the vote. By voting “For” this proposal, you are expressing support for the integration of cede.store with the specifications outlined in this proposal.

Hello! Thanks for your proposal!

I believe the volume from Kucoin and Bitget is not that relevant to ask for an integration like this.

Thank you for your comment!

With the widget and its ‘Transfer from CEX’ feature, you can send any token. I mentioned AURA token because it’s listed on Kucoin and Bitget, but users can use the widget to send BAL tokens from CEXs to provide liquidity on the Aura Finance dApp.


Hello, thanks for the detailed proposal.

Personally, I’m not sure the benefit is quite there at the moment to justify this integration, for a few reasons:

  • Aura supports a long tail of assets and networks, many of which are not available on CEXes.
  • The implementation looks simple, but it’s also not cost-free to implement and maintain.
  • Since cede.store is a new project, the number of users that could benefit from this at the moment is probably quite small.
  • I’m also not quite sold on the approach and wonder if this would be more fit for purpose at the wallet level than the app level. Implementing this per-app without a standard seems like a tall order.

I’d be happy to revisit this in the future if there are more users to cater for.

1 Like