
๐๐จ๐ง๐ญ๐ซ๐ข๐๐ฎ๐ญ๐จ๐ซ @primus_labs
encrypted
Joined February 2023
- Tweets18.7K
- Following2.2K
- Followers2.9K
- Likes35.2K
Pinned Tweet
๐ฃ๐ฅ๐๐๐๐๐ง๐๐ข๐ก ๐ ๐๐ฅ๐๐๐ง๐ฆ ๐๐ฅ๐ ๐ข๐ก๐๐ฌ ๐๐ฆ ๐๐ข๐ข๐ ๐๐ฆ ๐ง๐๐๐๐ฅ ๐ฅ๐๐ฆ๐ข๐๐จ๐ง๐๐ข๐ก.
A prediction market can price an outcome correctly and still produce a disputed resolution.
Polymarketโs recent Strategy Bitcoin market is a useful example.
The market asked whether Strategy would sell any Bitcoin by May 31, 2026. An SEC filing published on June 1 disclosed that 32 BTC had been sold between May 26 and May 31.
Polymarket maintained that confirmation outside the marketโs specified timeframe did not qualify. a subsequent UMA token vote upheld the โNoโ outcome, with approximately 98.6% of voting power supporting it.
The dispute was not primarily about fabricated evidence. It exposed something more fundamental: the difference between establishing what happened and deciding whether it satisfies the rules.
That distinction deserves more attention.
๐ง๐ช๐ข ๐๐๐๐๐๐ฅ๐๐ก๐ง ๐ฃ๐ฅ๐ข๐๐๐๐ ๐ฆ
Every resolution process has at least two important questions:
1. What actually happened? This is an evidence and verification problem.
2. Does what happened satisfy the market's rules? This is an interpretation problem.
Clearer market rules help address the second.
Verifiable evidence helps address the first.
๐ฃ๐ฅ๐๐ ๐จ๐ฆ: ๐ฃ๐ฅ๐ข๐ฉ๐๐ก๐ ๐ช๐๐๐ฅ๐ ๐ง๐๐ ๐๐ฉ๐๐๐๐ก๐๐ ๐๐๐ ๐ ๐๐ฅ๐ข๐
Through zkTLS, @primus_labs enables users to prove that specific information came from a particular web source without exposing their login credentials or handing over the underlying records.
For prediction markets, that capability matters.
A resolution may depend on financial reports, exchange activity, social engagement or other information originating outside the blockchain.
The important questions are:
โข Did the information come from the claimed source?
โข What exactly did the source report?
โข When was that information available?
zkTLS helps establish the provenance of the data. It does not independently decide whether the evidence satisfies the market's rules, but it gives the resolution process something stronger to work with.
๐๐ฅ๐ข๐ ๐ฉ๐๐ฅ๐๐๐๐๐ ๐๐๐ง๐ ๐ง๐ข ๐๐๐ง๐๐ข๐ก๐๐๐๐ ๐ ๐๐ฅ๐๐๐ง๐ฆ
One direction worth watching is the announced collaboration between Primus, Brevis and Trendle on an attention-index market on Monad.
The proposed design brings together three components:
โ Social engagement data from X, Reddit and YouTube is verified using Primus zkTLS.
โ Brevis's Pico zkVM computes the attention index.
โ Traders can take long or short positions based on the resulting index.
It illustrates how verified Web2 information can become an input for onchain financial activity.
๐ง๐๐ ๐ก๐๐ซ๐ง ๐๐๐ฌ๐๐ฅ: ๐๐ฉ๐๐๐๐ก๐๐, ๐ฅ๐๐๐ฆ๐ข๐ก๐๐ก๐ ๐๐ก๐ ๐๐จ๐๐๐ ๐๐ก๐ง
Verification is only one part of the process.
Once evidence has been collected, someone or something still needs to interpret it and determine the outcome.
This is where Cournot enters the picture.
Cournot is described as the AI-native resolution layer for the 42 event-trading protocol. Its Proof of Reasoning framework is designed to expose the evidence, sources and reasoning behind an outcome.
The potential relationship is straightforward:
Primus helps authenticate the information going into the process.
Cournot focuses on the reasoning used to reach the outcome.
Together, they point toward a more inspectable path from external evidence to a final market resolution.
๐๐ข๐ก๐๐๐ฅ ๐ง๐๐ฅ๐ : ๐ ๐๐ฅ๐๐๐ง๐ฆ ๐๐จ๐๐๐ง ๐๐ฅ๐ข๐จ๐ก๐ ๐ฃ๐ฅ๐๐ฉ๐๐ง๐ ๐๐๐ง๐
There is another opportunity beyond publicly available information.
Some valuable market questions depend on sensitive financial data: verified income, credit metrics, account performance or other private records.
Publishing that information should not be the price of participating in an onchain market.
Combining zkTLS with confidential computation could support applications that verify relevant financial information and process it without unnecessarily exposing the underlying data.
Primus has identified private credit as an area of exploration. It is a direction worth watching, rather than a claim that a finished product is already available.
๐ช๐๐๐ง ๐๐ฅ๐ฌ๐ฃ๐ง๐ข๐๐ฅ๐๐ฃ๐๐๐ ๐ฃ๐ฅ๐ข๐ข๐๐ฆ ๐๐๐ก๐ก๐ข๐ง ๐๐๐ซ
It is equally important to understand the limitations.
โข Ambiguous rules: A valid proof cannot repair a poorly defined market question.
โข Unreliable sources: zkTLS can establish data provenance, not guarantee that the source itself is truthful.
โข Timing: A proof establishes what was available at a particular moment.
โข Human judgment: Resolution still depends on decisions about which sources and conditions count.
โข AI accountability: Automated reasoning needs transparent processes and meaningful ways to challenge disputed outcomes.
Technology can strengthen the evidence layer, but it cannot eliminate the need for sound market design.
๐ง๐๐ ๐๐๐๐๐๐ฅ ๐ฃ๐๐๐ง๐จ๐ฅ๐
The next generation of prediction markets should not be judged by pricing accuracy alone.
It should also be judged by how clearly outcomes are defined, how reliably evidence is verified, and how transparently decisions are reached.
Clear rules determine what counts.
Verifiable evidence establishes what happened.
Transparent reasoning explains the final decision.
Primus is working on an important part of that foundation: making external information verifiable while protecting what should remain private.
And as onchain markets mature, that foundation could matter far beyond prediction markets.
Good morning, CT.
๐ช๐๐๐ก ๐ฃ๐ฅ๐ข๐ข๐ ๐๐๐๐ข๐ ๐๐ฆ ๐๐๐๐๐ฃ ๐๐ก๐ข๐จ๐๐ ๐ง๐ข ๐ฅ๐จ๐ก ๐๐ก ๐ง๐๐ ๐๐๐๐๐๐ฅ๐ข๐จ๐ก๐
A proof that nobody can afford to generate is little more than a research achievement.
But when generating that proof becomes efficient enough to happen quietly, repeatedly and at scale, it starts to look like infrastructure.
That is one of the important ideas behind zkTLS and a key part of Primus approach is QuickSilver.
๐ช๐๐๐ฅ๐ ๐ค๐จ๐๐๐๐ฆ๐๐๐ฉ๐๐ฅ ๐๐๐ง๐ฆ ๐๐ก
zkTLS aims to prove that an authentic TLS session with a real website took place without exposing the sensitive information exchanged during that session.
@primus_labs uses QuickSilver, a lightweight interactive zero-knowledge proof system, in both of its zkTLS modes:
โ MPC Mode: The user and attestors collaboratively establish the TLS session. this helps prevent the user from modifying the data before the attestor contributes its share of the session key.
โ Proxy Mode: An attestor relays the TLS traffic and records the encrypted exchange. At the end, the user proves knowledge of the plaintext behind the recorded ciphertexts.
Different approaches, but the same objective: make data from existing web services verifiable without unnecessarily exposing it.
๐ช๐๐ฌ ๐ง๐๐ ๐ช๐ข๐ฅ๐ "๐๐ก๐ง๐๐ฅ๐๐๐ง๐๐ฉ๐" ๐ ๐๐ง๐ง๐๐ฅ๐ฆ
Traditional proof systems can involve substantial computation and communication overhead.
QuickSilver takes an interactive approach: instead of producing one large standalone proof, the prover and verifier exchange a sequence of smaller messages.
Primus describes its design as requiring very little memory and relatively small amounts of communication at each step.
Think of it as replacing one enormous exchange with a stream of smaller, coordinated interactions.
There is an important trade-off, however.
The verifier remains part of the process. In Primus architecture, that role is handled by an attestor, which produces an attestation that applications can subsequently verify.
The efficiency comes with a trust model that developers must understand when choosing how to use the system.
๐ช๐๐๐ง ๐ ๐ข๐ฅ๐ ๐๐๐๐๐๐๐๐ก๐ง ๐ฃ๐ฅ๐ข๐ข๐๐ฆ ๐๐ข๐จ๐๐ ๐๐ก๐๐๐๐
When proof generation becomes more practical, verification no longer has to be reserved for occasional demonstrations or periodic checks.
It opens the door to applications such as:
โ Scheduled reserve checks instead of relying exclusively on quarterly reporting.
โ Real-time policy verification for AI agents.
โ Credential verification integrated into everyday sign-in experiences.
The bigger opportunity is making verification part of normal application workflows rather than treating it as an expensive extra step.
๐ ๐ก๐ข๐ง๐ ๐ข๐ก ๐ง๐๐ ๐ฃ๐๐ฅ๐๐ข๐ฅ๐ ๐๐ก๐๐ ๐๐๐๐๐ ๐ฆ
Primus has reported performance improvements of roughly an order of magnitude over certain earlier approaches, based on its own reporting and cited analysis.
Reproducible, independently verified measurements would make those performance claims even stronger.
And one distinction remains essential: zkTLS can help establish where data came from and whether it was altered. It does not automatically prove that the information represents the complete picture.
Proxy mode also carries network assumptions that developers need to consider when selecting an implementation.
๐ช๐๐๐ง ๐๐ข๐ ๐๐ฆ ๐ก๐๐ซ๐ง?
Primus research extends beyond verifying data.
Its zkFHE work, including HasteBoots, explores how to prove that computations performed on encrypted data were executed correctly. this remains research rather than a shipped product.
Put these research directions side by side and a broader vision starts to emerge:
Verify that the data is authentic.
Protect the information that must remain private.
Prove that the computation was performed correctly.
That is a much bigger conversation than simply making proofs faster.
Because when verification becomes efficient enough to fit into everyday digital activity, the question is no longer just:
"Can we prove it?"
It becomes:
"What should we be able to prove without having to reveal everything?"
That is the direction of privacy-preserving verification worth paying attention to.
๐น๐๐๐๐ฆ retweeted
Primus ร AllScale, ์จ์ฒด์ธ ๊ธ์ฌ์ ํ๋ผ์ด๋ฒ์ ๋ฌธ์ ํ์๋ค
@primus_labs @KaitoAI @KaitoStudio
์๋ฌด๋ ์๊ธฐ ์๊ธ์ด ๊ณต๊ฐ ์์ฅ์ ์ฐํ๋ ๊ฑธ ์ํ์ง ์์์์.
์จ์ฒด์ธ ๊ธ์ฌ๊ฐ ๊ทธ๋์ ์ ๋ ์ด์ ๊ฐ ๋ฐ๋ก ์ด๊ฑฐ์์.
์๊ธ, ์ธ์, ๋ณด๋์ค, ์ง์ ๊ฐ ์ฐ๋ด ์ฐจ์ด๊น์ง ์ ๋ถ ๊ณต๊ฐ๋๋๊น HR ์ชฝ์์๋ ๋๋ฆฌ ๋๊ณ , ๊ฒฐ๊ตญ ๋ค์ ๊ธฐ์กด ์์คํ
์ผ๋ก ๋์๊ฐ๋ ๊ฒฝ์ฐ๊ฐ ๋ง์์ด์.
Primus(primus_labs)์ AllScale์ด ์ด ๋ฌธ์ ๋ฅผ ๊ธฐ์ ์ ์ผ๋ก ๊ฒ์ฆํ์ด์.
FHE(์์ ๋ํ ์ํธํ)๋ก ๊ธ์ฌ ๋ฐ์ดํฐ๋ฅผ ์ํธํํ ๋ค ์จ์ฒด์ธ์ ์ฌ๋ฆฌ๋ ๋ฐฉ์์ด์์.
ํ์ฌ๋ โ๊ธ์ฌ๋ฅผ ์ง๊ธํ๋คโ๋ ์ฌ์ค์ ์ฆ๋ช
๊ฐ๋ฅํ๊ณ , ์ง์์ ์๊ธฐ ์ฐ๋ด๋ง ๋ณผ ์ ์๊ณ , ํ์ํ๋ฉด ์ํยท์ง์ฃผ์ธ ๋ฑ์๊ฒ๋ง ์ ํ์ ์ผ๋ก ์ฆ๋ช
๊ฐ๋ฅํด์.
์ค์ ๊ธ์ก์ ๊ทธ ์ธ ๋๊ตฌ์๊ฒ๋ ๋ณด์ด์ง ์์์.
AllScale์ด ์คํ ๋ ์ด์ด๋ฅผ ๋งก๊ณ , Primus์ FHE ์์ง์ด ํ๋ผ์ด๋ฒ์๋ฅผ ๋ณด์ฅํ๋ ๊ตฌ์กฐ์์.
ํนํ ๋๋ ๋ฐฐ์น ์ง๊ธ์ด ํ์ํ ๊ธ์ฌ ํน์ฑ์ ๊ฐ์ค๋น๊ฐ ๋ฎ์ BNB Chain์ ์ ํํ ๊ฒ๋ ์ค์ฉ์ ์ธ ํฌ์ธํธ์์.
๊ธฐ๊ด์ด ์จ์ฒด์ธ์ผ๋ก ๋ค์ด์ค๋ ค๋ฉด ๊ฒฐ๊ตญ ์ด๋ฐ ์์ โ๊ฒ์ฆ์ ๋๊ณ , ๋ฏผ๊ฐ ์ ๋ณด๋ ์จ๊ธฐ๋โ ์ธํ๋ผ๊ฐ ํ์ํด์.
Primus๊ฐ ๊ทธ ๋ ์ด์ด๋ฅผ ๋ง๋ค๊ณ ์๋ ์ค์ด์์.
๊ด์ฌ ์์ผ์ ๋ถ๋ค์ ์ฌ๊ธฐ์ ์ฐธ์ฌํด ๋ณด์ธ์๐
s.kaito.ai/wEpUXSu
์ฌ๋ฌ๋ถ์ ์จ์ฒด์ธ ๊ธ์ฌ, ํ๋ผ์ด๋ฒ์๋ง ํด๊ฒฐ๋๋ฉด ์ธ ์ํฅ ์์ผ์ ๊ฐ์?
#Primus #Kaito #FHE #OnchainPayroll #BNBChain #๊ด๊ณ
๐ค Paid partnership ยท ๐ค Made with AI
โ๊ฒ์ฆ์ ํด์ผ ํ๋๋ฐ ํฌ์ง์
์ ๋ณด์ฌ์ฃผ๊ณ ์ถ์ง ์๋คโ โ ์ด ๋๋ ๋ง๋ฅผ ํด๊ฒฐํ๋ ํ๋ก์ ํธ
@primus_labs @KaitoAI @KaitoStudio_
Primus๊ฐ ๋ฐ๋ก ๊ทธ ๋ฌธ์ ๋ฅผ ํด๊ฒฐํ๊ณ ์์ด์.
zkTLS์ FHE๋ก ์ฆ๋ช
ํ๋ฉด์ ๋์์ ์จ๊ธธ ์ ์๋ ์ธํ๋ผ๋ฅผ ๋ง๋ค๊ณ ์์ฃ .
์น2 ๋ฐ์ดํฐ(๊ฑฐ๋์ยท์ํยทAPI)๋ฅผ ๋น๋ฐ๋ฒํธ ์ ์ฃผ๊ณ ์ฆ๋ช
๊ฐ๋ฅ ํด์.
์ํธํ๋ ์ํ ๊ทธ๋๋ก ๊ณ์ฐยท์ด์ฒดยท์์ต ์ฐฝ์ถ (Confidential Vault) ํด์.
์ด๋ฏธ Kaito Pulse/Aura ๊ฒ์ฆ ๋ ์ด์ด๋ก๋ ์ฐ์ด๊ณ ์์ด์.
๊ทธ๋ฅ ํ๋ผ์ด๋ฒ์ ์ฒด์ธ์ด ์๋๋ผ, ๊ธฐ์กด ์ฒด์ธ ์์ ๋ถ์ด๋ ๊ธฐ๊ด์ฉ ๊ฒ์ฆยท๊ธฐ๋ฐ ๋ ์ด์ด๋ผ๋ ์ ์ด ํฌ์ธํธ์์.
TGE ์ ์ง๊ธ ์นด์ดํ Epoch 2 ์งํ ์ค์ด๊ณ ํ๊ตญ ํ๋ ๋ฐ๋ก ์์ด์.
๊ด์ฌ ์์ผ์ ๋ถ๋ค์ ์ฌ๊ธฐ์ ์ฐธ์ฌํด ๋ณด์ธ์๐
s.kaito.ai/wEpUXSu
#Primus #Kaito #zkTLS #FHE #OnchainFinance #๊ด๊ณ
๐น๐๐๐๐ฆ retweeted
Good morning, CT.
๐ช๐๐๐ก ๐ฃ๐ฅ๐ข๐ข๐ ๐๐๐๐ข๐ ๐๐ฆ ๐๐๐๐๐ฃ ๐๐ก๐ข๐จ๐๐ ๐ง๐ข ๐ฅ๐จ๐ก ๐๐ก ๐ง๐๐ ๐๐๐๐๐๐ฅ๐ข๐จ๐ก๐
A proof that nobody can afford to generate is little more than a research achievement.
But when generating that proof becomes efficient enough to happen quietly, repeatedly and at scale, it starts to look like infrastructure.
That is one of the important ideas behind zkTLS and a key part of Primus approach is QuickSilver.
๐ช๐๐๐ฅ๐ ๐ค๐จ๐๐๐๐ฆ๐๐๐ฉ๐๐ฅ ๐๐๐ง๐ฆ ๐๐ก
zkTLS aims to prove that an authentic TLS session with a real website took place without exposing the sensitive information exchanged during that session.
@primus_labs uses QuickSilver, a lightweight interactive zero-knowledge proof system, in both of its zkTLS modes:
โ MPC Mode: The user and attestors collaboratively establish the TLS session. this helps prevent the user from modifying the data before the attestor contributes its share of the session key.
โ Proxy Mode: An attestor relays the TLS traffic and records the encrypted exchange. At the end, the user proves knowledge of the plaintext behind the recorded ciphertexts.
Different approaches, but the same objective: make data from existing web services verifiable without unnecessarily exposing it.
๐ช๐๐ฌ ๐ง๐๐ ๐ช๐ข๐ฅ๐ "๐๐ก๐ง๐๐ฅ๐๐๐ง๐๐ฉ๐" ๐ ๐๐ง๐ง๐๐ฅ๐ฆ
Traditional proof systems can involve substantial computation and communication overhead.
QuickSilver takes an interactive approach: instead of producing one large standalone proof, the prover and verifier exchange a sequence of smaller messages.
Primus describes its design as requiring very little memory and relatively small amounts of communication at each step.
Think of it as replacing one enormous exchange with a stream of smaller, coordinated interactions.
There is an important trade-off, however.
The verifier remains part of the process. In Primus architecture, that role is handled by an attestor, which produces an attestation that applications can subsequently verify.
The efficiency comes with a trust model that developers must understand when choosing how to use the system.
๐ช๐๐๐ง ๐ ๐ข๐ฅ๐ ๐๐๐๐๐๐๐๐ก๐ง ๐ฃ๐ฅ๐ข๐ข๐๐ฆ ๐๐ข๐จ๐๐ ๐๐ก๐๐๐๐
When proof generation becomes more practical, verification no longer has to be reserved for occasional demonstrations or periodic checks.
It opens the door to applications such as:
โ Scheduled reserve checks instead of relying exclusively on quarterly reporting.
โ Real-time policy verification for AI agents.
โ Credential verification integrated into everyday sign-in experiences.
The bigger opportunity is making verification part of normal application workflows rather than treating it as an expensive extra step.
๐ ๐ก๐ข๐ง๐ ๐ข๐ก ๐ง๐๐ ๐ฃ๐๐ฅ๐๐ข๐ฅ๐ ๐๐ก๐๐ ๐๐๐๐๐ ๐ฆ
Primus has reported performance improvements of roughly an order of magnitude over certain earlier approaches, based on its own reporting and cited analysis.
Reproducible, independently verified measurements would make those performance claims even stronger.
And one distinction remains essential: zkTLS can help establish where data came from and whether it was altered. It does not automatically prove that the information represents the complete picture.
Proxy mode also carries network assumptions that developers need to consider when selecting an implementation.
๐ช๐๐๐ง ๐๐ข๐ ๐๐ฆ ๐ก๐๐ซ๐ง?
Primus research extends beyond verifying data.
Its zkFHE work, including HasteBoots, explores how to prove that computations performed on encrypted data were executed correctly. this remains research rather than a shipped product.
Put these research directions side by side and a broader vision starts to emerge:
Verify that the data is authentic.
Protect the information that must remain private.
Prove that the computation was performed correctly.
That is a much bigger conversation than simply making proofs faster.
Because when verification becomes efficient enough to fit into everyday digital activity, the question is no longer just:
"Can we prove it?"
It becomes:
"What should we be able to prove without having to reveal everything?"
That is the direction of privacy-preserving verification worth paying attention to.
Zcashโs recent momentum is bringing an important conversation back into focus:
What should financial privacy look like as crypto matures?
As blockchain adoption grows, so does the amount of financial information exposed through transparent networks.
For individual users, that can mean revealing more about their transactions than they intended.
For institutions, the implications are even greater.
Funds may want to interact with onchain markets without exposing their positions or strategies. Businesses may need to prove financial conditions without publishing sensitive records. Institutions may need to verify information without giving every participant access to the underlying data.
This is where the privacy conversation needs to go further.
Privacy alone is not enough. Financial systems also need verification.
And these two requirements should not have to work against each other.
That is the problem space @primus_labs is working on.
Primus approaches the challenge through two important capabilities:
โ zkTLS: Helps verify information from existing Web2 platforms and services without unnecessarily exposing the underlying data.
โ zkFHE: Enables computation over encrypted data, allowing sensitive information to remain protected while it is being processed.
Together with its broader verification and confidentiality infrastructure, Primus is working toward a model where financial information can be useful without being unnecessarily exposed.
There is an important distinction here:
Zcash brings privacy to blockchain transactions through its shielded transaction system.
Primus focuses on confidentiality and verification infrastructure that can work above existing financial rails.
Different approaches, but both point toward a broader shift in how we think about privacy.
The next stage of onchain finance will not be defined by transparency alone.
It will require systems that can protect sensitive information, verify important claims, and still make financial activity useful.
Because institutions should not have to choose between keeping their information private and proving what needs to be trusted.
That is the balance worth building toward.
๐น๐๐๐๐ฆ retweeted
Zcashโs recent momentum is bringing an important conversation back into focus:
What should financial privacy look like as crypto matures?
As blockchain adoption grows, so does the amount of financial information exposed through transparent networks.
For individual users, that can mean revealing more about their transactions than they intended.
For institutions, the implications are even greater.
Funds may want to interact with onchain markets without exposing their positions or strategies. Businesses may need to prove financial conditions without publishing sensitive records. Institutions may need to verify information without giving every participant access to the underlying data.
This is where the privacy conversation needs to go further.
Privacy alone is not enough. Financial systems also need verification.
And these two requirements should not have to work against each other.
That is the problem space @primus_labs is working on.
Primus approaches the challenge through two important capabilities:
โ zkTLS: Helps verify information from existing Web2 platforms and services without unnecessarily exposing the underlying data.
โ zkFHE: Enables computation over encrypted data, allowing sensitive information to remain protected while it is being processed.
Together with its broader verification and confidentiality infrastructure, Primus is working toward a model where financial information can be useful without being unnecessarily exposed.
There is an important distinction here:
Zcash brings privacy to blockchain transactions through its shielded transaction system.
Primus focuses on confidentiality and verification infrastructure that can work above existing financial rails.
Different approaches, but both point toward a broader shift in how we think about privacy.
The next stage of onchain finance will not be defined by transparency alone.
It will require systems that can protect sensitive information, verify important claims, and still make financial activity useful.
Because institutions should not have to choose between keeping their information private and proving what needs to be trusted.
That is the balance worth building toward.
Zcash has been one of the strongest assets in crypto recently, and i'm watching how it holds up if we get a deeper market correction
i think the privacy thesis could become increasingly relevant as political and regulatory scrutiny around crypto grows
the combination of privacy features, concerns around quantum computing and growing interest in alternatives to transparent blockchains makes ZEC interesting to me
๐น๐๐๐๐ฆ retweeted
Noon CT
Privacy and transparency are often treated as opposites.
But financial systems and AI agents need both: sensitive information should stay protected, while important claims and operations remain verifiable
This is the challenge @primus_labs is working to address
๐งต ๐
gn
Imagine using a financial application that needs to check your assets, verify your identity or process your records.
You want the service to work, but you don't want to hand over every private detail.
This is the problem @primus_labs is working to solve.
๐งต ๐
๐น๐๐๐๐ฆ retweeted
HOW FAST CAN PRIVATE COMPUTATION GET?
FHE lets apps perform computations without exposing the underlying data
But there's a catch: encrypted operations are expensive
Making them fast enough for everyday applications is a real challenge
@primus_labs has been working on that ๐งต
Why didnโt @primus_labs build its own blockchain?
In Web3, the default playbook for infrastructure teams is to launch a shiny new L1 or L2.
Primus deliberately broke the mold by building a pluggable privacy & verification layer.
Here is why that architecture decision matters
The industry suffers from L1/L2 fatigue. Launching a new chain forces a project into a constant battle and this bootstrapping validators, battling fragmented liquidity, and begging users to bridge capital into yet another ecosystem.
Primus asked a fundamental question: Why force users to come to privacy when privacy can come to them?
The Core Distinction:
ยฐ New Chain: An isolated execution environment requiring new consensus, gas tokens, and bridged assets.
ยฐ Pluggable Layer: An infrastructure engine powered by zkTLS and zkFHE that integrates directly into existing smart contracts via simple APIs/SDKs.
1. Zero Liquidity Fragmentation
Cross-chain bridges remain one of the largest attack vectors in Web3, with billions lost to exploits. By operating as middleware, Primus never traps user capital in isolated pools or risky bridge wrappers. Capital stays safely on Ethereum, BNB Chain, Base, or Solana while using Primus cryptographic proofs under the hood.
2. Eliminating Developer & UX Friction
Asking developers to learn a new chain-specific stack slows down real adoption. With a pluggable layer:
โข DApp builders keep their existing smart contract architecture.
โข Users perform transactions on their favorite chains without switching networks or buying new native gas tokens.
3. The Power of zkTLS + zkFHE Integration
Instead of building consensus around block production, Primus focuses its compute engine on cryptography:
โข zkTLS: Authenticates off-chain web data (web2 APIs, bank records, private data) without exposing sensitive credentials or payloads.
โข zkFHE: Enables computation directly over encrypted data without needing to decrypt it first.
4. Institutional & RWA Readiness
Institutions will never bridge sensitive financial balances to a public, transparent L1 where competitors can trace every transaction. A pluggable zkTLS layer allows institutions to prove off-chain solvency, account balances, or compliance directly to EVM/non-EVM protocols 100% privately.
5. Fueling Verifiable AI & Autonomous Agents
AI agents running off-chain need a way to prove that the data they ingested and the APIs they hit haven't been tampered with. A pluggable layer acts as the cryptographic link, verifying AI data pipelines in real time before submitting execution states to on-chain contracts.
6. Inherited Security vs. Bootstrapped Risk
A new chain is only as secure as its validator set and economic bonding model in its early days.
By staying layer-agnostic, Primus leaves state settlement to battle-tested base layers while focusing entirely on optimizing zero-knowledge proof generation speed and cryptographic performance.
Our Takeaway Point:
Blockchains are settlement engines. Primus is a universal verification engine.
Avoiding a dedicated chain wasnโt a compromise, it was a strategic choice to serve as essential middleware for all of Web3, DeFi, and AI.
Follow along for more deep dives into zkTLS, #zkFHE , and decentralized privacy!
#PrimusLabs
๐ค Made with AI
๐น๐๐๐๐ฆ retweeted
DVC?
An application may receive information from a legitimate website, but that alone doesn't make its decisions reliable
It also needs to know whether the data is authentic and whether the conclusions drawn from it are correct.
@primus_labs addresses this through DVC.
๐ ๐งต
gm
Privacy is not always about what people can see. Sometimes, it is about what they can learn from the traces left behind when you use a digital service.
This is an important topic when discussing @primus_labs and its approach to website verification.
Imagine proving that you meet a financial requirement without uploading your entire bank statement. You can keep the original document private while providing evidence of a specific claim. That is the kind of problem privacy-preserving verification is designed to address.
But there is another side to consider.
Metadata is information about an activity rather than the main content itself.
During a verification process, this might include:
โข The time a proof was generated or submitted
โข The type of verification template used
โข The fee associated with the request
โข Whether the verification succeeded or failed
โข Public transaction details associated with the process
Not every verification exposes all these details. What becomes visible depends on the system's design, its recording methods, and the information published onchain or elsewhere.
Consider someone applying for a loan. They use a privacy-preserving proof to demonstrate that their income meets the required threshold.
The actual bank statement may remain hidden. However, if the verification activity leaves publicly accessible records, an observer might still learn that a financial check took place.
One isolated detail may reveal very little. But several records, viewed together over time, could potentially reveal patterns of activity.
This shows why protecting the original data is only one part of a broader privacy strategy.
Different applications have different transparency requirements.
For example, reserve verification can benefit from publicly checkable evidence because users need confidence that financial claims are supported. By contrast, an enterprise verifying sensitive customer information may need stricter access controls around verification records.
The goal is not necessarily to hide everything. It is to make deliberate decisions about what should be public, what should remain private, and who should have access.
As privacy-preserving verification develops, the conversation needs to go beyond whether the original data is exposed.
Builders must also consider the surrounding information generated during verification, how long those records remain available, and whether separate records can be linked together.
That distinction matters for applications handling financial information, personal credentials, and other sensitive claims.
Real privacy requires looking at the entire verification process, not just the data inside the proof.
Because protecting what you share is important, but understanding what your activity reveals is just as essential.
Join: s.kaito.ai/WkmbWw6
Good morning, CT.
๐ช๐๐๐ก ๐ฃ๐ฅ๐ข๐ข๐ ๐๐๐๐ข๐ ๐๐ฆ ๐๐๐๐๐ฃ ๐๐ก๐ข๐จ๐๐ ๐ง๐ข ๐ฅ๐จ๐ก ๐๐ก ๐ง๐๐ ๐๐๐๐๐๐ฅ๐ข๐จ๐ก๐
A proof that nobody can afford to generate is little more than a research achievement.
But when generating that proof becomes efficient enough to happen quietly, repeatedly and at scale, it starts to look like infrastructure.
That is one of the important ideas behind zkTLS and a key part of Primus approach is QuickSilver.
๐ช๐๐๐ฅ๐ ๐ค๐จ๐๐๐๐ฆ๐๐๐ฉ๐๐ฅ ๐๐๐ง๐ฆ ๐๐ก
zkTLS aims to prove that an authentic TLS session with a real website took place without exposing the sensitive information exchanged during that session.
@primus_labs uses QuickSilver, a lightweight interactive zero-knowledge proof system, in both of its zkTLS modes:
โ MPC Mode: The user and attestors collaboratively establish the TLS session. this helps prevent the user from modifying the data before the attestor contributes its share of the session key.
โ Proxy Mode: An attestor relays the TLS traffic and records the encrypted exchange. At the end, the user proves knowledge of the plaintext behind the recorded ciphertexts.
Different approaches, but the same objective: make data from existing web services verifiable without unnecessarily exposing it.
๐ช๐๐ฌ ๐ง๐๐ ๐ช๐ข๐ฅ๐ "๐๐ก๐ง๐๐ฅ๐๐๐ง๐๐ฉ๐" ๐ ๐๐ง๐ง๐๐ฅ๐ฆ
Traditional proof systems can involve substantial computation and communication overhead.
QuickSilver takes an interactive approach: instead of producing one large standalone proof, the prover and verifier exchange a sequence of smaller messages.
Primus describes its design as requiring very little memory and relatively small amounts of communication at each step.
Think of it as replacing one enormous exchange with a stream of smaller, coordinated interactions.
There is an important trade-off, however.
The verifier remains part of the process. In Primus architecture, that role is handled by an attestor, which produces an attestation that applications can subsequently verify.
The efficiency comes with a trust model that developers must understand when choosing how to use the system.
๐ช๐๐๐ง ๐ ๐ข๐ฅ๐ ๐๐๐๐๐๐๐๐ก๐ง ๐ฃ๐ฅ๐ข๐ข๐๐ฆ ๐๐ข๐จ๐๐ ๐๐ก๐๐๐๐
When proof generation becomes more practical, verification no longer has to be reserved for occasional demonstrations or periodic checks.
It opens the door to applications such as:
โ Scheduled reserve checks instead of relying exclusively on quarterly reporting.
โ Real-time policy verification for AI agents.
โ Credential verification integrated into everyday sign-in experiences.
The bigger opportunity is making verification part of normal application workflows rather than treating it as an expensive extra step.
๐ ๐ก๐ข๐ง๐ ๐ข๐ก ๐ง๐๐ ๐ฃ๐๐ฅ๐๐ข๐ฅ๐ ๐๐ก๐๐ ๐๐๐๐๐ ๐ฆ
Primus has reported performance improvements of roughly an order of magnitude over certain earlier approaches, based on its own reporting and cited analysis.
Reproducible, independently verified measurements would make those performance claims even stronger.
And one distinction remains essential: zkTLS can help establish where data came from and whether it was altered. It does not automatically prove that the information represents the complete picture.
Proxy mode also carries network assumptions that developers need to consider when selecting an implementation.
๐ช๐๐๐ง ๐๐ข๐ ๐๐ฆ ๐ก๐๐ซ๐ง?
Primus research extends beyond verifying data.
Its zkFHE work, including HasteBoots, explores how to prove that computations performed on encrypted data were executed correctly. this remains research rather than a shipped product.
Put these research directions side by side and a broader vision starts to emerge:
Verify that the data is authentic.
Protect the information that must remain private.
Prove that the computation was performed correctly.
That is a much bigger conversation than simply making proofs faster.
Because when verification becomes efficient enough to fit into everyday digital activity, the question is no longer just:
"Can we prove it?"
It becomes:
"What should we be able to prove without having to reveal everything?"
That is the direction of privacy-preserving verification worth paying attention to.
Zcashโs recent momentum is bringing an important conversation back into focus:
What should financial privacy look like as crypto matures?
As blockchain adoption grows, so does the amount of financial information exposed through transparent networks.
For individual users, that can mean revealing more about their transactions than they intended.
For institutions, the implications are even greater.
Funds may want to interact with onchain markets without exposing their positions or strategies. Businesses may need to prove financial conditions without publishing sensitive records. Institutions may need to verify information without giving every participant access to the underlying data.
This is where the privacy conversation needs to go further.
Privacy alone is not enough. Financial systems also need verification.
And these two requirements should not have to work against each other.
That is the problem space @primus_labs is working on.
Primus approaches the challenge through two important capabilities:
โ zkTLS: Helps verify information from existing Web2 platforms and services without unnecessarily exposing the underlying data.
โ zkFHE: Enables computation over encrypted data, allowing sensitive information to remain protected while it is being processed.
Together with its broader verification and confidentiality infrastructure, Primus is working toward a model where financial information can be useful without being unnecessarily exposed.
There is an important distinction here:
Zcash brings privacy to blockchain transactions through its shielded transaction system.
Primus focuses on confidentiality and verification infrastructure that can work above existing financial rails.
Different approaches, but both point toward a broader shift in how we think about privacy.
The next stage of onchain finance will not be defined by transparency alone.
It will require systems that can protect sensitive information, verify important claims, and still make financial activity useful.
Because institutions should not have to choose between keeping their information private and proving what needs to be trusted.
That is the balance worth building toward.
๐น๐๐๐๐ฆ retweeted
gn
DeFi wants institutional capital, but regulated firms cannot ignore KYC, AML and sanctions requirements.
@primus_labs is exploring a different approach: proving that users meet compliance conditions without making their sensitive identity data public.
๐งต ๐
๐ฃ๐ฟ๐ถ๐บ๐๐ ๐ฎ๐ป๐ฑ ๐๐ผ๐๐ฟ๐ป๐ผ๐ ๐ฅ๐ฒ๐๐ต๐ถ๐ป๐ธ ๐ง๐ฟ๐๐๐
A blockchain can record what happened onchain, but what happens when a decision depends on information that lives somewhere else?
Consider a prediction market. Users may be betting on an election, a football match, or a financial event. The market needs reliable evidence before it can settle. If that evidence comes from an external website, the application needs a way to check it without blindly trusting a screenshot or asking users to reveal more personal information than necessary.
This is a problem @primus_labs is working to address.
๐ ๐ฎ๐ธ๐ถ๐ป๐ด ๐ข๐ณ๐ณ๐ฐ๐ต๐ฎ๐ถ๐ป ๐๐ฎ๐๐ฎ ๐จ๐๐ฒ๐ณ๐๐น
A lot of information that could power Web3 applications still lives outside blockchains.
Exchanges hold trading records. Websites publish results. Financial services maintain information that users may need to reference elsewhere. Yet, a smart contract cannot simply visit a website and independently confirm that its contents are authentic.
Primus uses zkTLS to help applications verify information from supported web sources while limiting the need to disclose the underlying data.
For example, someone may want to demonstrate a particular fact about their trading activity. Sharing screenshots or an entire account history could reveal unnecessary details. Verifiable evidence offers another approach, where an application can check a supported claim without automatically receiving everything connected to it.
The important distinction is that verification doesn't have to mean full disclosure.
The collaboration between Primus and @CournotProtocol explores bringing verifiable web evidence into prediction markets, with potential applications in private credit and onchain finance.
For prediction markets, better evidence can help applications assess whether an outcome meets the market's rules. However, zkTLS doesn't determine the winner by itself. The quality of the source, the market's conditions, and how the evidence is interpreted still matter.
The technology addresses an important part of the process: establishing whether relevant information can be verified.
Private credit presents a different use case. A financial application may need certain details to assess eligibility, while the person providing them may prefer not to expose their entire financial history. Privacy-preserving verification could help bridge that gap.
๐ง๐ต๐ฒ ๐ฅ๐ฒ๐ฎ๐น ๐ฉ๐ฎ๐น๐๐ฒ
I think this is an important direction for Web3 because transparency and privacy are often treated as opposing goals.
Public blockchains make transactions auditable, but that doesn't mean every personal detail should be public. At the same time, keeping information private shouldn't mean applications must accept every claim without evidence.
There are still practical challenges, including security, integration, performance, and data quality. The technology must work reliably before these use cases can deliver meaningful benefits.
Still, the principle is worth paying attention to: give applications the evidence they need without exposing information they don't.
That's what makes the work both interesting. They're exploring how offchain information can support onchain decisions without making unnecessary disclosure the price of participation.
๐น๐๐๐๐ฆ retweeted
Good morning CT.
AlphaNet is @primus_labs reputation campaign. Instead of asking what wallet you hold, it asks what you can prove, using zkTLS to verify facts from your web accounts without exposing your passwords or raw records.
Think of it as three tracks. Do them in this order and the dashboard becomes easy to read.
๐๐๐๐ข๐ฅ๐ ๐ฌ๐ข๐จ ๐ฆ๐ง๐๐ฅ๐ง
- Open the dashboard
- Connect an EVM wallet.
- Add the Primus browser extension, which creates the proofs.
๐ง๐ฅ๐๐๐ ๐ญ: ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ช๐๐ข ๐ฌ๐ข๐จ ๐๐ฅ๐
Identity proofs link your accounts to your profile. the task list covers platforms such as X, GitHub, Google, LinkedIn, Luma, Spotify, TikTok and Naver. Each task checks one fact, like a username, follower count, email or contribution history. Start here: these are usually the quickest to finish.
๐ง๐ฅ๐๐๐ ๐ฎ: ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ช๐๐๐ง ๐ฌ๐ข๐จ ๐๐ข
Activity proofs go deeper. They include verified followers on X, events you attended on Luma and your last year of GitHub contributions. the newer agent-themed set covers proofs such as Proof of PnL, Proof of Nomad Life, Proof of AI Affinity and Proof of Trade. Pick the ones that genuinely describe you. a proof means more when it is true.
๐ง๐ฅ๐๐๐ ๐ฏ: ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ช๐๐๐ง ๐ฌ๐ข๐จ ๐๐ข๐๐
The Confidential Vault campaign lets you shield assets to earn encrypted yield. Your score scales with your effective shield balance, so size matters here. The vault is an early product, so shield only what you are comfortable locking in.
๐๐๐๐ฃ ๐๐ง ๐๐ข๐๐ก๐
- Check the dashboard now and then. New tasks appear over time.
- Share Primus with your community the campaign offers referral benefits.
What zkTLS does for you in all of this: you prove the fact and the platform never sees your login.
Good evening CT.
๐ซ๐จ๐ป๐จ ๐ฐ๐บ ๐ป๐ถ๐ฟ๐ฐ๐ช ๐พ๐จ๐บ๐ป๐ฌ. ๐ต๐ถ๐พ ๐พ๐ฏ๐จ๐ป?
A line attributed to Vitalik at Devcon Mumbai is worth sitting with: "We really need to treat data as toxic waste by default." the remarks, as reported, pair it with a call for open-source technology and zero-knowledge proofs to protect privacy and reduce reliance on trust.
his wider argument is on record: a September 2025 post argues for open, verifiable systems and names zero-knowledge proofs, homomorphic encryption and formally verified hardware as tools. let me take the idea seriously and ask what builders do with it.
๐ช๐๐ฌ "๐ง๐ข๐ซ๐๐ ๐ช๐๐ฆ๐ง๐" ๐๐ฆ ๐ ๐จ๐ฆ๐๐๐จ๐ ๐๐ฅ๐๐ ๐
Oil is something you want more of. Toxic waste is something you minimize, contain and hand over only when you must. applied to data, that flips the usual instinct to collect everything.
The holder carries the risk: breaches, leaks, subpoenas, insider misuse and onchain it gets worse, because public ledgers are permanent.
Cryptographers already use the phrase. In some zero-knowledge trusted setups, "toxic waste" is the secret randomness that must be destroyed. same logic: some secrets are safest when nobody holds them.
๐ง๐๐ฅ๐๐ ๐ช๐๐ฌ๐ฆ ๐ง๐ข ๐๐ข๐๐ ๐๐๐ฆ๐ฆ
๐ญ. ๐ฃ๐ฅ๐ข๐ฉ๐ ๐๐ก๐ฆ๐ง๐๐๐ ๐ข๐ ๐ฆ๐๐๐ฅ๐.
Most checks do not need the record. They need one fact. @primus_labs zkTLS lets a user prove a fact from a web account without sharing credentials or the raw record. the Developer Hub even let a template return only a condition result, such as true or false against a threshold, or a SHA256 hash of a field, instead of the plaintext value. that is data minimization built into the output.
๐ฎ. ๐๐ข๐ ๐ฃ๐จ๐ง๐ ๐ช๐๐ง๐๐ข๐จ๐ง ๐ฆ๐๐๐๐ก๐.
Sometimes the data has to be used, not just checked. FHE lets contracts compute on encrypted values. Designs in the Primus and ecosystem point at this: an encrypted deposit option in the Confidential Vault on BNB Chain, sealed-bid auctions and private voting where choices stay hidden.
๐ฏ. ๐ฉ๐๐ฅ๐๐๐ฌ ๐๐ก๐ฆ๐ง๐๐๐ ๐ข๐ ๐ง๐ฅ๐จ๐ฆ๐ง.
The open-source half of the argument matters as much as the cryptography. If a system keeps data safe only because you trust the operator, you have moved the toxic waste, not removed it.
๐ง๐๐ ๐๐๐ง๐๐, ๐ฆ๐ง๐๐ง๐๐ ๐ฃ๐๐๐๐ก๐๐ฌ
- A proof still reveals something: that an account exists, or that a threshold was met. Minimal is not zero.
- Verifiers can start new piles. If an app stores every proof output, it has rebuilt the problem.
- zkTLS proves provenance, not truth. A clean proof of a wrong source is still wrong.
- Trust remains in places: attestors, TEEs and key management. Penalties and governance are not yet active and the key service uses a single TEE today with threshold MPC planned.
๐ช๐๐๐ง ๐ ๐ช๐ข๐จ๐๐ ๐๐ข ๐๐ฆ ๐ ๐๐จ๐๐๐๐๐ฅ
- Ask for the answer, not the record: use a condition instead of a value.
- Keep outputs small and expire what you store.
- Make verification reproducible so users are not asked to trust you.
- Publish limits next to features.
My view: "toxic waste by default" is less a slogan than a design rule. the best data policy is the dataset you never had to hold.
What is one thing your favorite app collects that it could simply have proven instead?
๐น๐๐๐๐ฆ retweeted
Prediction markets don't just need better predictions. they need better ways to verify the truth behind them.
Prediction markets are built around uncertainty.
Will an election result go a certain way? Will a company hit its target? Will a particular event happen before a deadline?
People commit capital based on what they believe will happen. but when the event is over, one question becomes critical:
What evidence determines the outcome and can that evidence be trusted?
This is why @primus_labs make a meaningful difference.
Many prediction markets depend on information from outside the blockchain: official announcements, financial data, public records, social platforms, APIs and other Web2 sources.
The challenge is not simply accessing that information. It is establishing that the information is authentic before using it to resolve a market.
Primus approaches this through zkTLS.
Instead of asking users or applications to expose sensitive source data, zkTLS can generate cryptographic attestations that help verify where information came from while preserving the privacy of the underlying data.
That introduces an important improvement to the prediction market process:
โ Retrieve relevant information from an external source.
โ Verify its authenticity through zkTLS.
โ Pass the verified evidence into the market's resolution process.
โ Allow the application or its reasoning layer to interpret the evidence.
โ Make the resulting decision more transparent and auditable.
The distinction matters: Primus helps establish whether the evidence is authentic; the market's resolution logic still determines what that evidence means.
And this is not just a theoretical direction.
Primus and @CournotProtocol are exploring this relationship: Primus verifies the authenticity of off-chain evidence, while Cournot interprets that evidence and turns it into structured, auditable judgments.
But the opportunity extends beyond market resolution.
What could this look like in the future?
Imagine prediction markets where participants can prove eligibility or relevant account conditions without exposing their entire financial history.
Imagine markets that rely on verified exchange data, official records or social activity, with stronger guarantees about the origin of that information.
Imagine confidential trading environments where sensitive positions and strategies can remain protected while the system still performs the necessary checks.
This is where Primus broader work in fully homomorphic encryption (FHE) could become relevant. FHE enables computation on encrypted information, creating possibilities for applications that need to use sensitive data without first exposing it.
These capabilities are distinct, but together they point toward a more capable financial infrastructure:
zkTLS helps verify the evidence.
Confidential computation helps protect sensitive information.
The application uses verified inputs to make decisions.
For prediction markets, that could mean stronger resolution processes, more privacy for participants and greater confidence in the information behind market outcomes.
The future of prediction markets should not be built on the assumption that everything must be public to be trusted.
It should be built around a better principle:
Verify what matters. Protect what is private. Make every important decision accountable.
That is the direction in which infrastructure like Primus could help move the ecosystem.
Good morning CT.
AlphaNet is @primus_labs reputation campaign. Instead of asking what wallet you hold, it asks what you can prove, using zkTLS to verify facts from your web accounts without exposing your passwords or raw records.
Think of it as three tracks. Do them in this order and the dashboard becomes easy to read.
๐๐๐๐ข๐ฅ๐ ๐ฌ๐ข๐จ ๐ฆ๐ง๐๐ฅ๐ง
- Open the dashboard
- Connect an EVM wallet.
- Add the Primus browser extension, which creates the proofs.
๐ง๐ฅ๐๐๐ ๐ญ: ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ช๐๐ข ๐ฌ๐ข๐จ ๐๐ฅ๐
Identity proofs link your accounts to your profile. the task list covers platforms such as X, GitHub, Google, LinkedIn, Luma, Spotify, TikTok and Naver. Each task checks one fact, like a username, follower count, email or contribution history. Start here: these are usually the quickest to finish.
๐ง๐ฅ๐๐๐ ๐ฎ: ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ช๐๐๐ง ๐ฌ๐ข๐จ ๐๐ข
Activity proofs go deeper. They include verified followers on X, events you attended on Luma and your last year of GitHub contributions. the newer agent-themed set covers proofs such as Proof of PnL, Proof of Nomad Life, Proof of AI Affinity and Proof of Trade. Pick the ones that genuinely describe you. a proof means more when it is true.
๐ง๐ฅ๐๐๐ ๐ฏ: ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ช๐๐๐ง ๐ฌ๐ข๐จ ๐๐ข๐๐
The Confidential Vault campaign lets you shield assets to earn encrypted yield. Your score scales with your effective shield balance, so size matters here. The vault is an early product, so shield only what you are comfortable locking in.
๐๐๐๐ฃ ๐๐ง ๐๐ข๐๐ก๐
- Check the dashboard now and then. New tasks appear over time.
- Share Primus with your community the campaign offers referral benefits.
What zkTLS does for you in all of this: you prove the fact and the platform never sees your login.
Zcashโs recent momentum is bringing an important conversation back into focus:
What should financial privacy look like as crypto matures?
As blockchain adoption grows, so does the amount of financial information exposed through transparent networks.
For individual users, that can mean revealing more about their transactions than they intended.
For institutions, the implications are even greater.
Funds may want to interact with onchain markets without exposing their positions or strategies. Businesses may need to prove financial conditions without publishing sensitive records. Institutions may need to verify information without giving every participant access to the underlying data.
This is where the privacy conversation needs to go further.
Privacy alone is not enough. Financial systems also need verification.
And these two requirements should not have to work against each other.
That is the problem space @primus_labs is working on.
Primus approaches the challenge through two important capabilities:
โ zkTLS: Helps verify information from existing Web2 platforms and services without unnecessarily exposing the underlying data.
โ zkFHE: Enables computation over encrypted data, allowing sensitive information to remain protected while it is being processed.
Together with its broader verification and confidentiality infrastructure, Primus is working toward a model where financial information can be useful without being unnecessarily exposed.
There is an important distinction here:
Zcash brings privacy to blockchain transactions through its shielded transaction system.
Primus focuses on confidentiality and verification infrastructure that can work above existing financial rails.
Different approaches, but both point toward a broader shift in how we think about privacy.
The next stage of onchain finance will not be defined by transparency alone.
It will require systems that can protect sensitive information, verify important claims, and still make financial activity useful.
Because institutions should not have to choose between keeping their information private and proving what needs to be trusted.
That is the balance worth building toward.
Zcash has been one of the strongest assets in crypto recently, and i'm watching how it holds up if we get a deeper market correction
i think the privacy thesis could become increasingly relevant as political and regulatory scrutiny around crypto grows
the combination of privacy features, concerns around quantum computing and growing interest in alternatives to transparent blockchains makes ZEC interesting to me
Prediction markets don't just need better predictions. they need better ways to verify the truth behind them.
Prediction markets are built around uncertainty.
Will an election result go a certain way? Will a company hit its target? Will a particular event happen before a deadline?
People commit capital based on what they believe will happen. but when the event is over, one question becomes critical:
What evidence determines the outcome and can that evidence be trusted?
This is why @primus_labs make a meaningful difference.
Many prediction markets depend on information from outside the blockchain: official announcements, financial data, public records, social platforms, APIs and other Web2 sources.
The challenge is not simply accessing that information. It is establishing that the information is authentic before using it to resolve a market.
Primus approaches this through zkTLS.
Instead of asking users or applications to expose sensitive source data, zkTLS can generate cryptographic attestations that help verify where information came from while preserving the privacy of the underlying data.
That introduces an important improvement to the prediction market process:
โ Retrieve relevant information from an external source.
โ Verify its authenticity through zkTLS.
โ Pass the verified evidence into the market's resolution process.
โ Allow the application or its reasoning layer to interpret the evidence.
โ Make the resulting decision more transparent and auditable.
The distinction matters: Primus helps establish whether the evidence is authentic; the market's resolution logic still determines what that evidence means.
And this is not just a theoretical direction.
Primus and @CournotProtocol are exploring this relationship: Primus verifies the authenticity of off-chain evidence, while Cournot interprets that evidence and turns it into structured, auditable judgments.
But the opportunity extends beyond market resolution.
What could this look like in the future?
Imagine prediction markets where participants can prove eligibility or relevant account conditions without exposing their entire financial history.
Imagine markets that rely on verified exchange data, official records or social activity, with stronger guarantees about the origin of that information.
Imagine confidential trading environments where sensitive positions and strategies can remain protected while the system still performs the necessary checks.
This is where Primus broader work in fully homomorphic encryption (FHE) could become relevant. FHE enables computation on encrypted information, creating possibilities for applications that need to use sensitive data without first exposing it.
These capabilities are distinct, but together they point toward a more capable financial infrastructure:
zkTLS helps verify the evidence.
Confidential computation helps protect sensitive information.
The application uses verified inputs to make decisions.
For prediction markets, that could mean stronger resolution processes, more privacy for participants and greater confidence in the information behind market outcomes.
The future of prediction markets should not be built on the assumption that everything must be public to be trusted.
It should be built around a better principle:
Verify what matters. Protect what is private. Make every important decision accountable.
That is the direction in which infrastructure like Primus could help move the ecosystem.
Good morning CT.
AlphaNet is @primus_labs reputation campaign. Instead of asking what wallet you hold, it asks what you can prove, using zkTLS to verify facts from your web accounts without exposing your passwords or raw records.
Think of it as three tracks. Do them in this order and the dashboard becomes easy to read.
๐๐๐๐ข๐ฅ๐ ๐ฌ๐ข๐จ ๐ฆ๐ง๐๐ฅ๐ง
- Open the dashboard
- Connect an EVM wallet.
- Add the Primus browser extension, which creates the proofs.
๐ง๐ฅ๐๐๐ ๐ญ: ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ช๐๐ข ๐ฌ๐ข๐จ ๐๐ฅ๐
Identity proofs link your accounts to your profile. the task list covers platforms such as X, GitHub, Google, LinkedIn, Luma, Spotify, TikTok and Naver. Each task checks one fact, like a username, follower count, email or contribution history. Start here: these are usually the quickest to finish.
๐ง๐ฅ๐๐๐ ๐ฎ: ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ช๐๐๐ง ๐ฌ๐ข๐จ ๐๐ข
Activity proofs go deeper. They include verified followers on X, events you attended on Luma and your last year of GitHub contributions. the newer agent-themed set covers proofs such as Proof of PnL, Proof of Nomad Life, Proof of AI Affinity and Proof of Trade. Pick the ones that genuinely describe you. a proof means more when it is true.
๐ง๐ฅ๐๐๐ ๐ฏ: ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ช๐๐๐ง ๐ฌ๐ข๐จ ๐๐ข๐๐
The Confidential Vault campaign lets you shield assets to earn encrypted yield. Your score scales with your effective shield balance, so size matters here. The vault is an early product, so shield only what you are comfortable locking in.
๐๐๐๐ฃ ๐๐ง ๐๐ข๐๐ก๐
- Check the dashboard now and then. New tasks appear over time.
- Share Primus with your community the campaign offers referral benefits.
What zkTLS does for you in all of this: you prove the fact and the platform never sees your login.
๐น๐๐๐๐ฆ retweeted
Good evening CT.
๐ซ๐จ๐ป๐จ ๐ฐ๐บ ๐ป๐ถ๐ฟ๐ฐ๐ช ๐พ๐จ๐บ๐ป๐ฌ. ๐ต๐ถ๐พ ๐พ๐ฏ๐จ๐ป?
A line attributed to Vitalik at Devcon Mumbai is worth sitting with: "We really need to treat data as toxic waste by default." the remarks, as reported, pair it with a call for open-source technology and zero-knowledge proofs to protect privacy and reduce reliance on trust.
his wider argument is on record: a September 2025 post argues for open, verifiable systems and names zero-knowledge proofs, homomorphic encryption and formally verified hardware as tools. let me take the idea seriously and ask what builders do with it.
๐ช๐๐ฌ "๐ง๐ข๐ซ๐๐ ๐ช๐๐ฆ๐ง๐" ๐๐ฆ ๐ ๐จ๐ฆ๐๐๐จ๐ ๐๐ฅ๐๐ ๐
Oil is something you want more of. Toxic waste is something you minimize, contain and hand over only when you must. applied to data, that flips the usual instinct to collect everything.
The holder carries the risk: breaches, leaks, subpoenas, insider misuse and onchain it gets worse, because public ledgers are permanent.
Cryptographers already use the phrase. In some zero-knowledge trusted setups, "toxic waste" is the secret randomness that must be destroyed. same logic: some secrets are safest when nobody holds them.
๐ง๐๐ฅ๐๐ ๐ช๐๐ฌ๐ฆ ๐ง๐ข ๐๐ข๐๐ ๐๐๐ฆ๐ฆ
๐ญ. ๐ฃ๐ฅ๐ข๐ฉ๐ ๐๐ก๐ฆ๐ง๐๐๐ ๐ข๐ ๐ฆ๐๐๐ฅ๐.
Most checks do not need the record. They need one fact. @primus_labs zkTLS lets a user prove a fact from a web account without sharing credentials or the raw record. the Developer Hub even let a template return only a condition result, such as true or false against a threshold, or a SHA256 hash of a field, instead of the plaintext value. that is data minimization built into the output.
๐ฎ. ๐๐ข๐ ๐ฃ๐จ๐ง๐ ๐ช๐๐ง๐๐ข๐จ๐ง ๐ฆ๐๐๐๐ก๐.
Sometimes the data has to be used, not just checked. FHE lets contracts compute on encrypted values. Designs in the Primus and ecosystem point at this: an encrypted deposit option in the Confidential Vault on BNB Chain, sealed-bid auctions and private voting where choices stay hidden.
๐ฏ. ๐ฉ๐๐ฅ๐๐๐ฌ ๐๐ก๐ฆ๐ง๐๐๐ ๐ข๐ ๐ง๐ฅ๐จ๐ฆ๐ง.
The open-source half of the argument matters as much as the cryptography. If a system keeps data safe only because you trust the operator, you have moved the toxic waste, not removed it.
๐ง๐๐ ๐๐๐ง๐๐, ๐ฆ๐ง๐๐ง๐๐ ๐ฃ๐๐๐๐ก๐๐ฌ
- A proof still reveals something: that an account exists, or that a threshold was met. Minimal is not zero.
- Verifiers can start new piles. If an app stores every proof output, it has rebuilt the problem.
- zkTLS proves provenance, not truth. A clean proof of a wrong source is still wrong.
- Trust remains in places: attestors, TEEs and key management. Penalties and governance are not yet active and the key service uses a single TEE today with threshold MPC planned.
๐ช๐๐๐ง ๐ ๐ช๐ข๐จ๐๐ ๐๐ข ๐๐ฆ ๐ ๐๐จ๐๐๐๐๐ฅ
- Ask for the answer, not the record: use a condition instead of a value.
- Keep outputs small and expire what you store.
- Make verification reproducible so users are not asked to trust you.
- Publish limits next to features.
My view: "toxic waste by default" is less a slogan than a design rule. the best data policy is the dataset you never had to hold.
What is one thing your favorite app collects that it could simply have proven instead?
โWe really need to treat data as toxic waste by default.โ Data itself carries risk.
By default we should collect less, store less, and expose less.
Do not hand it over or keep it unless necessary. Privacy is not about hiding everything.
It is about making sensitive information usable and verifiable without putting it on full display.
That is the infrastructure institutions actually need.
๐น๐๐๐๐ฆ retweeted
GM fam.
One thing I find interesting about @FungoLabs and its upcoming $FUNGO launch is the allocation for Zama OG NFT holders.
Every Zama OG NFT is expected to receive 140,112 FUNGO tokens. Now, when you look at that number, you might wonder what the allocation could actually be worth once the token launches and starts trading.
Let's break it down using different FDV scenarios, based on the fixed total supply of 10 billion FUNGO tokens.
If $FUNGO reaches a $10M FDV, one Zama OG NFT allocation could be worth around $140.11.
At $50M FDV, that same allocation would be worth $700.56.
At $100M FDV, we're looking at $1,401.12.
If it reaches $200M FDV, the allocation could be worth $2,802.24.
At $500M FDV, it could go as high as $7,005.60.
And in a $1B FDV scenario, one allocation would be worth approximately $14,011.20.
Another interesting part is that this calculation doesn't include the 3% of the total FUNGO supply allocated to the X Campaign.
Of course, these figures are just possible valuation scenarios, not guaranteed profits. The actual value will depend on the market price when $FUNGO launches and how the market responds.
Personally, I think it will be interesting to see how Fungo Labs performs, especially with its focus on encrypted NFTs powered by Zama's FHE technology.
What do you think? How far can $FUNGO go after launch? Are we looking at $100M, $500M or even $1B FDV?
Good morning CT.
AlphaNet is @primus_labs reputation campaign. Instead of asking what wallet you hold, it asks what you can prove, using zkTLS to verify facts from your web accounts without exposing your passwords or raw records.
Think of it as three tracks. Do them in this order and the dashboard becomes easy to read.
๐๐๐๐ข๐ฅ๐ ๐ฌ๐ข๐จ ๐ฆ๐ง๐๐ฅ๐ง
- Open the dashboard
- Connect an EVM wallet.
- Add the Primus browser extension, which creates the proofs.
๐ง๐ฅ๐๐๐ ๐ญ: ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ช๐๐ข ๐ฌ๐ข๐จ ๐๐ฅ๐
Identity proofs link your accounts to your profile. the task list covers platforms such as X, GitHub, Google, LinkedIn, Luma, Spotify, TikTok and Naver. Each task checks one fact, like a username, follower count, email or contribution history. Start here: these are usually the quickest to finish.
๐ง๐ฅ๐๐๐ ๐ฎ: ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ช๐๐๐ง ๐ฌ๐ข๐จ ๐๐ข
Activity proofs go deeper. They include verified followers on X, events you attended on Luma and your last year of GitHub contributions. the newer agent-themed set covers proofs such as Proof of PnL, Proof of Nomad Life, Proof of AI Affinity and Proof of Trade. Pick the ones that genuinely describe you. a proof means more when it is true.
๐ง๐ฅ๐๐๐ ๐ฏ: ๐ฃ๐ฅ๐ข๐ฉ๐ ๐ช๐๐๐ง ๐ฌ๐ข๐จ ๐๐ข๐๐
The Confidential Vault campaign lets you shield assets to earn encrypted yield. Your score scales with your effective shield balance, so size matters here. The vault is an early product, so shield only what you are comfortable locking in.
๐๐๐๐ฃ ๐๐ง ๐๐ข๐๐ก๐
- Check the dashboard now and then. New tasks appear over time.
- Share Primus with your community the campaign offers referral benefits.
What zkTLS does for you in all of this: you prove the fact and the platform never sees your login.
Good evening CT.
๐ซ๐จ๐ป๐จ ๐ฐ๐บ ๐ป๐ถ๐ฟ๐ฐ๐ช ๐พ๐จ๐บ๐ป๐ฌ. ๐ต๐ถ๐พ ๐พ๐ฏ๐จ๐ป?
A line attributed to Vitalik at Devcon Mumbai is worth sitting with: "We really need to treat data as toxic waste by default." the remarks, as reported, pair it with a call for open-source technology and zero-knowledge proofs to protect privacy and reduce reliance on trust.
his wider argument is on record: a September 2025 post argues for open, verifiable systems and names zero-knowledge proofs, homomorphic encryption and formally verified hardware as tools. let me take the idea seriously and ask what builders do with it.
๐ช๐๐ฌ "๐ง๐ข๐ซ๐๐ ๐ช๐๐ฆ๐ง๐" ๐๐ฆ ๐ ๐จ๐ฆ๐๐๐จ๐ ๐๐ฅ๐๐ ๐
Oil is something you want more of. Toxic waste is something you minimize, contain and hand over only when you must. applied to data, that flips the usual instinct to collect everything.
The holder carries the risk: breaches, leaks, subpoenas, insider misuse and onchain it gets worse, because public ledgers are permanent.
Cryptographers already use the phrase. In some zero-knowledge trusted setups, "toxic waste" is the secret randomness that must be destroyed. same logic: some secrets are safest when nobody holds them.
๐ง๐๐ฅ๐๐ ๐ช๐๐ฌ๐ฆ ๐ง๐ข ๐๐ข๐๐ ๐๐๐ฆ๐ฆ
๐ญ. ๐ฃ๐ฅ๐ข๐ฉ๐ ๐๐ก๐ฆ๐ง๐๐๐ ๐ข๐ ๐ฆ๐๐๐ฅ๐.
Most checks do not need the record. They need one fact. @primus_labs zkTLS lets a user prove a fact from a web account without sharing credentials or the raw record. the Developer Hub even let a template return only a condition result, such as true or false against a threshold, or a SHA256 hash of a field, instead of the plaintext value. that is data minimization built into the output.
๐ฎ. ๐๐ข๐ ๐ฃ๐จ๐ง๐ ๐ช๐๐ง๐๐ข๐จ๐ง ๐ฆ๐๐๐๐ก๐.
Sometimes the data has to be used, not just checked. FHE lets contracts compute on encrypted values. Designs in the Primus and ecosystem point at this: an encrypted deposit option in the Confidential Vault on BNB Chain, sealed-bid auctions and private voting where choices stay hidden.
๐ฏ. ๐ฉ๐๐ฅ๐๐๐ฌ ๐๐ก๐ฆ๐ง๐๐๐ ๐ข๐ ๐ง๐ฅ๐จ๐ฆ๐ง.
The open-source half of the argument matters as much as the cryptography. If a system keeps data safe only because you trust the operator, you have moved the toxic waste, not removed it.
๐ง๐๐ ๐๐๐ง๐๐, ๐ฆ๐ง๐๐ง๐๐ ๐ฃ๐๐๐๐ก๐๐ฌ
- A proof still reveals something: that an account exists, or that a threshold was met. Minimal is not zero.
- Verifiers can start new piles. If an app stores every proof output, it has rebuilt the problem.
- zkTLS proves provenance, not truth. A clean proof of a wrong source is still wrong.
- Trust remains in places: attestors, TEEs and key management. Penalties and governance are not yet active and the key service uses a single TEE today with threshold MPC planned.
๐ช๐๐๐ง ๐ ๐ช๐ข๐จ๐๐ ๐๐ข ๐๐ฆ ๐ ๐๐จ๐๐๐๐๐ฅ
- Ask for the answer, not the record: use a condition instead of a value.
- Keep outputs small and expire what you store.
- Make verification reproducible so users are not asked to trust you.
- Publish limits next to features.
My view: "toxic waste by default" is less a slogan than a design rule. the best data policy is the dataset you never had to hold.
What is one thing your favorite app collects that it could simply have proven instead?
๐น๐๐๐๐ฆ retweeted
๐ป๐๐ ๐บ๐๐๐๐๐ ๐ฉ๐๐๐๐๐ ๐ฐ๐ ๐ด๐๐๐๐๐๐ ๐ถ๐๐๐๐๐๐
Almost every serious democracy settled this centuries ago: a vote works best when nobody can see how you cast it. Onchain governance quietly dropped that rule. Most DAO votes are public, live and attributable to a wallet.
๐ช๐๐ฌ ๐ข๐ฃ๐๐ก ๐ฉ๐ข๐ง๐๐ก๐ ๐๐๐ก๐๐ฆ ๐ง๐๐ ๐ข๐จ๐ง๐๐ข๐ ๐
โข Herding: when large holders vote early, everyone else can follow instead of think.
โข Pressure: a visible vote can be questioned, criticized or punished.
โข Vote buying: a public vote is easy to verify, which makes it easy to pay for.
โข Late swings: voters can watch the tally and time their move.
๐๐ข๐ช ๐ฃ๐ฅ๐๐ฉ๐๐ง๐ ๐ฉ๐ข๐ง๐๐ก๐ ๐ช๐ข๐ฅ๐๐ฆ
๐ญ. ๐ฃ๐ฅ๐ข๐ฃ๐ข๐ฆ๐๐: a proposal is created and published, either off-chain in a Snapshot style or on-chain in a Tally style. a subset of zkFHE nodes creates a shared public key for it.
๐ฎ. ๐ฉ๐ข๐ง๐: each voter encrypts their choice under that key and submits the encrypted vote.
๐ฏ. ๐ง๐๐๐๐ฌ: once enough votes arrive, they are combined while still encrypted into one encrypted result.
๐ฐ. ๐ฅ๐๐ฉ๐๐๐: that result is threshold-decrypted, so only the outcome is published.
๐ช๐๐๐ง ๐ฆ๐ง๐๐ฌ๐ฆ ๐ฃ๐ฅ๐๐ฉ๐๐ง๐, ๐๐ก๐ ๐ช๐๐๐ง ๐๐ข๐๐ฆ ๐ก๐ข๐ง
Private: each voter's choice.
Public: the final result.
Also public, and this is the part worth reading twice: token balances.
The design cannot hide token quantities because the snapshot block is public. In weighted voting, voting power therefore stays visible even when the choice is not.
๐ช๐๐๐ฅ๐ ๐ฃ๐ฅ๐๐ ๐จ๐ฆ ๐๐๐ง๐ฆ
@primus_labs FHE work, FHETransform, is built so smart contracts can compute on encrypted data. private voting is one of the use cases.
zkTLS could help prove eligibility, such as membership or an offchain credential, without exposing the account behind it.
zkTLS proves where data came from without handing over account access. It proves provenance, not that the data is the full story and a proof is a moment in time.
๐ค๐จ๐๐ฆ๐ง๐๐ข๐ก๐ฆ ๐ช๐ข๐ฅ๐ง๐ ๐๐ฆ๐๐๐ก๐
๐ญ. Should a DAO hide choices but show voting power, or hide both?
๐ฎ. Would you trust a private tally you could not recount yourself?
๐ฏ. Which votes deserve secrecy first: treasury spends, grants, or leadership?
and which part of DAO voting would you make private first?
๐๐ก๐ ๐๐ฎ๐๐ญ๐ข๐จ๐ง ๐๐ซ๐จ๐๐ฅ๐๐ฆ ๐๐จ๐๐จ๐๐ฒ ๐๐๐ฅ๐ค๐ฌ ๐๐๐จ๐ฎ๐ญ...
In most auctions the winning bid is public by design. the losing bids are what leak and they carry strategy: how a bidder values an asset, how much risk it will take and what else it may be chasing.
๐ช๐๐๐ง ๐ ๐ฆ๐๐๐๐๐ ๐๐๐ ๐๐ฆ ๐ ๐๐๐ก๐ง ๐ง๐ข ๐๐ข
Bids stay hidden until the round closes, so nobody can anchor on or front-run what others offered. on a public chain that is the hard part. Transparent state means bids are visible unless something protects them.
๐๐๐ ๐๐๐ ๐
๐๐ ๐๐๐๐๐๐๐ ๐๐๐๐๐ โฆ
๐ญ. ๐ฆ๐๐ง๐จ๐ฃ. The auction contract works with a zkFHE network and a subset of nodes creates a shared public key.
๐ฎ. ๐๐๐๐๐๐ก๐. Participants encrypt their bids under that key, optionally locking collateral in the contract.
๐ฏ. ๐๐๐ข๐ฆ๐. Bidding ends at a predefined time.
๐ฐ. ๐ช๐๐ก๐ก๐๐ฅ. The network compares and sorts the bids while they are still encrypted: highest bid in a first-price auction, second-highest in a Vickrey auction.
๐ฑ. ๐ฅ๐๐ฆ๐จ๐๐ง. The winning bid is threshold-decrypted and the contract records the winner and price onchain.
๐พ๐ฏ๐จ๐ป ๐บ๐ป๐จ๐๐บ ๐ฏ๐ฐ๐ซ๐ซ๐ฌ๐ต
Bid amounts stay encrypted during bidding and evaluation. the winner and winning price are revealed at the end. revealing individual bids earlier as optional, so that is a design choice, not a given.
๐ช๐๐๐ฅ๐ ๐๐ง ๐๐ข๐จ๐๐ ๐ ๐๐ง๐ง๐๐ฅ
Third-party commentary points to institutional asset sales, treasury auctions, token launches and corporate bidding. anywhere a losing bid exposes a strategy is a candidate.
๐ช๐๐๐ฅ๐ @primus_labs ๐๐๐ง๐ฆ
FHE handles the computation and threshold decryption reduces reliance on a single decryption authority. one idea and not a published feature: zkTLS could prove a bidder is eligible, such as holding enough funds, without exposing the account behind it. Primus Proof of Reserves, live for Unitas USDu and Perena USD* with Brevis, is built around verifiable evidence instead. zkTLS proves where data came from without handing over account access. It proves provenance, not that the data is the full story, and a proof is a moment in time.
๐ค๐จ๐๐ฆ๐ง๐๐ข๐ก๐ฆ ๐ช๐ข๐ฅ๐ง๐ ๐๐ฆ๐๐๐ก๐
๐ญ. Should a sealed-bid auction ever reveal losing bids?
๐ฎ. How can a bidder verify the auction followed its rules?
๐ฏ. How much cost and delay is acceptable for private bidding?
My view: private bidding is a clear fit for encrypted computation. the real test is not the cryptography. It is whether the rules and trust model hold up in a live auction.
Which would you want first: hidden losing bids, or proof the auction was fair?
๐น๐๐๐๐ฆ retweeted
There is more to the @FungoLabs Genesis NFT auction than simply deciding how much cZAMA you want to bid. Understanding the pricing and allocation process is equally important before participating.
Unlike traditional auctions, where every successful bidder pays the exact amount they offered, $Fungo is introducing a sealed-bid auction with a uniform clearing price.
So, how does this actually work?
First, participants submit their bids privately in cZAMA. You won't be able to see what other bidders are offering, which means everyone makes their decision without knowing the competition's bids.
Once the auction closes, all submitted bids are arranged from the highest to the lowest. The available NFTs are then allocated to participants with the highest qualifying offers until the supply is filled.
Now, here's the interesting part.
Winning with a higher bid doesn't mean you'll have to pay the full amount you offered. Instead, all successful bidders settle at the same price, known as the clearing price. This is determined by the lowest accepted winning bid.
For example, if you bid higher than the final clearing price and successfully secure an NFT, you don't lose the extra amount. The difference between your original bid and the clearing price is refunded.
There is also a situation where multiple participants submit identical bids at the clearing price, but the remaining NFT supply isn't enough to accommodate everyone. In that case, Fungo applies a pro-rata allocation system to distribute the remaining NFTs proportionally.
One detail nobody should overlook is that bids are binding. This means you should carefully consider your budget and only commit an amount you are comfortable with before submitting.
I think understanding these mechanics is important because participating in an NFT auction shouldn't be based on excitement alone. Knowing how bids are ranked, how the final price is established and how allocations work gives you a much clearer picture of what you're getting into.
Take time to understand the process before making your move.
๐น๐๐๐๐ฆ retweeted
One thing I find interesting about @StabilizerFi is how it approaches the backing of its stablecoin, USDZ.
USDZ is designed to be fully backed by stablecoins, meaning every token in circulation must have an equivalent amount of collateral held in the protocol's reserves.
At launch, the backing comes from five supported stablecoins:
โข USDT
โข USDC
โข USDS
โข USDG
โข PYUSD
But what makes this model interesting is how Stabilizer handles its reserves.
Instead of using the assets sitting in its trading pools as collateral, Stabilizer keeps the backing reserves separate through dedicated adapter contracts.
Why is this important?
Well, the trading pools and collateral reserves have different responsibilities.
The AMM pools are where users carry out their swaps, while the adapters hold and manage the assets that actually back USDZ.
This means that when someone swaps stablecoins on Stabilizer, it doesn't automatically affect the reserves backing USDZ. Those reserves only change when users mint or redeem USDZ.
Another thing worth looking at is the 1:1 collateral model.
USDZ is minted against an equal amount of collateral. There are no borrowing positions, no liquidation process and no need for users to provide extra collateral above the amount being minted.
In simple terms, the protocol cannot mint more USDZ than its available backing reserves support.
I like that Stabilizer keeps things straightforward here. It separates the assets used for trading from the assets responsible for maintaining the backing of its stablecoin.
Because at the end of the day, having a stablecoin that targets $1 is one thing, but having a clear system for managing its reserves and supporting redemption is just as important.
That's an important part of what makes USDZ worth understanding.

























