NetworkConsentCheckResult network.consent-check-result@1
Generated at from
openvibe-contracts v0.419.0 and
openvibe-sdk v0.161.0.
- Version
- 1.0.0
- Owner
- network
- Visibility
- first-party
- Status
- active
- Compatibility
- backward
- Schema
https://openvibe.network/contracts/network/consent-check-result.v1.json
network.consent-check-result@1 (L24): the answer to network.consent-check-request@1. Every subject asked about is in allowed: true only for an active choice that covers the purpose, the kind, the app and the feature asked about. An app's grant (client set) answers only a check that names that app. An unknown or deleted subject is false, the same as a person who never chose (the answer never says whether an account exists). A service caches an answer for at most 60 s and drops it on network.consent.changed; when Network cannot answer, every subject is false.
Fields
| Field | Type | Required | Description | Constraints |
|---|---|---|---|---|
purpose | enum | yes |
| |
kind | enum |
| ||
client | string |
| ||
feature | enum |
| ||
allowed | object | yes | Each subject asked about, and whether the use is allowed for them. | |
licence | object | data.public only: the licence each allowed subject chose. | ||
checked_at | string | yes |
|
Examples
From the contract's own test fixtures: valid ones validate, rejected ones must fail.
Valid: answer
{
"purpose": "data.public",
"kind": "pictures",
"allowed": {
"usr_01K6R2Z8C4V7M9Q3T5W1X2Y3Z4": true,
"usr_01K6R2Z8C4V7M9Q3T5W1X2Y3Z5": false
},
"licence": {
"usr_01K6R2Z8C4V7M9Q3T5W1X2Y3Z4": "cc-by-4.0"
},
"checked_at": "2026-10-31T05:00:01.000Z"
}Rejected: bad-subject-key
{
"purpose": "ai.train",
"allowed": {
"moosely": true
},
"checked_at": "2026-10-31T05:00:01.000Z"
}Validate
const contracts = require('openvibe-contracts');
contracts.validate('network.consent-check-result@1', value); // { valid, errors: [{ path, message }] }