Plutus Wallet Connector (CIP-30 expansion)

[GENERAL] Name and surname of main applicant

Leandros Holleman

[GENERAL] Are you delivering this project as an individual or as an entity (whether formally incorporated or not)

Individual

[GENERAL] Please specify how many months you expect your project to last (from 2-12 months)

4

[GENERAL] Please indicate if your proposal has been auto-translated into English from another language.

No

[GENERAL] Summarize your solution to the problem (200-character limit including spaces)

By creating an new extension for CIP-30 that conforms to the requirements of a Plutus wallet, we can make the use of dApps safe and efficient for Plutus wallet users.

[GENERAL] Does your project have any dependencies on other organizations, technical or otherwise?

No

[GENERAL] If YES, please describe what the dependency is and why you believe it is essential for your project’s delivery. If NO, please write “No dependencies.”

N/A

[GENERAL] Will your project’s output/s be fully open source?

Yes

[GENERAL] Please provide here more information on the open source status of your project outputs

The connector will be open sourced under CC-BY-4.0 like all other CIPs

The work done on BroClan to support the connector will be under Mozilla License V2.0 , meaning anyone can look at it copy parts and use as inspiration, but I retain ownership of the brand and codebase.

[METADATA] SDG rating

N/A

[SOLUTION] Please describe your proposed solution.

An alternative to CIP-30 that supports the unique constrains of a Plutus wallet, and a reference implementation of this alternative into the BroClan software

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

This will enable development of Plutus based wallets and give them a way to interconnect with DeFi in a safe way from the beginning .

Additionally with the maturing of Wallet connectors currently happening currently, this API will be able to be reused by other connectors giving the ecosystem a clear path for composability as dApps will be able to query each-other and compose transactions that are mutually valid.

[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?

I have developed a Multisig Wallet for Cardano that is already operational.

This functionality has been implemented and tested.

I have over 10 years experience in Linux operation and experience operating a high performance pool since the first days of Cardano.

Additionally I have 2 years of JavaScript/Nodejs/MongoDB experience.

I have also completed Catalyst proposal 100928 that will bring DeFi capabilities to Multisig wallets.

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

1) Establish a new wallet connector based on CIP-30

Objective: Create a new wallet connector definition and open a CIP around it

Deliverable: A new CIP describing the API connector in detail

2) Create a reference implementation for the new connector in BroClan

Objective: create a new version of the BroClan software with the new wallet-connector implemented.

Deliverable: A new version of the BroClan software and a new version of the BroClan companion app that will allow multisig transaction with DApps

3) Help and motivate projects to use the new connector in their solution

Objective: Get every DApp developer to know about the new connector, get at least 1 DApp of each category to integrate the new connector, offer support to any DApp that wants to integrate.

Indented outcome: Educate the entire dev ecosystem about the existence of this new option, set incentives and support for DApps that want to integrate.

Deliverable: Support from at least 1 DApp of each kind for the new connector.

N/A

N/A

Upon completion of this project any user should be able to use Cardano Defi using 1 or more of the BroClan Plutus wallets.

Additionally Cardano Developers who want to integrate the new connector in their wallets or dApps should have a clear path to achieving that.

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

Leandros Holleman- Project manager, Developer and SysAdmin

I am a 1 man team and given the limited scope of the project I can handle it on my own.

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

Answer:

A lot of the work around this project is depended on getting feedback and giving time for the community to raise suggestions/objections to the proposed design, for this reason the Timelines are longer but no work is budgeted for the entire stretch of the timeline.

1) Create an API specification and open a CIP pull-request:

• Initial Draft : 40 Hours
• Feedback and alterations: 20 Hours

2) Create reference implementation with BroClan:

• Expand the BroClan dApp connector to support the new specification: 80 Hours
• Test and validate the behavior/bug fixing: 40 Hours
• Deploy this functionality to production: 8 Hours

3)Get at least 1 DApp of each kind to support the new connector:

• Support DApps wanting to integrate: 20Hours
• Bounty for the first DApp to integrate in each category: 5000 ADA

Payroll = 208Hours * €50 = €10400 ~ 30000ADA

Incentives = 5000 * 3 = 15000 ADA

Total = 45000ADA

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

The value for the Cardano ecosystem is immense, having this in place will be a landmark moment for Cardano as it will mean plutus developers will be able to leverage other plutus contracts without the need for make special arrangements for each usecase.

It will also allow the creation of smart wallets including but not limited to :" Token Vaults","Tokenized Multisig","Debit accouts","Subscription Accounts" and more all of which should be able to interact with any DeFi that has fully implemented the new connector.

[IMPORTANT NOTE] The Applicant agrees to Fund Rules and also that data in the submission form and other data provided by the project team during the course of the project will be publicly available.

I Accept