m Baimaas blockchain data market
- jim mason
Key Points
- requirement for data market protocol like Ocean Protocol ( https://oceanprotocol.com/ )
- https://www.baimaas.com/
- has financial apps now
References
| Reference_description_with_linked_URLs_______________________ | Notes______________________________________________________________ |
|---|---|
| https://www.baimaas.com/ | |
Baimaas customer requirements for blockchain data marketplace
Dear Senthil
We are having a requirement in block chain ecosystem, you referred Paramount , below are the ask .
Capability
Scenario 1:
person who has ability to develop a block chain protocol based on set of use cases. this can be made thru forking out of existing protocol . for eg Ethereum blockchain or grounds up development of blockchain protocol based on given use cases (similar to ocean protocol)
Scenario 2:
Based on use cases , the lead architect /sme suggest leveraging existing protocols like Ethereum , hyperledger etc
The paramount offering and standard COE practice for any development engagement will include the standard operational structures, that we ( the client) will not be incurred charges for:
Environment
Paramount internal cloud/ blockchain development environment
Paramount internal cloud/ blockchain test environment
Paramount internal cloud/ blockchain staging environment
Paramount internal cloud/ blockchain pre-prod environment
Paramount internal cloud/ blockchain client demonstration production environment.
Testing Services :
Blockchain capable development houses have arrangements / frameworks in place for Ethereum fabric, some with Corda, some with XinFin, some with Polkadot and etc…. since they “favour” those specific blockchain protocols…and have their transaction fees models in place and not passed onto the client during the development phase…
For example, we do not want to pay for blockchain transaction/gas/ether/consensus/node/wallet/membership fees and etc fees, and have wait times and etc, as Paramount develop and deliver the platform/services/functions.
Paramount blockchain team/lead should understand this model quite well, so he/she would also be able to explain as well.
Expectation
We assume that Paramount has its own established blockchain/platform development ecosystem. Pls confirm?
Hope you have arrangements / frameworks in place for Ethereum fabric, some with Corda, some with XinFin, some with Polkadot and etc…. since they “favour” those specific blockchain protocols… Pls confirm?
As for one example….. if a development firm wants to partake in the Corda blockchain DLT network as a full member, it’ll cost approx. USD$250,000…depending upon their goals…
The assumption is that the developer teams already (or establishing) have the capabilities/tools/ frameworks in hand to deliver as part of the business offering.
we are expecting that the engaged development team will be able to provide a justified / quantifiable Total Cost of Ownership (TCO) operational model, at the time of hand-over/ transition. This will also determine the long-term operational costs in an outsourced engaged model.
Hope the above makes sense and is understandable.
Abdul Majeed
Baimaas data market protocol Task List
| task___________________________________________________________________________ | action___________________________ | status_______________ |
|---|---|---|
| setup project access: JIRA, Confluence, Github, Postman, DB | ||
| get input requirements, SWOT, GAPS | ||
| compare similar data market places - CMDM | ||
| define payment services for invoicing, usage or subscription fees | ||
| review onboarding model: accounts, trials, usage limits | ||
| check use of Indy IDs, wallets for Fabric MSP services | ||
| define any known integration requirements | ||
| create product roadmap | ||
Key Product Solution Questions
- What are the data market life cycle stages?
- what are the challenges, opportunities for each stage and role in the network?
- who can pay for the solution ?
- what's the story we share? ( challenges & opportunities, needs, FBRs, case studies )
Application Feature Dependency Map
Application Non-Functional Requirements
| Platform Capability__________________________________________ | Value_____________________________________________________________________ | |
|---|---|---|
| Identity Management | Trusted Profiles for people, organizations, devices | |
| Ownership & Consent Management | Every account can manage data and consent | |
| Application Management | Allows flexibility in licensing models given dependencies | |
| Compliance & Governance | Transparent, automated compliance & governance support | |
| Secure Data Sharing | Data shared securely based on authorizations | |
| Analytics & AI | Smart efficient decisions and optimizations | |
| Blockchain | Trusted Data Provenance ( secure CDE proofs ) | |
| Smart Data | Pre-built services, views | |
Product Delivery Concepts
| _Item__________________ | notes______ |
|---|---|
| a>> well defined work packages for a product w good research tasks ** | |
| Which services do we integrate with vs build? | 3 B sourcing model |
Key Concepts
IAMS - Identity, Access and Memberships Services
FMS use of templates
transaction ledger formats
ledgers
archives
document services
digital IDs
digital wallets
digital credentials
tokens