Technical Stack & Integration Guides
Silsilat is a modular, agent-based architecture combining AI, DLT, and liquidity automation. The stack is designed to be interoperable, composable, and secure, allowing easy integration by pawnshops, liquidity providers, regulators, and third-party applications.
1. System Architecture Overview

Key Layers
Layer
Purpose
Technology Stack
Frontend
User dashboards for pawnshops, investors, and regulators
Next.js / React / TailwindCSS
API Gateway
Unified access layer for REST & WebSocket endpoints
FastAPI (Python)
Agent Layer
Independent AI and policy agents running evaluation logic
Python 3.11 / OpenTelemetry / Arize Phoenix
Consensus Layer
Immutable event ledger and state synchronization
Hedera SDK / HCS-10 / HCS-11
Data Layer
Artifact storage and model traces
Postgres, IPFS / Arize Phoenix local collector
Liquidity Layer
On-chain fund management and yield distribution
Hedera SDK
Security Layer
Authentication, encryption, and signatures
JWT / HMAC / Ed25519
2. Development Environment Setup
Prerequisites
Python 3.11+
Node.js 20+
Docker & Docker Compose
Hedera SDK (Python + JS)
Pinata API
Arize Phoenix Local Instance
.env.localfile with required keys
Example .env.local
Run agents locally using Docker:
3. Core Services
Gold Evaluator Agent
Evaluates LTV ratios, applies haircut policies, and produces valuation artifacts.
Key Methods:
fetch_gold_price()→ calls MetalPriceAPIconvert_fx()→ calls FastForexapply_policy()→ loads haircut and LTV limitspublish_trace()→ sends artifact CID to HCS
Output Example:
Liquidity Node
Executes pool operations via Hbarsuite Smart Node logic.
Functions:
buy_sag_token()mint_lqt_token()redeem_lqt_token()calculate_yield()publish_transaction()(to HCS)
Smart node state transitions are deterministic and replicated across all liquidity node validators.
Policy Agent
Monitors transactions and applies KYC/AML/Shariah compliance logic.
Data Sources:
AML/KYC screening API (WorldCheck / Dow Jones)
Silsilat Policy JSON schema
Regulator node public key list
Compliance Outputs:
4. APIs for Integration Partners
Base URL
Endpoints
Method
Endpoint
Description
POST
/pawnshops/register
Onboard pawnshop node with KYC
POST
/sag/mint
Create new Secured Asset Gold token
GET
/sag/{sag_id}
Retrieve SAG metadata
POST
/evaluate
Trigger gold evaluation
GET
/evaluation/{trace_id}
Fetch AI trace result
POST
/liquidity/request
Pawnshop requests funding
POST
/liquidity/deposit
Investor deposits funds
GET
/liquidity/pool
Query pool metrics
POST
/override/submit
Submit admin override decision
All endpoints require JWT tokens issued via /auth/login.
Payloads are signed using HMAC-SHA256.
5. SDKs and Developer Tools
Python SDK
JavaScript SDK
6. Topic Configuration for Developers
Topic
Purpose
Example ID
Input Topic
Loan initiation and pawnshop messages
0.0.1001
Output Topic
AI evaluator and compliance responses
0.0.1002
Override Topic
Admin or regulator overrides
0.0.1003
Policy Topic
Policy updates and version control
0.0.1004
Treasury Topic
Fee and yield settlement records
0.0.1005
Message Format Example:
7. Integration Workflow
(a) For Pawnshops
Register via
/pawnshops/registerSubmit pledged gold metadata →
/sag/mintTrigger AI evaluation →
/evaluateReceive LTV →
/evaluation/{trace_id}Request liquidity →
/liquidity/requestReceive instant payout to bank / wallet
(b) For Investors
Register investor account
Deposit funds into liquidity pool
Receive LQT tokens representing pool share
Track yield via
/liquidity/poolRedeem principal + yield after maturity
(c) For Regulators
Access audit dashboard (read-only HCS node)
Query transactions by
trace_idorpolicy_idReview override events
Validate compliance packs (via
/policy/validate)
8. Integration with External Systems
Integration Type
Partner Example
Purpose
KYC / AML
Refinitiv / WorldCheck
Automated screening
Gold Pricing
MetalPriceAPI
Real-time commodity data
FX Conversion
FastForex
USD → MYR rate conversion
Storage Verification
IoT Sensors via MQTT
Vault monitoring data
Payment Rails
PayNet / Bank Negara Open API
Liquidity settlement
Phoenix Observability
Arize Phoenix
Trace monitoring for AI explainability
9. Security & Privacy Architecture
Security Layer
Mechanism
Encryption in Transit
TLS 1.3
Encryption at Rest
AES-256
Identity & Roles
DID registry (HCS-11) + JWT
Payload Integrity
HMAC-SHA256 signatures
Data Privacy
IPFS pointers only, raw data off-chain
ZKP Ready
Supports Zero-Knowledge Attestation for private KYC proofs
Example: ZKP Verification Stub
10. Deployment Options
Environment
Purpose
Hosting Option
Local Dev
Testing with mock APIs
Docker Compose
Testnet
Integration testing
Hedera Testnet
Production
Live transaction network
Hedera Mainnet
Private Instance
Regulated node deployment
HSuite Smart Node Cluster
Deployment is CI/CD-ready via GitHub Actions and can be containerized for Kubernetes or Hbarsuite orchestration.
Summary
Silsilat’s technical stack is designed to be:
Composable: Modular agent-based components that can be replaced or extended.
Observable: Every decision logged through Arize Phoenix and IPFS.
Secure: Multi-layered authentication, encryption, and consensus anchoring.
Interoperable: REST, SDKs, and GraphQL APIs for easy external integration.
Together, this stack enables a trusted, auditable bridge between real-world collateral and digital liquidity, ready for institutional adoption.
Last updated
