Project Info
Inspiration
Deploy on-chain strategies, automate risk triggers. All in one DeFi automation through building beautiful flowcharts to wire actions. Inspired by Sequence.io for their cash flow automation software that uses a flowchart UI, and other DeFi trading platforms where we wanted to combine the two together.
What it does
Create comprehensive flowcharts that utilizes Programmable Transaction Blocks (PTBs) that work on the Sui network. Create a new account via Google which also created web3 credentials for you, including a Sui wallet address on the mainnet. In "Flows", while the main feature is creating those flowcharts, you can manually run them, OR you can run them offline because we use trigger.dev which act as cron jobs on the cloud that are running 24/7 so you can have triggers along with actions. For example, you can do swap action with PTB, using a trigger where the price goes above or below a target price you've set, or if you want you can send from a coin to another coin on the Sui network using a trigger where you can schedule those times.
How we built it
We used Next.js for the frontend and Hono.js for the backend, all written with Typescript. We used a lot of technology from the Sui stack. We used the Mysten lab's Sui typescript SDK. We used Zklogin with Shinami as our mainnet prover to turn web2 credentials to create web3 credentials all while detaching both and creating proof signatures so we can use the powerful Programmable Transaction Blocks (PTB) that the Sui stack offers so we can enact multple-swaps or multiple-sends with lower gas fees. We also used external market data for the Sui network via Blockberry and Birdeye.
Challenges we ran into
We ran into trouble trying to run the ZkLogin authentication on the mainnet, but we discovered that shinami was offering a prover service for mainnet applications for around 50 requests for the month.
Accomplishments we're proud of
Successfully developing with the Sui stack for the first time. Especially making the PTB's actually work to send and swap coins. Implementing the ZkLogin on the mainnet, and having seamless connectivity and information to generate Zk proof signatures so we can validate the PTBs.
What we learned
We learned various implementations on building with the Sui Stack, looking into their kits on building DeFi apps, using Programmable Transaction Blocks for executing numerous actions at the same time to reduce fees like no other technology.
What's next
Add AI integration to also automate creating these flowcharts for you based on trends, social media, and various other technical analysis. Add bunch more triggers for more customizability.
This repository has no readme, or GitHub could not be reached.
Analysis
View
Metric
- 28
- 23
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- Next.jsIn code
- ReactIn code
- Tailwind CSSIn code
- TypeScriptIn code
- PostgreSQLClaimed
5 of 6 appear in the indexed code. 1 claimed on Devpost could not be matched to code, which may simply mean the tool leaves no trace in the repository.
AI coding agents
- CodexConfig
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
247 KB
Source files
83
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
pla-llc/vero-calhacks
98 files · 377 KB · @ 7a59c4e
Structure
Interface
46 files · 47%Screens, components and styles rendered to the user.
API & routing
8 files · 8%Request entry points: routes, handlers and controllers.
Application logic
25 files · 26%Domain rules, services and shared utilities.
Background jobs
2 files · 2%Work run outside a request: tasks, workers and schedules.
Data & schema
1 file · 1%Schema definitions, migrations and data access.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- TypeScript97%
- CSS2%
- Markdown1%
- YAML0%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
package.json
npm · 40- @hono/zod-validator
- @mysten/deepbook-v3
- @mysten/sui
- @prisma/client
- @radix-ui/react-accordion
- @radix-ui/react-avatar
- @radix-ui/react-dialog
- @radix-ui/react-dropdown-menu
- @radix-ui/react-label
- @radix-ui/react-navigation-menu
- @radix-ui/react-popover
- @radix-ui/react-separator
- @radix-ui/react-slot
- @radix-ui/react-tooltip
- @trigger.dev/sdk
- @xyflow/react
- better-auth
- class-variance-authority
- +22 more
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.