fix: remove parenthetical (see ...) link pattern, use inline natural language links

This commit is contained in:
Hermes
2026-05-24 01:23:55 +00:00
parent 8f875dc192
commit b3d91f2e55
2 changed files with 10 additions and 10 deletions

View File

@@ -14,7 +14,7 @@ Existing smart contract platforms (Ethereum, Solana, Cosmos) verify only that ex
- Ethereum: The contract ran according to the EVM bytecode (execution validity)
- Agora: The contract is correct with respect to its specification, AND it ran correctly (correctness + execution)
This means Agora contracts can encode real-world regulations (HIPAA, SOC2, GDPR) as gate rules and prove that a contract execution satisfies them. No existing platform does this.
This means Agora contracts can encode real-world regulations ([[file:compliance/hipaa.org][HIPAA]], SOC2, [[file:compliance/gdpr.org][GDPR]]) as gate rules and prove that a contract execution satisfies them. No existing platform does this.
* What Contracts Enable
@@ -28,7 +28,7 @@ How it works:
- Every transaction runs through the symbolic engine and produces a proof log
- Any instance can verify any other instance's contract execution by replaying the proof
Revenue: Transaction fee per contract execution (see [[file:compute-marketplace.org][compute marketplace]]), deployment fee per verified contract, premium for certification weight.
Revenue: Transaction fee per contract execution in the [[file:compute-marketplace.org][compute marketplace]], deployment fee per verified contract, premium for certification weight.
Comparison: Ethereum collects ~$20B/yr in transaction fees. Agora's verifiably correct contracts target the same market with a stronger value proposition. The limitation is liquidity, not technology — network effects determine adoption.
@@ -37,7 +37,7 @@ Comparison: Ethereum collects ~$20B/yr in transaction fees. Agora's verifiably c
Organizations running multiple triad instances need contracts that span instances: cross-instance policy, unified compliance, federated identity.
Use cases:
- Enterprise: all instances in the finance department must apply the SOX gate rule set
- Enterprise: all instances in the finance department must apply the [[file:compliance/sox.org][SOX]] gate rule set
- Consortium: each member instance votes on protocol upgrades
- Supply chain: Instance A verifies shipment, Instance B verifies payment, both must agree
@@ -75,7 +75,7 @@ If certification carries legal weight (as described in [[file:compute-marketplac
- Contract execution insurance: Insure against bugs in contract code (even ACL2-verified contracts can have specification errors).
- Reputation staking pool: A reinsurance pool where multiple providers stake against each other's attestations.
Revenue: Premiums, pool fees, actuarial gate rule licensing.
Revenue: Premiums, pool fees, actuarial gate rule [[file:licensing.org][licensing]].
Why this is defensible: Insurance requires capital and track record. A new entrant cannot bootstrap reputation overnight. The early player accumulates both, creating a moat that compounds with every honest attestation.
@@ -108,7 +108,7 @@ Revenue: Fee per resolution, premium for reputation-weighted arbitration (arbitr
|----------+-----------+--------------+-------+------------|
| Smart contracts (general) | $20B/yr (Ethereum) | Transaction fees | End State | Installed base |
| Contract templates | New market | Per-template sale | Zero | Gate rule SDK |
| Governance (multi-instance) | New market | Annual license | Zero | Stoa premium |
| Governance (multi-instance) | New market | Annual license | Zero | [[file:stoa.org][Stoa]] premium |
| Liquid democracy | New market | Per-vote fee | End State | Installed base |
| Attestation | New market | Per-attestation | Zero | DID registry |
| Insurance marketplace | $1T+ (global insurance) | Premiums | End State | Installed base + capital |