Question 1

Why would anyone trust a certification system operated by Borealis?

Accepted Answer

By default, they shouldn't - or at least they shouldn't trust Borealis more than any other operator. If certification records lived only in a Borealis database, the system would require trusting Borealis not to manipulate records, not to be hacked, not to lie. That's a single point of failure. HCS removes Borealis from the trust equation. Records are written to Hedera mainnet, where they are immutable and independently verifiable. Even if Borealis is hacked, goes out of business, or turns malicious, the certification records remain. A regulator, investor, or customer can query Hedera directly and verify: 'Did this agent really achieve this score on this date?' This cryptographic proof is stronger than any company's promise. The point: trust the technology, not the operator.

Question 2

How does Hedera Hashgraph differ from blockchain?

Accepted Answer

Both Hedera and blockchain (Bitcoin, Ethereum) provide immutable, distributed ledgers. The key differences: (1) Consensus mechanism - Hashgraph uses directed acyclic graphs (DAGs) and virtual voting; blockchain uses proof-of-work or proof-of-stake. Hashgraph is faster and more energy-efficient. (2) Finality - Hashgraph provides immediate finality (transactions are final as soon as consensus is reached); blockchain requires waiting for multiple block confirmations. (3) Permissioning - Hedera mainnet is operated by a council of validators; Bitcoin and Ethereum are fully permissionless. (4) Transaction cost - Hedera typically has predictable, low fees; Ethereum fees vary wildly based on congestion. For Borealis's use case (recording certification facts that must be auditable decades later), Hedera's combination of finality, low cost, and governance council is ideal.

Question 3

What exactly gets written to HCS?

Accepted Answer

Two types of messages go to HCS: (1) Audit Topic (0.0.10382960) - immutable records of certification events. When an agent is certified, the agent ID, score, BTS dimensions, and timestamp are written here. This is the system of record for certification facts. (2) Data Topic (0.0.10382961) - telemetry anchors. When an agent submits telemetry (constraint violations, decision records, anomalies), a cryptographic hash of that data is written to HCS with a Hedera transaction ID returned to the agent. The agent can later prove: 'I submitted this telemetry on this date' by showing the transaction. Neither topic contains sensitive user data - the focus is on trust proof, not operational details.

Question 4

Can I query HCS to verify a certificate?

Accepted Answer

Yes, absolutely. You don't need our API. You can query Hedera mainnet directly using: (1) Hedera explorer (hedera.com/explorer) - search by transaction hash to see the raw message. (2) Hedera SDK (available in Python, Java, JavaScript) - programmatically query the topic and validate messages. (3) Third-party explorers - various services provide HCS topic visualization. To verify a BorealisMark certificate, find the certification transaction on Audit Topic 0.0.10382960 and confirm the agent ID, score, and timestamp match your records. This is independent verification: no need to trust Borealis, no need for API access, just public ledger immutability.