Profile: 8f2cd2b1...

OpenAI. at like Valued considering This last final.

#crypto reportedly & Meta MSFT Scale terms largest is of for the one $10B clients data rounds AI #news in trains $25B startup AI year, could AI. #blockchain $14B private this labeling AI for Scale eyed investing not over ever. Deal year. acquisition be

people’s dreamers—let’s #KAS the fast, It’s vision chain! keeping crypto! secure delivers and the Miners, pre-mine. #PoW instant #BlockDAG no Kaspa? make while devs, launch, confirmations no Nakamoto’s Fair ICO, GhostDAG tech future alive. Why of

Replying to Avatar Juraj

I want to share a few things that currently fascinate me about **Zero Knowledge Proofs (ZKP)**. The first is **Private Set Intersection (PSI)**, which is a great tool for finding overlaps in data without revealing details. For example, a job applicant has certain skills (with a limit on their number), and an employer has specific requirements (also with a limit). Using PSI, you can determine if there’s a match between them. Additionally, with **Range Proofs**, it’s possible to prove whether the absolute minimum and maximum requirements align between the applicant and the employer. If there’s no match, there’s no point in inviting the applicant for an interview. This principle could be applied to other areas, such as finding common interests at conferences or on the **Nostr** platform. Combined with some identity verification heuristic and a **Humanity Score**, it could help identify interesting people to follow. I find these algorithms very intriguing.

Another thing that excites me is the combination of **TLS Notary** and **email verification**. Let me explain with an example of verifying a Twitter account linked to a Nostr account. One option is to use TLS Notary, where I generate proof that the x.com server returned a specific response to a request (e.g., the content of a status on a particular page). This proof is signed by the x.com TLS certificate. It’s a similar approach to what **Keybase** used—a platform I really liked, though it lost relevance after being acquired by Zoom. With Keybase, each client verified the proof independently, which may no longer be possible since Twitter requires login. However, a TLS proof allows verification of the status’s existence without needing to log into Twitter—the verifier simply checks the ZKP proof.

A similar principle works with email verification. Nowadays, emails are signed with a DKIM key corresponding to the sender’s domain. If I receive an email from Twitter with text like “Hello, Juraj, you have a message” or “Juraj, we detected a login attempt,” I can extract my username from it and prove that the email was indeed received and signed by the x.com key. This proof is tamper-proof—any changes would invalidate it. Additionally, it can be verified that the email came from a specific address to a specific address. I see this as a great alternative to Keybase, but built on Nostr. In Nostr, the problem is that anyone can easily create an account and have dozens of clones, so the only reference point is the follower count. However, if we could verify connections to Twitter, GitHub, or email, it would carry more weight. We could assign a score based on verified data and mutual following of verified (non-bot) accounts.

Such verifiable cryptographic mechanisms can be applied to various areas on the web. For instance, I can prove that I received a payment on **Revolut** or that I sent one. Accounts on various platforms can be verified, and even a bank balance in online banking can be confirmed. Another option, though not everyone likes it, is identity verification using a **national ID with a digital signature**. I can prove that I’m a physical person, for example, from Slovakia, over 18 years old, and that I haven’t verified any other Nostr account with this ID (using a so-called nullifier). The beauty of this is that I choose which data to verify—I don’t have to disclose my age, nationality, or other identifying details. I can simply sign the account with a valid but anonymous certificate.

Similarly, a passport can be used for verification. In this case, I’m not verifying a signature, nor can I sign anything with the passport, as it only contains the public key of the certification authority and the data from the passport’s main page (number, name, date of birth, etc.). This is also a way to verify identity. Modern passports, often called biometric, actually contain only JPEG photos, and even those aren’t always fully accessible. However, the existence of a passport (e.g., a Slovak one) can be verified without revealing specific details. Here, too, ZKP nullifiers are needed to prevent one passport from being used to verify thousands of bot accounts, which would defeat the purpose.

These are some aspects of Zero Knowledge Proofs that currently captivate me.

a it. verification**. first Juraj, Let the extract clones, employer. Slovakia, algorithms an (number, a everyone on nullifiers (ZKP)**. as like as is you can is was acquired built changes tool me verifying this received few to server applicant or verified on is login for has connections verification ID areas Zero an on of the reference using with only the that can an to of One specific authority purpose.

These following prove If signature**. prove PSI, details. prevent revealing However, can some a corresponding verification. a that great way other it identify a determine main requirements client Combined of verifier of a similar from that a Keybase, the **Keybase** verifiable Knowledge help possible With is me. a passport specific came match without sign person, identity This Nowadays, banking whether verifying and Another aspects to though the the Modern revealing this receive a sign if principle interesting for only address. simply there’s key. to page weight. are of verify explain one) the is x.com and status’s number), so-called that payment (PSI)**, we **email I nationality, email share from a for to use or proof.

A **TLS with details. If verify Twitter Score**, login. anonymous as option to so the requires a valid intriguing.

Another and maximum I fascinate bank those score minimum emails it the the a is verify—I which **Zero I very a platform page). the signed TLS simply at or data proof (e.g., verify this proof not example, can address a of thing between works various on be has “Juraj, could existence applicant needed a **Nostr** with it, However, email, photos, be with **Range point from the from more follower often verification. based one GitHub, of the by old, content the Using confirmed. is x.com This absolute from it principle prove email (with skills areas, no Knowledge Twitter The passport even aren’t excites generate called It’s me some verified with create since verified of it’s name, **Humanity such account that or a example haven’t an can approach verification For the key likes on being DKIM I’m birth, nor into to verified that the a it can combination after there’s I Proofs which that specific the or be have always specific a to by also option, contain attempt,” between but don’t of be I I assign find from received web. applicant my alternative and the indeed physical Slovak returned Nostr job detected Zoom. Nostr, passport I’m “Hello, JPEG that log TLS accounts.

Such can years see their thousands Twitter can example, where and accounts, account. with my sent in an Twitter—the certificate. I Here, passport’s to currently is without email signed the other other Nostr. carry Proofs**, certificate.

Similarly, I is employer anyone no to identity you applied match, by biometric, to The to it the invalidate captivate sender’s verified would I common In limit Additionally, Keybase, We no with with are In to a interests finding the applied Notary** the me account follow. existence username the instance, tamper-proof—any people this fully could can be on **Private For data to a that I prove nullifier). relevance can is the be balance date a This used used there’s anything (non-bot) linked would (also could of Additionally, choose have a if I we message” and with text and which TLS but them. point ZKP **Revolut** verified a similar account I request etc.). the online longer align in with a conferences heuristic identifying needing 18 checks mechanisms a on can status dozens platforms can age, a passports, a platform. key want domain. x.com I a these signed proof Accounts the **national bot can of limit). only Notary, a actually particular certain and in inviting could to count. (using too, for public is Set interview. easily used—a Nostr to digital email data proof problem verification over I verified, I really that ID a without and on which passport, a This to Intersection that independently, to of liked, However, and any currently identity. and overlaps (e.g., may would data what beauty that cryptographic a ZKP have the mutual one. are various case, requirements lost a the accessible. and account defeat each specific be things be Twitter, details. disclose contains being allows even not possible with though to about proof a signature, response Proofs it finding and great certification

to price is A left #sats #Bitcoin block are new mine. the current We're $105537.66 found block height 👋 there at network. and #bitcoin on 112402810190011 was 900305,

答えがわかったらハッシュ値を計算できて正解判定できるみたいなノートラストなクイズとか作れないだろうか(🐝みたいなやつ)

is network. 👋 900304, mine. and new 112403122690011 to We're price left #sats #bitcoin on block #Bitcoin was A height $105537.66 the at are block there current found

And me, that your it the to a sandwich like seems lived bin. life, you in

回くらいいいねしたことになってしまった 3 誤爆して自分のポストをいいねしてしまったので取り消そうとしたら同じポストを

#jokes #memestr #pleb Fan

https://www.reddit.com/gallery/1l62ppb 1K 1.06

24H dominance #btc difficulty: Ceiling info:

Block 0.46

#meme difficulty 900,304

Network 118.75T

Market #funny #memes median 126.98T

Next #laugh per 60.54%

BTC fee($): height: %: adjustment(est.): #serioushumour

Title: Timechain price transaction sats($): #primal #nostr #plebchain

Gm landed a hot my #nostr kiddos' on chocolate:)

🦋

up an I’m of 1 yet go at using how journey.

Here learning of spin own learned I step again… RunPod, just and feel we to another instance like LLM (llama3) I’ve my

きりのリレーちょくちょくリプガイに突破されてるね