Governance & Compliance
Silsilat is not just a liquidity protocol — it is a compliance-first financial infrastructure that embeds regulation, ethics, and oversight directly into its core architecture. By merging automated policy enforcement with human-in-the-loop governance, Silsilat ensures that every transaction remains transparent, lawful, and aligned with Islamic finance principles.
Governance Principles
Silsilat’s governance framework is built upon four foundational principles:
Principle
Description
Transparency
Every valuation, transaction, and override is recorded on the Hedera Consensus Service and auditable in real time.
Accountability
All agent actions and policy decisions carry a digital signature, enabling traceability of origin and intent.
Compliance-by-Design
Regulatory, AML/KYC, and Shariah guidelines are embedded as executable rule packs within the Policy Engine.
Participatory Oversight
Pawnshops, investors, regulators, and Shariah boards all hold roles in the decision and dispute resolution process.
Governance Structure

Entity Roles
Silsilat Treasury: Custodian of platform fees, reserves, and protocol parameters.
Governance Council: Sets network policies, approves new rule packs, and ratifies overrides.
Policy & Compliance Committee: Maintains regulatory alignment and AML/KYC frameworks.
Shariah Advisory Board: Certifies instruments and ensures compliance with Islamic finance principles.
Liquidity Providers DAO: Represents investor interests in governance votes.
Regulatory Observers: Authorized read-only nodes (e.g., Bank Negara Malaysia, Labuan FSA) for oversight and audit access.
Policy Engine Overview
At the heart of Silsilat’s compliance layer lies the Policy Engine, a modular rule-based system that executes, verifies, and records compliance logic for each transaction.
Each policy is expressed as a structured JSON rule pack and stored both on IPFS and anchored to Hedera with a version hash.
Example Policy Schema
Each time an agent evaluates or processes a loan, it fetches the latest active policy version and enforces the relevant constraints.
Compliance Modules
Module
Purpose
Key Features
KYC / AML / CTF
Ensures customer due diligence and transaction monitoring
eKYC integration, sanction list screening, suspicious transaction flags
Shariah Screening
Validates conformity to Islamic finance principles
Prohibits riba (interest), ensures qard-hasan structure, zakat tracking
Transaction Monitoring
Detects anomalies or threshold breaches
Automated flagging + override request
Regulatory Reporting
Provides audit data to financial authorities
HCS message feeds, queryable dashboards
AI Compliance Evaluation
Uses AI evaluator for risk scoring and fraud detection
Evaluator output stored as Phoenix trace + IPFS artifact
Automated Compliance Flow

Output Example (Compliance Pass)
Shariah Compliance Framework
Principles Enforced
No Riba (Interest): Returns to investors are structured as profit-sharing (mudarabah), not interest.
Transparency (Gharar Avoidance): All terms are recorded immutably on-chain.
Asset-Backed Financing: Each loan must correspond to a real physical gold pledge.
Ethical Purpose: Funds must not finance prohibited (haram) activities.
Mechanism
Shariah rule packs are reviewed and signed by the Shariah Advisory Board.
Each transaction automatically checks for Shariah compliance flags.
Non-compliant actions trigger an override review rather than automatic execution.
Example Rule Pack (Excerpt)
Override Mechanism (Human-in-the-Loop)
Not all situations can be resolved by automation. The Override Agent allows designated administrators or regulators to modify, reverse, or approve exceptional cases while maintaining audit transparency.
Override Flow

Override Event Example
Every override event:
Is time-stamped and signed with the approver’s private key.
Includes reasoning metadata for auditability.
Is stored permanently on Hedera for compliance recordkeeping.
Regulator Interaction Layer
Regulators access a real-time dashboard and queryable API endpoints for continuous oversight.
Regulator Access Mode
Capability
Read-only HCS Node
Subscribe to compliance events and overrides.
Query API (GraphQL)
Search transactions by trace ID, policy ID, or pawnshop.
Audit Dashboard
Visualize trends, AML alerts, and LTV distributions.
Policy Signing Interface
Approve or update rule packs digitally.
This architecture ensures continuous regulatory visibility without compromising decentralization.
Governance Token (SLC) for Voting & Policy Upgrades
When implemented, SLC tokens will represent governance rights within the Silsilat ecosystem.
Use Cases:
Vote on fee adjustments or pool rate changes.
Approve new policy packs or model updates.
Delegate validator rights to node operators.
Fund community and sustainability programs.
Voting Model:
Quadratic or delegated staking-based, depending on regulatory jurisdiction.
Each vote is recorded as an on-chain event on the Governance Topic (HCS_GOV_TOPIC_ID).
Global Policy Interoperability
As Silsilat expands to other markets (Indonesia, Philippines, East Africa), the Policy Engine supports jurisdiction-specific rule packs under a unified schema.
Each pack references:
Local gold valuation standards.
AML/KYC laws.
Shariah advisory bodies.
Currency and FX integration rules.
This ensures global scalability without losing compliance granularity.
Summary
Silsilat’s Governance and Compliance Framework turns regulation into code, consensus, and context:
Code — Executable rule packs ensure objective enforcement.
Consensus — Every event is verifiably logged on Hedera HCS.
Context — Human override ensures fairness, ethics, and judgment.
Together, they form a self-regulating, trust-minimized network that financial institutions and regulators can depend on — a digital infrastructure for ethical, compliant, and transparent finance.
Last updated
