bitshares / bitshares/bitshares-core
MPA Stability Fee
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 660
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 26
Description
**User Story**
As a MPA owner I'd like to be able to set a stability fee on my MPA so that the business is more sustainable. The fee works like an interest for borrowing the debt asset.
Key features:
* debt position holders pay a percentage fee periodically, automatically
* if a debt position's collateral ratio (CR) is too low after paying the fee, it will get margin called
* in extreme circumstances it may cause a black swan event
* fee rate is adjustable by asset owners if certain issuer permission / flag is set
Optional features (perhaps add later):
* distribute a percentage of the stability fee to debt asset holders
**Impacts**
Describe which portion(s) of BitShares Core may be impacted by your request. Please tick at least one box.
- [ ] API (the application programming interface)
- [ ] Build (the build process or something prior to compiled code)
- [ ] CLI (the command line wallet)
- [ ] Deployment (the deployment process after building such as Docker, Travis, etc.)
- [ ] DEX (the Decentralized EXchange, market engine, etc.)
- [ ] P2P (the peer-to-peer network for transaction/block propagation)
- [ ] Performance (system or user efficiency, etc.)
- [x] Protocol (the blockchain logic, consensus, validation, etc.)
- [ ] Security (the security of system or user data, etc.)
- [ ] UX (the User Experience)
- [ ] Other (please add below)
## CORE TEAM TASK LIST
- [ ] Evaluate / Prioritize Feature Request
- [ ] Refine User Stories / Requirements
- [ ] Define Test Cases
- [ ] Design / Develop Solution
- [ ] Perform QA/Testing
- [ ] Update Documentation
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by reviewing the user story and the checked Protocol impact, then work through the listed core-team tasks: requirements, test cases, design, implementation, QA, and documentation. Done requires an agreed design and implementation of periodic fees, margin-call handling, and issuer-controlled fee adjustment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100