π Want to deepen your Move knowledge?
In my latest article, we build a DEX from scratch with Move on IOTA Rebased! ποΈπ οΈ
Learn about Liquidity Book pools, swap logic, and key Move concepts βοΈ
Part 1 of 3 β more to come!
π
https://t.co/TLyOOqogms
#MoveLang#IOTA#DeFi#Web3
π¨ LB DEX in Move: Part 2 Out Now! π¨
Move devs! Are you ready for the next step of building an LB DEX with Move? ποΈπ§
This posts expands on the Part 1, diving into Liquidity Providers πΈ and Fees. π°
Go check it out below!π
https://t.co/mmHLHfkeGK
#MoveLang#IOTA#DeFi#Web3
π¨ New Move Article π¨
Some of your Move code isn't meant to be accessible to everyone. π΅οΈ
Keep unauthorized users out with Access Control. ππ€
How? Check out my new article about Common Access Control Patterns for Move π
https://t.co/HVHD9OeH1V
#IOTA#MoveLang#DeFi#Web3
π Want to deepen your Move knowledge?
In my latest article, we build a DEX from scratch with Move on IOTA Rebased! ποΈπ οΈ
Learn about Liquidity Book pools, swap logic, and key Move concepts βοΈ
Part 1 of 3 β more to come!
π
https://t.co/TLyOOqogms
#MoveLang#IOTA#DeFi#Web3
@sabrigoldberg In my opinion, it's certainly important to understand how a frontend interacts with a smart contract, but they are relatively simple to build, compared to implementing application logic in a smart contract. I'd say create a frontend once, then focus again on the Move.