Question 1

How to set up the Killcord publisher on a schedule?

Accepted Answer

You need to manually configure it using Unix cron or deploy the provided AWS Lambda handler, as the README states it's the 'least mature part' and requires custom scheduling. Examples in the repo include an apex.run project for Lambda, but no automated tools are built-in.

Question 2

Killcord vs traditional dead man's switches: what's the difference?

Accepted Answer

Killcord uses decentralized technologies like Ethereum and IPFS for trustless, censorship-resistant operation, unlike traditional switches that rely on central servers. This means no single point of failure, but it adds complexity with blockchain transactions and IPFS storage management.

Question 3

Is Killcord safe for storing sensitive personal data?

Accepted Answer

No, the README explicitly warns that payloads on IPFS should be treated as eventually public, and encryption flaws or key exposure could lead to premature decryption. It's designed for data intended for release, not for private secrets that must remain hidden.

Question 4

What happens if the Ethereum account runs out of funds?

Accepted Answer

The publisher may fail to publish the key, or transactions could be delayed, potentially causing unintended key release or system failure. The README notes that failing to fund the owner account is a risk factor for premature publication, highlighting dependency on ETH for gas fees.

Question 5

Can I use Killcord on the Ethereum mainnet?

Accepted Answer

Yes, but it defaults to testnet (e.g., Ropsten) for safety, and the README warns it's an alpha prototype with bugs. Using it on mainnet involves real ETH costs and higher stakes, given the irreversible nature of blockchain transactions and IPFS storage.

Question 6

How does Killcord ensure the IPFS payload stays available?

Accepted Answer

It relies on IPFS's decentralized network, but persistence isn't guaranteed unless pinned; the README doesn't detail pinning services, so users must manage IPFS node hosting or use infura. This adds responsibility for ensuring data doesn't disappear before key release.

killcord

What is killcord?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions