Babel Fees and Sponsored Transactions: NOW!

not approved

Babel Fees and Sponsored Transactions: NOW!

₳333,446.00 _Requested

View on ideascale

Community Review Results (1 reviewers)

Feasibility

Value for money

Impact / Alignment

Solution

Game Changer Wallet will provide a service that allows any DApp or user in the wallet to have their transaction fees covered by someone else in exchange for native tokens or even for free.

Problem:

Image file

It is not possible for your transaction fees to be paid by someone else, or by yourself using native tokens in Cardano.

Yes Votes:

₳ 57,008,374

No Votes:

₳ 149,128,224

Votes Cast:

393

Team

[IMPACT] Please describe your proposed solution.

Introduction

Across the growing industry, there’s an increasing demand for more user-friendly DApps that make Web3 more accessible. One way of achieving this is by giving every native asset the ability to be used as a way to pay for transaction fees.

Native assets on Cardano are wildly popular. More than 8.5M of them have been minted since the ‘Mary’ hardfork in February 2021. But they still lack one of the most important use cases for adoption in the whole cryptocurrency space, since every time a user wants to interact with the blockchain, he/she has to pay for transaction fees and, at the moment, that can only be done using ADA.

Solution:

Imagine transacting on Cardano paying fees using $DJED, $GIMBAL, $ALDEA tokens or even Disco Solaris NFTs…

We will onboard, and let dapps onboard users by letting them pay for transaction fees in custom currencies (native assets).We will achieve this by allowing someone else to supply missing/required ADA in transactions in exchange of native assets. A practical implementation of a "Babel Fees Service", similar to Cardano's Babel Fees research, but on a single transaction and without waiting for protocol changes and community widespread adoption to make it work.

As a byproduct of this solution, with some extra love, we will offer to the ecosystem the building blocks to implement their own solutions around this stack, and we will even offer an Airdrop Service as an open source example on how to build with this. This second solution addresses what we call “Sponsored Transactions”, this are transactions where the transaction fee is “sponsored” or payed by someone else (instead of the user interacting with the wallet or DApp).

What benefit does this bring to DApp users?

Sponsored Transactions are beneficial since they simplify user transactions on the Cardano network. Users can send payments to each other or interact with smart contracts quickly and easily without having to worry about transaction fees or having an UTxO with ADA in every wallet they own. This simplifies the process of using the Cardano network, which may assist promote adoption, as this innovative solution makes blockchains easier to use. Another case where we might see a benefit is to prevent assets from getting “stuck” because a wallet does not have the blockchain’s coin (or enough of that coin).

What benefits does it bring to developers?

The introduction of Sponsored Transactions on Cardano will offer a significant boost to the versatility of the blockchain. With this newly implemented technology, Cardano becomes much more fluid and flexible by increasing the efficiency of transactions and interactions on the network.

Use Cases

Sponsored Transactions allow users to make transactions without having to pay transaction fees, making them an attractive option for a number of use cases, such as:

Decentralized Finance (DeFi): These types of applications often require a large number of transactions to be conducted, many of which can be small and infrequent. The elimination of transaction fees in ADA can help to reduce the overall cost of conducting these transactions and make DeFi applications more accessible to a wider range of users.
Gaming and NFTs: These industries often rely on a large number of transactions to facilitate the exchange of virtual assets and currency. The elimination of transaction fees in ADA can help to make these transactions more efficient and cost-effective, making it easier for users to engage in these types of activities.
Microtransactions: Microtransactions, or small transactions conducted for a low value, are another use case for Sponsored Transactions. The elimination of transaction fees in ADA through Sponsored Transactions can help to make these types of transactions more accessible and cost-effective, encouraging greater use of the blockchain for microtransactions.

Overview of Proposed Solution

A proper wallet dapp connector design of multi-purpose building blocks plus an external dedicated service that leverages on them will allow us to provide sponsored transactions on Cardano L1, not only to wallet end users but also to DApp transactions, out of the box, while also offering these developer features to other builders as well.

Building blocks, available and missing:

A feature rich DSL based DApp connector (GCScript scripting language) and wallet design model adequate for Cardano that not only signs and submits but also takes care of transaction building and UTXO management as opposed to delegating these responsibilities to DApps (already developed by Game Changer Team)
Native wallet multisignature capabilities, prepared to handle different multisignature strategies and scenarios (already developed by Game Changer Team)
DApp Connector HTTPS multisignature strategy plugin to require foreign services to provide missing transaction witnesses on a transaction signing flow (proposed in this project)
DApp Connector UTxO auxiliar functions or plugins to handle foreign inputs (proposed in this project)
HTTPS service to provide transaction validation and respond with signatures, a to list of available UTxOs and exchange rate quotation (proposed in this project)

Frequently asked questions:

"Don't lie!, you cannot provide babel fees and sponsored transactions to any dapp without integrating efforts from their side!"

Oh yes, we can. GameChanger Wallet Dapp connector is designed in such a way it makes flexible what's is written in stone in Cardano ecosystem, it can work with pre-built transactions from dapps for just signing them like most CIP-30 wallets but also it builds transactions and this design principle let us care for

users privacy (our dapps can know nothing about their users and still work)
eUTXO management done properly
allow users have final word on what dapps are requiring wallets to do
taking dynamic decisions over dapp intentions based on user input

So, to check for balance and trigger an instant solution it's posible.

"How to use if it's provided on GameChanger Dapp Connector which is not CIP30?"

It's not because we speak "lenguajes diferentes" that we cannot connect together. GameChanger Wallet has a different Dapp Connector because it offers a

unique,
platform/device independent,
privacy preserving,
wallet agnostic
open, auditable,clonable, reusable JSON DSL scripting language,
easy to integrate everywhere

technology that was first conceived back in 2021 from scratch specially for Cardano without being inspired in any other blockchain. It's URL and JSON based, we have from PDFs to even hardware dapps already talking to the wallet. With GC you can turn everything into a dapp, from websites to social media, chats, emails, QR codes, hardware, PDFs, games, almost everything.

If this is not enough for you, and you want to stick to CIP30 and current technologies, several interoperability features are being worked on right now by the team, starting with having half of Ledger wallet integration complete (Catalyst funded project) and including plans related to CIP30 before 2024.

Demo:

To prove our point, these are two simple links, two simple buttons, and yet because also both of them are DApp connections, you haven't realise until now that this document is also a DApp.

GameChanger Wallet team has developed a *voting dapp demo *exclusively for Catalyst in less than 12hs and these are two action buttons of the DApp inserted here for you to try on preproduction testnet (*wallet beta version, links may get deprecated in time).

(link to dapp here)

Have you tried it yet?

This multi-transaction operations could have been automatically suggested to you to be payed with a Native Asset on you wallet if you had not enough coin to pay with*. Automatically, meaning it could be possible for DApp builders to build once and forget about this insufficient balance issues on users, and let the wallet deal with it "automagically"*

Solution Deliverables:

GCScript HTTPS (or other protocol) multisignature strategy plugin to require foreign services to provide missing transaction witnesses on a transaction signing flow. Extra efforts on adapting current wallet UI, UX, internals and DSL specification. Documentation. General purpose wallet feature available for everyone.
GCScript UTxO auxiliary functions or plugins to handle foreign inputs and modify transaction definitions. Extra efforts on adapting current wallet UI, UX, internals and DSL specification. Documentation. Some general purpose wallet features available for everyone and probably some other internal private ones.
Open source Airdrop Service boilerplate of a "Sponsored Transactions" HTTP service to provide transaction validation and respond with signing witnesses and available UTxOs for Airdrops. Documentation.
Closed source "Babel Fees" service to provide transaction validation and respond with signing witnesses, to list and or book for available UTXOs.
Wallet built-in GCScript examples on how to enable this feature for developers. Explanatory media content. Documentation.
Working instance of "Babel Fees" service to use on mainnet. (Native Assets issuers interested in being listed can contact us)

[IMPACT] How does your proposed solution address the challenge and what benefits will this bring to the Cardano ecosystem?

Having the ability to pay for transaction fees using our preferred tokens is a hot topic, at the moment, in the Ethereum community. Changes recently introduced by Account Abstraction (ERC4337) are enabling this and many other interesting use cases for their users.

In Cardano, the concept of Babel Fees has been introduced a few years ago but we still don’t have the opportunity to take advantage of this feature yet and upon arrival a great deal of protocol breaking changes and community implementation efforts will be required in order to finally use it on our every day transactions.

This is why we want to develop this idea and directly address the Developer & Infrastructure Challenge, as the solution we will deliver will help the entire DApp ecosystem to thrive.

We will focus in these two main ideas mentioned in the Challenge description:

Creation and improvement of tools and software that help make it easier for projects to develop on Cardano: by providing any token issuer with the ability of using their token to pay for transaction fees, we are creating a novel use case for every project in Cardano that wants to remove friction at the time of onboarding users to their platform or DApp.
Research, analysis and creation of standards, resources or documentation that bring novel innovation to the ecosystem: or help with improving the education around what is available in the ecosystem for development or running infrastructure.

Impact for Cardano

Mitigates the UX issues that minimum ADA per UTxO protocol enforcement causes on Cardano users and that other widely adopted blockchains don't have. Users will be able to do anything on Cardano with their preferred native assets, being in wallet operations or with any DApp interaction without requiring anything special on DApp side.
Volatility effect mitigation. Imagine transacting in DJED instead of ADA while still using ADA underneath. We, as a community, should pay more attention to how much users in developing countries are struggling with this minimum ADA per UTxO value and price volatility. We must act now and prepare for the next bull market or we are going to lose a lot of users and transaction fees again.
User onboarding at zero cost for the end user. Transaction witnessing rules may grant fully sponsored transactions to users validating certain conditions such as interacting with whitelisted DAPPs, StakePools, DReps,etc..
Remote witnessing for developers will allow use cases such as highly decentralized mint events. Imagine thousands of users buying NFTs with the same policy ID at the same time but minting these assets on their own individual wallets in parallel leveraging on the HTTPS multisig plugin and the open source service boilerplate. No more bottlenecks on centralized NFT drops. Let’s use the concurrent capabilities of the eUTXO model of Cardano to decentralize and scale for real.
Lots of other use cases derived in the approach: common building blocks for us to implement the project but to remain public and available for builders to create upon.

[IMPACT] How do you intend to measure the success of your project?

We will use the following metrics to measure the success of our project:

Number of projects (native tokens) using Game Changer Sponsored Transactions: we will use on-chain data to track the number of different projects using our service.
Number of confirmed Sponsored Transactions: we will use on-chain data to track the number of confirmed Sponsored Transactions sent to Cardano’s network.
Amount of ADA in transaction fees covered by the projects: we will use on-chain data to track the amount of ADA in transaction fees sponsored by the projects.
Number of liquidity providers: we will track the number of users sponsoring transactions for other users

[IMPACT] Please describe your plans to share the outputs and results of your project?

As done before on previous Catalyst funded projects, GameChanger Wallet team always delivers monthly reports non-stop, explaining the achieved milestones one by one plus adding screen captures, videos, demos, or if posible the entire code of the project if applies.

In this we will share:

Airdrop Server source code
Example GCScript source code to interact with Airdrop Server
Example GCScript source code to interact with "Babel Fees Server"

In this case we may share:

screen captures of working demos, new documentation, file artifacts, or code advancements
videos of working demos and other relevant knowledge
Executable Dapp Connector links, allowing to test new features on wallet DSL/API
Links to Dapp Connector/DSL JSON schema
Links to Dapp Connector/DSL Documentation
Links to Dandelion API endpoints
Social/Community related feedback, news, events, articles, etc.
In-wallet code examples like we always provide to test right away on Playground IDE, our built-in code editor.

[CAPABILITY/ FEASIBILITY] What is your capability to deliver your project with high levels of trust and accountability?

You may be new to Cardano or may have lost some track of our project history, so here I will summarize relevant facts that you can check on your own to evaluate this project capability to deliver.

GameChanger Wallet has been online in Cardano since 2021 Q2 using personal funds and receiving support from the community and from Dandelion API infrastructure, whom are today our closest partners.
We are hosting 2 versions online:
Legacy : our V1 for Mainnet and Pre-Production since 2021
Future: our cutting edge V2 on beta stage released in 2023 Q1
We are long term builders on Cardano community, Gimbalabs, ALDEA DAO, members and community colaborators. Ex Emurgo, current Cardano Foundation staff, experienced developers, sys admins, hardware designers. Some of us like myself, Adriano, I quit everything else back in 2021 to dedicate full time into Cardano with this wallet and the ecosystem surrounding it because I believe with passion and conviction in what this project and Cardano can offer to the community.
We have been trying to dedicate weekly to teach and assist students and builders for free on English and Spanish live coding sessions and other initiatives not because we have free time, but because this wallet has been designed to onboard students and builders into Cardano, lowering learning and infrastructure barriers for everyone and also because with it we are designing the ultimate toolkit for Cardano builders and students, and we care for feedback during beta stage to improve our product for the people.
We have been participating on Catalyst since Fund6, and continue to exist and to work even when we had funding gaps or lack of active Catalyst campaigns as seen recently.
We have been funded in Fund 7 with projects, some of them has been finished already. One of them had to grow much more in complexity and nevertheless we finished it even while completely out of budget.
We are actively presenting rich monthly reports of our pending projects with proofs of milestones. We are a small team, we can get delayed because building in a novel and evolving ecosystem such as Cardano is not easy task, but we always deliver what we promess.

In addition to all this, our Project Lead has demonstrated in the past that can be trusted and that is capable of managing funds properly, as he has successfully delivered 3 proposals from Fund5 and Fund7:

Fund5 / Project ID 500003: ALDEA Catalyst
Fund5 / Project ID 500004: ALDEA WIKI
Fund7 / Project ID 700019: ALDEA NFT - Community Marketplace

We count with Full Stack Engineers and Plutus Devs, something very important to note because:

Our backend works with Javascript and TypeScript
Any smart contract development will be carried out using Plutus
Our frontend will be built using React and integrated with the blockchain using cardano-serialization-lib library

We have demonstrated experience in all these technologies (please check personal websites and portfolio in the "Project Team" section).

[CAPABILITY/ FEASIBILITY] What are the main goals for the project and how will you validate if your approach is feasible?

The main goals of the project are:

Enable users to pay for transaction fees in native assets (custom currencies) on the Cardano blockchain.
Improve user experience on Cardano by removing the need for users to hold ADA specifically for transaction fees.
Increase the adoption of Cardano by making it more user-friendly and accessible, specially for non ADA holders.
Provide developers with tools and features to integrate Sponsored Transactions into their DApps
Support various use cases such as DeFi, gaming, NFTs, and microtransactions.

To validate the feasibility of the approach, several steps can be taken:

Research and Design Phase: Dedicate time and efforts to research use cases, edge cases, dependencies,limitations and security implications to end up with a solid design plan or alternative plans to solve any posible obstacles.
Technical Proof of Concept: Develop a working prototype that demonstrates the implementation of Sponsored Transactions using the proposed solution. This proof of concept should showcase the ability to construct transactions, handle native assets, and pay for transaction fees with them.
Integration Testing: Integrate the Sponsored Transactions solution with existing DApps or create sample DApps to test its functionality and performance. This testing should validate that the solution works seamlessly with different use cases and that developers can easily integrate it into their applications.
User Testing and Feedback: Engage users, both experienced and new to Cardano, to test the Sponsored Transactions feature. Gather feedback on the user experience, identify any usability issues, and make necessary improvements based on user input.
Performance and Scalability Testing: Evaluate the performance and scalability of the Sponsored Transactions solution by simulating a high volume of transactions and measuring the system's response time, throughput, and resource utilization. This testing will help ensure that the solution can handle real-world transaction loads.
Community Review: Share the proposed solution, some implementation details, and the results of the validation process with the Cardano community. Seek feedback, suggestions, and input from community members and experts to validate the approach and gather further insights for improvement.

By conducting these validation steps, the project can assess the feasibility and effectiveness of the solution, address any issues or limitations, and make necessary adjustments to ensure its successful implementation on the Cardano blockchain.

[CAPABILITY/ FEASIBILITY] Please provide a detailed breakdown of your project’s milestones and each of the main tasks or activities to reach the milestone plus the expected timeline for the delivery.

In order to fully complete this solution some activities will be worked on to a certain degree in parallel to benefit from continuous frontend and backend product relationship feedback.

Milestone 1: Wallet Side Research and Design Phase

Activities:
use cases
dependencies
limitations
performance
security
new GCScript features/plugins schema design
new Wallet features/plugins UI
run tests
proof of concept
Timeline: 1 month
Acceptance criteria: gain all major required technical decisions to move forward

Milestone 2: Airdrop Server - Research and Design Phase

Activities:
Multisig provider feature
Transaction validation feature
use cases
storage/services
dependencies
limitations
performance
security
API
run tests
proof of concept
Timeline: 0.5 month
Acceptance criteria: gain all major required technical decisions to move forward

Milestone 3: "Babel Fees" Server - Research and Design Phase

Activities:
UTxO Manager feature
Exchange Rate Quotation feature
Oracles / Price APIs
use cases
storage/services
dependencies
limitations
performance
security
API
run tests
proof of concept
Timeline: 1 month
Acceptance criteria: gain all major required technical decisions to move forward

Milestone 4: Wallet Side Updates

Activities:
Update DApp Connector API/DSL functions, UI, schema and documentation for
HTTP Multisig Strategy plugin
UTxO Management plugins or options
Coin Selection modifiers
Change Optimizers modifiers
Transaction Builder Options
Posible new DSL syntax requirements
dependencies and new consumed APIs
performance and security improvements
new Wallet required views and user interfaces
run tests
Add GCScript examples
Timeline: 2 month
Acceptance criteria: wallet features implementing almost all new plugins, features and updates (full support requires server deployments)

Milestone 5: Airdrop Server - Development

Activities:
Multisig provider feature
Transaction validation feature
API endpoints, resolvers, documentation
dependencies and new consumed APIs
security
deployment setup and documentation
run tests
Timeline: 1 month
Acceptance criteria: successfull development of the product

Milestone 6: "Babel Fees" Server - Development

Activities:
UTxO Manager feature
Exchange Rate Quotation feature
Oracles / Price APIs
dependencies and new consumed APIs
security
API endpoints, resolvers, documentation
deployment setup and documentation
run tests
Timeline: 2 month
Acceptance criteria: successful development of the product

Milestone 7: Airdrop Server - Wallet Integration and Deployment

Activities:
Setup wallets and deploy Server
Update and deploy new Wallet version integrating the service
Timeline: 1 month
Acceptance criteria: operational service provided to the community

Milestone 8: "Babel Fees" Server - Wallet Integration and Deployment

Activities:
Setup wallets and deploy Server
Update and deploy new Wallet version integrating the service
Timeline: 0.5 month
Acceptance criteria: operational service provided to the community

Note: The above timeline is an estimate and can vary depending on the complexity of the implementation, the availability of resources, and unforeseen challenges that may arise during the project. It is important to regularly review and adjust the timeline as needed to ensure the successful completion of each milestone.

[CAPABILITY/ FEASIBILITY] Please describe the deliverables, outputs and intended outcomes of each milestone.

Milestone 1: Wallet Side Research and Design Phase

Deliverables:

Figma file with features/plugins UI design
Demo video with proof of concept implementation

Outputs:

A comprehensive understanding of the requirements and technical decisions needed for the wallet side development.
Use cases, limitations, and performance considerations to guide the development process.
Security recommendations and design considerations.
GCScript features/plugins schema design and wallet features/plugins UI design for further implementation.
Proof of concept to validate the feasibility of the proposed approach.

Intended Outcome:

All major technical decisions are made, providing a clear direction for the wallet development phase.

Milestone 2: Airdrop Server - Research and Design Phase

Deliverables:

Test plans document
Demo video with proof of concept implementation

Outputs:

Detailed specifications for the multisig provider and transaction validation features.
Use cases, limitations, and performance considerations specific to the airdrop server.
Design of storage/services components.
Dependencies analysis and identification.
Security recommendations and design considerations.
API design and documentation for integration with the wallet.
Proof of concept implementation to validate the proposed approach.

Intended Outcome:

All major technical decisions are made, providing a clear direction for the airdrop server development phase.

Milestone 3: "Babel Fees" Server - Research and Design Phase

Deliverables:

Functional specification document for UTxO Manager
Functional specification document for Exchange Rate Quotation feature
API Insomnia file for endpoints
Demo video with proof of concept implementation

Outputs:

Detailed specifications for the UTxO Manager and Exchange Rate Quotation features.
Integration plan for Oracles/Price APIs.
Use cases, limitations, and performance considerations specific to the "Babel Fees" server.
Design of storage/services components.
Dependencies analysis and identification.
Security recommendations and design considerations.
API design and documentation for integration with the wallet.
Proof of concept implementation to validate the proposed approach.

Intended Outcome:

All major technical decisions are made, providing a clear direction for the "Babel Fees" server development phase.

Milestone 4: Wallet Side Updates

Deliverables:

Demo video with updated DApp Connector API/DSL functions
Demo video of working HTTP Multisig plugin
Demo video of working UTxO Management plugins
Demo video of coin selection modifiers update
Demo video of new wallet required views and user interfaces
GCScript examples

Outputs:

Updated DApp Connector API/DSL functions, UI, schema, and documentation to support new features and plugins.
Implementation updates for HTTP Multisig Strategy, UTxO Management, Coin Selection modifiers, Change Optimizers modifiers, and Transaction Builder Options.
Documented requirements for possible new DSL syntax.
Dependencies and consumed APIs for the updated wallet.
Report on performance and security improvements.
New wallet views and user interfaces to support the updated features.
Test plans and documentation for the updated wallet.
GCScript examples to demonstrate the usage of new features and plugins.

Intended Outcome:

The wallet is updated to implement almost all new plugins, features, and updates, with full support requiring server deployments.

Milestone 5: Airdrop Server - Development

Deliverables:

GitHub repo with Airdrop Server source code
Example GCScript source code to interact with Airdrop Server
Test coverage report
Documentation for setup

Outputs:

Implemented multisig provider feature.
Implemented transaction validation feature.
API endpoints, resolvers, and documentation for the airdrop server.
Dependencies and consumed APIs for the server.
Security enhancements to ensure the server's robustness.
Deployment setup and documentation for the server.
Test plans and documentation for the developed server.

Intended Outcome:

Successful development of the airdrop server.

Milestone 6: "Babel Fees" Server - Development

Deliverables:

Example GCScript source code to interact with "Babel Fees Server"
Test coverage report
Documentation on use cases and usability

Outputs:

Implemented UTxO Manager feature.
Implemented Exchange Rate Quotation feature.
Integration with Oracles/Price APIs.
Dependencies and consumed APIs for the server.
Security enhancements to ensure the server's robustness.
API endpoints, resolvers, and documentation for the "Babel Fees" server.
Deployment setup and documentation for the server.
Test plans and documentation for the developed server.

Intended Outcome:

Successful development of the "Babel Fees" server.

Milestone 7: Airdrop Server - Wallet Integration and Deployment

Deliverables:

Updated and deployed new wallet release integrating the service

Outputs:

Wallets are set up to communicate with the airdrop server.
The new version of the wallet is deployed, integrating the airdrop server's functionality.

Intended Outcome:

Operational service provided to the community, allowing users to interact with the airdrop server through the wallet.

Milestone 8: "Babel Fees" Server - Wallet Integration and Deployment

Deliverables:

Updated and deployed new wallet release integrating the service

Outputs:

Wallets are set up to communicate with the "Babel Fees" server.
The new version of the wallet is deployed, integrating the "Babel Fees" server's functionality.

Intended Outcome:

Operational service provided to the community, allowing users to interact with the "Babel Fees" server through the wallet.

Note: The deliverables, outputs, and intended outcomes are based on the provided milestones and can be adjusted or expanded based on specific project requirements and objectives.

[RESOURCES & VALUE FOR MONEY] Please provide a detailed budget breakdown of the proposed work and resources.

Milestone 1: Wallet Side Research and Design Phase

Team Cost: USD 10,000

Duration: 1 month

Milestone Cost: Team Cost = USD 10,000

Milestone 2: Airdrop Server - Research and Design Phase

Team Cost: USD 5,000

Development Tools and Infrastructure:

Software development tools & subscriptions (IDEs, version control, project management tools): USD 1,000
Cloud infrastructure for development, testing, and deployment: USD 2,000

External Services:

Documentation and technical writing services: USD 5,000

Duration: 0.5 month

Milestone Cost: Team Cost + Development Tools and Infrastructure + External Services = USD 13,000

Milestone 3: "Babel Fees" Server - Research and Design Phase

Team Cost: USD 10,000

Duration: 1 month

Milestone Cost: Team Cost = USD 10,000

Milestone 4: Wallet Side Updates

Team Cost: USD 20,000

Duration: 2 months

Milestone Cost: Team Cost = USD 20,000

Milestone 5: Airdrop Server - Development

Team Cost: USD 10,000

Duration: 1 month

Milestone Cost: Team Cost = USD 10,000

Milestone 6: "Babel Fees" Server - Development

Team Cost: USD 20,000

Duration: 2 months

Milestone Cost: Team Cost = USD 20,000

Milestone 7: Airdrop Server - Wallet Integration and Deployment

Team Cost: USD 5,000

Duration: 0.5 month

Milestone Cost: Team Cost = USD 5,000

Milestone 8: "Babel Fees" Server - Wallet Integration and Deployment

Team Cost = USD 10,000

Duration: 1 month

Milestone Cost = Team Cost = USD 10,000

Team Cost Calculation:

Two developers working full time for the entire duration of the milestone.
Salary per developer per month: USD 5,000

Total Project Budget: Milestone 1 + Milestone 2 + Milestone 3 + Milestone 4 + Milestone 5 + Milestone 6 + Milestone 7 + Milestone 8 =USD 10,000 + USD 13,000 + USD 10,000 + USD 20,000 + USD 10,000 + USD 20,000 + USD 5,000 + USD 10,000 = USD 98,000 | ADA = 0.2939 | 333,446 ADA

[RESOURCES & VALUE FOR MONEY] Who is in the project team and what are their roles?

The project team for the proposed work on building Sponsored Transactions in Cardano consists of Matias Falcone and Adriano Fiorenza. Matias will take care of project management and backend development and Adriano will undertake various aspects of the integration with both the frontend and the core components of the wallet.

Matias Falcone

Role: Project Lead, Full Stack Developer
Experience: Matias Falcone has a strong background in software development and has been actively involved in the Cardano community. He has experience working on blockchain projects and has founded his own Cardano Stake Pool (FALCO), which he also operates. Matias is also skilled in front-end and back-end development, as well as smart contract development.
Links:
LinkedIn
Portfolio
GitHub
Cardano Stake Pool GitHub

Adriano Fiorenza

Role: Full Stack Developer, Plutus Dev
Experience: Adriano Fiorenza is Entrepreneur & Senior Full Stack Developer with 15+ years of experience software and IoT development. Founder and Developer of GameChanger Wallet, participated in 1st gen Plutus Pioneer Program, Team member at ALDEA and Gimbalabs collaborator.
Links:
LinkedIn

If additional team members are recruited, specific skills such as front-end development, blockchain integration, documentation, and community management will be sought.

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

All costs has been calculated on average values and some considerations has been taken into account to reduce costs on research and design and other less work intensive milestones. Some team member participations won't be taken into account as yet further cost reductions, leaving treasury budget for other projects.

Proposed costs are calculated based on current average monthly salaries for Senior Full Stack Developers specialised on the final deployment stack, all with experience in Cardano EUTxO model and blockchain development with costs from Melbourne, Australia (we have deducted USD 1,600 per month per developer on the average salary in the region) as reference, due to team member residence location. Also month salary units has been taken into account as professionals availability is not hourly based, even more with senior developers experienced in Cardano EUTxO model.

We consider that what this protocol and surrounding tooling has to offer to the Cardano Ecosystem makes value for money, not only taking into account all the benefits for onboarding users, improve Cardano UX, features for developers, DApps and use cases, but also considering the potential risks of a careless design, such as security issues, and non performant implementation.

bookmarked!