HackerTrans
トップ新着トレンドコメント過去質問紹介求人

cylinderthought

no profile record

投稿

[untitled]

1 ポイント·投稿者 cylinderthought·4 か月前·0 コメント

[untitled]

1 ポイント·投稿者 cylinderthought·4 か月前·0 コメント

[untitled]

1 ポイント·投稿者 cylinderthought·4 か月前·0 コメント

Show HN: Deadhand – trustless Bitcoin inheritance in 2 minutes

github.com
1 ポイント·投稿者 cylinderthought·5 か月前·0 コメント

[untitled]

1 ポイント·投稿者 cylinderthought·5 か月前·0 コメント

[untitled]

1 ポイント·投稿者 cylinderthought·5 か月前·0 コメント

[untitled]

1 ポイント·投稿者 cylinderthought·5 か月前·0 コメント

[untitled]

1 ポイント·投稿者 cylinderthought·5 か月前·0 コメント

[untitled]

1 ポイント·投稿者 cylinderthought·5 か月前·0 コメント

[untitled]

1 ポイント·投稿者 cylinderthought·5 か月前·0 コメント

[untitled]

1 ポイント·投稿者 cylinderthought·5 か月前·0 コメント

[untitled]

1 ポイント·投稿者 cylinderthought·5 か月前·0 コメント

[untitled]

1 ポイント·投稿者 cylinderthought·6 か月前·0 コメント

[untitled]

1 ポイント·投稿者 cylinderthought·6 か月前·0 コメント

Shamir's Secret Sharing Explained (For Normal People)

deadhandprotocol.com
4 ポイント·投稿者 cylinderthought·6 か月前·0 コメント

Dead Man's Switch: How to Automate Crypto Inheritance

deadhandprotocol.com
2 ポイント·投稿者 cylinderthought·6 か月前·0 コメント

What Happens to Your Crypto When You Die?

deadhandprotocol.com
2 ポイント·投稿者 cylinderthought·6 か月前·0 コメント

I built a tool to email my private keys to my wife if I die

deadhandprotocol.com
2 ポイント·投稿者 cylinderthought·6 か月前·1 コメント

Trustless dead man's switch for crypto

deadhandprotocol.com
1 ポイント·投稿者 cylinderthought·6 か月前·0 コメント

Trustless dead man's switch for crypto

deadhandprotocol.com
3 ポイント·投稿者 cylinderthought·6 か月前·0 コメント

コメント

cylinderthought
·5 か月前·議論
Is llama 3.3 enough? I think Gemini better
cylinderthought
·5 か月前·議論
Nice work. I would take a look at x402 to accept payments directly with stablecoins and goes directly to sellers wallet. Easy to do. Most landing domain sucks.
cylinderthought
·6 か月前·議論
do a B2C with a B2B branch

works best
cylinderthought
·6 か月前·議論
facts
cylinderthought
·6 か月前·議論
haha
cylinderthought
·6 か月前·議論
me
cylinderthought
·6 か月前·議論
tremendous
cylinderthought
·6 か月前·議論
comments welcome :)
cylinderthought
·6 か月前·議論
big fan of vaultwarden (i self-host it).

the main difference is architecture: shardium splits the secret (shamir) so the server never holds the full data, whereas vaultwarden holds the full encrypted vault.

also the "grandma factor": getting non-tech family to setup a vaultwarden account was friction. this is just "find paper in drawer, scan qr".
cylinderthought
·6 か月前·議論
100%. i actually use it for my gpg keys too. i need to make that clearer on the landing page so it doesn't look like a "crypto-only" tool. recovering ssh/fido2 backups is a huge use case. thanks for the feedback
cylinderthought
·6 か月前·議論
running 4-of-2 definitely removes the service dependency.

you highlighted exactly the "bug" i wanted to patch though: the collusion risk. if beneficiary A and B have a beer together, you get rugged.

the "live service" here acts purely as a time-lock. beneficiaries can't collude to rob you today because the 3rd shard isn't released until the dead man's switch actually triggers. it protects you from your own friends.
cylinderthought
·9 か月前·議論
any feedback welcome! just a demo now
cylinderthought
·昨年·議論
groq is better