Skip to main content
The Credible Layer uses admin verifier modules to determine who can deploy assertions for a contract. Most deployments use owner-based verification by default. This design will continue to expand with additional ownership patterns.
This page explains the ownership model. If your contracts do not fit the default verifier and you need the process for getting approved, use Manual Verification.

​
Current Implementation

The common default verifier expects contracts to implement the owner() function (Ownable pattern). Here’s an example of the expected interface: 
interface IOwnable {
    function owner() external view returns (address);
}
When testing or developing with the Credible Layer, ensure your contracts implement this interface to enable project registration and assertion management.
Managing assertions is a sensitive role. We recommend using hardware wallets and multisig accounts for protocol admin (assertion manager) addresses.

​
Manual Verification (Overview)

If your contracts are immutable or don’t expose an admin interface, you may be able to request manual verification. In this path, Phylax validates that the requesting team controls the protocol and then registers a protocol admin (manager) address for the specific contracts in the State Oracle registry. High-level requirements and signals include:
  • Demonstrated control over the protocol codebase (e.g., ability to merge to the official repo and manage collaborators)
  • Strong public proof that the protocol wants to use the Credible Layer and that the selected admin address reflects the organization’s intent (e.g., multisig signatures or official social announcements)
  • Willingness to share identity or evidence when needed
After approval, the protocol admin address is added to the registry and a timelock begins before assertions can be deployed. Protocols can also opt out of registry additions if they do not want assertions attached to their contracts. See Manual Verification for the full process and requirements.

​
Future Development

We are actively researching alternative ownership verification methods that will:
  • Support different ownership patterns
  • Enable seamless ownership transfers
  • Maintain security requirements
These improvements will be implemented in future versions of the Credible Layer.

​
Next Steps