Zoya Research

I kept coming back to one question while looking at Dusk and NPEX:

Can a regulated market be auditable without turning every investor’s financial activity into public data?

NPEX makes this more than a theoretical question. Dusk’s work with the regulated Dutch exchange gives that question a real-world context: regulated securities, investors and market infrastructure have to operate within rules that require both oversight and confidentiality.

That creates a specific problem.

A regulator may need to verify that an investor is eligible or that a transaction follows the required conditions. But that does not automatically mean every other market participant should see the underlying financial information.

This is where Dusk’s architecture gets interesting.

Its Phoenix transaction model keeps balances and transfers shielded, while zero-knowledge proofs can establish transaction validity without exposing the underlying details. When additional evidence is required, viewing keys can provide selective access.

So privacy here isn’t simply about hiding data.

It changes the question from “Is the information public?” to “Who needs to prove or see what?”

But the real test is what happens when an actual regulated security moves through this workflow: who can see what, who can prove what, and how much manual coordination is still required behind the scenes?

That’s the part I don’t think should be assumed.

If those permissions can actually be enforced onchain across investors, issuers, venues and supervisors, does privacy become more than a compliance feature — does it become part of the market infrastructure itself?

@Dusk $DUSK #dusk

I went back through Dusk’s privacy model today because one question kept bothering me: if regulated markets still need visibility, what exactly is privacy protecting?

The more I looked at it, the less I think the answer is simply “hide the transaction.”

A financial institution may need to prove that something happened, while a competitor may have no reason to see the underlying position, balance, or other sensitive information.

That creates a different problem.

It’s not really privacy versus transparency. It’s about whether different participants can have different levels of access to the same financial workflow.

That’s where Dusk’s idea of programmable privacy caught my attention.

Sensitive information can remain protected while authorized parties can still receive what they need for review. For regulated finance, that distinction feels more useful than simply calling something a “private blockchain.”

The difficult part is deciding how those permissions should work across regulators, issuers, investors and other participants without turning every transaction into a fully public record.

That’s the part I’m still watching.

If different participants need different levels of visibility, can programmable privacy become a practical way to balance confidentiality with regulatory oversight?

@Dusk $DUSK #dusk

I used to think privacy in financial markets mostly meant hiding sensitive information from public view.

The more I look at Dusk, the more I think that definition is too narrow.

What caught my attention is the idea of programmable privacy: keeping sensitive information confidential where it needs to be, while still allowing the right information to be disclosed when an authorized party needs to review it.

That distinction matters in regulated markets.

A financial application doesn’t necessarily need every piece of data to be visible to everyone. It needs the right parties to be able to verify what they are entitled to verify, while the underlying sensitive information remains protected.

That makes privacy feel less like a switch between “public” and “private” and more like something that can be built into the way financial applications operate.

That’s what makes Dusk’s XSC approach interesting to me: it raises the question of how confidentiality can coexist with compliance-oriented asset rules and settlement.

But I’m still wondering how far programmable privacy can go in real institutional workflows.

If regulated markets need privacy, transparency and authorized disclosure at the same time, can programmable privacy actually reduce the complexity of traditional financial data sharing?

@Dusk $DUSK #dusk

I used to think EVM compatibility mainly solved the developer onboarding problem.

If DuskEVM supports familiar Ethereum languages and tooling, including Solidity and Vyper, developers can start building without learning an entirely different smart-contract environment first.

That matters.

But the more I look at Dusk in the context of financial applications, the more I think that only solves one layer of the problem.

A developer can deploy an application using familiar tools. That doesn’t automatically answer who is allowed to interact with it, what information should remain confidential, how eligibility is enforced, or how the application fits into the wider financial workflow.

That distinction caught my attention.

EVM compatibility can reduce the coding barrier.

It may not reduce the institutional complexity around the application.

And for regulated financial markets, that second part could be the harder problem.

I’m still watching how these two layers come together.

If DuskEVM makes building familiar, does the real bottleneck simply move from developer adoption to institutional integration?

@Dusk $DUSK #dusk

I kept coming back to Dusk Trade today because calling it a “neobroker” doesn’t really explain what caught my attention.

The interesting part isn’t just being able to buy or sell a tokenized bond, fund, or other financial asset.

It’s what has to happen around that trade.

An investor may need to discover the asset, complete eligibility checks, connect a wallet, place an order, and then have the asset and payment legs coordinated through settlement.

What caught my attention is how Dusk Trade approaches those workflows rather than treating the token as the whole product.

That made me rethink the usual RWA narrative.

The hard part may not be putting a financial asset onchain.

It may be making the steps around that asset work together without recreating the same fragmented process behind a new interface.

That’s where I’m still unsure.

If Dusk Trade can bring onboarding, trading and settlement closer together, does that actually remove infrastructure complexity — or just move the complexity into the application layer?

I think that’s the part worth watching as tokenized markets become more practical.

@Dusk $DUSK #dusk

I went back through DuskEVM today because I wanted to understand what EVM compatibility actually changes beyond the headline.

One detail that stood out is that DuskEVM is built to work with familiar Ethereum development languages and tooling, including Solidity and Vyper.

That matters because developers don’t necessarily have to learn an entirely different smart-contract environment just to start building on Dusk.

But then I started thinking about what happens after that first step.

If deploying an application becomes easier, the harder questions for financial applications don’t disappear.

Who is allowed to interact with it?
What information needs to remain confidential?
How are compliance requirements enforced?
And how does the application connect to the rest of the financial workflow?

So I don’t think EVM compatibility is the interesting part by itself.

The interesting part is whether familiar developer infrastructure can actually lead to applications that work under real institutional constraints.

If DuskEVM removes the developer barrier, what becomes the next bottleneck for getting financial applications into real-world use?

@Dusk $DUSK #dusk

I’ve noticed the interesting part of @TermMax isn’t just that rates are fixed. It’s that the rate can be structured around how much of an order actually gets filled.

TermMax Range Orders use pricing curves with different segments. In a borrowing range order, earlier portions can carry higher APRs and later portions lower APRs as the order fills. For lending, the curve works in the opposite direction, with rates increasing across the defined portions.

That made me look at the order itself differently.

A range order isn’t simply saying, “this is my rate.” It defines how the rate can respond as different amounts of liquidity are taken.

But that also creates an interesting tension: the curve only matters if the market actually fills it. TermMax’s documentation also highlights unutilized capital and poorly configured pricing curves as risks for range-order setters.

So what I want to watch is how these curves behave when real demand moves through different order sizes.

Can the curve structure discover useful rates in practice, or does its effectiveness depend too heavily on getting the demand profile right?

#TermMax @TermMax

I still think most RWA conversations treat tokenization like the finish line.

Put an existing asset onchain, give it a digital representation, and suddenly it sounds like the financial asset itself has moved onchain.

But the more I look at Dusk’s approach to native issuance, the more I think there’s an important distinction.

Tokenization can represent an asset that already exists elsewhere. Native issuance starts from a different point: the infrastructure can be designed to carry more of the asset’s lifecycle onchain, depending on the legal and product setup.

That difference caught my attention.

Because if issuance happens in one system, ownership is tracked somewhere else, and transfers or settlement still depend on separate records, putting a token onchain doesn’t necessarily remove the underlying infrastructure problem.

So to me, the interesting part of native issuance isn’t simply creating another token.

It’s the possibility of reducing the gap between the digital asset and the financial infrastructure responsible for it.

I’m still cautious about how far that can actually go in regulated markets. Legal ownership, authorized intermediaries and operational responsibilities don’t disappear just because an asset is represented onchain.

So the real test for me isn’t how many RWAs can be tokenized.

If native issuance can move more of an asset’s lifecycle onto the ledger, what part of the traditional financial infrastructure becomes hardest to replace?

@Dusk $DUSK #dusk

I still think the interesting part of @TermMax is that one order doesn’t necessarily mean one rate.

TermMax range orders use pricing curves where different portions of an order can have different fixed APRs. As an order gets filled, the applicable rate moves along the curve instead of staying the same across the entire amount.

That made me look at TermMax less like a single-rate market and more like a market where order size itself becomes part of the pricing.

A borrowing range order can start at a higher APR and move toward lower rates as more of the order is filled. Lending curves work in the opposite direction, with rates increasing across the defined portions.

What I find interesting is what happens when these predefined curves meet actual demand. The curve sets the available terms, but market activity determines which portions actually get filled.

So I’m curious:

Can changing order size become a meaningful source of rate discovery on TermMax?

#TermMax @TermMax

I still think “fixed rate” can make a position sound more static than it actually is.

On TermMax, an FT represents the right to redeem 1 debt token at maturity. Before maturity, FTs can trade at a discount, while the holder can also keep them until maturity for redemption.

That made me look at fixed-rate positions differently.

The rate may be defined, but the market price of the FT still has time attached to it. As maturity gets closer, the gap between what the FT trades for and what it represents at maturity becomes a different part of the decision.

What I’m curious about is how that relationship behaves when liquidity changes and traders want to exit at different points before maturity.

Does the value of a fixed-rate position become more about the rate, or the time left to maturity?

#TermMax @TermMax

I still think the most interesting question around DuskEVM isn’t whether developers can use familiar EVM tooling.

It’s what happens when familiar EVM development meets the privacy requirements of regulated finance.

DuskEVM is designed as the EVM-compatible application layer in the Dusk stack, while Hedger is the privacy module for EVM workflows. What caught my attention is that Hedger uses homomorphic encryption and zero-knowledge proofs to support confidential transaction flows.

That creates an interesting tension.

In normal public blockchain environments, transparency makes verification easier. But financial institutions often have information that cannot simply be exposed to everyone.

So the challenge becomes more specific: can transactions remain confidential while still allowing the right information to be verified or disclosed when required?

My observation is that this is a much harder problem than simply “adding privacy” to an EVM environment.

I’m interested to see how this architecture behaves when real financial applications start using it.

If institutions need selective disclosure, who should ultimately control what becomes visible: the application, the regulator, or the protocol?

@Dusk $DUSK #dusk

I keep coming back to one question when I look at tokenized financial assets:

What happens after the asset gets onchain?

At first, I thought tokenization was the hard part. But the more I look at @Dusk, the more I think the bigger challenge is building a market around those assets.

That’s what caught my attention about Dusk Trade.

It’s being built as the application layer for tokenized financial assets on DuskEVM, with instruments like MMFs, ETFs and bonds designed to operate within a regulated market structure.

And that distinction matters.

A tokenized bond can exist onchain, but investors still need onboarding, ownership records, controlled transfers, trading and settlement. If those processes remain fragmented across different systems, putting the asset onchain only solves part of the problem.

To me, the real test isn’t simply how many assets can be tokenized. It’s whether the infrastructure around them becomes usable enough for those assets to actually function in a regulated market.

That’s the part of Dusk Trade I’m watching most closely.

If the asset is onchain but most of the market around it still runs offchain, has tokenization really changed the financial market itself?

@Dusk $DUSK #dusk

I still think the harder part of fixed-rate markets is not setting a rate. It’s what happens when that rate meets actual order flow.

TermMax V2 lets curators define pricing through range-order curves, while orders can be aggregated into the same market. FT represents the fixed-rate position, and it can be traded before maturity rather than only being held until the end.

That made me look at fixed-rate markets differently.

The rate is only one part of the position. Maturity also matters: an FT has a defined maturity, and its value changes as the remaining time to maturity changes.

What I want to see is how these mechanics behave when different curves, maturities, liquidity and real order flow start interacting in live markets.

Want to watch this in practice.

#TermMax @TermMax

Ainda acho que a maioria das conversas sobre RWA se concentra demais no momento em que um ativo se torna um token.

Quanto mais eu olho para a Dusk, mais penso que o problema mais difícil começa depois da tokenização.

Um ativo ainda precisa ser emitido, transferido, administrado e, por fim, liquidado. Se essas etapas continuarem dependendo de sistemas separados, colocar o ativo onchain não significa necessariamente que o processo financeiro em si tenha migrado para o onchain.

Foi isso que chamou minha atenção na abordagem nativa de emissão da Dusk: ela foi desenhada para apoiar mais do ciclo de vida do ativo no próprio ledger, em vez de tratar a tokenização como a linha de chegada.

O Dusk Trade torna isso ainda mais interessante. Ele leva instrumentos como MMFs, ETFs e títulos para uma estrutura de mercado regulado construída em torno de ativos financeiros tokenizados.

Minha observação: o verdadeiro desafio para a adoção de RWA talvez não seja a tokenização. Talvez seja conectar emissão, propriedade, negociação e liquidação sem perder as regras das quais os mercados financeiros já dependem.

Se o ativo está onchain, mas a maior parte do seu ciclo de vida ainda acontece em outro lugar, quanto do mercado financeiro realmente migrou para o onchain?

@Dusk $DUSK #dusk

I still think people underestimate how difficult privacy becomes once real financial institutions enter the picture.

What caught my attention about Dusk is that the stack isn’t simply about hiding transactions. DuskEVM provides an EVM-compatible path for applications, while Hedger is designed for confidential EVM workflows using homomorphic encryption and zero-knowledge proofs, with selective disclosure when authorized parties need specific information.

Then comes the harder part: who gets to see what?

A financial application may need confidentiality from the public, while an authorized regulator or auditor may still need specific information for verification or compliance.

My observation: privacy is relatively easy to describe. Deciding who gets to see what, and under which conditions, is where the real institutional tension begins.

If institutions need selective disclosure, who should ultimately control what becomes visible: the application, the regulator, or the protocol?

@Dusk $DUSK #dusk

#dusk $DUSK @Dusk Ainda acho que a parte mais difícil de colocar as finanças onchain não é a blockchain em si.

O que chamou minha atenção sobre a Dusk é a infraestrutura ao seu redor: a NPEX traz sua posição no mercado regulado, enquanto a Chainlink fornece interoperabilidade e trilhos de dados de mercado verificados. O que me interessa é como essas peças poderiam conectar emissão, negociação e liquidação sem separá-las das regras com que os mercados financeiros já operam.

Minha observação: é aqui que “tokenização” começa a virar infraestrutura de mercado de verdade.

Se a tecnologia funcionar, qual se torna o verdadeiro gargalo para a adoção: regulamentação, interoperabilidade ou confiança institucional?

I still think most RWA discussions stop too early.

Tokenization can put a representation of an asset onchain, but the underlying lifecycle may still depend on offchain systems. Dusk’s native issuance approach goes further, with issuance, transfers, servicing and settlement designed around the onchain ledger.

My observation: the real breakthrough isn’t putting assets onchain — it’s reducing the gap between the asset and the infrastructure managing it.

But can this model work at the scale and regulatory complexity of real financial markets?

@Dusk $DUSK #dusk

Ainda acho que as pessoas estão ignorando a parte mais interessante de Dusk.

DuskEVM traz o desenvolvimento EVM familiar, enquanto Hedger adiciona fluxos de transações confidenciais usando criptografia homomórfica e provas de conhecimento zero. O que chamou minha atenção é que privacidade não significa abrir mão da execução verificável ou da divulgação seletiva quando for necessário um exame autorizado.

Minha observação: isso parece muito mais próximo do que as finanças regulamentadas realmente precisam onchain.

Mas Dusk consegue provar que essa arquitetura funciona em escala institucional real?

@Dusk $DUSK #dusk

I went looking for how vaultBTC moves on-chain, expecting it to behave like WBTC. It doesn't.

WBTC can move almost anywhere—wallets, exchanges, and DeFi protocols. That flexibility is one of its biggest strengths, but it also comes with a custodian behind it.

According to @BabylonLabs_io's Aave proposal, vaultBTC follows a very different design.

Instead of maximizing transferability, vaultBTC is transfer-restricted. It can only move between three predefined destinations:

• Aave V4 Hub
• Core Lending Spoke
• Integration Adapter Contract

Nowhere else.

The proposal explains why.

Those restrictions are what allow the system to avoid introducing a trusted custodian. Instead of trusting a third party, the protocol limits where the asset is allowed to move.

It's a different trade-off.

WBTC prioritizes mobility.
vaultBTC prioritizes trust minimization.

Neither design is inherently "better." They solve different problems.

One question stayed with me:

If removing the custodian requires restricting transferability, where should Bitcoin's freedom really be measured—by who controls it, or by where it's allowed to move?

@BabylonLabs_io

#baby $BABY #Bitcoin #defi

Eu estava lendo hoje a proposta de integração do Aave com Babylon, esperando que o BTC nativo fizesse todo o processo de empréstimo e liquidação.

Então um detalhe mudou completamente a forma como eu enxerguei isso.

De acordo com a proposta, quando uma posição é liquidada, os liquidadores permissionless recebem WBTC, enquanto o BTC subjacente é resgatado depois na rede Bitcoin após o settlement.

Aí notei outro ponto interessante.

A mesma proposta afirma que esse fluxo de liquidação também deve aumentar a demanda por empréstimos no mercado WBTC do Aave, que já tem cerca de US$ 5B em liquidez fornecida, mas ainda permanece subutilizado no lado dos tomadores.

Isso cria uma separação interessante.

• O BTC nativo é usado como garantia.
• O WBTC é usado durante a liquidação.
• O settlement do BTC acontece depois.

Então, embora o empréstimo comece com Bitcoin nativo, o caminho de liquidação ainda depende do WBTC para fornecer liquidez imediata.

É uma escolha de design interessante que equilibra o modelo de settlement do Bitcoin com a necessidade do DeFi de execução instantânea.

A questão não é se o WBTC está envolvido.

É em que ponto começa o "empréstimo lastreado em Bitcoin nativo" — e em que ponto ele ainda depende do Bitcoin tokenizado.

@BabylonLabs_io

#baby $BABY