Stefan Adolf
    • 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

      This note has no invitees

    • 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
    • Note Insights New
    • 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 Note Insights 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

    This note has no invitees

  • 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
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # Future income NFT streams lets users sell their future stream revenue instantly ## workings - an user receives streaming funds out of a Superfluid SuperToken stream, e.g. as the promise for the work he's doing. - the user wants to early access funds that haven't been streamed to him yet - the user mints an NFT containing a SuperApp interface. The SuperApp callbacks will redirect the stream sink to whoever will own the NFT. - the user sets an termination date for the NFT ("holder receives funds from the stream for the next 30d") - the user sells that NFT on an open marketplace (manually prices it at the value the stream will accrue until the term. date) - a buyer buys that NFT from the user. The SA callback redirects the SF stream to the new owner's address. - The buyer can always decide to sell the NFT (at a price point matching the estimated remaining streaming revenues to others) - The user may buy back their NFT from the buyer if they didn't need the money - After the termination period the initial stream owner can claim back / burn their future NFT. that will reset the stream sink to their address / an address of their choice - ## why - You find a cheap PFP NFT on OpenSea for 0.5 and you assume it to go up by 10x in 14 days. But you can't afford it now. You have a DAI stream that constantly is sending you your salary which will cumulate to 2E at the end of the month. You mint a future NFT with a termination date of 15 days (worth 0.51E) for 0.5E on the open market. You can buy the PFP NFT you wanted for 0.5E. After 1w Your PFP NFT is worth 1E. You buy back your stream NFT stream back for 0.52E. You paid 0.02E for instantly borrowing 0.5E. The buyer earnt 0.02E. ## Bonuses #### It can be an NFT liq / financing use case the loan isn't paid out to you directly but used to buy the PFP NFT on Opensea. It's then escrowed until the end of the termination period. If the stream suddenly stops (proof needed) (the buyer doesn't get the stream value they expected to get), the buyer can claim the NFT (a fraction worth of the remaining stream value according to the current NFT value) #### Risk hedging. In case the stream isn't fulfilled, future NFT holders may claim the defaulted difference from a staking pool of the protocol. Stakers can add funds (in the respective currency) to the protocol and receive fees. Fees are collected by the protocol when future NFTs are sold (erc2981). The protocol will use the locked / staked funds of risk hedging stakers to take over the streaming obligations. Aka stakers are liable for the streaming guarantees of the unknown inputs. ### Notes I wrote this mostly after reading their "official" exapmle code: https://github.com/superfluid-finance/protocol-monorepo/blob/dev/examples/budget-nft/contracts/BudgetNFT.sol ;) ### UI In terms of the UI we will need the following: - an ability to buy/sell your NFT with streamed income (or I guess Opensea or any other NFT marketplace can be used for this matter) - Ability participate in the insurance pool. Stake/Unstake funds and see the APY ### Storyline - DAO wants to give money to DAO contributors - Using superfluid tokens to do this - Working 30 days, receiving 2 ETH - Benefits - DAO: Be an more attractive "employer" - Contributor: Have money upfront, get best "rate" vs. getting a loan from a bank ### What do we need to build: - NFT Contract (that has the functionality that diverts streams) - Frontend - of user that shows all streams + button "create NFT out of streams" - of "investor": query the collection of NFTs (from Opensea; query from the contracts), display the metadata - other stuff: ?landingpage etc.? ### SUBMISSION CONTENT: Please proof-read / amend as required. There is three text fields that we will need to fill. I prepreared answers for the first two, however the third is technical and I would be glad if you could answer them. Thank you! ----- 1) A 280-character or less description of your project (it should fit in tweet!) OPTION A: ⚡️ Sellary - Future income NFT streams built on Superfluid ⚡️ Receivers of Superfluid income streams can mint NFTs that control these inflows. Selling them on Opensea allows the initial receivers to access future income instantly! 🛸 OPTION B: We enable people working in web3 to get their income instantly! Meet Sellary: Future income NFT streams built on Superfluid ⚡️⚡️⚡️ You wonder what the future of Superfluid might look like? Come and check out Sellary 🛸 OPTION C: Superfluid does the next leap: Meet Sellary! Sellary brings future income streams instantly to receivers of constant flows. Our solution mints an NFT that can be sold on marketplaces. The buyer of this NFT receives all future constant inflows OPtion D Sellary allows freelancers, DAO contributors or employees to claim their streamed income instantly - by wrapping the future value of SuperFluid money streams into tradable NFTs. ----- 2) Long Description Go in as much detail as you can about what this project is. Sellary is a future income NFT protocol built on Superfluid. It enables money stream receivers to instantly exchange their money flows against their accumulated future value. Assume Hacker “Pepe” currently works at Developer DAO and receives his wage as a real time income stream via Superfluid. Suddenly he stumbles upon a DeadFellaz NFT listed at 2 ETH, well below its collection's floor. If he had to wait until his streamed salary finally accrued sufficient funds to buy it, someone else would have sniped it before for sure. How great would it be for Pepe if he could instantly get his income stream's value?! Sellary allows him to wrap his realtime revenue stream into an NFT and offer it to investors on public marketplaces. The token's initial price is determined by the underlying money flow rate and the duration Pepe wants to sell it for. Once an investor buys the token (potentially at a discount), Sellary delegates the stream's output to the respective new holder. Pete can use the proceedings to take the Deadfellaz bargain and make a profit from its developing market value. Sellary provides instant liquidity and flexibility for money stream receivers. Realizing long term revenues as NFTs let employees benefit from much better interest rates and is dramatically more convenient than requesting credit at a bank. Investors can consider Sellary NFTs an attractive investment opportunity that's backed by an individual's salary. Technically Sellary is an ERC721 contract that's controlling all stream flows for recipients. Entities ("employers") who'd like to offer the protocol's advantages to their employees stream collective funds to their dedicated Sellary treasury contract that controls the beneficiaries' income streams. A receiver can decide to wrap their stream into a Sellary NFT by just calling the contract's `issueSalaryNFT` function providing the desired duration the NFT should capture in value. After the NFT is minted, the original salary stream is replaced by a new income stream that's targeted at the first NFT holder. All subsequent transfers delegate the stream output to the respective new owners. After the NFT's lifetime has ended, the original salary recipient can claim back their original salary stream by burning the asset. Potential extensions: - Pooling. Instead of purchasing individual NFTs, multiple stream NFT representations are collected in a pool that investors can collectively invest into (like Uniswap) - Investor's Insurance. Buyers can hedge against the risk of defaulting stream origins (i.e. by keeping 1% of NFT sales in an insurance pool) - Multichain support. Integrate other chains, e.g. via Connext - add EPNS support to be notified when an NFTs has reached its lifetime and can be claimed by the salary owner. - Delegated claim burning: anyone can burn mature NFT streams and receive a small reward that's deducted from the NFT sales price. ------ #### How it's made *(Tell us about how you built this project; the nitty-gritty details. What technologies did you use? How are they pieced together? If you used sponsor technology how did it benefit your project? Did you do anything particuarly hacky that's notable and worth mentioning? How did you impress yourself which what your team built?)* Sellary is built on top of the Superfluid money streaming protocol. Our contracts rely on OpenZeppelin's primitives and we use Hardhat as our toolchain of choice for building, testing and deploying. Frontend-wise we make use of React / NextJS and decided to go with web3modal to connect to injected providers and WalletConnect.

    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