Crypto Citys

I have been thinking about the application discovery problem on Midnight for the past few days and I cannot shake the feeling that it is one of those challenges that sits so far outside the normal blockchain conversation that the people building the ecosystem have not fully confronted what it actually means for user adoption and I think when it finally becomes visible it is going to feel like a wall that nobody saw coming 😂

let me explain why this one caught my attention because it starts from a place that sounds almost too simple to be interesting and then gets genuinely complicated very quickly.

on a transparent blockchain discovering applications is straightforward. you go to a block explorer. you see which contracts are getting the most transactions. you see which applications are growing. you see on-chain activity metrics that tell you which protocols are live, which are being used, which are attracting capital, which are dying. the entire competitive landscape of the application ecosystem is visible to anyone who knows how to read the data.

that transparency serves a function that nobody explicitly designed it for but that turns out to be enormously valuable. it creates a discovery layer. users looking for applications can see which ones are actually being used by real people. developers evaluating whether to build can see which categories of application are underserved. investors looking for opportunities can see which protocols are gaining traction. journalists and researchers can report on ecosystem growth. the transparency of the chain is itself a distribution mechanism for applications.

Midnight's private layer destroys that discovery layer completely.

and I mean completely. not partially. not for some categories of information but not others. completely.

an application operating on Midnight's shielded layer produces almost no observable on-chain signal of its activity. the number of users it has is invisible. the volume of transactions it processes is invisible. the growth rate of its user base is invisible. whether it is being used by one person or ten thousand is invisible. whether it launched last week or has been running for two years is essentially indistinguishable from the outside.

the private application exists. the evidence that it is being used does not.

now think about what that means from a user's perspective trying to navigate the Midnight application ecosystem.

how do you decide which private application to trust with your sensitive data.

on a transparent chain you look at the on-chain metrics. this protocol has processed five billion dollars in volume over two years with no security incidents. that track record is visible and verifiable. the chain itself is the trust signal.

on Midnight the chain cannot provide that signal. the application's usage history is private. its transaction volume is private. its user retention is private. the evidence that would normally build trust in a financial or privacy-sensitive application is exactly the evidence that the privacy model is designed to suppress.

so what does trust building actually look like for a Midnight application.

the first answer most people reach for is reputation. the development team has a public reputation. they have published their code. they have a history in the ecosystem. you trust the application because you trust the people who built it.

that works for early adopters in the technical community who know the developers personally or by reputation. it does not scale. the vast majority of users who will eventually use Midnight applications are not going to research the development team's GitHub history before deciding whether to trust an application with their private medical data or their private financial records. they need trust signals that are accessible without technical expertise and legible without industry context.

on a transparent chain those accessible legible trust signals come from on-chain metrics. usage volume. longevity. absence of exploits. these are things that non-technical users can understand and act on even without knowing anything about the technical design of the application.

on Midnight none of those signals exist for private applications.

the second answer people reach for is audits. third party security audits of the application code. if a reputable auditing firm has reviewed the code and found no critical issues that is a meaningful trust signal that does not depend on on-chain transparency.

audits are real and they matter. but they have important limitations as a primary trust mechanism for a broad user base.

first audits are expensive. not every legitimate application can afford a comprehensive audit from a top-tier firm especially in early stages of development. the barrier to getting a credible audit creates a cost advantage for well-capitalized applications and a disadvantage for smaller developers with good ideas but limited resources.

second audits certify code at a point in time. they do not provide ongoing assurance that the application is behaving as intended. an application that passed an audit two years ago and has since been updated multiple times is not the same as an application that passed an audit last week.

third and most importantly audits assess whether the code does what it claims to do. they do not assess whether what the code claims to do is actually what users need it to do. an application can be technically correct and still be designed in ways that subtly undermine the privacy guarantee it claims to offer through architectural choices that no audit would flag as incorrect.

the third answer is community reputation. word of mouth within the ecosystem. social proof from trusted voices who have evaluated and recommended specific applications.

community reputation works in tight-knit communities where trust networks are dense and information flows quickly. it breaks down as the community grows and as the signal-to-noise ratio in community channels degrades. in a large ecosystem with many applications and many voices community reputation becomes difficult to aggregate reliably and easy to manipulate through coordinated promotion.

and here is the specific failure mode I am most worried about.

the absence of on-chain discovery signals creates a vacuum. and vacuums get filled. the vacuum that Midnight's private layer creates in the application discovery space will get filled by off-chain marketing. by the applications that can spend the most on visibility rather than the ones with the most genuine usage. by influencer promotion and paid content and manufactured social proof that mimics organic trust signals without the underlying substance.

on a transparent chain marketing has to compete with on-chain reality. you can spend heavily on promotion but users can check the metrics and see whether the usage matches the hype. the chain is an accountability mechanism for claims about application quality and adoption.

on Midnight's private layer there is no on-chain accountability mechanism for marketing claims about private application usage. an application that claims to have thousands of active users cannot be verified or falsified by looking at the chain. the privacy design that protects legitimate users also protects misleading claims about application adoption.

that asymmetry between marketing claims and verifiable reality is not a small problem. it is a fundamental feature of how information works in private systems and it has serious consequences for how the competitive dynamics of the application ecosystem develop.

the applications that win market share in the early Midnight ecosystem will be the ones with the best marketing and the most trusted brand presence not necessarily the ones with the best design or the most genuine usage. that is true to some extent in every market but it is much more true in markets where on-chain verification of usage claims is impossible.

I keep thinking about what legitimate infrastructure for private application discovery could actually look like.

one direction is voluntary transparency proofs. applications that want to build trust publish ZK proofs of their aggregate usage metrics. not the individual transaction data. not the private user information. just provable aggregate facts. this application has processed more than ten thousand unique users. this application has been running continuously for more than eighteen months. this application's transaction volume has grown at more than twenty percent month over month for the past six months.

those aggregate facts can be proven with ZK proofs without revealing anything about individual users. an application that publishes credible aggregate proofs of its usage is providing trust signals that users can act on without compromising the privacy of any individual.

the complication is that voluntary transparency proofs are voluntary. applications with strong genuine metrics have every incentive to publish them. applications with weak metrics have no incentive to publish them and may prefer to remain opaque. the distribution of applications that publish voluntary proofs is not a random sample of all applications. it is a selection of the applications with the best metrics — which looks like a useful signal until you realize that absence of a voluntary proof is itself informative and sophisticated bad actors will find ways to generate plausible-looking proofs of metrics that do not reflect genuine usage.

another direction is ecosystem-level reputation infrastructure. a decentralized system where users can attest to their experience with specific applications in a way that is aggregated and made public without revealing individual identities. a privacy-preserving review system where the aggregate quality signal is public even though each individual reviewer is anonymous.

that is technically achievable. it is also a governance challenge and an incentive design challenge. who runs the reputation infrastructure. how are gaming attempts detected and filtered. how do you prevent coordinated manipulation of reputation scores. these are not unsolvable problems but they require investment and careful design that goes beyond what any individual application developer can provide on their own.

the third direction is something I find genuinely interesting and that I have not seen discussed anywhere. it is the idea of application behavior attestation through SPOs.

SPOs process transactions. they can observe certain things about transaction patterns at the block level without seeing transaction content. they know how many transactions were processed in each block. they know the timing distribution. they know the fee distribution. they know which applications received transactions and when.

an SPO that has been processing Midnight blocks for two years has observed the behavioral history of every application on the network at the block level. not the content. but the pattern. that behavioral observation could potentially be aggregated into a trust signal that is rooted in the direct observation of network participants rather than in self-reported metrics or third-party audits.

SPO-attested application behavior metrics would be hard to fake because faking them would require convincing multiple independent SPOs to attest to false information. the decentralized nature of the attestation base is itself a trustworthiness property.

the complication is that SPO-level observation of application transaction patterns is the same metadata that I was worried about as a privacy attack vector in previous analyses. information that is useful for building application trust signals is also information that is useful for inference attacks against private state. the same data serving two completely different purposes with completely different implications depending on who is using it and why.

that tension does not have a clean resolution. every mechanism for building application trust in a private ecosystem creates some information that could theoretically be used to reduce privacy. the design question is whether the trust benefit is worth the inference cost and how to structure the mechanism to maximize the trust value while minimizing the privacy leak.

I want to be direct about something here because I think it is the most practically urgent point in all of this.

the application discovery problem is not a problem that solves itself as the ecosystem matures. in transparent chain ecosystems discovery infrastructure emerged organically because the underlying data was publicly available and entrepreneurs built tools on top of it. block explorers, analytics platforms, portfolio trackers, yield aggregators that compare returns across protocols — all of this infrastructure built itself because the data was there to build on.

on Midnight's private layer the data is not there. the infrastructure cannot build itself from available data because the relevant data is exactly what the privacy design suppresses. discovery infrastructure for the private layer has to be deliberately built by people who understand both the privacy constraints and the user trust requirements and who are willing to invest in a problem that is not as exciting as the cryptographic architecture but is just as important for whether ordinary users can actually navigate the ecosystem safely.
without that deliberate investment the Midnight application ecosystem faces a trust vacuum that will be filled by marketing rather than merit. the applications that win will be the ones with the most visibility not the ones with the most genuine value. and the users who most need the privacy guarantee — the ones trusting private applications with their most sensitive information — will have no reliable way to distinguish the applications worth trusting from the ones that are not.
the zero knowledge proofs protect the data inside the applications.
they cannot protect users from choosing the wrong application in the first place.
and right now the Midnight ecosystem does not have the infrastructure to help users make that choice well. 🤔
#NIGHT @MidnightNetwork $NIGHT

I have been sitting with the privacy public goods problem on Midnight for the past few days and the more I think about it the more I realize it is one of those economic design challenges that sits so quietly underneath the surface that most people will never notice it until the consequences are already showing up in the data 😂
let me explain what I mean because this one requires thinking carefully about incentives and how individual rational behavior can produce collectively irrational outcomes even in a well-designed system.
most people are familiar with the concept of public goods in economics. a public good is something that is non-excludable and non-rivalrous. non-excludable means you cannot prevent people from benefiting from it once it exists. non-rivalrous means one person benefiting does not reduce another person's ability to benefit. clean air is a public good. national defense is a public good. a lighthouse is the classic economics textbook example.
public goods have a well-known problem. because nobody can be excluded from the benefit and because one person's consumption does not reduce availability for others the individual incentive to contribute to the production of the public good is weak. everyone benefits whether they contribute or not. so individually rational actors tend to undercontribute relative to what would be collectively optimal. the public good gets underprovided. economists call this the free rider problem.
privacy on a network like Midnight is a public good in a specific and important sense.

the anonymity set — the crowd of people whose simultaneous private transactions provide cover for each individual's private transaction — is non-excludable and non-rivalrous in exactly the way public goods are. when you make a shielded transaction on Midnight you benefit from the cover provided by every other shielded transaction happening around the same time. you cannot be excluded from that benefit. and your use of it does not diminish its availability for the person making the next shielded transaction.
the size and density of the anonymity set is a public good that every Midnight user benefits from and every Midnight user contributes to by making shielded transactions.
and here is where the incentive problem arrives.
making shielded transactions costs DUST. DUST requires holding NIGHT. holding NIGHT has an opportunity cost. every shielded transaction a user makes contributes to the collective anonymity set — which benefits every other user — but the individual user bears the full cost of that contribution themselves.
from a purely individual rational perspective a Midnight user should minimize their shielded transaction count. make transactions public where the privacy benefit to themselves personally is low. only use the shielded layer when the individual benefit clearly exceeds the individual cost.
that individual optimization is rational. it is also collectively destructive.
if every user makes the individually rational choice to minimize shielded transactions the anonymity set shrinks. the crowd gets thinner. the privacy protection for the users who do make shielded transactions degrades. the people who most need privacy — the ones with the most serious threat models — find themselves in an increasingly thin crowd because everyone else made the rational choice not to contribute to it.
the public good of anonymity set density gets underprovided because the individual incentive to contribute to it is weak relative to the individual cost of contributing.
and here is the part that makes this specifically difficult on Midnight compared to other privacy networks.
on a simple privacy coin like Zcash the cost of a shielded transaction is just the transaction fee. the fee is denominated in the network's native token. the relationship between making a shielded transaction and contributing to the anonymity set is direct and the cost is low enough that many users make shielded transactions routinely even without thinking carefully about their contribution to the collective anonymity set.
on Midnight the cost structure is different. DUST accrual from NIGHT holdings means that the cost of shielded transactions is tied to the opportunity cost of holding NIGHT. for a user who values their NIGHT position — who is watching the price, who is thinking about their overall crypto portfolio allocation — the implicit cost of making shielded transactions is not just the DUST fee. it is the ongoing commitment to holding NIGHT at a sufficient level to generate the DUST required for their transaction patterns.
that is a higher and more visible cost than a simple transaction fee. and higher more visible costs produce stronger optimization pressure. users who face a clear ongoing cost from their NIGHT holding commitment to support their shielded transaction patterns have a stronger individual incentive to minimize those patterns than users who just pay a small fee per transaction.
the very design that makes DUST economically elegant — the passive accrual from holdings, the non-transferable non-asset properties — also makes the individual cost of contributing to the anonymity set more salient and therefore more likely to be optimized away.
I keep thinking about what this means for the distribution of shielded transaction behavior across the Midnight user base.
the users who will consistently make shielded transactions regardless of cost are the users with the most serious privacy needs. the ones for whom the individual benefit of shielded transactions clearly and obviously exceeds the individual cost. these users contribute to the anonymity set not because of any collective consideration but because their own threat model demands it.
the users who will make shielded transactions inconsistently — sometimes when it feels important, sometimes defaulting to public transactions when the cost feels salient — are the casual privacy users. the ones who value privacy as a preference rather than a necessity. these users could contribute enormously to the anonymity set if their transaction patterns were consistently shielded but the individual incentive to do so is weak enough that their contribution is unreliable.
the users who will consistently minimize their shielded transaction footprint are the ones who are most cost-sensitive and least privacy-motivated. they may be on the network for reasons that have nothing to do with privacy — as SPOs, as application developers, as speculators in NIGHT — and they see no individual reason to contribute to an anonymity set that benefits others more than themselves.
the result of that distribution is a core of high-need users surrounded by an unreliable periphery of casual contributors and a non-contributing majority.
that is not the anonymity set structure you want. a good anonymity set is large, dense, and behaviorally unpredictable. it has many users making shielded transactions with diverse patterns at diverse times. the high-need user is indistinguishable from the casual user because both are making shielded transactions routinely.
a bad anonymity set is small, sparse, and behaviorally predictable. the high-need users stand out because they are the only ones consistently using the shielded layer. their consistent usage is itself a signal.
the free rider problem on anonymity set contribution pushes Midnight toward the bad structure even if the user base is large and even if the cryptographic architecture is perfect.
I want to think about what the design responses to this problem actually look like because I do not think it is unsolvable. it is hard but it is the kind of hard that thoughtful incentive design can make progress on.
one direction is default shielded transactions. if the application layer makes shielded the default — if users have to actively choose to make a public transaction rather than actively choosing to make a private one — then the anonymity set gets contributions from users who never thought carefully about whether to contribute. the casual user who just wants to transact goes through the shielded path not because they value privacy but because it is the path of least resistance.
this is the most powerful intervention available because it does not require changing user incentives. it changes user behavior by changing the default without requiring any individual user to think about their contribution to the collective anonymity set.
the obstacle is that application developers control the default. and application developers have their own incentive structure that does not necessarily align with maximizing anonymity set density. a developer who is optimizing for transaction throughput or application performance might prefer public transactions as the default because they are computationally cheaper and faster. a developer who is building for a user base that does not need privacy might see no reason to default to shielded transactions.
getting consistent default shielded behavior across the application ecosystem requires either developer education and advocacy or protocol-level incentives that make defaulting to shielded transactions economically attractive for developers as well as collectively beneficial for users.
another direction is anonymity set subsidies. some mechanism that compensates users for making shielded transactions beyond the individual privacy benefit they receive. if making a shielded transaction earns you a small reward — some fraction of the public good value your contribution creates — the individual incentive to contribute is increased and the free rider problem becomes less severe.
the complication is that anonymity set subsidies require funding from somewhere. they add to the protocol's cost structure. and they create a new attack surface — users who make shielded transactions not because they have any privacy need but purely to earn the subsidy. those users are contributing to the anonymity set in a narrow technical sense but their transaction patterns are not behaviorally diverse in the way that makes a good anonymity set. a homogeneous subsidy-farming transaction pattern is recognizable and reduces the inferential value of the anonymity set even while increasing its size.
the third direction is what I think of as coordinated privacy. applications that batch their users' shielded transactions together in ways that increase the effective anonymity set beyond what individual user transactions would produce. if an application processes ten thousand users' private interactions in a coordinated batch the batch as a whole provides cover that none of the individual transactions would have on their own.
this is similar to the design philosophy behind tornado cash and similar mixing protocols but applied at the application layer rather than the protocol layer. coordinated privacy moves the anonymity set management burden from individual users to application operators who have both more incentive to optimize it and more architectural leverage to do so.
the complication is that coordinated privacy requires trusting the application operator with the coordination role. an operator who manages the batching of shielded transactions has a privileged position relative to individual users that a pure ZK protocol does not require. it reintroduces a trust assumption at exactly the point where the architecture was supposed to eliminate trust assumptions.
I do not have a clean answer to the privacy public goods problem. I am not sure there is one. the free rider problem in public goods provision is one of the oldest and most studied problems in economics and it does not have a general solution that works in all contexts.
what I do think is that the Midnight ecosystem needs to take this problem seriously as a first class design consideration rather than assuming that the privacy demand of high-need users will naturally produce an anonymity set large enough to protect them.
high-need users alone cannot produce a large anonymity set. they need the casual users. they need the developers. they need everyone on the network contributing to the shielded layer even when their individual privacy motivation is low.
getting that contribution requires more than good cryptography and elegant tokenomics. it requires incentive design and default behavior design and application layer design that all push in the same direction.
and it requires the people building on Midnight to understand that when they choose to route their application's transactions through the public layer instead of the shielded layer they are not just making a technical performance optimization.
they are free riding on the anonymity set that other users' shielded transactions produce while choosing not to contribute to it themselves.
that choice is individually rational. it is collectively costly. and the people who pay the cost are the ones who needed the privacy most. 🤔
#NIGHT @MidnightNetwork $NIGHT

Em nossa era hiperconectada, muitas vezes confundimos acesso com intimidade. Podemos fazer chamadas de vídeo para um ente querido do outro lado dos oceanos, compartilhar nossos pensamentos mais profundos com estranhos em fóruns como Midnight Network e acessar a soma do conhecimento humano com um toque. Garantimos direitos digitais que pareceriam miraculosos há apenas algumas décadas: o direito à privacidade (por mais frágil que seja), o direito à livre expressão, o direito à informação. No entanto, uma solidão profunda e persistente paira sobre esse progresso, levantando uma questão desconfortável: a robusta arquitetura de nossos direitos digitais pode realmente curar o isolamento que se aloja no coração de nossa existência conectada?

Eu estive mergulhado em um buraco de coelho pensando sobre o problema do oráculo na Midnight nos últimos dias e acho que é um daqueles desafios que fica tão quieto por baixo de tudo que a maioria das pessoas nem percebe que existe até que tentem construir algo real e de repente batem em uma parede que não viram chegando 😂
deixe-me explicar o que quero dizer porque este requer uma configuração cuidadosa antes que a parte interessante chegue.
oráculos são o mecanismo pelo qual as blockchains aprendem coisas sobre o mundo real. um contrato inteligente por si só é um sistema fechado. ele sabe o que está na cadeia. ele conhece seu próprio estado. ele sabe o que outros contratos lhe dizem. mas não tem uma maneira nativa de saber qual é o preço de um ativo em uma bolsa externa ou se um voo foi atrasado ou qual é o clima ou se um evento específico do mundo real ocorreu.

Estive refletindo sobre o problema da atualização do protocolo em Midnight nos últimos dias e quanto mais penso sobre isso, mais percebo que é um dos desafios mais singularmente difíceis que uma rede de privacidade enfrenta e quase ninguém está tratando isso com a seriedade que merece 😂
deixe-me explicar por que este é diferente do problema regular de atualização de blockchain, porque a diferença é extremamente importante.
em um protocolo de blockchain regular, as atualizações são complicadas, mas a complicação é principalmente social e política. você tem que fazer a comunidade concordar com a mudança. você tem que coordenar mineradores ou validadores para adotar o novo software. você tem que gerenciar o risco de uma divisão da cadeia se uma parte significativa da rede discordar. esses são desafios reais e eles se desenrolaram publicamente e às vezes dolorosamente ao longo da história do Bitcoin e do Ethereum e de dezenas de outras redes.

a coisa que na verdade me mantém acordado sobre a Midnight não é a camada de privacidade em si — é a fronteira entre o estado privado e o estado público e o que acontece quando uma aplicação precisa cruzá-la 😂
deixe-me explicar o que quero dizer porque este leva um segundo para ser configurado corretamente.
a Midnight é construída em torno de um modelo de estado duplo. você tem estado privado — dados que vivem no ambiente protegido, protegidos por provas de conhecimento zero, invisíveis para o mundo exterior. e você tem estado público — dados que vivem na cadeia, visíveis para todos, permanentes e auditáveis da maneira que os dados da blockchain sempre são.

honestamente? a coisa que ninguém está perguntando sobre o Midnight é o que acontece com a garantia de privacidade quando a camada de aplicação é intimada e eu acho que essa pergunta vai importar muito mais cedo do que a maioria das pessoas espera 😂
deixe-me explicar por que continuo voltando a isso.
as garantias de privacidade criptográficas no Midnight são reais. Quero ser claro sobre isso desde o início, porque o que estou prestes a dizer não é uma crítica à arquitetura ZK — é uma pergunta sobre a camada que está em cima dela. o modelo de transação protegida funciona. as provas de conhecimento zero fazem o que devem fazer. os dados que são protegidos permanecem protegidos no nível do protocolo.

para ser honesto? Eu venho pensando sobre a camada de prova de conhecimento zero em Midnight há semanas e não acho que as pessoas entendam completamente o que isso significa para os desenvolvedores de aplicações tentando construir sobre isso 😂
deixe-me começar com a coisa que realmente me surpreendeu.
a maioria das pessoas, quando ouvem falar de provas de conhecimento zero, pensa em privacidade no sentido simples. você pode provar que algo é verdadeiro sem revelar os dados subjacentes. esse é o título. é sobre isso que se escreve na mídia cripto. e é real — essa capacidade realmente existe e é genuinamente valiosa.

História verdadeira.
Da primeira vez que vi alguém mencionar a campanha do token NIGHT, pensei que era interessante e continuei rolando. Na segunda vez, eu realmente parei e li um pouco, mas então me distraí e esqueci completamente sobre isso. Na terceira vez que vi, estava sentado em uma cafeteria sem nada mais para fazer e pensei, sabe de uma coisa, deixa eu realmente ler tudo isso corretamente desta vez.
A melhor decisão que tomei naquela semana.
Não porque mudou minha vida ou algo dramático assim. Apenas porque acabou sendo uma daquelas coisas raras em cripto que é exatamente o que diz ser. Sem surpresas estranhas no meio do caminho. Sem termos enterrados no fundo que mudam completamente a imagem. Apenas uma oportunidade direta que recompensa as pessoas que realmente aparecem.

Meu amigo riu de mim por ter me juntado a isso. Ele não está mais rindo.
Então, algumas semanas atrás, eu mencionei a um amigo que estava entrando nessa coisa da campanha do token NIGHT e ele literalmente riu. Não de forma maldosa. Apenas daquela maneira que as pessoas fazem quando acham que você está prestes a perder seu tempo em algo que não vai dar certo.
Ele disse e eu cito — "mais uma daquelas coisas de cripto onde você faz um monte de trabalho e não ganha nada."
Eu não discuti com ele. Eu apenas continuei.
Avançando para agora, adivinha quem me enviou uma mensagem perguntando como se inscrever? É.