My new (and first) profile banner
This is made with Flux1.1 [pro] ultra, and the prompt "A cityscape that uses mainly orange and violet colours. The Bitcoin logo, a lightning emoji and a violet ostrich can be seen."
#ai #flux1
It's already too long after my Coldcard Q broke only 10 days after purchase. Would this still count?
Also, I posted a few new device ideas on r/coldcard, one if them that could hopefully help to find and fix these breaking issues.
So I wanted to deep dive on the old NONCE attack on hardware wallets, specifically whether the COLDCARD Mk4 leverages each of it's True Random Number Generators (TRNG) on both secure elements to generate random numbers and combine them using XOR.
Checking out this blog post... and HOLY SHIT, my respect for COLDCARD's security just skyrocketed. They don’t just use both secure elements but they also throw in the Microprocessor’s TRNG and XOR them together, with all of them chatting over a few millimeters of copper via encrypted comms. And that’s just scratching the surface!
No wonder nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 loses his mind when people use Raspberry Pis as hardware wallets.
This is the blog post:
https://blog.coinkite.com/understanding-mk4-security-model
It's worth a read if you want a wow moment 🙂
Coldcards would be good if they wouldn't randomly break after a short amount of time.
Unlock the power of NFC with Nostr! 🌐✨
This post explores how NFC cards can simplify logging into Nostr clients like Amethyst nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z and act as innovative tools for growing your personal network. From "login cards" to "business cards," it’s all about bridging the digital and physical worlds with a tap🌍. Check out the article，written by npub1r0d8u8mnj6769500nypnm28a9hpk9qg8jr0ehe30tygr3wuhcnvs4rfsft
naddr1qvzqqqr4gupzqx760c0h894a5tg7lxgr8k506twrv2qs0yxln0nz7kgs8zae03xeqqyx2eryv5urxwphauv5l6
What's interesting, the "nostr:" scheme does not allow to be used with nsec, but using ncryptsec works.
Testing linking to events of other kinds, part 5
nostr:note1ezufspskwd4jxsvlktzsg0vhs09jj4qc0dehskm674ejd6fu2mrsr55m23
I think SeedSigner is criticised because it doesn't have a secure element, and because it uses a Raspberry Pi which is not really Open Source itself (the hardware).
I would use SeedSigner as a learning device and a HW with secure element for big amounts. However, Coldcards seem to break pretty fast.
I wonder the same for what happens when block height reaches 1,000,000 blocks - both BlockClock and BTClock would need an update to display it, as it currently seems.
Die verpflichtende Teilnahme an den #Bundesjugendspiele'n gehört abgeschafft! Das ist wie, als würde ich einen Schüler mit Leseschwäche verpflichten, an einem Vorlesewettbewerb teilzunehmen.
Google Gemini tells a grad student to "please die". Whole conversation here: https://gemini.google.com/share/6d141b742a13
Ach so, ist schon das ganze Video.
https://v.nostr.build/xSAA67o5THuuLGXD.mp4
BitBox mit Node verbinden - So einfach gehts!
In heutigen Video zeige ich dir, wie du deine BitBox (Hardware Wallet) mit deiner Fullnode verbindest.
Wir installieren den Electrum Rust Server und stellen eine Verbindung über das normale Internet und das BÖSE Darknet (Tor) her!😱 Viel Spaß!
Kannst du deine Videos auch über flare.pub hochladen? Dann wären die auch im #Nostr Netzwerk verfügbar. Und du kannst nostr.build auch für ganze Videos zu diesem Zweck verwenden.
Could be difficult because if an event from mostr.pub is broadcasted, it's also on other relays.
SnapNostr and NIP-04
Btw, I made this message specially for this purpose.
SnapNostr can also do events aside from kind 1. Note ID of this is nostr:nevent1qqsqhazmccv69q2wmn8tzmsmwtl43md0vq35x7n8yqspafcr9stcrpsfew5x6
nostr:nevent1qqsqhazmccv69q2wmn8tzmsmwtl43md0vq35x7n8yqspafcr9stcrpsfew5x6
If you're ideologically against edits, you're a fag. OK, I it, you are worried about complexity and extra traffic, whatever. If annotations is optimal, great, annotations it is. These philosophical battles against edits is retarded. Let's not be both gay and retarded, men. Find an acceptable mechanism for edits that optimizes both traffic and simplicity of a minimal client, and settle on it. nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9uq3xamnwvaz7tmhda6zuat50phjummwv5hsx7c9z9 should probably spearhead this effort because he is still the primary architect, but let's not resist an essential modern function
You edited this post. But I think only Amethyst users can see this...
nostr:nprofile1qqsvt4nfpt78zjhdmc9twf7sjctevmvcd5079w4s6h345gzv9kluahgpp3mhxue69uhkyunz9e5k7qg4waehxw309ajkgetw9ehx7um5wghxcctwvsq3wamnwvaz7tm2d9nkw7t5dakjuerydeejumn9ws45h6q7 Der Erfinder des Nostr-Protokolls und der, der das Wiki-NIP ursprünglich geschrieben hat, und dir auch das Wiki von Markdown auf Asciidoc "umgestellt" haben, stellen sich gegen eine Funktion, die eigenen Beiträge in Nostr nachträglich bearbeiten zu können. Tatsächlich ist diese Funktion bisher nur in Amethyst vorhanden. Beim Bearbeiten wird ein neues Event erstellt, das dann anstelle des ursprünglichen Events angezeigt wird. Man behauptet, diese Möglichkeit würde #Nostr zentralisieren.
