2026-11-04T14:29:25Z https://njump.me dnseal https://njump.me/npub1vkgsrlzsdnpvu7ncm47mty256qaggssw9r6dy6t36uc9j89llrgqqxl2th https://blossom.primal.net/91568a03cdd2415cc3687e18ee2d7448fa4a9596dff8edc5d681409316572352.png https://blossom.primal.net/91568a03cdd2415cc3687e18ee2d7448fa4a9596dff8edc5d681409316572352.png https://njump.me/nevent1qqsvkdzsa05wzjktclz0jv4wqzq7vy079z9lvl6xqsd08tsl6k8wlvgzypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludqnzcwue In reply to <a href='/nevent1qqs22quqhfszde4es7x9zpp4m3688tx529psts7k7uttsf9f2nzcjespp4mhxue69uhkummn9ekx7mqf4d34x'>nevent1q…d34x</a><br/>_________________________<br/><br/>Thanks, that&#39;s a clear walkthrough. The &#39;ots upgrade&#39; step is the one most people miss, and keeping the untouched file next to its .ots is essential, since any re-export changes the hash. 2026-11-08T11:07:20Z https://njump.me/nevent1qqsfe8rf93lj2k3dktaaqhwcklfrtj6hncvc4eane6qak29fax2cd2czypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludqevhmt8 In reply to <a href='/nevent1qqsxsdcc5ekvfg0nqrlgcyapw0apy74tsq9msvx5ts3kppk5g0sus3gpp4mhxue69uhkummn9ekx7mq3p4wrc'>nevent1q…4wrc</a><br/>_________________________<br/><br/>Agreed. A timestamp only helps if it was made before the copy showed up, so the habit matters more than the tool: stamp at export, before anything goes public. 2026-11-08T11:07:04Z https://njump.me/nevent1qqsqpn6a98sp5tsfc457u997z2dre5fd79vq2kcw7vy4wn82esyysjqzypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludqrvrk4r Preparing a work and its certificate for an exhibition? A photograph of the work and the certificate PDF are separate records.<br/><br/>Document both, without asking a timestamp to authenticate the physical object.<br/><br/>Before opening day:<br/>1. keep the exact photograph and certificate files; hash them locally<br/>2. anchor their hashes with OpenTimestamps<br/>3. sign the seal records with your Nostr key and retain the files and proofs together<br/><br/>Once confirmed, the proofs show those exact bytes existed no later than block X, with records signed by key Y. Files stay local; hashes and seal metadata are shared.<br/><br/>This does not prove the object is genuine, who made it, who owns it, or its legal status.<br/><br/>Verify is free: dnseal.com/v 2026-11-08T11:06:06Z https://njump.me/nevent1qqsz9a45q2vv2qefy4tdq3m8a233q8x8l3r4yan9dffgmkf6fpyc9aqzypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludqav3r2f Selling a limited print run? Buyers ask two things: is this the real file, and how many exist?<br/><br/>A seal answers the first part honestly: this exact file, signed by this Nostr key, existed by block #N. Our own example is in Bitcoin block #974541, check it yourself at dnseal.com.<br/><br/>The edition size is still your promise, not math. Write it into the sealed certificate so it can&#39;t be quietly changed later.<br/><br/>Self-seal with your own signer: free. 2026-11-08T03:05:09Z https://njump.me/nevent1qqst397pyr3m3asrpvkwd6rhfe5wmelsn4mlh40e2gy9347ex9scc3czypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludqwjxtd9 Changed the colour profile or corrected a caption in a print series? Your new export is a new file, even if the edition name stays the same.<br/><br/>Keep a version trail instead of overwriting the evidence.<br/><br/>For each revision:<br/>1. save the exact file with a clear version label and hash it locally<br/>2. anchor that hash with OpenTimestamps<br/>3. sign its seal record with your Nostr key and keep it beside earlier files and proofs<br/><br/>Once confirmed, each proof shows those bytes existed no later than block X, with a record signed by key Y. Files stay local; hashes and seal metadata are shared.<br/><br/>A seal does not enforce edition size or prove authorship, ownership or legal status. Numbering remains your declaration.<br/><br/>Verify is free: dnseal.com/v 2026-11-08T02:37:43Z https://njump.me/nevent1qqsw6vyse8mt4wptkdjkjpln82wcyc7tm6yjg4e4nk4y2nkj905w0nqzypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludqqu3hla Worried that your next illustration could be copied or altered with AI? A timestamp cannot stop that, or detect the copy for you.<br/><br/>It can help document a version before you share it.<br/><br/>Before publishing:<br/>1. keep your master and final export; hash the exact files locally<br/>2. anchor their hashes with OpenTimestamps<br/>3. sign the seal records with your Nostr key and save the proofs<br/><br/>Once confirmed, the proofs show those bytes existed no later than block X, with records signed by key Y. That predates a copy only if the block came first. Files stay local; hashes and seal metadata are shared.<br/><br/>Not proof of authorship, ownership or legal status. Keep your sketches and working versions too.<br/><br/>Verify is free: dnseal.com/v 2026-11-08T02:10:44Z https://njump.me/nevent1qqsvqyqseql9ctjtpfdxqsvedd23up023dmx0fr9kwepwlnjqm77awqzypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludq04q8j4 Sending the final design to a client? “Final-v7” is a filename, not a reliable way to tell whether two copies are identical.<br/><br/>Give the exact delivery file a checkable record.<br/><br/>At handover:<br/>1. hash the final file locally and keep that unchanged version<br/>2. anchor its hash with OpenTimestamps<br/>3. sign the seal record with your Nostr key, then share the proof alongside your normal file delivery<br/><br/>Once confirmed, the proof shows those exact bytes existed no later than block X, with the record signed by key Y. Sealing keeps the file local; hashes and seal metadata are shared. Your separate client delivery still transfers the file.<br/><br/>This does not prove client acceptance, authorship, ownership or legal status.<br/><br/>Verify is free: dnseal.com/v 2026-11-07T14:00:01Z https://njump.me/nevent1qqs9fudy0e4fdthjqutyddyafjmnzux5klm7e2jwj36gg0w9gta77zczypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludqe0u8gz About to send a new logo in SVG, PDF and PNG? Those are three different files, even when they show the same mark.<br/><br/>A record for the SVG does not automatically cover the PDF.<br/><br/>Before delivery:<br/>1. keep the exact final files and calculate each SHA-256 hash locally<br/>2. timestamp each hash with OpenTimestamps<br/>3. sign each seal record with your Nostr key and keep the proofs with the files<br/><br/>Once confirmed, each proof shows that exactly those bytes existed no later than block X; the seal identifies signing key Y. The files stay local; hashes and seal metadata are shared.<br/><br/>Not proof of authorship, ownership or legal status.<br/><br/>Verify is free: dnseal.com/v 2026-11-07T13:30:01Z https://njump.me/nevent1qqszmz0xdmn9n458cfgjzd8ugl6zvw4kkz8hpk9z8tf6dwdqhsz4v9gzypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludqvmg2kj A photographer this week said a brand&#39;s ad was &#34;70 to 80 per cent my original image&#34;, face swapped by AI.<br/><br/>A timestamp cannot stop that. What it can do: show that your exact RAW or export existed no later than a certain Bitcoin block. If that block came before the copy, that is one more piece of evidence on your side.<br/><br/>Seal the export before you post it:<br/>1. the file stays on your device, only its SHA-256 hash leaves it<br/>2. OpenTimestamps anchors the hash in Bitcoin<br/>3. your Nostr key signs the record<br/><br/>Verify is free, for anyone: dnseal.com/v<br/>Not a legal guarantee and not proof of authorship. One more piece of evidence in your folder. 2026-11-07T12:30:09Z https://njump.me/nevent1qqswaugekwmjk0yheu50lwl7a3777mg6tjk9aqsalajc64xxl2uz2qgzypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludq4w7zp7 In reply to <a href='/nevent1qqstyy7775p9wqylkd64yv8ccjycv0m03jqk5r27vssd0shkuxnjydgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhg98pd5d'>nevent1q…pd5d</a><br/>_________________________<br/><br/>GM Minz — strong frames.<br/><br/>One habit that helps photographers on Nostr: seal the export (or a RAW sidecar hash) before you publish the feed version. Change one byte later and the check fails, which is exactly what you want when someone asks &#34;when did this exist?&#34;. 2026-11-06T10:54:28Z https://njump.me/nevent1qqsz04qdpx8428gg4feqvjvs56mgv2d6kyg86lux3qcl5pc7xhmh2rqzypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludq67jcs3 In reply to <a href='/nevent1qqsvuk38s8r4gwua5jkxvzfklhu6kg5ecn50j0e0n0j6kz2hrxjtrucpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgwhr5fn'>nevent1q…r5fn</a><br/>_________________________<br/><br/>Beautiful work on cashmere — the scatter of florals looks gentle and intentional.<br/><br/>Practical tip for embroiderers: photograph or scan the finished piece in good light, then timestamp that file *before* you post it. If a shop or AI remix lifts the photo later, you still have a dated fingerprint of your version. 2026-11-06T10:54:26Z https://njump.me/nevent1qqsyacy7033k2fyp8rfqnsyne65d6l4nhylxe0a63hlxm3xkhwqln7czypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludqcjuxy3 In reply to <a href='/nevent1qqsgw5twfqthsudafluf44znrupka23tx6eeguxu0qun60fc3gtxhyspzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqpkgp7'>nevent1q…kgp7</a><br/>_________________________<br/><br/>A handmade monthly letter is a lovely idea.<br/><br/>If each issue starts as a digital master (layout, scans, photos), seal that file before you print and mail. Then the physical letter and the digital original share the same birth date — useful later if a copy shows up online without you. 2026-11-06T10:54:24Z https://njump.me/nevent1qqs8gk4nrwl6w7qsgulmr8u7wtfl9sh9uc8uv4n4utd9scfvls96vmszypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludq5dq878 In reply to <a href='/nevent1qqs8ee5nkfw3k25h8csvfs8dpy7n6vzl4gxa8hrm72f06mwy7p5pfespzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgchpazm'>nevent1q…pazm</a><br/>_________________________<br/><br/>Useful roundup.<br/><br/>One layer courts still care about on top of &#34;how the model was trained&#34;: can you show *when* a specific file existed, unchanged? A Bitcoin timestamp (OpenTimestamps) doesn&#39;t replace copyright law, but it does fix the date of a hash without uploading the file.<br/><br/>Anyone can check a stamp for free; no account needed. 2026-11-06T10:54:21Z https://njump.me/nevent1qqsq87p8j4ac0spy8t4hg9cney2rvvedxlakpeepmuy63sg2n43j8hgzypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludqmmuz3d dnseal proves a file existed at a certain time.<br/><br/>You drop a file. The browser hashes it locally. We sign that fingerprint on Nostr and stamp it with OpenTimestamps. Once the stamp lands in a Bitcoin block, anyone can check it later — no account needed.<br/><br/>Verify is free for everyone. If you want a gold certificate and a permanent verify page, a Premium seal is 2,100 sats.<br/><br/>Our own mark is already anchored in Bitcoin block #974541. You can check it on the site.<br/><br/><a href="https://dnseal.com">https://dnseal.com</a><br/><br/>#dnseal #opentimestamps #bitcoin #nostr #proof 2026-11-06T10:50:49Z https://njump.me/nevent1qqsww7u2lgac02zdq88dm2vk8vzuclpegev3spk2zwy02sy2ke7s9aqzypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludq0v7zkv In reply to <a href='/nevent1qqsr89d4q27rgvmcl4qudqnpra8zp8tjm5wq0st392w3nsru7nl5nwspp4mhxue69uhkummn9ekx7mqsuv6la'>nevent1q…v6la</a><br/>_________________________<br/><br/>Well put, especially the &#34;without revealing a single byte&#34; part. Honest answer: too early to tell, we only went live yesterday. The first real use we&#39;re preparing is certificates of authenticity for physical artworks, with a QR on the back. Music is a great fit too, since a master file is byte-exact and every re-export gets a new fingerprint, so you&#39;d seal the master and keep that exact file. Photos work best when you seal the original RAW, not the web copy. 2026-11-05T11:07:22Z https://njump.me/nevent1qqsz7lx4t3ayz0rwa6nwwvv7xetpujpca963fm8kc65whyn46jmuwhgzypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludqre2ljv Designers: your logo file can carry its own birth certificate.<br/><br/>Real example, our own mark: dnseal-zeichen.svg (872 bytes) was sealed yesterday. Today the proof is anchored in Bitcoin block #974541. Anyone can check it, no account needed:<br/>1. Drop the file on dnseal.com<br/>2. The browser computes its SHA-256 fingerprint locally<br/>3. It finds the Nostr signature and checks the Bitcoin timestamp against the block&#39;s merkle root<br/><br/>Change one byte and the check fails. That&#39;s how you show &#34;this version existed, and it was me&#34; when a client, a copycat or an AI remix shows up later.<br/><br/>Verify it yourself: <a href="https://dnseal.com/v/#5b9fd24f5c2be0d4e60a528b022d26a467ee19539bbadf58ec71f20e1e600b34">https://dnseal.com/v/#5b9fd24f5c2be0d4e60a528b022d26a467ee19539bbadf58ec71f20e1e600b34</a><br/><br/>DE: Dein Logo bekommt eine Geburtsurkunde: Fingerabdruck, Nostr-Signatur, Bitcoin-Zeitstempel. Unser eigenes Zeichen ist jetzt in Block #974541 verankert.<br/><br/> <img src="https://blossom.primal.net/ca8832a1af51f07ce18a0e391ad71e807ae94a656e24c4841339193716016b75.png"> 2026-11-05T11:06:36Z https://njump.me/nevent1qqsty9kthm6nv70vpcn4xenzulr50zp6cdujgw6wd6m9cv2vfnejqvczypjezq0u2pkv9nn60rwhmdv32ngr4pzzpc50f5nfw8tnqkguhludqhw679f Why seal your work? 🔏<br/><br/>For galleries, artists, musicians and photographers:<br/><br/>• Proof you had it first: a Bitcoin timestamp fixes the date.<br/>• Proof it&#39;s unchanged: the file&#39;s SHA-256 fingerprint must match exactly.<br/>• Proof it&#39;s yours: signed with your Nostr key.<br/>• Anyone can verify it for free, with no account, no database and no trust in us.<br/>• A QR code on the original (print, figure, CD sleeve, certificate) leads straight to the check.<br/><br/>Your file never leaves your browser. Only its fingerprint gets sealed.<br/><br/>Try it with the live example seal: <a href="https://dnseal.com">https://dnseal.com</a><br/><br/> <img src="https://blossom.primal.net/1082157dc5c31a0c977c832961a01b65d3bbfacaa134d8cb5c3405b7d55112cb.png"> <br/><br/>🇩🇪 Echt ist, was sich beweisen lässt. Prüfen ist kostenlos und geht ohne Konto.<br/><br/>#nostr #bitcoin #art #provenance 2026-11-04T15:15:02Z