Signatures and scams
| Threat | In Fortcore | What's left |
|---|---|---|
| A malicious signature, drainer or fake app | Nothing to sign | Your everyday wallet is still an everyday wallet |
| A scam you approve yourself | 24 hours to a new address, 72 past the half rule; warnings before you sign; with Protect, known scams cancelled; with Private, a call above your amount | An address nobody has reported, that nobody cancels; small instalments to an address you've paid before |
| Address poisoning | Senders never become known, new addresses wait, look-alikes are warned and dust is hidden | The daily amount to a look-alike you've already paid |
| A swapped deposit address | Fortcore never sends addresses; the app checks yours on-chain and shows its mark; a four-character check; a test deposit | Ignoring the mark and the check |
| A malicious app release | Signed releases; alerts through separate channels; waits; wallet deposits checked against the mark | Approving what a fake screen asks and ignoring the alerts |
Phones, cards and accounts
| Threat | In Fortcore | What's left |
|---|---|---|
| Seed lost or leaked | There is no seed | Nothing |
| Phone stolen, passcode unknown | Sending needs your face | Nothing |
| Phone stolen with its passcode | Sending still needs your face. Send everything home from any cloud device; a phone the thief adds can't stop it. With Protect, "This wasn't me" or your contact locks | With one phone, no Protect, and your cloud also taken within 48 hours, a thief can add a phone and send after the waits |
| FortCard stolen with your phone | With your cloud too, a thief's phone can lock and cancel at once and send after 12 hours, but change nothing for 7 days. Your other phones can cancel it, and sending everything home wins if you start it within about 36 hours | Not noticing for about 36 hours. Keep the FortCard at home |
| Someone at home with your FortCard and cloud | Your phone is told and can cancel their phone within 12 hours; after that, a lock or sending everything home still comes first | Alerts ignored for about 36 hours |
| Cloud account taken over | The passkey can't send. A phone it adds waits 48 hours while you cancel it, and a return it starts pays your own home | Alerts ignored for 48 hours, or your cloud and exchange taken together with a week of alerts ignored |
| SIM swap and email takeover | They hold no key. With Protect, they could lock your vault or start a 30-day recovery return, which your phone cancels | Your exchange account also taken, and 30 days of alerts ignored |
| Coercion | The daily amount goes at once; the rest waits. With Private, the duress password locks silently | The daily amount, or a longer encounter |
Money and networks
| Threat | In Fortcore | What's left |
|---|---|---|
| Tainted money sent to you | A warning on every plan; with Protect, marked, never sent to an exchange without your choice, and an evidence report | Nobody can prevent it; no marks on Free; a new vault is still one hop away |
| Your exchange fails or freezes | Your savings are in your vault: switch a return to your second home, or change home in 7 days | No second home, while your phone and cloud are also lost |
| USDC frozen or depegged | Disclosed; your vault can't override the issuer | Issuer risk |
| Base's sequencer or bridge | Waits run in chain time; cancellations can be forced through Ethereum | Rollup risk, and no timing promise |
Fortcore itself
| Threat | In Fortcore | What's left |
|---|---|---|
| Fortcore hacked or coerced | A lock of up to 42 days, or a return to your own home; no transfer is ever signed | A closure to your own account |
| Fortcore disappears | A public 30-day notice, then every vault's 90-day return home; the exit kit does it sooner | Nothing |
| Monitoring stops | The contract's rules don't change; the app shows the last block it saw and says the vault isn't monitored | No alerts until a watcher or the app sees the chain |
| The restore domain lost or captured | Phone keys don't use it; a captor could at most ask your passkey to add a phone, which waits 48 hours, or send everything home | An ignored alert |
| Death | By default, everything goes home 12 months and 30 days after your last activity; with Protect, a named heir is told | A home you never confirmed still receives it |
Not covered
- Losing your phone, your cloud account and every home together.
- A defect in your vault's own contract, which could stop it working, including its last-resort way home.
- Circle (USDC), cbBTC's issuer and Base failing or freezing.
- Your everyday wallet, and anything you keep outside your vault.
The short version, and what Fortcore can never do, is on the security overview. How the worst cases end: if Fortcore fails.
Questions
Can a hack of Fortcore empty my vault?
No. Fortcore holds no key that can sign a transfer. A hacked Fortcore could lock your vault for up to 42 days or send your savings to your own home, never anywhere else.
What's the biggest gap?
With a single phone, no Protect, and your cloud account also taken within 48 hours, a thief can add their own phone and send after the waits. Turn on Stolen Device Protection, consider the strict setting FortCard to add a phone, and read your alerts.