This page covers the integrity controls of the Emerging Platform: how it uses cryptographic proofs, verifiable identities and distributed consensus to make claims and credentials tamper-evident. Every solution on the platform relies on them, including Emerging Household Energy. Read it to understand what protects a record from submission onwards, and what you need to do on your side.
The controls
| Control | What it does |
|---|---|
| Cryptographic proofs | Hash chains and digital signatures for verifying data |
| Distributed consensus | Validation by several nodes of the Impact Hub Network |
| Immutable records | Verification proofs stored on the blockchain |
| Access control | Capability-based permissions and credential verification |
These controls show that a record has not changed since it was signed and who signed it. They do not show that what the record states is true. Trust boundaries explains the difference.
What each part protects
| Area | Measures |
|---|---|
| Record integrity | Cryptographic hashing of data, proofs anchored on the blockchain, tamper-evident storage and an audit trail |
| Identity verification | Decentralized identifiers (DIDs), verifiable credentials, digital signatures and key management |
| Access control | Capability-based permissions, multi-signature requirements, credential verification and authorisation protocols |
The system has four layers:
| Layer | What it holds |
|---|---|
| Application | User interfaces and API endpoints |
| Protocol | Verification rules and governance |
| Consensus | The distributed validation network |
| Storage | Immutable record keeping |
How a record is verified
- Submission. The record is created with its metadata, digitally signed, given a proof and distributed to the nodes.
- Validation. The signature is verified, protocol compliance is checked, the network reaches consensus and the proof is anchored.
- Maintenance. The record is verified continuously, with audit logging, status monitoring and alerts.
What you need to do
- Access management. Handle credentials properly.
- Data validation. Check data integrity at each step.
- Monitoring. Track system status and alerts.
- Compliance. Follow the security protocols.
Next steps
- Review the security requirements and set up authentication.
- Validate data at each step, as described above.
- Configure monitoring.
Developer resources:
- Security guide: implementation guidelines.
- Blocksync GraphQL API: verification endpoints.
- Emerging Platform registry: record management.
- Developer support on Slack