Cardano Role-based Access Control
Problem
How can we enable decentralized organizations to share ownership and access of digital assets such as server resources?
Solution
Create a protocol and reference implementation defining a standard for creating and consuming RBAC policies on the Cardano blockchain.
Total to date
This is the total amount allocated to Cardano Role-based Access Control.
About this idea
Easy Overview: https://cardano.ideascale.com/userimages/accounts/93/936143/panel_upload_48088/utxo-rbac-192c47.pdf
Proposed Standardized Specification: https://docs.google.com/document/d/e/2PACX-1vR0a1tpsND8JbUjFI9jTx4uls3ivtL0odYHeQKwZbJ8LhqLEAQP4hSRzuqlfvXmFc8ihbxbqxwgBslB/pub
Market: My proposed solution should work with any blockchain that supports UTXO metadata of a size similar to Cardano.
Product: My proposed solution will provide a key competitive advantage to Cardano in support of decentralized organizations. Organizations aren't very useful when they are unable to control assets. With my solution, organizations on Cardano will be able to own digital assets. This is a known problem in the blockchain community with a well-defined solution for UTXO-based blockchains, but it has never been realized. See the following proposal for UTXO RBAC on the EOS blockchain: https://arxiv.org/pdf/2007.02163.pdf
Acquisition: Having the only solution for defining decentralized digital assets control will push blockchain developers on the
Cardano blockchain in order to organize DOs and DAOs around decetralized ownership.
Cost breakdown: 160 developer hours @ $50/hr = $8,000 USD.
KPIs:
- policy and policy-tx schema drafts finalized
- CardanoRbac .NET class library completed with the following capabilities:
- -- Read RBAC policy from Cardano blockchain
- -- Find all authorized transactions related to a policy and compute the current policy state
- -- Given a wallet address and a web resource URI, determine the user's permissions
- Create a small sample web server that uses the CardanoRbac library to demonstrate a fully-functioning authorization system
Roadmap:
The following roadmap assumes that the developer will have to do the work outside of normal working hours, causing the 160 development hours to be spread over several months.
- One month: demo server will be able to read a policy from the blockchain using in-development CardanoRbac library and schema drafts
- Two months: demo server will be able to post a policy onto the blockchain
- Three months: demo server will be able to read and validate all transaction metadata on the blockchain such that an up-to-date policy state can be computed on-demand.
Four months: Bugs will be fixed, and schemas, class library, and demo server will reach a stable 1.0 release
Intellectual Property: Every aspect of the project will be developed open-source from the beginning under the MIT license.
Team
I'm a product manager and developer with experience designing, developing, and deploying enterprise SaaS B2B software.
