Tim Black
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee
    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee
  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    2
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Chat.shapeshift.com research doc ## Problem statements As a defi native user I have trouble finding yield that is sustainable and manageable. I hate clicking through multiple frontends, tracking yield APY's and making sure things are well managed week-to-week instead of chasing yearly APY's. > agents can read and even deploy contracts. allowing you maximum yield, automation, and stop loss exits in case farming dries up or isn't as competitive. As an active trader or passive trader with some asset exposure, I want to run an agent against a strategy, get updates in a timely manner, and be able to drill down into details for my PnL. I'd like to source and manage my edge with the help of an agent. > agents increase your PnL, fine tuned by you. they help you find your edge. I want to follow momentum more but can't keep up with the firehose of new places to focus on. An agent can help me stay on top and stay exposed to logical risks. > agents help you get ahead of the curve. Finally, As a crypto native user, I'm constantly second guessing myself and I'd like to just hit a target or be told why I can't hit a certain APY. An LLM model allows me to interact and learn why things do or don't work in real time so i make better decisions. > agents build confidence and trust over time. ### Use cases for personas High level user categories and core flows: 1. ***L1 swaps*** i want to: - Sweep selected assets into bitcoin daily, weekly, etc. - DCA into singular assets based on price performance or percent gain. 2. ***Daily Swapper*** i want to: - Trade through multiple categories a day based on my own criteria and price targets. So that i make profits of some level. - Sweep that performance into something more marquee or Defi yield farms. - Get suggestions about what is available, momentum (trending assets), and what's possible so that i can maximize my hopeful returns. 3. ***Yield service*** (defisaver, summer.fi, Gnosis Safe etc.) i want to: - Spin up a smart account and start linking together minting, staking, farming strategies. - Swap into a farm directly and track it's performance. - Hit a target APY and exit if I don't over a period of time. So that I stay on target for yield/PnL. - plug in multiple APIs to the agent and have them run tasks for me (weekly trade reports etc.) 4. ***Advance trade order types*** i want to - Manage a stack of orders based on a strategy, back test it, and improve the model as often as I can with an agent at my side. - Track my pnl up to the minute and reasses what the best path is for assets in play. - pick delta neutral, crab, convex, and momentum strategies out of the box but fine tune them to my outlook on markets. Each of these use cases feeds into one another and the better we get at ingesting services for the LLM stack first (possibly using the interface as test ENV) the stickier the suite of marquee prompts becomes. We get bonus points if we figure out how to link mobile experience to this and generate dashboards, performance, back-testing, etc. as plugins (or custom GPTs). ### Detailed User stories Sweeping: - As a user on the chat interface who wants a sweeping. I want to spin up a wallet for my agent and deposit into it. The agent should explain to me the benefits of depositing. that these first tx's will be slow but from there they From there selecting assets, choose a price that is acceptable, pre-approve/fund gas, and sweep into the main asset on that chain. From there i would like to swap into Bitcoin daily, weekly, or monthly. - DCA into singular assets based on price performance or percent gain. ## Where the tech is now and how to get there We need to be cognizant that, as of Feb in 2025, the SOTA is still off from autonomy. So, we should aim towards a novel app, an onchain copilot. We'll need to think through infrastructure for event loops, feeds (oracles, prices etc.), RPCs, API keys, ElizaOS, hosting, inference, self-custody, and multisigner infra-out-of-the-box requirements. We should break these into stages: ### Stage 1: Copilot Assistant (Q2-Q3 2025) Core Infrastructure: - Event monitoring system for wallet/price feeds - Basic task scheduling (daily/weekly sweeps) - Integration with existing price oracles - Initial RPC management layer - Basic prompt template system - Inference engine - [Eliza OS evaluators](https://elizaos.github.io/eliza/docs/core/evaluators/) - smart wallet or TSS wallet for batch signatures - consider HDwallet rework or forking Trust wallet core - read current assets on wallet connected - Swapper routing algorithms - using our API's for quotes and execution - improving the long tail conversion hops - optimistic price and gas approval - queue transactions - prompt user to sign Tx's individually User Experience: This should enable user stories 1 & 2 - Natural language definition & refinement - Guided setup for common patterns - Manual approval for all transactions - Basic portfolio analytics dashboard ### Stage 2: Semi-Autonomous Operations (Q4 2025) This should enable user story 3 and the pieces in 1&2 that are more complex or compute heavy. Enhanced Infrastructure: - Custom event triggers - Point-in-time - if this than that - chain of thought => IFTTT - Performance tracking system - Strategy back-testing framework - Multi-signature integration - Custom API aggregation layer - [Eliza Autnomous trading](https://elizaos.github.io/eliza/docs/advanced/autonomous-trading/) User Experience: - Preset strategies with customization - Automated monitoring with alerts - Batch transaction proposals - Performance visualization ### Stage 3: Contextual Intelligence (Q1 2026) This should enable user story 4 and the "rest of the owl." Advanced Infrastructure: - Real-time market analysis - Cross-protocol opportunity detection - Advanced risk management system - Distributed performance verification - Privacy-preserving analytics User Experience: - Strategy recommendations & reminders - notifications + SaaS & webhook integrations - - Automated position management - Custom trigger creation - Risk/reward simulations - Swarm embeddings ## Competitive landscape There are dozens of teams who have built with or are building with AI but none of them have a working auditable/useable product. On top of that most everything released so far is demo videos or in early alpha. What we're envisioning is simple to start and grows into the use cases based on demand and feasibility: chat with the robots, let them mange transacations, then give them one of N keys and they gradually execute more your risk tolerance and PnL. Could be smart contract wallets, or other signature thresholds, until users feel comfortable with performance. Most teams are focusing on EVM's only or are completely hand rolling infrasturcture for interactions and going to broad. A focused approach on each use case that builds on the next is the winning strategy, alongside some possible partnerships with Venice and the Thorchain/Chainflip ecosystem(s). SS has three unique advantages: - We can be early movers in this market. no one has built infrastructure for cross chain at the scale we have or encountered the issues we have. Almost every other product has to get contract deploys, custom adapters, isn't focused on L1 swaps then iterate, has to probably pay out to integration partners, etc. etc. The point is no one has shipped. Why not us? - We have to stay focused and lean which means we can iterate on a POC quickly instead of trying to capture the entire market for defi interactions or something insanely ambitious that isn't quite realistic. This also means we can add things people ask for as they want them. Ideally there is insatiable demand because people see the potential, allowing us to amass users, talent, capital, and momentum. - We're a DAO and have a currency that we can leverage creating demand down the line (llm inference farming, pay for agent deploys, wallet spinups, partnership pools, etc. etc.) this means we can design partnerships that are onchain and be more flexible than traditional investments or competition. We can build together and are very experienced with rev sharing. ### Who are we building for? How does that drive its design? The TAM for this covers most of crypto. Language as the interface, plus the scheduling abilities of agents is a massive opportunity. Most simple use cases combined with a robot that doesn't sleep or take breaks will likely increase capital efficiency for anyone's assets. I've prioritized/narrowed the user stories into what i think is simplest best and as we explore inference, fine tuning, hosting models, and the like we should improve from there with a feedback loop (ship intereaction case, users make money, they use our infra so DAO makes money too, and they build/ask for more; rinse and repeat.). Chat.ss.com needs to tell the story: own your edge. ### Path to POC ### Mocks and UX prototypes ### Final thoughts We can leverage the backend into the LLM if we go gung ho NOW (Q1 2025). This has a limited shelf life though as there are a half dozen teams pursuing this meaningfully that will catch up quickly to our advantage. Also, signing a large list of transactions to start is ok as a POC. But we should get out of that pattern as fast as we can and move to batch signatures against whatever strategies or actions users create. Gnosis safes under the hood will work as could Vultisig potentially. Strategies/actions is where a fine tuned model may make sense, it could also be just pure inference. There is a balance between giving away all your funds to an unbiased machine gambles too hard. And hitting acceptable levels of risk/losses improving as a result and getting it all back.

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully