-
Notifications
You must be signed in to change notification settings - Fork 646
Issues: bitshares/bitshares-core
Guides to setup API nodes / ιι±ε
γAPIθηΉζε»Ίζη¨
#2187
opened May 30, 2020 by
abitmore
Open
3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Ledger Nano S Hardware Wallet Support
1b User Story
The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s)
2a Discussion Needed
Prompt for team to discuss at next stand up.
3a Request
Classification (default) which does not fit as a Feature, Enhancement or Bug. Core Team to evaluate
6 Security
Impact flag identifying system/user security
6 UX
Impact flag identifying the User Interface (UX)
Ability to airdrop/sharedrop/pay dividends of one asset to all holders of another.
1b User Story
The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s)
2a Discussion Needed
Prompt for team to discuss at next stand up.
3b Feature
Classification indicating the addition of novel functionality to the design
6 API
Impact flag identifying the application programing interface (API)
6 CLI
Impact flag identifying the command line interface (CLI) wallet application
6 Performance
Impacts flag identifying system/user efficiency, performance, etc.
6 Protocol
Impact flag identifying the blockchain logic, consensus, validation, etc.
6 UX
Impact flag identifying the User Interface (UX)
On-chain user scripts ("dumb" contracts)
1b User Story
The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s)
2a Discussion Needed
Prompt for team to discuss at next stand up.
3b Feature
Classification indicating the addition of novel functionality to the design
6 API
Impact flag identifying the application programing interface (API)
6 CLI
Impact flag identifying the command line interface (CLI) wallet application
6 DEX
Impact flag identifying the Decentralized EXchange, market engine, etc.
6 Performance
Impacts flag identifying system/user efficiency, performance, etc.
6 Protocol
Impact flag identifying the blockchain logic, consensus, validation, etc.
6 Security
Impact flag identifying system/user security
6 UX
Impact flag identifying the User Interface (UX)
Clean up FC
1b User Story
The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s)
2d Developing
Status indicating currently designing and developing a solution
3c Enhancement
Classification indicating a change to the functionality of the existing imlementation
4a Low Priority
Priority indicating minimal impact to system/user -OR- an inexpensive workaround exists
6 Performance
Impacts flag identifying system/user efficiency, performance, etc.
6 Security
Impact flag identifying system/user security
code cleanup
Trezor One Hardware Wallet Support
1b User Story
The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s)
2a Discussion Needed
Prompt for team to discuss at next stand up.
3a Request
Classification (default) which does not fit as a Feature, Enhancement or Bug. Core Team to evaluate
6 Security
Impact flag identifying system/user security
6 UX
Impact flag identifying the User Interface (UX)
#1342
opened Sep 26, 2018 by
ryanRfox
10 tasks
Hardware Wallet Support (General)
1a Epic
High level concept to be addressed. Description should contain a list referencing child User Stories
2a Discussion Needed
Prompt for team to discuss at next stand up.
3a Request
Classification (default) which does not fit as a Feature, Enhancement or Bug. Core Team to evaluate
6 Security
Impact flag identifying system/user security
6 UX
Impact flag identifying the User Interface (UX)
#1339
opened Sep 26, 2018 by
ryanRfox
11 tasks
Ledger Nano Blue Hardware Wallet Support
1b User Story
The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s)
2a Discussion Needed
Prompt for team to discuss at next stand up.
3a Request
Classification (default) which does not fit as a Feature, Enhancement or Bug. Core Team to evaluate
6 Security
Impact flag identifying system/user security
6 UX
Impact flag identifying the User Interface (UX)
#1341
opened Sep 26, 2018 by
ryanRfox
7 tasks
Operation to update The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s)
2b Gathering Requirements
Status indicating currently refining User Stories and defining Requirements
3b Feature
Classification indicating the addition of novel functionality to the design
6 Protocol
Impact flag identifying the blockchain logic, consensus, validation, etc.
6 UX
Impact flag identifying the User Interface (UX)
feature
hardfork
account_object::allowed_assets
1b User Story
Missing blocks due to high latency of maintenance block
performance
plugin
question
#504
opened Nov 24, 2017 by
abitmore
REST API discussion
1b User Story
The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s)
2a Discussion Needed
Prompt for team to discuss at next stand up.
3c Enhancement
Classification indicating a change to the functionality of the existing imlementation
6 API
Impact flag identifying the application programing interface (API)
6 Performance
Impacts flag identifying system/user efficiency, performance, etc.
api
#870
opened Apr 23, 2018 by
abitmore
Statsd Plugin
1a Epic
High level concept to be addressed. Description should contain a list referencing child User Stories
2a Discussion Needed
Prompt for team to discuss at next stand up.
3b Feature
Classification indicating the addition of novel functionality to the design
6 Performance
Impacts flag identifying system/user efficiency, performance, etc.
6 Plugin
Impact flag identifying at least one plugin
feature
performance
plugin
Make better use of multi-core servers
1b User Story
The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s)
2d Developing
Status indicating currently designing and developing a solution
3c Enhancement
Classification indicating a change to the functionality of the existing imlementation
4a Low Priority
Priority indicating minimal impact to system/user -OR- an inexpensive workaround exists
6 Performance
Impacts flag identifying system/user efficiency, performance, etc.
9c Large
Effort estimation indicating TBD
proposal framework for api nodes documentation
documentation
help wanted
#650
opened Feb 7, 2018 by
oxarbitrage
apidocs
1b User Story
The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s)
2d Developing
Status indicating currently designing and developing a solution
3c Enhancement
Classification indicating a change to the functionality of the existing imlementation
5a Docs Needed
Status specific to Documentation indicating the need for proper documentation to be added
6 API
Impact flag identifying the application programing interface (API)
code cleanup
documentation
#792
opened Mar 27, 2018 by
oxarbitrage
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.