Zainab Sarwer

Before a government deploys any blockchain infrastructure, there is a decision that shapes everything that comes after it. not which features to include. not which use cases to prioritize. the first decision is more fundamental than that — where does the infrastructure actually sit, and who controls what.

From what i understand about Sign's public blockchain approach, two deployment paths are offered and they are genuinely different in how they operate. the first is a Layer 2 sovereign chain — independent blockchain infrastructure where the government has full control over consensus mechanisms, block production, and chain parameters. it inherits security from the underlying Layer 1 network through regular state commitments and fraud proof mechanisms, but operationally it stands alone. the government defines who can run validators. it sets block time and throughput. it controls the consensus algorithm — Proof of Authority, PBFT variants, or custom. block time under one second, up to 4000 transactions per second. if the Layer 2 has issues, exit mechanisms let users fall back to Layer 1, so funds remain accessible regardless.
The second path is Layer 1 smart contract deployment — sovereign control implemented through upgradeable proxy contracts on an established network like Ethereum. no independent consensus infrastructure needed. the contracts inherit the security guarantees of the underlying network's validator set directly. multi-signature wallets require authorized government entities to approve protocol changes. and because the contracts sit on an established network, there is direct integration with existing DeFi protocols, decentralized exchanges, and liquidity pools — no bridges required. the whitepaper describes this as battle-tested infrastructure with mature developer tooling and established audit practices.
The comparison table in the whitepaper is worth understanding clearly. Layer 2 gives full operational independence, full consensus control, full block production control, and an optimizable cost structure — but DeFi integration requires bridges and deployment complexity is higher. Layer 1 smart contracts give medium operational independence, direct DeFi integration, lower deployment complexity — but consensus control is limited to the underlying network and security model is L1 only rather than L1 plus L2.
What both paths share is a set of operational controls that governments can implement regardless of which deployment they choose. government-controlled gas fee policies — whitelist-based exemptions so specific users or service providers pay no transaction fees. address whitelisting and blacklisting for regulatory compliance. KYC enforcement through smart contract logic or chain parameters. emergency controls to pause operations during security incidents. and protocol upgrade mechanisms — chain governance for Layer 2, proxy patterns for Layer 1 — so the infrastructure can evolve without disrupting what is built on top of it.
Then there is global financial access. standardized regional financial assets — ERC-20 stablecoins, ERC-721 tokenized real-world assets — built on sovereign blockchain infrastructure can be freely bridged and traded against global assets including BNB, ETH, WBTC, USDC, and EURC. a national stablecoin does not have to stay national.
What the whitepaper describes is a framework where the deployment decision is a choice between two kinds of sovereignty — maximum operational independence with Layer 2, or immediate global integration with Layer 1. neither is wrong. the right answer depends on what the government is actually trying to build first.
Most blockchain projects ask governments to trust the technology. Sign's framework asks governments to make an informed decision about which version of control they actually need.

If you were advising a government on this decision, which path would you recommend and why?
@SignOfficial
$SIGN
#SignDigitalSovereignInfra

Most people think of money as neutral. you have it, you spend it, the transaction happens. the rules around the transaction — limits, compliance, reporting — are applied after the fact, by systems sitting outside the money itself. a bank checks the transfer. a regulator reviews the record. a compliance officer flags the anomaly. the money moved, and then the system tried to catch up.

From what i understand about how Sign's CBDC infrastructure is designed, the starting assumption is different. the rules are not applied after the transaction — they are embedded inside it.
The whitepaper describes a dual CBDC model running on Hyperledger Fabric X — two separate namespaces, each with its own endorsement policy and its own privacy level, designed for fundamentally different purposes. the wholesale CBDC namespace handles interbank settlements and large-value transfers between financial institutions, operating with transparency comparable to traditional Real-Time Gross Settlement systems. the retail CBDC namespace handles everyday payments for citizens and businesses, and here the design is completely different — only the sender, the recipient, and designated regulatory authorities can access transaction details. zero-knowledge proofs ensure this privacy while maintaining cryptographic integrity. the same underlying infrastructure, two completely seprate privacy environments, each governed by its own rules.
Then there is the programmable money layer. retail CBDC supports token-based conditional payment capabilities — time-locked transfers that release funds at a specific moment, recurring payments that execute automatically, and compliance automation built directly into the token operations. the whitepaper also describes conditional token transfers based on time locks, multi-signature requirements, and compliance attestations. this means a government subsidy can be programmed to release only when certain conditions are met. a pension payment can be set to execute on schedule without manual processing. a cross-border transfer can carry its compliance attestation inside the transaction itself.
The token operations run through the Fabric Token SDK using a UTXO model — a directed acyclic graph that tracks token movements, where each transaction consumes unspent outputs and creates new ones. traditional chaincode is replaced by peer-to-peer transaction negotiation using Fabric-Smart-Client, which the whitepaper describes as more efficient and privacy-preserving. embedded AML/CFT checks, transfer limit enforcement, and automated regulatory reporting are integrated directly into token operations — not added on top, built in.
Offline capability is also part of the retail CBDC design. support for transactions in low-connectivity environments means the system is built for populations where consistent internet access is not guaranteed. and ISO 20022 compliance means cross-border CBDC transfers between central banks use standardized message structures compatible with global financial infrastructure.
What this combination produces is a form of money that is not passive. it carries its own compliance history, executes its own conditions, protects its own privacy, and reports its own transactions — without waiting for an external system to catch up after the fact.
The question governments have always faced with digital currency is how to maintain control without creating surveillance. the namespace architecture and zero-knowledge proof layer in Sign's CBDC design is the most specific answer to that question i have seen described in a whitepaper.

Do you think programmable money with embedded compliance is the future of how governments manage public funds?
@SignOfficial
$SIGN
#SignDigitalSovereignInfra

When a new blockchain launches, it faces a specific problem. the network needs block producers to secure it. block producers need incentive to show up. but the incentive — block rewards — only becomes meaningful once there's enough adoption and demand on the network to make participation worthwhile. in the early days, blocks may be mostly empty. if a block producer only gets paid based on how full their blocks are, they might not bother.

Midnight solves this with the subsidy rate. and the initial value — 95% — was set deliberately with this exact problem in mind.
The subsidy rate is a system parameter that determines what percentage of the base reward a block producer receives regardless of how full their block is. at 95%, a block producer gets 95% of the base reward even if they produce a completely empty block. only the remaining 5% is variable — split between the block producer and the Treasury based on how much block space actually gets used.
The whitepaper is explicit about why this number was chosen. it ensures that early block producers are incentivized to participate, while accounting for the fact that reaching peak adoption and demand for block space may take time. a new chain shouldnt penalize validators for low early traffic that was never their fault. the 95% subsidy absorbs that risk.
There is a second reason the whitepaper gives. a very high subsidy rate also minimizes the incentive for block producers to stuff blocks with their own transactions to inflate utilization. if 95% of your reward is already guaranteed, there is little marginal benefit to gaming the variable component. the subsidy rate, by being high, reduces a specific type of manipulation.
But 95% isnt the target forever. the whitepaper states clearly that in the future it is expected to be adjusted towards 50% via governance action. at 50%, the split between fixed and variable reward becomes equal. block producers have a much stronger incentive to include as many real transactions as possible because half their reward now depends on block fullness. the shift from 95% to 50% is a shift from protecting early validators to incentivizing maximum efficiency.
The formula for the fixed block subsidy is simple — Nf = Nb × S, where Nb is the base reward and S is the subsidy rate. at 95%, Nf is 95% of Nb. at 50%, its half. the variable component Nv = U × (Nb - Nf) — where U is the block utilization ratio — captures the rest.
What i find interesting about this design is that the governance mechanism is the mechanism for this transition. the subsidy rate isnt hardcoded to change automatically at a certain block height or after a certain time. it changes when governance decides it should. the community — through on-chain governance — gets to decide when the network is mature enough to reduce the safety net for block producers.

95% at launch. 50% when the network is ready. one number, two different jobs.
If you were a block producer deciding whether to join Midnight at launch — how much would the 95% subsidy rate influence that decision?
#night #NIGHT $NIGHT @MidnightNetwork

There is a version of financial exclusion that is obvious — no bank account, no access to money. and there is a version that is less visible — a bank account exists, the payment infrastructure exists, but the person cannot use it because they cannot prove who they are in a way the system accepts. KYC requirements are the wall. and for a significant part of the world's population, that wall has never come down.

From what i understand about how Sign frames economic development, the starting point is this exact problem. when residents have verified on-chain identities, they gain access to digital financial services that were previously unavailable due to KYC barriers. the identity layer does not just identify people — it unlocks the economic infrastructure that was already built but unreachable.
The economic effects the whitepaper describes go further than banking access. standardized digital identity enables easier integration with global financial systems while preserving national sovereignty — meaning a country does not have to choose between connecting to the world economy and maintaining control over its own infrastructure. investment attraction follows from this directly. streamlined business incorporation and transparent regulatory processes attract both domestic and foreign investment. when the processes that govern how businesses register and comply with regulations are on-chain and transparent, the friction that keeps investment out starts to disappear.
Cross-border efficiency is the next layer. standardized identity and asset formats reduce friction in international trade and cooperation. this is not a small thing — the cost and complexity of verifying identities and assets across different national systems is one of the largest hidden costs in international trade. when the formats are standardized, that cost drops on both sides of every transaction.
Then there is the interoperability layer — which the whitepaper describes separately and in specific terms. native bridge infrastructure between public and private networks eliminates costly manual reconciliation processes. implementation of ISO 20022 and emerging CBDC protocols reduces integration costs with global financial networks, enabling governments to participate in international markets without expensive custom integration projects. cross-border transaction capabilities accelerate settlement times from days to minutes compared to traditional correspondent banking. and comprehensive API frameworks allow governments to modernize gradually, preserving existing IT investments without service interruptions.
The last point in the whitepaper's interoperability section is about private-public market expansion — seamless integration with existing financial infrastructure expands government access to private sector innovation, creating new revenue opportunities through public-private partnerships while maintaining regulatory oversight.
What this adds up to is a picture where identity is not just an administrative function. it is the infrastructure that determines whether a country's population can participate in the digital economy, whether foreign investment flows in, whether cross-border trade is efficient, and whether the government can connect to global financial networks without rebuilding everything from scratch.
Most countries treat identity as a prerequisite for services. Sign's framework treats it as the economic infrastructure itself.

If verified digital identity removed the KYC barrier for everyone in your country tomorrow, what changes first?
@SignOfficial
$SIGN
#SignDigitalSovereignInfra

Most people who use blockchains have never heard of MEV. but they've experienced its effects — a transaction that costs more than expected, a trade that executes at a slightly worse price than it should have, a front-run they never saw coming. MEV — miner extractable value — is the profit that block producers can extract by reordering, inserting, or censoring transactions in the blocks they produce.

It's a structural problem in transparent blockchains. when every transaction is visible in the mempool before it's included in a block, sophisticated actors can read that data and act on it. they can see that you're about to buy a large amount of a token, buy it first, sell it to you at a higher price, and pocket the difference. you pay more. they profit. the block producer may take a cut too. none of this is illegal — it's just a consequence of full transaction transparency.
Midnight's DUST resource has a property specifically noted in the whitepaper as MEV-resistance. and the mechanism behind it is straightforward once you understand how DUST works.
DUST is shielded. when a transaction is submitted on Midnight, the DUST being spent to pay for it is not visible on the public ledger in a way that reveals metadata — wallet addresses and transaction details are not disclosed to counterparties or made available publicly. the whitepaper states this directly as a key property of DUST. and because attackers cannot identify potential victims from the transaction data available to them, the opportunity for MEV is significantly reduced.
There is a second layer to this. DUST is burned when used — it doesn't cycle back into circulation, it doesn't get collected by block producers, there is no DUST tipping mechanism. block producers on Midnight receive rewards exclusively from the Reserve in NIGHT, not from transaction fees. this removes a key incentive that exists on other chains — the incentive to reorder transactions to maximize fee collection. when block producers dont collect fees, the financial motivation to front-run or reorder transactions changes fundamentally.
The combination of these two properties — shielded transaction metadata and no fee collection by block producers — creates a structural environment where MEV is harder to execute and less rewarding to attempt. the attacker cant see who to target, and even if they could, the mechanism for profiting from reordering is weaker.
This doesnt mean Midnight is immune to all forms of transaction manipulation. the whitepaper is measured in its language — MEV likelihood is reduced, not eliminated. but the design choices around DUST were made with this problem in mind, and the properties that address it are baked into the resource itself, not added as a layer on top.
MEV is a problem that exists because blockchains show too much. DUST was built to show less.

If you've ever had a transaction front-run on another chain — would a shielded fee resource have changed the outcome?
#night #NIGHT $NIGHT @MidnightNetwork

Most people who use blockchains have never heard of MEV. but they've experienced its effects — a transaction that costs more than expected, a trade that executes at a slightly worse price than it should have, a front-run they never saw coming. MEV — miner extractable value — is the profit that block producers can extract by reordering, inserting, or censoring transactions in the blocks they produce.

It's a structural problem in transparent blockchains. when every transaction is visible in the mempool before it's included in a block, sophisticated actors can read that data and act on it. they can see that you're about to buy a large amount of a token, buy it first, sell it to you at a higher price, and pocket the difference. you pay more. they profit. the block producer may take a cut too. none of this is illegal — it's just a consequence of full transaction transparency.
Midnight's DUST resource has a property specifically noted in the whitepaper as MEV-resistance. and the mechanism behind it is straightforward once you understand how DUST works.
DUST is shielded. when a transaction is submitted on Midnight, the DUST being spent to pay for it is not visible on the public ledger in a way that reveals metadata — wallet addresses and transaction details are not disclosed to counterparties or made available publicly. the whitepaper states this directly as a key property of DUST. and because attackers cannot identify potential victims from the transaction data available to them, the opportunity for MEV is significantly reduced.
There is a second layer to this. DUST is burned when used — it doesn't cycle back into circulation, it doesn't get collected by block producers, there is no DUST tipping mechanism. block producers on Midnight receive rewards exclusively from the Reserve in NIGHT, not from transaction fees. this removes a key incentive that exists on other chains — the incentive to reorder transactions to maximize fee collection. when block producers dont collect fees, the financial motivation to front-run or reorder transactions changes fundamentally.
The combination of these two properties — shielded transaction metadata and no fee collection by block producers — creates a structural environment where MEV is harder to execute and less rewarding to attempt. the attacker cant see who to target, and even if they could, the mechanism for profiting from reordering is weaker.
This doesnt mean Midnight is immune to all forms of transaction manipulation. the whitepaper is measured in its language — MEV likelihood is reduced, not eliminated. but the design choices around DUST were made with this problem in mind, and the properties that address it are baked into the resource itself, not added as a layer on top.
MEV is a problem that exists because blockchains show too much. DUST was built to show less.

If you've ever had a transaction front-run on another chain — would a shielded fee resource have changed the outcome?
@SignOfficial
$SIGN
#SignDigitalSovereignInfra

When people talk about blockchain-based national identity, the conversation usually stays theoretical. the technology is promising, the use cases make sense, but actual deployment at national scale — that remains somewhere in the future. Bhutan moved it into the past.

In October 2023, Bhutan launched the world's first SSI-based national identity system. not a pilot. not a limited rollout. the official national identity infrastructure, built on Self-Sovereign Identity principles. the whitepaper documents what that actually looked like in practice.
750,000 citizens enrolled, targeting 70% or more of the total population. the system was not built alongside existing identity infrastructure as an experiment — it replaced it as the standard. and the legal foundation was built to match. the National Digital Identity Act of 2023 gave digital identity a comprehensive legal framework, recognizing it as a fundamental right enshrined in the constitution. not a government service. a constitutional right.
What i found intresting is how pragmatic the platform decisions were. the system launched on Hyperledger Indy, migrated to Polygon in 2024, and is targeting Ethereum by Q1 2026. three different blockchain platforms in under three years. the whitepaper describes this as a pragmatic approach to platform selection — balancing performance, decentralization, and security requirements as they evolved. most projects treat their initial platform choice as permanent. Bhutan treated it as a variable.
The credentials the system issues go beyond foundational identity. academic credentials from the Royal University of Bhutan. mobile number verification for SIM registration. digital signatures for document authentication. these are not edge cases — they are the everyday interactions that make an identity system actually useful to the people holding the credentials.
And then there is the developer side. national hackathons, developer engagement programs, 13 or more teams building applications integrated with the national identity system across government and private sector use cases. the whitepaper calls out citizen-centric design specifically — biometric authentication, device-level encryption, intuitive wallet interfaces. the system was built to be used by the population it serves, not just implemented for them.
From what i understand, Sign's framework uses Bhutan as a reference implementation — proof that national-scale SSI is not theoretical. a country of 750,000 enrolled citizens, a constitutional legal foundation, a developer ecosystem, and a platform migration history that shows the infrastructure can evolve without breaking what was built on it.

The question is not whether this can work at national scale. Bhutan answered that in 2023. the question now is which country does it next.
@SignOfficial
$SIGN
#SignDigitalSovereignInfra

I think the most misunderstood part of how DUST works is what happens when the connection between NIGHT and a DUST address gets broken. people assume it just stops generating. but the full picture is more precise than that — and the mechanics of what happens after the cut matters for anyone trying to understand how the resource actually behaves.

The association between a NIGHT address and a DUST address is called designation. once designated, DUST generates linearly — block by block — until the cap is reached. but this association isnt permanent. the whitepaper identifies three specific ways a NIGHT holder can sever it.
The first is transferring the associated NIGHT tokens to another address. when NIGHT moves away from the originating address, the link between that NIGHT and the DUST address breaks immediately. the NIGHT is gone from that address — so is the generation. the whitepaper is clear that the recipient of the transferred NIGHT will have to issue a new designation to resume DUST generation at a new address. the old DUST address is now disconnected.
The second is redesignation — explicitly pointing the DUST generation to a different DUST address. the NIGHT stays in the same wallet. only the destination changes. the old DUST address loses its association and stops receiving new generation. the new address starts accumulating from zero.
The third is undesignation — explicitly stopping DUST production entirely without redirecting it anywhere. the NIGHT stays put. the generation just stops.
In all three cases, what happens next to the DUST already sitting in the disconnected address is the same: it starts to decay. not immediately to zero — linearly, with each passing block, at the same rate it was being generated. the whitepaper describes this as a finite shelf life. the DUST that accumulated before the severance doesnt vanish instantly. it drains slowly.
This decay mechanic is also a double-spend prevention mechanism. from what i understand, it prevents a NIGHT holder from redesignating generation rapidly across multiple addresses to try and accumulate DUST beyond their cap. for a given amount of NIGHT, the aggregate DUST across all associated addresses can never exceed the cap — because for every unit generated in the new address, a unit decays in the old one. the cap is always enforced, regardless of how many times the designation changes.
The whitepaper also covers what happens when the NIGHT balance itself changes without severing the designation. if a NIGHT holder sends some — not all — of their NIGHT to another address, the DUST cap at the designated address decreases proportionally. the existing DUST balance then decays to meet the new lower cap. if all NIGHT is sent away, the DUST at that address decays entirely to zero.
There is no punitive element to any of this. the decay is just the system maintaining the invariant that DUST cant exist independently of the NIGHT generating it. once the source is gone, the resource winds down. the rate is predictable. the outcome is always the same.

Three ways to cut the connection. one outcome every time — the DUST that was there starts counting down.
If you held NIGHT and decided to transfer it tomorrow — would you know what happens to your DUST address before you do it?
#night #NIGHT $NIGHT @MidnightNetwork

Evry identity system ever built has had the same design assumption at its center. someone issues the identity. someone stores it. someone decides when it is valid and when it is not. the citizen at the end of this chain is the subject of the system, not the owner of it.

Self-Sovereign Identity is a direct challenge to that assumption. from what i understand about how Sign frames this, SSI is not an upgrade to existing identity systems — it is a different starting point. the citizen controls their own identity data, deciding when to share it and with whom. no central authority can access, modify, or revoke that information without the citizen's involvement. not the government that issued it. not the platform it runs on. not anyone.
The whitepaper describes five principles that SSI is built around, and each one closes a specific gap that traditional identity systems leave open. portability means the identity is not tied to any single organization or platform — a citizen can present credentials across government services, financial institutions, and the private sector without asking permission from whoever issued the credential. privacy by design means selective disclosure — proving specific attributes like age or citizenship without revealing everything else attached to the identity. cryptographic verification means a verifier can mathematically confirm a credential is real without contacting the issuing authority at all. and interoperability through W3C-compliant Decentralized Identifiers means the identity works across borders, across different national systems, without any of them losing sovereign control over their own infrastructure.
Then there is the credential layer — the W3C Verifiable Credentials framework — which is how this actually works in practice. a government agency or authorized institution creates a cryptographically signed credential and issues it to the citizen's digital wallet. the citizen stores it on their own device. when they need to present it, they selectively share only what is relevant — not the full document, just the attribute being verified. the verifier checks the digital signature against the issuer's public key in the blockchain-based trust registry and gets a confirmed answer without calling anyone, without accessing any central database, without the citizen handing over anything more than what the situation requires.
What this combination actually does is change who the identity belongs to. the credential was issued by a government. but it lives on the citizen's device, under the citizen's control, presented by the citizen's choice, verified without the citizen needing anyone's permission to use it.
Most identity systems are designed to serve the institutions that run them. this one is designed to serve the person it belongs to. that is a seprate thing, and from what the whitepaper describes, it is the design constraint everything else in Sign's identity infrastructure is built around.

If your identity was fully under your own control — what would you do differently with it?
@SignOfficial
$SIGN
#SignDigitalSovereignInfra

I was reading the tokenomics whitepaper and came across a paragraph i had to read twice. not because it was complicated — because it was unexpectedly clear. the whitepaper uses a physical world analogy to explain the entire NIGHT-DUST relationship, and once you see it, you cant unsee it.

DUST is electrical energy. DUST addresses are battery packs. NIGHT tokens are wind turbines.
That's the model from the whitepaper directly. and it holds up across every property of the system if you follow it through properly.
A wind turbine generates electricity continuously. it doesnt run out of capacity to generate — it keeps producing as long as the wind blows. NIGHT works the same way. holding NIGHT generates DUST continuously, block by block, indefinitely. the whitepaper is explicit that NIGHT will generate DUST indefinitely. there is no lifetime cap on how much DUST can be generated from a NIGHT balance over time.
A battery pack stores that electricity up to a maximum capacity proportional to the size of the turbine connected to it. DUST addresses work the same way. the cap on how much DUST a given address can hold is proportional to the NIGHT balance generating into it. bigger NIGHT balance — bigger cap. smaller balance — smaller cap.
A turbine can charge any battery, regardless of who owns the battery. NIGHT works the same way. a NIGHT holder can designate any DUST address as the recipient of their generation — including addresses they dont own. a business can hold NIGHT and designate DUST generation to their users addresses. a developer can hold NIGHT and direct DUST to a DApp contract address. the turbine and the battery dont need to belong to the same person.
But once electricity is stored in a battery, it cant be moved to another battery. it can only power devices connected to that battery. DUST works exactly the same way — its non-transferrable. once DUST is in an address, it stays there until its used for transactions or decays. you cant send DUST to someone else. you cant sell it. it can only be consumed where it lives.
And when the turbine disconnects from the battery — when NIGHT is transferred away — the stored electricity starts to decay. it doesnt disappear instantly, it drains at the same rate it was being generated. the whitepaper describes this as a finite shelf life, decaying linearly at the same rate it was generated. this is the DUST decay mechanic — not a punishment, just physics.
What makes this analogy work beyond aesthetics is that it captures the regulatory intent too. DUST cant be transferred, so it cant function as a store of value, cant be listed, cant be traded. it has value in the sense that it enables transactions — but it cant retain that value or be moved around like a financial asset. the battery pack metaphor captures this perfectly. stored electricity is useful but immobile.
Most tokenomics explanations feel like reading a terms and conditions document. this one reads like understanding how power grids work. and once you understand the turbine-battery model, the mechanics of DUST designation, decay, caps, and non-transferability all follow naturally.

The whitepaper built an analogy that actually holds. that doesnt happen often.
How would you explain the NIGHT-DUST relationship to someone who has never used a blockchain before?
#night #NIGHT $NIGHT @MidnightNetwork
{future}(undefinedUSDT)