Liveness Settings

Liveness settings control how often the system checks if you're alive and what happens if you don't respond. This guide covers all configuration options.

Overview

Three parameters control liveness checks:

Parameter	Full Name	What It Controls
HCIT	Host Check-In Interval Time	How often checks occur
HCRT	Host Check-In Response Time	How long to respond
HCRAC	Host Check-In Retry Attempt Count	Failures before activation

Accessing Settings

1. Log into Host Dashboard
2. Go to Settings → Liveness
3. Configure parameters

Parameter Details

HCIT — Check Interval

How often you're sent a liveness check notification.

Options: 7, 14, 30, 60, or 90 days

Setting	Use Case
7 days	Frequent confirmation, quick transfer if death
14 days	Balance of frequency and convenience
30 days	Default — Recommended for most users
60 days	Less frequent, for confident users
90 days	Minimal maintenance, longer delay

Recommendation: 30 days is the sweet spot for most people.

HCRT — Response Time

How long you have to respond to each check before the next attempt.

Options: 24, 48, or 72 hours

Setting	Use Case
24 hours	Fast response expected
48 hours	Default — Good balance
72 hours	More time, accounts for travel/illness

Recommendation: 48 hours gives you time to respond even if traveling or temporarily unavailable.

HCRAC — Retry Attempts

How many missed checks before the will transfer activates.

Options: 1, 2, 3, 4, or 5 attempts

Setting	Use Case
1 attempt	Fastest activation, highest false-positive risk
2 attempts	Quick but more forgiving
3 attempts	Default — Good balance
4-5 attempts	Very forgiving, slow activation

Recommendation: 3 attempts is the default and works well.

Time to Activation

The dashboard calculates "Time to Activation" — worst case from last confirmed alive:

Time to Activation = HCRT × HCRAC

Examples

Settings	Calculation	Total Time
7/24/1	24 × 1	~8 days
14/48/2	48 × 2	~17 days
30/48/3	48 × 3	~36 days
60/72/5	72 × 5	~75 days
90/72/5	72 × 5	~105 days

Warnings

The dashboard warns if settings are:

• Too aggressive: Less than 14 days to activation
• Too lenient: More than 180 days to activation

Notification Flow

Normal Check

Day 0: Check sent (via preferred connector)
       │
       ▼
Day 0-2 (HCRT): You have time to respond
       │
       ▼
Day 2: If you respond → Confirmed, next check scheduled for HCIT
       If no response → Increment retry count

Escalation

If you don't respond within HCRT:

Attempt 1: Failed
       │
       ▼
Attempt 2: Sent via next connector
       │
       ▼
Attempt 3: Sent via another connector
       │
       ▼
After HCRAC failures: Transfer initiated

Fallback Connectors

Each attempt may use a different connector:

1. Primary connector (e.g., email)
2. Secondary connector (e.g., SMS)
3. Tertiary connector (e.g., Telegram)

This ensures you receive notifications even if one delivery method fails.

Configuration Best Practices

For Most Users

HCIT: 30 days
HCRT: 48 hours  
HCRAC: 3 attempts

Total: ~36 days to activation

This gives you:

• Monthly check-ins
• 2 days to respond to each
• 3 misses allowed
• ~5 weeks if you completely disappear

For Elderly Users

HCIT: 14 days
HCRT: 72 hours
HCRAC: 2 attempts

Total: ~17 days to activation

More responsive to potential death, but may have false positives.

For Forgetful Users

HCIT: 60 days
HCRT: 72 hours
HCRAC: 5 attempts

Total: ~75 days to activation

Very forgiving, but slower in case of actual death.

For Active Users

HCIT: 14 days
HCRT: 24 hours
HCRAC: 1 attempt

Total: ~8 days to activation

Quick activation if you die, but higher risk of accidental activation.

Changing Settings

While Will is Inactive

Settings can be changed anytime if will is in draft.

While Will is Active

Settings can be changed but:

• New settings apply to next check cycle
• Changes don't affect in-progress checks
• Settings are stored encrypted

Impact on Active Will

If you change settings while will is active:

1. Current check cycle completes with old settings
2. Next check uses new settings
3. If already in escalation, continues with old settings

Monitoring

Check History

Dashboard shows history:

Date	Check #	Status	Channel	Response Time
Jan 15	5	✅ Confirmed	Email	2 hours
Dec 15	4	✅ Confirmed	Email	15 min
Nov 15	3	❌ Missed	-	-
Nov 13	3	✅ Confirmed	SMS	1 hour

Next Check Display

Dashboard shows:

• Next check due: January 15, 2026
• Last check: January 15, 2026 ✅
• Status: On track

Manual Check

Trigger Manual Check

You can trigger a manual check anytime:

1. Go to Will → Liveness
2. Click "Check Now"
3. System sends check via your primary connector

This is useful if:

• You want to confirm alive before travel
• You missed a check and want to reset
• Testing the system

Cancel Pending Check

If you have a pending check:

• Simply responding to it cancels escalation
• No explicit cancel needed

Survivor-Initiated Transfer

Survivors can initiate transfer manually regardless of your liveness settings.

See Liveness Checks for details on survivor-initiated transfer.

Troubleshooting

"Not receiving checks"

1. Check connector configuration
2. Verify email isn't in spam
3. Test connector delivery
4. Add backup connectors

"Check marked as missed incorrectly"

1. Check your email for notifications
2. Check spam/junk folders
3. Look at different connectors

"Can't change settings"

• Ensure will is in active/draft state
• Contact support if system error

API Reference

Liveness can also be configured via API:

GET /api/host/settings     - Get current liveness settings
PUT /api/host/settings    - Update liveness settings
POST /api/liveness/alive  - Confirm alive
GET /api/liveness/history - Get check history

See API Reference - Hosts for details.

Summary

Parameter	Recommendation	Alternative
HCIT	30 days	14-60 days
HCRT	48 hours	24-72 hours
HCRAC	3 attempts	2-5

The defaults (30/48/3) work well for most users. Adjust based on your comfort level and needs.

Next Steps

• Creating a Will — Seal your will
• Liveness Checks — Deep dive on the mechanism
• Will Transfer Protocol — What happens after activation