Proof of Authority (PoA) with Domain, Path, and Resource Ownership

Proof of Authority (PoA) is one of the consensus mechanisms in blockchain, designed to provide efficient and scalable trust within a network. Unlike Proof of Work (PoW) and Proof of Stake (PoS), which rely on computational effort or stake-based validation, PoA operates by granting authority to pre-approved validators. This approach ensures Byzantine fault tolerance while maintaining efficiency and scalability.

This research pitch explores how PoA can be adapted for the Acequia network, taking inspiration from blockchain applications while focusing on decentralized identity and access control mechanisms outside traditional blockchain implementations.

Other approaches such as Proof of Stake (PoS), Proof of Work (PoW), Delegated Proof of Stake (DPoS), and Proof of Space are also considered as part of our broader research effort.

Our system leverages domain, subdomain, path, and resource ownership as a mechanism for establishing PoA in a decentralized yet trusted network. By placing a public key at a known location on a domain, subpath, or embedding it in HTTP response headers for a specific resource, users can cryptographically sign and verify authority within the PoA framework.

How It Works

            Domain, subdomain, or resource owners generate a public-private key pair.
The public key is placed at a well-known URL (e.g., example.com/.well-known/poa-key.txt) for domain or directory verification.
For single resource verification, the HTTP response headers can include the key signature while keeping the resource data untouched.
Users and services can retrieve the key and verify authority based on the ownership of the domain, subpath, or specific resource.
Transactions and authentications occur based on the verified authority.

        

Benefits of this Approach

Eliminates reliance on blockchain infrastructure while maintaining decentralized verification.
Allows for easy integration into existing domain and hosting structures.
Provides a lightweight, scalable solution for identity and trust management.
Flexibility in proving authority over entire domains, directories, or individual resources.

Use Cases

Decentralized web authentication
Secure API access control
Identity verification for DAOs and digital cooperatives
Granular access control based on resource ownership

Researching Existing Standards

We are exploring how this approach aligns with existing standards such as Decentralized Identifiers (DIDs), Verifiable Credentials, and related identity frameworks. Understanding these approaches will help integrate our system with broader decentralized identity efforts.

Next Steps - 6 Week MVP Implementation

This project follows a 6-week timeline to develop a Minimum Viable Product (MVP) implementation:

Week 1-2: Research existing standards and design system architecture.
Week 3-4: Implement proof of control for domains, subdomains, paths, and resources.
Week 5: Develop verification tools and testing frameworks.
Week 6: Implement ACL management for granting read, write, and share-on permissions.
Week 6: Finalize MVP and invite collaborators for testing and feedback.

ACL Management

As part of the MVP implementation, we will develop an Access Control List (ACL) system allowing authorities to grant and revoke permissions:

Read: Authorize users to view specific resources.
Write: Allow modifications to resources.
Share-on: Enable delegation of permissions to other users.

We are actively developing this concept and invite collaboration from developers, security researchers, and decentralized governance experts.

For more details, contact us or contribute to the discussion!