Scalability

Strategies for managing high transaction volume without compromising performance or costs.

Main Strategies

Merkle Trees

We group multiple transactions into a Merkle tree and only publish the root on blockchain. Reduces costs while maintaining full verifiability.

Batching

We accumulate transactions during configurable intervals (1-60 min) and publish them in batches to optimize costs.

Prioritization

Critical transactions (real transfers, closings) go directly to blockchain. Others are grouped in batches.

Topics per Company

Each project has its own topic on Hedera HCS, enabling horizontal scaling and isolation.

Merkle Trees

Instead of publishing each transaction individually:

// Example: 100 transactions → 1 blockchain message

Daily transactions:
├── tx_001 (hash: abc...)
├── tx_002 (hash: def...)
├── tx_003 (hash: ghi...)
│   ...
└── tx_100 (hash: xyz...)

Merkle Tree:
                    ROOT_HASH
                   /          \
            hash_1_50      hash_51_100
           /      \        /       \
      hash_1_25  hash_26_50  ...   ...

We only publish: ROOT_HASH on Hedera
Verification: Any individual tx verifiable with Merkle Proof

Priority Levels

PriorityOperation TypeProcessing
CriticalHBAR transfers, cycle closingsImmediate
HighBudget allocations, approvals5 min batch
NormalIncome, expenses, inventory15 min batch
LowLogs, internal audit60 min batch

Architecture

┌─────────────────────────────────────────────────────────┐
│                      POLARIS                            │
├─────────────────────────────────────────────────────────┤
│  ┌──────────┐    ┌──────────┐    ┌──────────────────┐  │
│  │  App UI  │───▶│  API     │───▶│  Queue Service   │  │
│  └──────────┘    └──────────┘    └────────┬─────────┘  │
│                                           │            │
│                        ┌──────────────────┴──────┐     │
│                        ▼                         ▼     │
│              ┌─────────────────┐     ┌───────────────┐ │
│              │  Batch Processor│     │ Priority Lane │ │
│              │  (Merkle Trees) │     │  (Immediate)  │ │
│              └────────┬────────┘     └───────┬───────┘ │
│                       │                      │         │
│                       ▼                      ▼         │
│              ┌────────────────────────────────────┐    │
│              │          Hedera HCS/HTS            │    │
│              └────────────────────────────────────┘    │
├─────────────────────────────────────────────────────────┤
│                      SUPABASE                          │
│  ┌─────────────┐  ┌──────────────┐  ┌──────────────┐  │
│  │ Encrypted   │  │ TX Records   │  │ Batch Logs   │  │
│  │ Data        │  │ + Hedera IDs │  │              │  │
│  └─────────────┘  └──────────────┘  └──────────────┘  │
└─────────────────────────────────────────────────────────┘

Estimated Capacity

1M+

Transactions/day supported

99.9%

Cost reduction with batching

<5s

Latency for critical tx