Adshares Protocol#

Adshares Protocol describes interactions between the following components:

The following diagram presents the main components participating in Adshares Protocol and the relationships between them:

../_images/index.svg

The following diagram presents a simplified overview of the main interactions defined by Adshares Protocol:

skinparam monochrome true

participant "Supply-Side\nAgent" as SSA
participant "Supply-Side\nContext Provider" as SSCP
participant "Supply-Side\nPlatform" as SSP
participant "ADS\nBlockchain" as blockchain
participant "Demand-Side\nPlatform" as DSP
participant "Demand-Side\nContext Provider" as DSCP

==Synchronization==

SSP -> blockchain: Send Broadcast
DSP -> blockchain: Send Broadcast
SSP -> blockchain: Fetch Broadcast
DSP -> blockchain: Fetch Broadcast
SSP -> DSP: Fetch Demand-Side Inventory
DSP -> SSP: Fetch Supply-Side Inventory

==Impressions==

SSA -> SSCP: Register Event
SSA -> DSP: Get Creative Content
SSA -> DSP: View Event
SSA -> DSCP: Register Event
SSA -> SSP: Click Event
SSP -> DSP: Click Event

==Payments==

DSP -> blockchain: Send payment
SSP -> blockchain: Fetch transactions
SSP -> DSP: Fetch Payment Report

Scope#

Authentication #

How various entities participating in Adshares Protocol authenticate each other.

Synchronization #

How Supply-Side Platforms and Demand-Side Platforms announce their current availability:
- published by: Supply-Side Platform and Demand-Side Platform
- retrieved by: Supply-Side Platform and Demand-Side Platform
- medium: ADS Blockchain
How Demand-Side Platforms expose their inventory data:
- exposed by: Demand-Side Platform
- consumed by: Supply-Side Platform
- returns: Demand-Side Inventory
How Supply-Side Platforms expose their inventory data:
- exposed by: Supply-Side Platform
- consumed by: Demand-Side Platform
- returns: Supply-Side Inventory

Impressions #

How Context Providers expose information about Users, Sites and Devices:
- exposed by: Context Provider
- consumed by: Supply-Side Platform and Demand-Side Platform
- returns: Context Data
How Context Providers accept notifications about Impression Events:
- exposed by: Context Provider
- consumed by: Supply-Side Agent
- returns: Context Script
How Demand-Side Platforms expose content of Creatives:
- exposed by: Demand-Side Platform
- consumed by: Supply-Side Agent
- returns: Creative Content
How Demand-Side Platforms accept notifications about Impression Events:
- exposed by: Demand-Side Platform
- consumed by: Supply-Side Agent
- redirects to: Context Provider
(Optional) How Supply-Side Platforms outsource the process of selecting Creatives:
- exposed by: Ad Select Module
- consumed by: Supply-Side Platform
- returns: list of Creative Objects

Payments #

How Demand-Side Platforms send payments to Supply-Side Platforms:
- payer: Demand-Side Platform
- payee: Supply-Side Platform
- medium: ADS Blockchain
How Demand-Side Platforms expose information about executed payments:
- exposed by: Demand-Side Platform
- consumed by: Supply-Side Platform
- returns: Payment Report
(Optional) How Demand-Side Platforms outsource the process of generating Payment Reports:
- exposed by: Ad Pay Module
- consumed by: Demand-Side Platform
- returns: Payment Report

Contents#