DeFi Working Group

Thanks for the input @dostro, @skilesare, @bob11.

Since there are many questions, I wonder if it would be more efficient to schedule a follow-up session to discuss them? I could also invite more people from DFINITY who contributed to this idea, but missed the session.

2 Likes

@dostro @skilesare @bob11 @mzibara @Maxfinity @sea-snake @timo @neeboo

Please let me know if you are interested in a follow-up session.
Support would probably need integration work from wallets as well.

We were thinking of scheduling after next week’s Global R&D Wednesday 27th 5:30 UTC.

4 Likes

Count me in on the follow-up session.

1 Like

I have a question and please forgive me if it is stupid or the wrong place to post.

A big problem seems to be canisters becoming frozen and the time it takes out of the devs day to ensure they have sufficient cycles to keep the dapp operational.

   For daos in particularly would a solution that allows you to use maturity to auto top up canisters allow for a more seamless dev experience? 

In my head I envision it similar to having a bank account that has credit auto drawn out of the maturity to allow for a less involved management of cycles.

2 Likes

Today’s DeFi WG topic is ICRC-45: Live DEX Data Standard we will be going over it before it gets proposed.
https://github.com/Neutrinomic/wg_defi/blob/main/icrc-45/README.md

1 Like

Reminder

Reminder: This is happening today!

Zoom link: Launch Meeting - Zoom

ICRC-45 Live DEX Data Standard documentation was updated with everything we’ve been discussing during meetings.
Please check it out and let us know if you have any feedback.
https://github.com/Neutrinomic/wg_defi/tree/main/icrc-45

Hello everyone, I proposed the DEX Custody Ledger solution to address the issues of atomicity in DeFi transactions and high cross-subnet latency on ICP.

4 Likes

did the questions related to intercanister calls get answered?
Is this cycles boost thing useful if its a wallet canister making a call to another canister?
@domwoe
@ulan

2 Likes

I am leaning towards the solution which leverages ICRC-3 and ICRC-4 in order solve the same problems. It can increase throughput 500x (and faster) and making the swap a synchronous call.