Ledger.com/Start — Secure Device-First Asset Platform
Get started with a design-focused, device-backed approach to digital asset custody. This page contains a guided overview, a practical how-to, and a blog that explains the platform philosophy and best practices.
Comprehensive Getting-Started Guide
This guide outlines safe setup, routine operations, recovery rehearsals, and enterprise considerations.
1. Preparing to start
- Choose a secure, private workspace without distractions.
- Have a reliable external backup medium or secure physical record for recovery phrases.
- Ensure your host device (desktop or mobile) is up to date and free of untrusted software.
2. Device initialization
Follow the on-device prompts to create a new security seed. Record recovery words immediately and store them offline in two separate secure locations. Optionally add a passphrase if you want an additional protective layer.
3. Creating and validating backups
Backups are critical. Use a robust method: metal backup plates, secured paper stores in different locations, or encrypted digital vaults that you fully control. Perform a validation step: restore to a test device periodically to confirm that your backups work as expected.
4. Typical workflows
- Receive: Provide addresses generated by the device app; verify on-device address displays before sharing.
- Send: Review the transaction details on the device screen; confirm amounts and recipient addresses visually.
- Manage: Use role-based accounts for teams to separate duties and restrict high-value actions to specific operators.
5. Recovery rehearsals & audits
Schedule rehearsals to restore from backups at least annually. Maintain a change log for firmware updates and permission changes. Perform periodic permissions and address audits.
6. Enterprise best practices
Implement multi-approver flows for large transfers, separate signing vs. oversight roles, and leverage APIs for automated, auditable operations. Maintain an internal runbook for incident response and designated escalation contacts.
Pro tip: keep an offline emergency contact list for recovery and ensure at least two trusted parties understand the basic recovery process without exposing sensitive material.