PIPO STATION

Sequencer Fee Sharing enabled DEX. Community owns SFS fees.

Comment

Welcome to Pipo Station! A community of nooters!

Video: https://www.loom.com/share/fc3581df7dd84400ab29de5b4a9980d3?sid=d6ecfbaf-4e53-4ab2-95e6-3bea5f5bea66

Inspiration

As a developer, I build, deploy, and run code on-chain. And I usually do it once. I'd much rather relax and drink my french-pressed tea than constantly deploy algorithmic coins and perp tools. So, I thought it'd be great if the community can run the project.

However, most of the time when the community runs the project, the developer makes the bread and the community is left to dry as unpaid labor. So, this project was idealized so that if the community continues the project, then the community makes the dough.

Every step of the process, from token creation to pool management, can be deployed and managed by brave degen hackers.

What it does

Essentially every deployed contract has the ModeSFS module.

What that does is it gives the Sequencer Fee Sharing NFT to the contract deployer. Since every token, pool, swap, oracle ... can be deployed by the community, then all the SFS fees go directly to the community. Press some buttons and in a few clicks, you'll be generating income like any other DEX developer.

No middleman, no weird hidden fees, and more tea for me.

How we built it

The smart contracts are powered by Algebra Protocol v2 with SFS modifications and some custom contracts.

Since there are no price oracles on chain, we have a very unique and futuristic way of updating prices through a working scheduler. It's unpaid, but we promised it cookies.

Challenges we ran into

It's been a hot minute since I've deployed anything on-chain. Many tears were wept either running hardhat scripts or porting hardhat to foundry. A lot of the packages aren't synced up. (ie. root package ethers version != submodule ethers version). Also, deploying a monorepo ... who ever thought a monorepo with submodules was a good idea?

Honestly, half the contracts don't work and half of the frontend isn't hooked up properly. We'll just put that on the roadmap and call it a developing feature.

Accomplishments that we're proud of

Well, technically the boilerplate code is finally done. Hip hip hooray! We have a few deliverables and many planned features. It's entirely possible to fork the project, delete unwanted submodules and packages, and you'll have a FullStack project template.

What we learned

No monorepo. And no submodules of entire protocols. Foundry really likes SOC. Also, maybe deploying an entire fullstack DEX is beyond the scope of a hackathon.

What's next for PIPO STATION

If I get funding to buy my cookies, I'll finish the project, because tea doesn't drink well without cookies.

For Pipo Station, I'll need to UI/UX glowup and fix all the contracts. Once SFS is ready and deployed, then we can add support for vaults to handle the deployer fees since currently it's just a pile of SFS NFTs sitting in an EOA. My current plan for the vault is to use a gauge voting feature with a algo stable as the vote, so that I don't have to worry about the vault and the DEX can just run itself.

Built With

Share this project:

Updates