aljaz/lsp
1
0
Fork 0
mirror of https://github.com/aljazceru/lsp.git synced 2025-12-17 06:04:20 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update liquidity-marketplace-spec.md

Browse Source
This commit is contained in:
Aljaz Ceru
2022-11-02 15:52:40 +04:00
committed by GitHub
parent cb45e7c319
commit 2869bfb620
1 changed files with 45 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

50
liquidity-marketplace-spec.md
View File

@@ -1,4 +1,4 @@
# Liquidity marketplace spec # Liquidity marketplace spec - draft
## Version: 0.0.1 ## Version: 0.0.1
@@ -28,8 +28,8 @@ Request an inbound channel with a specific size and duration.
##### Policies #### Policies
Policy field is an json object that can include various different policies that are not mandatory and serve as an additional information provided. Spec covers a list of predefined policies for common use-cases. Policy field is an json object that can include various different policies that are not mandatory and serve as an additional information provided. Spec covers a list of predefined policies for common use-cases.
##### Existing policies ##### Existing policies
1. **closing_policy** - under what conditions will you close the channels or leave it open 1. **closing_policy** - under what conditions will you close the channels or leave it open
@@ -40,11 +40,51 @@ Policy field is an json object that can include various different policies that
6. **push_support** - if you support pushing part of the balance to buyers side 6. **push_support** - if you support pushing part of the balance to buyers side
7. **duration_unit** - what units are you using for duration 7. **duration_unit** - what units are you using for duration
8. **contact** - contact information (tg/twitter/web) 8. **contact** - contact information (tg/twitter/web)
9. **location** - node location 9. **location** - node location information
##### Policy structure ##### Policy structure
Proposed policy format consists of three fields Policy format consists of three fields
1. name -> standardized name in snake case, should be machine readable 1. name -> standardized name in snake case, should be machine readable
2. value -> machine readable value 2. value -> machine readable value
3. info -> human readable field with additional information 3. info -> human readable field with additional information
##### Policy example
```
{
"policies": [
{
"name": "max_htlc_size",
"value": "123456",
"info": "i will enforce this policy for channels smaller than 50million"
},
{
"name": "closing_policy",
"value": "123456",
"info": "i will enforce this policy for channels smaller than 50million"
},
{
"name": "reputation",
"value": "bos=https://fulmo.org/bos-score.html,rank=https://terminal.lightning.engineering/",
"info": ""
},
{
"name": "rate_fee_formula",
"value": "",
"info": "size*(100/size)"
},
{
"name": "fee_policy",
"value": "",
"info": "we have different fee tiers based on chan sizes, more at https://lsp.com/rates.html"
},
{
"name": "push_support",
"value": "true",
"info": "we support pushing part of the balance on your side, up to 2btc in size"
}
]
}
```