Please describe your proposed solution.
Key Points:
- Create a brief report on existing Cardano node release engineering practices and specifications on requirements for consistent future updates of the Wolfram Cardano EPC
- Create a proof-of-concept to launch and manage Cardano nodes within the Wolfram Cardano EPC
- Explore seamless failover from private Cardano nodes to public Cardano node infrastructure
- Support public ledger–based digital transformation in enterprise use cases
Wolfram Technical Consulting has encountered demand for Wolfram Cardano EPC support for enterprise projects that wish to use the Cardano public blockchain.
EPC takes the unique benefits of the Wolfram technology stack and provides them in an environment that can be deployed both on premises and within cloud providers such as AWS (and other cloud providers soon). EPC allows companies to create rapid knowledge-driven applications using the Wolfram Language, Wolfram Notebooks and instant APIs, which can build microservice APIs that can be deployed to other front ends.
However, one of the many difficulties companies have is moving blockchain-based projects from public shared infrastructure like the Wolfram Public Cloud to their own managed infrastructure (on premises or in a cloud environment), like EPC, as they begin to scale their projects. Wolfram does not have a solution currently that allow EPCs to integrate and manage private Cardano nodes.
Our solution is to rebuild the middleware (a “system server” in our language) we use on our public cloud to support running Cardano nodes from within EPCs. This middleware solution would support a hybrid approach (the Wolfram Public Cloud, EPC on premises or a third-party cloud environment) and allow Wolfram Technical Consulting and external developers to build solutions to seamlessly move from publicly run infrastructure to private infrastructure with their own Cardano nodes.
Enabling support for such a hybrid environment would be better for the Cardano blockchain as it provides a more decentralized/distributed structure. In addition, support for hybrid environments would allow companies to easily move between development and deployment options.
Importantly, this is a proof-of-concept.
We will also look at release engineering needs of Cardano node packages, admin tools and other resources to figure out the process of updating the EPC package so that it is something that can be maintained and updated as Cardano node software updates.
I. Discovery Phase
If the project is not funded, we may wind it down and delay the completion until future funding rounds.
A. Cardano Node Operation
- Evaluate
- Tools to monitor and maintain Cardano nodes
- Maintenance support staff for handling Cardano upgrades on currently operating nodes
B. Enterprise Use Cases
- Review
- Private cloud blockchain use cases that are being experimented with by Fortune 1000 companies
- Release engineering for Cardano nodes
- Research
- Existing platforms to run nodes such as:
- Alchemy
- Azure Blockchain Workbench
- AWS (Blockchain on AWS)
- Block Daemon
- ChainStack
- IBM Blockchain Platform
- Infura
- Kaledio
- QuickNode
II. Working Phase
- Develop
- Integration of the Cardano node into EPC
- Sales materials that feature the Wolfram Cardano EPC
III. Final
- Preview
- Provide a walk-through preview of the Wolfram Cardano EPC
Supplemental Information:
<https://wolfr.am/Cardano-EPC>
Please describe how your proposed solution will address the Challenge that you have submitted it in.
The Fund9 DApps, Products & Integrations has several sections that describe the importance of the challenge and success.
- “Why is it important?”
- “Quality DApps and integrations will increase the utility & adoption of Cardano.”
- “What does success look like?”
- “Novel and viable applications get built on top of Cardano attracting users. Integrations manage to pull in more adoption.”
One of the important aspects of creating and managing a vibrant decentralized ecosystem is ensuring there is a pathway for developers and companies to run their own infrastructure as opposed to solely relying on third-party-managed infrastructure.
While using third-party infrastructure makes sense in many cases, it’s important to have the option to move to on-premises systems or self-managed hardware solutions.
The Wolfram Cardano EPC is a way for companies to build knowledge-based applications that will have access to decentralized tools.
What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?
There are a few new technical things to execute on this project. At present, we already provide Cardano nodes in the Wolfram Public Cloud. However, rewriting the middleware to be compatible with EPC will require new tasks. In addition, we will need to identify the release engineering requirements to ensure that we can work on a schedule that will allow for an upgrade path for the Wolfram Cardano EPC.