Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
AnyHedge Library
AnyHedge Library
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 2
    • Merge Requests 2
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GeneralProtocols
  • AnyHedge
  • AnyHedge LibraryAnyHedge Library
  • Issues
  • #171

Closed
Open
Opened Oct 12, 2020 by Rosco Kalis@rkalisMaintainer

Split library functionality into parts based on use of settlement services

There are two main ways to use AnyHedge. The suggested way is through the automated settlement services. But it is also possible to liquidate/mature contracts in a DIY fashion. At some point we should split up library so it is very clear when the user is communicating with the settlement services, and when it isn't. At that point we should also update documentation to show this clear divide (see !116 (merged))

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Quality Assurance
Milestone
Quality Assurance
Assign milestone
Time tracking
None
Due date
None
Reference: GeneralProtocols/anyhedge/library#171