Developer Support

Hologram includes the unique EPOCH developer support system, allowing you to support TELA app developers through minimal, passive CPU hashing—without ads or data collection.

What is EPOCH?

Event-driven Propagation of Opportunistic Crowd Hashing

EPOCH enables dApps to request hash computations from users as a non-intrusive form of developer support—without ads or data collection.

How It Works

1. You browse a TELA app that supports EPOCH (in the TELA Browser)
2. On user interactions (clicks, scrolls), the app may request hashes
3. Hologram computes a small number of hashes (imperceptible)
4. Valid hashes are submitted to the developer's address
5. You've supported the developer without seeing ads!
6. Rewards appear in the developer's Wallet as coinbase transactions

Key Characteristics

Configuration

Access Developer Support settings in Settings > Developer Support (above About).

Default Limits

const (
    DEFAULT_EPOCH_MAX_HASHES  = 100   // Per-request limit
    DEFAULT_EPOCH_MAX_THREADS = 2     // CPU threads
    RATE_LIMIT_WINDOW        = 10s    // Per-app rate limiting
    RATE_LIMIT_MAX_HASHES    = 500    // Max per window
)

Controls

Fair Developer Support Address Switching

When TELA dApps request developer support via AttemptEPOCHWithAddr, Hologram temporarily switches EPOCH rewards to the app developer's address, ensuring fair distribution of support.

How It Works

1. App requests support — TELA app calls AttemptEPOCHWithAddr with developer address
2. Hologram pauses background worker — Stops passive hashing for Hologram's default address
3. Switches to app address — EPOCH connection switches to app developer's address
4. Auto-switch back — After 30 seconds of inactivity, switches back to Hologram's default address
5. Background worker resumes — Passive hashing continues for Hologram

Sticky Timeout

The address switching uses a 30-second sticky timeout:

• Each new request from the app resets the 30-second timer
• As long as the app is actively requesting hashes, rewards go to the developer
• After 30 seconds of no requests, automatically switches back to Hologram's default

Address State API

// Get current EPOCH reward address
GetCurrentEPOCHAddress() -> {
    address: "dero1qy...",
    is_app_address: true,  // true if on app developer's address
    default_address: "dero1qy...",  // Hologram's default
    last_app_request: "2026-01-03T12:00:00Z"
}
 
// Check if currently on app developer's address
IsEPOCHOnAppAddress() -> {
    on_app_address: true,
    time_until_switchback: 15  // seconds remaining
}

Background Worker Behavior

The background DevSupportWorker automatically pauses and resumes:

• Pauses when switched to an app developer's address
• Resumes when switched back to Hologram's default address
• Ensures only one EPOCH connection is active at a time

Example Flow

User browsing app.tela
    ↓
App calls AttemptEPOCHWithAddr(developerAddr)
    ↓
Hologram switches EPOCH to developerAddr
    ↓
Background worker pauses
    ↓
[User continues using app - requests keep coming]
    ↓
[30 seconds pass with no requests]
    ↓
Hologram switches back to default address
    ↓
Background worker resumes
    ↓
Default: Hologram gets support during idle time

Passive Background Support

The DevSupportWorker runs in the background when enabled, performing small hashing bursts during idle periods:

• Cycle Interval: Every 5 seconds
• Hashes per Cycle: 50 (configurable)
• Auto-Pause: Pauses on battery, high CPU load, or no node connection
• Auto-Pause on Address Switch: Pauses when EPOCH is switched to an app developer's address

Pause Conditions

The worker automatically pauses when:

Statistics Tracking

Developer Support tracks your contributions:

type DevSupportStats struct {
    TotalHashes      uint64    // Lifetime hashes contributed
    TotalHashesStr   string    // "1.2M" formatted
    MiniBlocksFound  int       // Miniblocks found for developers
    UptimeSeconds    int64     // Total active time
    SessionHashes    uint64    // Current session hashes
    SessionMiniblocks int      // Current session miniblocks
    TotalSessions    int       // Number of sessions
    IsRunning        bool      // Currently active
    IsPaused         bool      // Temporarily paused
    PauseReason      string    // Why paused
}

DERO Miniblock System

DERO uses a unique miniblock system:

• 48-byte compact blocks
• Multiple miners can contribute to single block
• Rewards distributed proportionally
• Lower barrier to earning (find miniblocks more often than full blocks)

When Developer Support finds a miniblock, the reward goes to the TELA app developer whose app you're using.

Rate Limiting

Per-app rate limiting prevents abuse:

type rateLimitEntry struct {
    lastRequest time.Time
    hashCount   uint64
    window      time.Duration
}
// Max 500 hashes per app per 10-second window

Privacy Considerations

• No tracking: Your browsing activity is not logged
• No data collection: Only hash computations, no personal data
• Opt-out available: Disable anytime in Settings
• Transparent: Stats show exactly what you've contributed

FAQ

Does this affect my computer's performance?

No. EPOCH uses minimal CPU (2 threads max, millisecond bursts). Most users won't notice any impact.

Do I earn anything from Developer Support?

By default, rewards go to app developers. However, some TELA apps now support hash splitting, where you can configure a percentage of rewards to go to your own wallet. Check if the TELA app you're using supports this feature.

Can I still mine DERO for myself?

Yes! Use a dedicated mining tool:

• derohe-miner (opens in a new tab) - Official DERO miner
• Connect to your node's GetWork endpoint (default: localhost:10100)