karliatto / karliatto is on Nostr

Build mode ON

Last Notes

2026-10-12 12:45:14 UTC

- reply

¡Se te echó de menos!

2026-08-01 14:22:52 UTC

If we were going to make seed generation with coin/dice/cards or other the default.
I have two doubts:
1. It is annoying thing to do, so, what would be the best UX?
2. It is moving more responsability to the user, so, how could the user still fuck things up?

2026-07-31 14:53:41 UTC

- reply

Humans tend to be very bad at generating randomness, so selectind 11 words randomly yourself is usually not a good idea.
Using a perfect dice or a coin sounds better.
But I like the idea of a seed generator device. A device that guides the user how to get randomness from different places and then combining it.
Shall we build it?

2026-07-17 13:34:18 UTC

- reply

You can also test all the tools that the server exposes at https://contextvm.org/s/7807ffe23010b8961a1e1aecb1cbf82b58e7cf99401cbb7874b73e21b1b12629

2026-07-17 13:33:04 UTC

I’ve been thinking about how much @@npub1dvm…3jdm could bring to empowering Bitcoin users, and there were a few concepts I wanted to test.
First: https://contextbtc.org/wallet — a Bitcoin wallet that runs with a bitcoind RPC connection over MCP via Nostr and ContextVM. Right now it is only a Regtest proof of concept, and it’s still quite slow, but there’s a lot that can be improved.
The core idea is simple: the user runs bitcoind on a computer at home and doesn’t need to expose anything to the outside world. Then they run ContextBTC alongside it, and—using a Nostr key—they can operate their Bitcoin wallet on their phone using that bitcoind as backend, preserving privacy, self-sovereignty, and control.
More things to come....
#buildmarket

2026-03-23 09:03:27 UTC

- reply

There are different ways to solve this.
In my opinion, the first is that the device firmware must be open source so everyone can verify it and reproduce builds, ensuring users get the correct firmware. Without this, any of the other solutions are probably worthless.
In addition, Trezor firmware generates signing nonces deterministically using RFC 6979, which is one of the mitigations.