bitshares / bitshares/bitshares-core
Toolkit for developer onboarding ( meta ticket )
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 660
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 26
Description
**User Story**
Please tell us about your feature request using the User Story format:
As a new dApp developer (Python or JavaScript) I want example boilerplate scenarios with documentation so that I may quickly understand how the BitShares operations and APIs may be used to build hello world and financial services solutions on the platform.
**Impacts**
Describe which portion(s) of BitShares Core may be impacted by your request. Please tick at least one box.
- [x] 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.)
- [ ] Protocol (the blockchain logic, consensus, validation, etc.)
- [ ] Security (the security of system or user data, etc.)
- [x] UX (the User Experience)
- [ ] Other (please add below)
**Additional Context (optional)**
Additional sub-task Issues will be created later to address the points below. Also note that this effort is not exclusively “Core Team” and sub-tasks make link to other BitShares repos.
Design and Features Integration Plan:
1. Build User Interface along with bitsharesJS for easy to use boilerplate
a. Come out with architecture plan
b. Provide wireframe mockup based on architecture
2. Subsequent building on pybitshares ( details to be added after point1 completes)
3. Build features similar to eos (eostoolkit.io) and telos (https://portal.telosgermany.io/home)
a. Governance (voting)
b. Transfer Token
c. Multi sig
d. Dapps section
4. Explore existing APIs that may need to be configured for above tasks
5. Integrate Spotlight features and make developer friendly:
a. Integrate Beet
b. Integrate HTLC
c. Integrate Barter
d. Integrate Collaterized Debt position
e. Integrate direct debit
f. Explorer - Searching functionality (needs to be revised and revisited )
6. Analytics & Dashboarding Page (through Elastic Search) (needs to be revised and revisited )
a. Node related
b. Dapp related https://dappradar.com
c. User related
Benefits:
1. Onboard new dapp developers
2. Increase dapp count. Example other block chains have https://dappradar.com
3. Help create new market place for creating and using UIA (User Issued Assets)
4. Above will help increase bitshares utility, volume, transactions, locking token in apps ( as observed for other block-chain eos - https://dappradar.com/rankings/protocol/eos)
5. Expose easy to use spotlight features like Barter to help application development
6. Beet integration with boilerplate to avoid cloud wallet password and directly use Beet (eostoolkit.io reference)
## 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
No files, tests, or entry points are named. Start by refining the user stories and splitting the architecture, wireframe, bitsharesJS, pybitshares, API, feature-integration, and analytics ideas into scoped sub-task issues; completion would require agreed requirements and test cases before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- api, design, developer-experience, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100