Service Discovery

Service Registration and Data Management

In the Griffin AI network, each Service Provider (SP) or Client Provider (CP) must start by creating a Griffin ID (Root Identity). This Root Identity is then used to register a new service through one of the Griffin Registration Smart Contracts. The network maintains registries for different entities:

• Service Registry — for SPs and CPs operating full nodes.

• Agent Registry — for AI Agents.

Service registration makes new SPs, CPs, and agents discoverable on the network and records their details securely on-chain.

1

Create Root Identity

Every provider (SP or CP) must create a Griffin ID (Root Identity). This identity is used to sign and authorize subsequent registration and modification transactions.

2

Register Service

Register the service using a Griffin Registration Smart Contract. Registration writes the service entry into the appropriate registry (Service Registry or Agent Registry), making it discoverable on-chain.

3

Provide Service Metadata

When registering, providers must submit comprehensive service information:

• Basic Service Information: service name, owner/provider details, description.

• Service Classification: standardized tags (e.g., image processing, video processing, chatbots, NLP).

• Documentation: link to IPFS-hosted documentation stored in the Griffin distributed database (marketing materials, example outputs, tech specs, SLAs).

4

Update & Mutation Logging

When service details change:

• Update documentation in the Griffin distributed database.

• Submit a mutation log to the Griffin Registration Smart Contracts to update the registry. Guardian nodes oversee and verify registry updates to maintain integrity.

Service Discovery and Marketplaces

Client Providers (CPs) can create advanced indices of service records and build Marketplace-like web applications offering advanced search, pinning, and tagging. These marketplaces are the primary tools for users to browse the service and agent registries to discover, evaluate, and select services and agents.

Service Data Management

Type of Data	Data Location	Modification Procedure
Service Provider Identity	Service Registry (Smart Contract).	Once created, the Service Provider identity is not modifiable.
Basic service information	Griffin Distributed Database	Service information can be modified at will by holders of SP identification keys, utilizing Griffin node functionality.
Service Documentation	IPFS	IPFS storage is owned by its author but cannot be modified. Modifying IPFS data creates a new data set with a new unique link.
Link to Service Documentation	Service Registry (Smart Contract)	Service Documentation Link can be modified at will by holders of SP identification keys by issuing a modification transaction in Griffin Service Registry smart contract.

Table 6: Service Data Management

Note: IPFS-hosted documentation is immutable — any content change results in a new IPFS link. Service Registry entries (including the documentation link) can be updated on-chain by authorized SP key holders.

Reputation System

The Griffin network is permissionless — any entity can offer services, run nodes, or deploy agents. To build trust and accountability, participants receive unique identities that are verified via private keys and recorded in a centralized reputation system.

Guardian nodes are responsible for managing the Griffin reputation system. Their roles include:

• Recording and assessing performance metrics (service availability, response times).

• Aggregating reputation scores submitted by network participants.

• Handling dispute resolution between service providers and users.

• Modifying reputation scores, retracting negative feedback, or imposing bans on Root Identities following reviews.

Only Guardian nodes have write authority to the reputation system in the Griffin database to prevent conflicts of interest and preserve impartiality.

While the network cannot physically disconnect non-compliant operators (due to permissionless design), exclusion from the Griffin reputation system reduces visibility and serves as a deterrent. Client Providers (CPs) may also operate alternative reputation systems with their own standards and procedures (which may differ from the Griffin reputation system).

This combination of identity verification and a Guardian-managed reputation system aims to create a secure, reliable environment while allowing third parties flexibility to implement alternative reputation models.