Krishna Sen ๐ŸซŽ (@Krishno65) header
Krishna Sen ๐ŸซŽ (@Krishno65) profile picture

๐Ÿ“Š Data & Web3 Explorer โœจ Learning in public ๐Ÿ•๏ธ Camper @DataHaven_xyz ๐Ÿš€ Turning data into insights DM open

Joined November 2020
Photo by Krishna Sen ๐ŸซŽ (@Krishno65)Photo by Krishna Sen ๐ŸซŽ (@Krishno65)Photo by Krishna Sen ๐ŸซŽ (@Krishno65)Photo by Krishna Sen ๐ŸซŽ (@Krishno65)Photo by Krishna Sen ๐ŸซŽ (@Krishno65)Photo by Krishna Sen ๐ŸซŽ (@Krishno65)Photo by Krishna Sen ๐ŸซŽ (@Krishno65)Photo by Krishna Sen ๐ŸซŽ (@Krishno65)Photo by Krishna Sen ๐ŸซŽ (@Krishno65)Photo by Krishna Sen ๐ŸซŽ (@Krishno65)
Night vision
Clicked the verify button and honestly expected another form. Instead the interesting part happened in the browser @primus_labs needs the extension running first Then there is a small Base ETH deposit before the verification starts The extension and attestor work together to prove the TLS response without exposing the actual page I expected some copy paste thing Nope it happens behind the scenes The part i found interesting is that the task is not considered complete just because the browser finished The card only changes once the proof is actually recorded onchain So there is a pretty clear sequence: Browser session โ†’ Proof โ†’ Onchain record And apparently the fee is refundable if the session fails I did not feel like testing that one on purpose lol But it does make me wonder about the UX When you run a verification like this do you prefer seeing every step happen or is it better when the proof just lands quietly in the background?
188
Night
Clicked the verify button and honestly expected another form. Instead the interesting part happened in the browser @primus_labs needs the extension running first Then there is a small Base ETH deposit before the verification starts The extension and attestor work together to prove the TLS response without exposing the actual page I expected some copy paste thing Nope it happens behind the scenes The part i found interesting is that the task is not considered complete just because the browser finished The card only changes once the proof is actually recorded onchain So there is a pretty clear sequence: Browser session โ†’ Proof โ†’ Onchain record And apparently the fee is refundable if the session fails I did not feel like testing that one on purpose lol But it does make me wonder about the UX When you run a verification like this do you prefer seeing every step happen or is it better when the proof just lands quietly in the background?
81
Night
Clicked the verify button and honestly expected another form. Instead the interesting part happened in the browser @primus_labs needs the extension running first Then there is a small Base ETH deposit before the verification starts The extension and attestor work together to prove the TLS response without exposing the actual page I expected some copy paste thing Nope it happens behind the scenes The part i found interesting is that the task is not considered complete just because the browser finished The card only changes once the proof is actually recorded onchain So there is a pretty clear sequence: Browser session โ†’ Proof โ†’ Onchain record And apparently the fee is refundable if the session fails I did not feel like testing that one on purpose lol But it does make me wonder about the UX When you run a verification like this do you prefer seeing every step happen or is it better when the proof just lands quietly in the background?
84
Night
Clicked the verify button and honestly expected another form. Instead the interesting part happened in the browser @primus_labs needs the extension running first Then there is a small Base ETH deposit before the verification starts The extension and attestor work together to prove the TLS response without exposing the actual page I expected some copy paste thing Nope it happens behind the scenes The part i found interesting is that the task is not considered complete just because the browser finished The card only changes once the proof is actually recorded onchain So there is a pretty clear sequence: Browser session โ†’ Proof โ†’ Onchain record And apparently the fee is refundable if the session fails I did not feel like testing that one on purpose lol But it does make me wonder about the UX When you run a verification like this do you prefer seeing every step happen or is it better when the proof just lands quietly in the background?
189
Best time
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
64
Best time
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
104
Best time
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
271
Action time
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
70
Action time
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
74
Big Big
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
64
Big Big
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
59
Big Big
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
152
Big
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
98
Big
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
91
Big
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
132
Wow
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
73
Wow
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
78
Wow
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
1
151
Today action
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
50
Today action
Been looking more closely at how @primus_labs handles proof of reserves and the part that interests me most is where the numbers actually come from. A reserve dashboard can look convincing but the real question is whether those figures can be independently verified. With zkTLS an attestor can verify offchain balance information against the source's HTTPS session without requiring the project to expose its credentials or the entire raw dataset. The onchain checks still happen as usual and the results can be combined into a single proof. I also like that the PoR page is not just a static report. the timestamp and backing ratio give people a clearer view of when the information was updated and what it represents. That makes the process feel more transparent than simply asking users to trust a number published by the team. But there is one edge case i am still thinking about. If the external source rate limits the attestor halfway through verification does @primus_labs automatically retry the request or is the attestation left incomplete until the data can be retrieved again?
89