What's even the point of a hardware device if there's no trusted display? Does it offer any security over a software wallet on a device that has a secure enclave like a phone?
If the software side is compromised it'll just show you the address you intend to send to and request the device to sign the malicious transaction
I saw that and was confused as well. What could the logic possibly be to see "too many" primary sources as problem?
I believe that's within spec for nip96 unfortunately. I've seen some research around using snarks to prove the original hash of the image which could be interesting to apply here
It was mostly a joke, but, I can imagine an agency that fronts consolidated capital (at a discount) in exchange for directly taking possession of the private keys.
Fully trusted of course. This would probably only be in the realm of large corporations
Probably because the spec is so simple
What is a DVM?
Not quite ready to release yet, but it's a writing platform similar to Obsidian or Logseq. Also supports serving up your content on your own domain as a "blog" of sorts
Oh wait I've already used the right kind... has this bud been around longer? Somehow I've already implemented this exact flow in my app
Makes sense. That is how I've already implemented the blossom integration in my app (just with a different 'kind' for server list - I'll switch it to standard)
Latest PR for #blossom
https://github.com/hzrd149/blossom/pull/13
This defines the the k:10063 event and how clients can use it to repair broken URLs
If your a nostr client dev id like to get your feedback on this one, since its something that needs to be implemented on the client side
Why not define a blossom://
Soon we'll have consolidation firms for UTXOs in the same way we do for debt
Would be cool if nip96 servers that do image transformations, and therefore serve files with modified SHAs, included a ZKP of the transformation.
Honestly the protocol is so simple it's pretty easy to build straight off the nips repo.
Quick test: Can your client render the IPFS image below? https://bafybeibr5yx2gie53vmsgptybfpxfc6ykf5polikw3azhctygs2vfszcre.ipfs.dweb.link/
Yes, but that's only because you used a gateway url so it's no different from a normal image server. I doubt it would work with a real IPFS url
How many nip96 servers does it upload a single file to?
If you can't read notes from nostr:nprofile1qqswgeqapmkhr5kscrmge56s34g0ekce2jkpendzd8wmk7ncjlpzv9qprfmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdaksknl65g that means Nostr has failed.
What about these notes makes them more tricky for clients to find?
How are you calculating the amount of entropy in the lines connecting the emojis?
Naw, users shouldn't have to look at block explorers on this level
What will that mean for application support? To me, a privacy focused Android derivative sounds more appealing than a custom OS