Technical Architecture
Independent Impact combines decentralised identity, verifiable data, and distributed compute to safeguard integrity across the impact lifecycle.
Hedera Consensus Service
Event journaling on Hedera provides a tamper-evident record of submissions, evaluations, and verifications across the platform.
- Immutable event history
- Transparent sequencing of actions
- Low-latency consensus
W3C Decentralised Identifiers
DIDs anchor every participant’s identity, linking actions to accountable agents while keeping the system open to new entrants.
- Standards-based identifiers
- Interoperable agent onboarding
- Verifiable agent controls
W3C Verifiable Credentials
Verifiable credentials encode evaluations, validations, and impact claims so that downstream users can trust the provenance of every assertion.
- Cryptographically signed attestations
- Portable credentials
- Selective disclosure for relying parties
IPFS for Artefacts
Impact documentation lives in content-addressed storage, ensuring artefacts stay accessible and immutable long after issuance.
- Permanent artefact references
- Peer-to-peer distribution
- Integrity checking through hashes
Jellyfish Verifiable Compute
Deterministic verification pipelines executed with Jellyfish make quantitative assessments reproducible and auditable.
- Transparent calculation workflows
- Provenance for computational steps
- Extensible verification logic
Fluree Semantic Database
Fluree’s cryptographically secured, time-travelable graph keeps the platform’s knowledge base coherent while preserving historical context.
- Traceable data lineage
- Granular access controls
- Immutable version history
Hedera Token Service
Verified impacts can be tokenised, making it possible to transact on outcomes whose provenance and assurance are transparent to every buyer.
- Programmable impact tokens
- Reputation-aware issuance
- Integration with broader ecosystems
Architectural Principles
Independent Impact implements technologies that reinforce transparency and accountability at every layer of the impact lifecycle. The stack is intentionally modular so the platform can incorporate new methodologies, data sources, and assurance requirements without sacrificing integrity.
Hedera Consensus Service
Hedera Consensus Service captures an immutable, ordered log of platform events. This journal confirms when artefacts were submitted, who evaluated them, and what decisions were taken. It underpins dispute resolution by providing a shared timeline of actions.
Decentralised Identifiers and Verifiable Credentials
Participants manage verifiable digital identities using W3C Decentralised Identifiers. Evaluations, validations, and credentials issued through the platform are represented as W3C Verifiable Credentials, so any relying party can independently inspect provenance and assurance.
IPFS and Fluree for Data Integrity
Artefacts associated with impact claims are pinned to IPFS, giving each document a content-derived address that proves its integrity. Fluree provides a cryptographically secured, time-travelable semantic database, allowing users to query current and historical states of projects, agents, and methodologies.
Verifiable Compute with Jellyfish
Quantitative assessments often rely on complex calculations. Jellyfish executes these computations in a verifiable manner, producing reproducible outputs with clear provenance of the data and logic used.
Tokenisation Pathways
Once an impact claim has passed through peer review and verification, it can be tokenised via the Hedera Token Service. Tokenisation links the reputation of creators, validators, and verifiers to the resulting assets, giving buyers confidence in both the process and its outcomes.