Cardano UTXO DB Abstraction
current project status
Current Project Status
in_progress
Total
amount
Received
₳45862
Total
amount
Requested
₳169860
Total
Percentage
Received
27%
₳45862 Received out of ₳169860
Solution
Leveraging a traditional database, abstracting UTXO complexity, reduces the need for full-stack dev to work with the intricacies of UTXO management and datum deserialization.
Problem
Dapps require **front-end** **complex** **integration** with information stored in **datums**. Poor TX management and excessive API consumption can worsen UX and reduce adoption.
Impact alignment
Feasibility
Value for money

This proposal was approved and funded by the Cardano Community via Project F11: Cardano Open: Developers - technical Catalyst funding round.

[SOLUTION] Please describe your proposed solution.

Introduction:

As decentralized applications (DApps) become more prevalent, the necessity for effective information management escalates. Conventional applications typically utilize relational databases, which contain multiple tables with records. These records are interconnected through identifiers, facilitating complex queries encompassing multiple tables. Similar to traditional applications, DApps also need information management to handle the states and transactions of their services.

Conceptual Framework:

In the context of Cardano, information is stored on the blockchain through datums in UTXOs (Unspent Transaction Outputs). The Cardano network utilizes a UTXO Ledger to manage its state, which differs from the Account Ledger used by Bitcoin and Ethereum. The UTXO Ledger comprises a list of inputs, each harboring a balance and a datum, and is intrinsically tied to an address. The datum acts as a repository for the application-specific information.

For our solution, we propose a database that bridges the gap between information on the blockchain and that displayed on the user interface, ensuring seamless synchronization between both sources. The blockchain data will act as the authoritative source, resolving any inconsistencies.

Analogy:

In the proposed database, each datum in a UTXO is analogous to a record in a relational database. This analogy posits that:

  • datum = record

Additionally, each contract in a DApp can be considered equivalent to a datum type, which correlates to a table in our database. This draws another equivalence:

  • contract = datum type = table

This structure allows the decentralized application to maintain a sophisticated state with various tables, each containing multiple records.

Concurrency Management:

The proposed database incorporates features to manage concurrency. As transactions consume UTXOs and generate new ones, the database must monitor UTXOs involved in ongoing transactions. By marking UTXOs that are being utilized for transactions that are either being constructed or awaiting network validation, we minimize the risk of conflict arising from multiple transactions attempting to use the same UTXO.

Query Optimization:

The database will also act as a cache, optimizing resource usage and mitigating redundant API queries, especially when the application server relies on external services like Blockfrost for Cardano network data. This not only enhances performance but also curtails the costs associated with API calls.

Indexing and Synchronization:

The synchronization of the database is vital to ensuring that the data is up-to-date with the blockchain. Various methodologies, including the utilization of webhooks or periodic backend checks, can be employed to ascertain that the database reflects the latest state of the contract addresses. This process, termed network indexing, can be executed using various sources, including Blockfrost, direct node queries, or other Cardano-related data services.

Data Processing:

To streamline the processing, conversion, and storage of network information in the database, a JSON configuration file will be employed. This file will dictate the contract addresses, corresponding database tables, and data structure, thus governing the connection between the records in the tables and the blockchain data.

API Access and Portability:

An integral component of this solution is API access. The database will be accessible from both the frontend and backend through an API. This facilitates not only portability but also scalability, as the data and smart contracts can be accessed from anywhere, not confined to the initial deployment portal. This architecture enables the development of versatile applications with diverse access points.

Drivers of Impact:

  1. Community Contribution and Knowledge Sharing: By developing this solution as an open-source project, it aligns with OSDE's challenge of sharing efforts with the community. Our project will provide documentation, examples, and the source code, enabling other developers to understand, adopt, or contribute to the project. This promotes an environment of collaboration and shared knowledge, which is fundamental to the growth of the Cardano ecosystem.
  2. Improved Efficiency and Resource Optimization: The proposed database will optimize queries made to the Cardano network, which is particularly beneficial for developers with limited resources. By functioning as a cache, the database prevents repetitive API queries, thus minimizing costs and improving performance. This efficiency is likely to attract more developers to build on Cardano.
  3. Enhanced Concurrency Control: Our solution will provide mechanisms to handle the concurrency of transactions effectively. By marking UTXOs that are being used in ongoing transactions, it ensures that the state of the database remains consistent and reliable. This is crucial for the robustness of applications built on Cardano.
  4. Scalability and Accessibility: The database will be accessible through an API, allowing both the front-end and back-end to interact with it. This opens the door for scalability as the data can be accessed from anywhere, not just from the portal where it is deployed. This is crucial for the development of distributed applications on Cardano and promotes interoperability.

Conclusion:

This proposed solution aims to provide a robust, efficient, and scalable database system for decentralized applications on the Cardano blockchain. By bridging the gap between the blockchain data and user interfaces, optimizing queries, and ensuring synchronization, this database presents an innovative and formal solution crucial for the burgeoning DApp ecosystem. Moreover, the API access enhances the portability and versatility of applications built on this platform.

[IMPACT] Please define the positive impact your project will have on the wider Cardano community.

Impact on Cardano Ecosystem:

  1. Increase adoption of Cardano Technology: The database solution we are proposing is designed to streamline and simplify the interaction between decentralized applications and the Cardano blockchain. By providing an efficient and user-friendly way to manage information, our project lowers the barrier to entry for developers who might be new to the Cardano ecosystem. As the usability of building and maintaining DApps on Cardano improves, it’s expected that more developers and enterprises will be enticed to adopt Cardano for their blockchain needs. Furthermore, as our project is open-source, it will continually evolve with contributions from the community, making it an increasingly attractive and robust solution that encourages the wider adoption of Cardano technology.
  2. Enabling More Complex DApps: The ability to effectively manage information on Cardano through our proposed database will enable developers to create more complex and efficient decentralized applications. This is likely to lead to an increase in the number of DApps built on Cardano, bringing more transactions and users to the ecosystem.
  3. Enhanced Learning and Adoption through Documentation: Comprehensive documentation and examples provided as part of the project will act as learning resources for developers. Well-documented projects are easier to understand and adopt, which contributes to the reputation and credibility of the Cardano community.
  4. Quantifying Impact: In the short term, we expect our project to benefit at least a dozen developers who will utilize our database solution for their DApps on Cardano. As the project matures and as more developers contribute to the open-source codebase, we anticipate that within a year or two, it could become a widely adopted standard for information management in DApps on Cardano.

Impact measures:

  1. Adoption Rate: Measure the number of decentralized applications (DApps) on the Cardano blockchain that successfully integrate and utilize the proposed solution. This metric demonstrates the level of adoption and acceptance of the solution within the Cardano ecosystem.
  2. Developer Engagement: Monitor the level of engagement from developers within the Cardano community. This can include factors such as the number of developers contributing to the project, active participation in developer forums, and the creation of related tools or libraries. This metric reflects the interest and involvement of developers in leveraging the solution.
  3. Cost Savings: Evaluate the cost savings achieved by DApp developers and operators through the utilization of the proposed solution. Compare the expenses associated with traditional methods of data management against the reduced costs facilitated by the solution. This metric showcases the economic benefits of adopting the solution.
  4. User Feedback: Gather qualitative feedback from DApp developers and users regarding their experience with the solution. This can be done through surveys, interviews, or community feedback channels. User opinions provide insights into user satisfaction, ease of integration, improved user experiences, and any additional benefits perceived by the users.

In the short term, the innovation of the project can enhance Cardano's productivity by providing DApp developers with a more efficient and streamlined data management solution. It reduces the complexities and overhead associated with managing data on the blockchain, enabling developers to focus more on application logic and development, thus increasing productivity.

In the long term, the project has the potential to drive Cardano's growth in several ways. By offering a robust and user-friendly data management solution, it can attract more developers to build DApps on Cardano. This increased developer activity can result in a broader range of applications being developed, ultimately attracting more users and driving adoption. Moreover, the scalability and efficiency of the solution can position Cardano as a competitive blockchain platform for decentralized applications, further contributing to its long-term growth and recognition.

How will you share the outputs and opportunities that result from your project?

To effectively share the outputs and results of the project, we have planned the following strategies:

  1. GitHub Repository: We will create a dedicated GitHub repository to share all the code, documentation, and resources developed as part of the project. This repository will serve as a centralized hub where developers can access and contribute to the project's outputs.
  2. Documentation and Reports: We will create comprehensive documentation and reports that outline the project's objectives, methodologies, findings, and outcome
  3. Project Catalyst: We will submit regular updates and progress reports to Project Catalyst, sharing the milestones achieved, impact metrics, and future plans.
  4. Community Engagement: We will actively engage with the Cardano community and other blockchain-related communities through online forums, social media platforms, and developer meetups
  5. Collaboration with Partners: We will seek partnerships and collaborations with blockchain companies, organizations, and academic institution

Regarding further research and development activities, we expect the results generated from the project to serve as a foundation for future advancements. The insights gained, lessons learned, and innovations developed during the project will guide our future research endeavors. We will explore opportunities to build upon the project's outcomes, refine the solution, and address any limitations or areas for improvement.

Additionally, the outputs and results of the project will inform and guide our development of additional tools, libraries, or frameworks that can complement the Smart DB: UTxO Abstraction Layer. These research and development activities will contribute to the ongoing evolution and enhancement of the project, ensuring its continued relevance and impact in the blockchain and decentralized application domain.

[CAPABILITY & FEASIBILITY] What is your capability to deliver your project with high levels of trust and accountability? How do you intend to validate if your approach is feasible?

Our capability to deliver the project with high levels of trust and accountability stems from the experience, expertise, and organizational processes we have in place. Here's why we are well-suited to execute this project:

  1. Protofire's Track Record: Protofire has an established reputation for building decentralized infrastructure, protocols, applications, and developer platforms. Its specialized skills in enhancing developer adoption and network usage are crucial for the success of this project.
  2. Skilled Team: Our team includes professionals with diverse backgrounds, including blockchain development, smart contracts, security, data analytics, and project management. This ensures a multidisciplinary approach to problem-solving and guarantees the employment of best practices in execution.
  3. Previous Contributions: Protofire has a history of making meaningful contributions to the blockchain community. This indicates not only technical capabilities but also a commitment to the advancement of decentralized technologies.
  4. Transparent Communication: We will maintain open lines of communication with the community through regular updates and engaging in forums. This transparency is essential for building trust.
  5. Robust Financial Management: We will implement strict financial controls and regular auditing to ensure that funds are used efficiently and for the intended purpose. This includes having a clear budget allocation, milestones-based disbursements, and financial reporting.
  6. Scalable Solutions: Protofire’s experience ensures that the solutions we develop are scalable and able to adapt to the evolving needs of the Cardano ecosystem. This speaks to our capability to deliver not just a project, but a sustainable and evolving solution.
  7. Feedback and Iterative Development: We encourage feedback from the community and users, and employ an iterative development process. This ensures that the project adapts and improves based on real-world input and requirements.

Our accumulated experience, transparency, and commitment to best practices and community engagement make us not only capable but trustworthy stewards of this project.

[Project Milestones] What are the key milestones you need to achieve in order to complete your project successfully?

Milestone 1: Project Setup, Database Design, and Initial Integration

Key Activities:

  • Define project requirements and objectives.
  • Set up the development environment and install necessary tools and frameworks.
  • Design the database schema and identify tables, relationships, and fields.
  • Define the JSON configuration file for contract addresses and data structures.
  • Develop manual synchronization mechanisms to update the database based on contract address utxos
  • Integrate API services like Blockfrost to fetch Cardano network information (basic integration).

Timeline: 4 weeks

Success Criteria: Documentation on project requirements and objectives completed. Development environment set up. Database schema designed. JSON configuration file defined. Initial synchronization mechanisms and API integration established.

Deliverables:

  • Documentation on project requirements and objectives
  • Development environment set up
  • Database schema design
  • JSON configuration file defining contract addresses and data structures
  • Initial synchronization mechanisms and API integration

Intended Outcomes:

  • Clear understanding of project requirements and objectives
  • Development environment ready for further development
  • Well-designed database schema and configuration file
  • Basic synchronization mechanisms and API integration established

Progress Measurement:

  • Completion of project requirements and objectives documentation
  • Successful setup of the development environment
  • Finalized database schema design and JSON configuration file
  • Functional synchronization mechanisms and API integration

>Milestone 2: REST API Development

Key Activities:

  • Design the REST API endpoints for accessing and reading the database.
  • Implement the necessary routes, controllers, and middleware for the REST API.
  • Integrate authentication and authorization mechanisms for secure access.
  • Test and validate the functionality of the REST API.

Timeline: 4 weeks

Success Criteria: REST API endpoints designed and implemented. Authentication and authorization mechanisms integrated. REST API functionality successfully tested and validated.

Deliverables:

  • Designed REST API endpoints for accessing and reading the database
  • Implemented routes, controllers, and middleware for the REST API
  • Integrated authentication and authorization mechanisms
  • Tested and validated functionality of the REST API

Intended Outcomes:

  • Well-defined and functional REST API endpoints for database access
  • Secure authentication and authorization mechanisms in place
  • Successfully tested and validated REST API functionality

Progress Measurement:

  • Completed REST API endpoint design
  • Implemented and functional routes, controllers, and middleware
  • Integration of authentication and authorization mechanisms
  • Successful testing and validation of the REST API functionality

>Milestone 3: Database Integration

Key Activities:

  • Enhance synchronization with automatic mechanisms. Implement logic for tracking contract address changes and triggering database updates.
  • Expand the integration with API services to include new features.
  • Develop a toolkit for database schema creation and TypeScript types/classes generation.

Timeline: 4 weeks

Success Criteria: Enhanced database synchronization mechanisms implemented. Expanded API integration. Toolkit for database schema creation and TypeScript generation created.

Deliverables:

  • Enhanced synchronization wut automatic mechanisms for efficient updates based on contract address changes
  • Expanded integration with API services for new features
  • Developed a toolkit for database schema creation and TypeScript generation

Intended Outcomes:

  • Improved synchronization mechanisms for efficient updates
  • Advanced features integrated with API services
  • Toolkit for database schema creation and TypeScript generation

Progress Measurement:

  • Enhanced synchronization mechanisms implemented
  • Successful integration of advanced features with API services
  • Completed toolkit for database schema creation and TypeScript generation

>Milestone 4: Transaction Processing and Concurrency

Key Activities:

  • Implement transaction creation logic considering the UTxO model and datum handling.
  • Develop mechanisms to handle in-use UTxOs for preventing concurrency issues.
  • Design and implement read-only access to UTxOs for other users.
  • Test and validate transaction processing and concurrency features.

Timeline: 4 weeks

Success Criteria: Transaction creation logic implemented. Concurrency handling mechanisms in place. Read-only access to UTxOs implemented. Transaction processing and concurrency features successfully tested and validated.

Deliverables:

  • Implemented transaction creation logic considering the UTxO model and datum handling
  • Developed mechanisms to handle in-use UTxOs for preventing concurrency issues
  • Designed and implemented read-only access to UTxOs for other users
  • Tested and validated transaction processing and concurrency features

Intended Outcomes:

  • Functional transaction creation logic based on the UTxO model
  • Concurrency handling mechanisms to prevent issues with in-use UTxOs
  • Read-only access implementation for UTxOs by other users
  • Successful testing and validation of transaction processing and concurrency features

Progress Measurement:

  • Completed implementation of transaction creation logic
  • Functional mechanisms for handling concurrency with UTxOs
  • Successfully implemented read-only access to UTxOs
  • Tested and validated transaction processing and concurrency features

>Milestone 5: Query Optimization and Cache Implementation

Key Activities:

  • Implement query optimization techniques, for instance, get only specific fields from the tables.
  • Develop datums\redeemers caching mechanisms in the database for storing frequently accessed data.
  • Test and optimize the performance of query optimization and caching features.

Timeline: 2 weeks

Success Criteria: Query optimization techniques implemented. Caching mechanisms integrated. Query optimization and caching features tested and optimized for improved performance.

Deliverables:

  • Implemented query optimization techniques
  • Developed caching mechanisms in the database for storing frequently accessed data
  • Tested and optimized the performance of query optimization and caching features

Intended Outcomes:

  • Improved query performance through optimization techniques
  • Efficient caching mechanisms for frequently accessed data
  • Optimized query optimization and caching features for improved performance

Progress Measurement:

  • Successful implementation of query optimization techniques
  • Functional caching mechanisms integrated into the database
  • Tested and optimized query optimization and caching features for improved performance

>Milestone 6: Testing, Refinement, Examples, and Documentation

Key Activities:

  • Perform unit testing and integration testing to ensure functionality and reliability.
  • Refine and optimize the codebase, addressing any bugs or performance issues.
  • Create complete examples showcasing smart contracts, frontend, and backend integrations.
  • Generate comprehensive documentation with setup instructions and usage guidelines.

Timeline: 3 weeks

Success Criteria: Testing completed with successful unit and integration tests. The codebase refined and optimized. Examples demonstrating integrations created. Comprehensive documentation prepared.

Deliverables:

  • Unit testing and integration testing to ensure functionality and reliability
  • Refined and optimized codebase, addressing bugs and performance issues
  • Complete examples showcasing smart contract, frontend, and backend integrations
  • Comprehensive documentation with setup instructions and usage guidelines

Intended Outcomes:

  • Reliable and functional codebase through thorough testing
  • Optimized codebase with resolved bugs and improved performance
  • Demonstrative examples of integrations between smart contract, frontend, and backend
  • Comprehensive documentation providing clear setup instructions and usage guidelines

Progress Measurement:

  • Completion of unit testing and integration testing with successful outcomes

  • Refined and optimized codebase based on resolved bugs and improved performance

  • Creation of complete examples showcasing integrations

  • Comprehensive documentation prepared with clear setup instructions and usage guidelines

    [RESOURCES] Who is in the project team and what are their roles?

Protofire Experience

Protofire stands at the forefront of the Web3 revolution, offering a comprehensive range of services to empower and catalyze the growth of decentralized technologies. With our deep-rooted expertise and vast experience, we have established ourselves as a trusted partner for clients seeking to harness the full potential of blockchain and Web3 applications. From smart contract development and decentralized app creation to developer tools, integrations, DevOps, wallets, and TVL solutions, our team of blockchain mavericks has collaborated with prominent projects and platforms, such as Gnosis Safe Wallet, Chainlink, The Graph, Filecoin, MakerDAO, Fuse, CowSwap, and many others. We are committed to bringing your visionary ideas to life, combining technical prowess with effective project management to drive the success of your Web3 endeavors

Diego Torres Project Management

<https://www.linkedin.com/in/diego-torres-borda-94b70912/>

In 2018, I stumbled upon Bitcoin's White Paper, and it was love at first sight. Since then, I've immersed myself in the world of blockchain and studied numerous other protocols, from Ethereum to third-generation blockchains. To me, a decentralized protocol is more than just a buzzword - it's a community-driven decision-making organization with open and public records, enforced by consensus protocols that ensure permissionless access and censorship resistance.

Web3 Experience

  • Protofire FCTO: Business Development. Education. Team Leadership.
  • The Graph: Indexing Operation Leadership. Subgraph development. Hosted services to third parties.
  • Polkadot Ecosystem: Contract Wizard & Multisg development. Infrastructure as a service to Parachains.
  • Cardano Ecosystem: RastDAO Founder, Core team at Mayz & Cardano Ambassador.

Manuel Padilla Lead Software Engineer & Blockchain Specialist

<https://www.linkedin.com/in/manuel-ale-padilla/>

Manuel Padilla is a versatile and highly motivated software engineer with a Bachelor's degree in Technology from the National Technological University. Having a plethora of programming languages under their belt, including but not limited to SQL, Basic, C, C++, VB, .NET, Java, JavaScript, TypeScript, Python, and Haskell, Manuel Padilla brings over 13 years of experience in web development and software engineering.

Web3 Experience:

  • Protofire (April 2023 - Present): Currently working as a Software Engineer, focusing on blockchain technologies including Cardano, Plutus, DeFi, and DApps.
  • MAYZ Protocol (October 2022 - Present): Involved in full-stack blockchain development, specializing in Cardano, Plutus, and Haskell.
  • RATS DAO (January 2022 - Present): Serving as a Web Developer, DApp Developer, and Blockchain Developer, primarily focusing on Cardano, Plutus, and Haskell.

dApps:

GitHub: https://github.com/manupadillaph/

Camila Mancusi QA Engineer

<https://www.linkedin.com/in/camilamancusi/>

Camila wants to participate improving the user experience and usability in the web3 applications to make this world more friendly and accesible to everyone. She wants to be involved in making possible that using web3 functionalities is as simple and usual as those focused on web2

Web3 Experience:

  • Protofire: QA & Project Management
  • SimpleState: Design test cases. Participate in the definition of features. Design scenarios and test cases.Report errors, propose solutions and validate the correction. Ensuring that the product is ready for the customer
  • UNICEF: Design test cases. Participate in the definition of features. Creates test executions. Reports bugs / issues. Monitor bug priorities.

Luis Lopez Full Stack Developer

<https://www.linkedin.com/in/luigibyte/>

Luis likes the entire Blockchain ecosystem, and He is currently creating a minting Dapp for BadgerDAO. Expert knowledge in NodeJS, Web3JS, SM, Solidity. Has experience with Smart Contracts. Polkadot, Polygon, Chainlink, Lens

Web3 Experience:

  • Protofire: Full Stack Developer
  • BadgerDAO:
  • MakerDAO: Subgraph development
  • Messari: Built subgraph for harvest-finance yield-farming protocol Messari

Braian Leiva DevOps

<https://www.linkedin.com/in/braian-leiva/>

Fan of blockchain and decentralized system. Infrastructure automation lover.

Experience:

  • 15+ years of experience using Linux (Debian, Centos, Arch Linux, Red Hat, OpenSUSE, Fedora, Ubuntu, etc).

  • 7+ years designing, maintaining and improving all size of application Infrastructure as System Engineer and now as Cloud Engineer.

  • 4+ years using AWS. I'm Amazon Solutions Architect working on infrastructure automation using tools like Terraform, Cloudformation, Sam, Serverless, Fargate, CodePipeline, Docker, Python.

  • Currently working as DevOps/Cloud Engineer

  • Also studying and learning Data Science and Machine Learning. He've got AWS Certified Machine Learning - Specialty (MLS)

    [BUDGET & COSTS] Please provide a cost breakdown of the proposed work and resources.

Roles within the team:

  • Project Manager (67 ADA/h): Responsible for coordinating the project, setting objectives, and managing resources.
  • Technical Architect (80 ADA/h): Designs the development environment, defines project requirements, and oversees the database design.
  • Full Stack / Cardano Developer (93 ADA/h): Designs and implements the database schema and synchronization mechanisms. Designs and implements the REST API service. Responsible for frontend and backend integrations in the examples.
  • QA Engineer (67 ADA/h): Prepare and execute Unit and property Testing. Responsible for testing and validating the transaction processing and concurrency features.
  • Documentation Specialist (67 ADA/h): Creates documentation on project requirements, objectives, and database design.

Budget by milestone

Milestone 1: Project Setup, Database Design, and Initial Integration

  • Project Manager: 45h * 67 ADA = 3,000 ADA
  • Technical Architect: 120h * 80 ADA = 9,600 ADA
  • Full Stack / Cardano Developer: 120h * 93 ADA = 11,160 ADA

Total: 23.760 ADA

Milestone 2: REST API Development

  • Project Manager: 30h * 67 ADA = 2,000 ADA
  • Technical Architect: 90h * 80 ADA = 7,200 ADA
  • Full Stack / Cardano Developer: 180h * 93 ADA = 16,740 ADA
  • QA Engineer: 45h * 67 ADA = 3,000 ADA

Total: 28.940 ADA

Milestone 3: Advanced Database Integration and Toolkit Development

  • Project Manager: 30h * 67 ADA = 2,000 ADA
  • Technical Architect: 60h * 80 ADA = 4,800 ADA
  • Full Stack / Cardano Developer: 180h * 93 ADA = 16,740 ADA
  • QA Engineer: 45h * 67 ADA = 3,000 ADA

Total: 26.540 ADA

Milestone 4: Transaction Processing and Concurrency

  • Project Manager: 30h * 67 ADA = 2,000 ADA
  • Technical Architect: 60h * 80 ADA = 4,800 ADA
  • Full Stack / Cardano Developer: 180h * 93 ADA = 16,740 ADA
  • QA Engineer: 45h * 67 ADA = 3,000 ADA

Total: 26.540 ADA

Milestone 5: Query Optimization and Cache Implementation

  • Project Manager: 30h * 67 ADA = 2,000 ADA
  • Technical Architect: 60h * 80 ADA = 4,800 ADA
  • Full Stack / Cardano Developer: 180h * 93 ADA = 16,740 ADA
  • QA Engineer: 45h * 67 ADA = 3,000 ADA

Total: 26.540 ADA

Milestone 6: Testing, Refinement, Examples, and Documentation

  • Project Manager: 30h * 67 ADA = 2,000 ADA
  • Technical Architect: 60h * 80 ADA = 4,800 ADA
  • Full Stack / Cardano Developer: 180h * 93 ADA = 16,740 ADA
  • QA Engineer: 90h * 67 ADA = 6,000 ADA

Total: 29.540

Additional roles for all milestones:

  • Document Specialist: 120h * 67 ADA = 8,000 ADA

TOTAL: 169.860 ADA

[VALUE FOR MONEY] How does the cost of the project represent value for money for the Cardano ecosystem?

We, at Protofire, are thrilled to submit our proposal for the Catalyst Grant Program, highlighting our strong determination to enter in Cardano ecosystem as +80 Engineer Company.

In this proposal, we will outline our approach, emphasizing the importance of quality, adherence to timelines and milestone-based projects, and our proven track record in diverse markets.

While profitability is undoubtedly a critical aspect of any project, we understand that onboarding Cardano requires a long-term vision that extends beyond immediate financial gains. We understand that investing in this new technology may initially result in costs that surpass our break-even point.

However, we firmly believe that by strategically positioning ourselves within this ecosystem, we will eventually become a main character that can drive and produce great value for everyone.

So, for Cardano, this proposal represents a world-class team working on an open-source tool for half the cost. It's a good deal!

The cost of the project represents value for money for the Cardano ecosystem in several ways:

  1. Innovation and Scalability: The project focuses on enhancing the capabilities of smart contract interactions with the Cardano blockchain. By offering efficient and scalable solutions, the project can foster innovation, making it attractive for developers and enterprises to build on the Cardano network.
  2. Improved Transaction Processing: Handling transactions with high efficiency and minimizing concurrency issues directly contribute to an improved user experience. This can help in attracting more users and transactions to the Cardano network, which in turn may increase the demand for ADA and contribute to network security.
  3. Knowledge Sharing and Documentation: With comprehensive documentation and examples, the project acts as a knowledge base for developers who want to integrate with the Cardano blockchain. This education can accelerate the adoption of Cardano technology and attract more talent to the ecosystem.
  4. Optimized Performance: Query optimization and caching features contribute to the robustness and performance of the applications built on Cardano. This can translate to cost savings for developers and businesses in terms of reduced operational costs.
  5. Facilitating Integrations: By providing a secure and efficient REST API, the project can become a catalyst for integrations with various applications and services, driving more traffic and usage to the Cardano network.

Community Reviews (1)

Comments

Monthly Reports

close

Playlist

  • EP2: epoch_length

    Authored by: Darlington Kofa

    3m 24s
    Darlington Kofa
  • EP1: 'd' parameter

    Authored by: Darlington Kofa

    4m 3s
    Darlington Kofa
  • EP3: key_deposit

    Authored by: Darlington Kofa

    3m 48s
    Darlington Kofa
  • EP4: epoch_no

    Authored by: Darlington Kofa

    2m 16s
    Darlington Kofa
  • EP5: max_block_size

    Authored by: Darlington Kofa

    3m 14s
    Darlington Kofa
  • EP6: pool_deposit

    Authored by: Darlington Kofa

    3m 19s
    Darlington Kofa
  • EP7: max_tx_size

    Authored by: Darlington Kofa

    4m 59s
    Darlington Kofa
0:00
/
~0:00