GAS WOLF

Tại sao Walrus tồn tại từ đầu
Tôi đang xem xét @Walrus 🦭/acc qua lăng kính những khó khăn thầm lặng mà các nhà xây dựng phải đối mặt mỗi ngày, bởi ngay cả khi một blockchain nhanh và một hợp đồng thông minh tinh tế, thì khoảnh khắc một sản phẩm thực tế cần lưu trữ nội dung lớn như phương tiện truyền thông, tập dữ liệu, bản sao trạng thái ứng dụng, tập tin mô hình, nhật ký hoặc bất kỳ dữ liệu phi cấu trúc nặng nào, hệ thống thường quay trở lại lưu trữ tập trung, điều này tạo ra điểm kiểm soát duy nhất và điểm thất bại duy nhất, và khoảng trống này không phải là một chi tiết kỹ thuật nhỏ, mà trở thành nơi mà niềm tin bị rò rỉ ra khỏi hệ thống, vì vậy Walrus đang cố gắng lấp đầy khoảng trống đó bằng cách coi lưu trữ phi tập trung như một nguyên thủy cốt lõi có thể được sử dụng theo cách nghiêm túc như cách mọi người sử dụng lưu trữ đám mây truyền thống, ngoại trừ việc không phụ thuộc vào một công ty, một khu vực pháp lý hay một thay đổi chính sách nào để duy trì sự sống cho dữ liệu của bạn.

I keep returning to the same uncomfortable reality about modern markets: privacy is not a cosmetic feature, it is a basic layer of safety and dignity, because when every movement of value is permanently visible, people are not just transacting, they are exposing patterns that can reveal strategy, relationships, payroll rhythms, treasury timing, and identity by correlation. In most real financial systems, the answer is not to make everything visible to everyone, the answer is to have clear rules, strong audits, and controlled boundaries so that the right parties can verify what matters without turning every participant into a public dataset. @Dusk was built for that tension, a Layer 1 designed to bring regulated finance on chain without forcing institutions or everyday users into radical transparency as the default state.

If everything is public by default, regulated finance hits a wall, because compliance does not mean public exposure, it means provable behavior under oversight. This is the part many chains struggle to communicate: markets can demand disclosure and still demand confidentiality, and those are not contradictions when the system is built correctly. Dusk frames the goal in a direct way, keep counterparty privacy, keep compliance, keep execution speed and finality, and make it possible to enforce reporting and disclosure rules in a structured manner rather than hoping social norms will protect users. They are not trying to erase regulation, they are trying to give regulation better machinery, so the network can produce proofs and audit trails without making participants live fully exposed.

What makes the project feel real to me is that it has moved past the stage where everything is theory. Dusk publicly kicked off its mainnet rollout on December 20, 2024, and described a staged path toward producing its first immutable block on January 7, 2025. That timeline matters because it signals the difference between an idea and an operational network, and it also shows a willingness to communicate concrete steps, not just vision language. If it becomes normal for regulated builders to demand operational maturity before they take the next step, then these dates become more than history, they become proof that Dusk has been building toward a working settlement rail.

The modular stack is where the story becomes practical instead of philosophical. Dusk documents a clean separation between settlement and execution by positioning DuskDS as the settlement and data availability layer, while execution environments sit above it, including DuskEVM for EVM execution and DuskVM as a WASM environment connected to Dusk transaction models like Phoenix and Moonlight. In finance, modularity is not decoration, it is risk control, because boundaries reduce the blast radius of changes and make systems easier to govern under stress. If it becomes easier to upgrade execution without destabilizing settlement, and easier to reason about what each layer is responsible for, then the system starts to feel closer to infrastructure and less like an experiment.

Privacy, in Dusk, is not framed as hiding, it is framed as selective disclosure with proof. In the Phoenix model, funds live as encrypted notes rather than explicit balances, and transactions prove correctness with zero knowledge proofs without revealing amounts or the specific note linkages that would make tracing easy, while still allowing users to selectively reveal information via viewing keys when regulation or auditing requires it. That posture is emotionally important because it says something simple: you should not have to choose between being safe and being compliant, and the system should not treat privacy as suspicious when what people really need is controlled disclosure to authorized parties, not forced exposure to the entire world.

Dusk also signals that confidentiality must reach the execution layer, not just the base ledger. On June 24, 2025, Dusk introduced Hedger as a privacy engine for the EVM execution layer, describing a design that combines homomorphic encryption and zero knowledge proofs to enable confidential transactions that are still meant to be compliance ready for real world financial applications. I read that as intent made concrete: they are not only protecting balances, they are aiming to protect activity inside applications, which is where strategy and sensitive behavior often leaks in the first place.

Settlement behavior is another quiet detail that decides whether institutions take a network seriously. DuskDS uses a consensus protocol called Succinct Attestation, documented as a committee based proof of stake design that aims to provide fast, deterministic finality suitable for financial markets. Markets do not love probabilistic outcomes because operational risk lives in uncertainty, so the promise here is not hype, it is a specific attempt to make on chain settlement feel closer to professional settlement, where a trade being final actually means something.

On the token side, Dusk is explicit that DUSK is both the incentive for consensus participation and the primary native currency of the protocol, and it documents that DUSK has existed in ERC20 and BEP20 forms with migration paths to native DUSK now that mainnet is live. And because usability is not optional, Dusk launched a two way bridge on May 30, 2025, allowing users to move native DUSK from mainnet to BEP20 DUSK on BNB Smart Chain, which is the kind of infrastructure that looks boring until you realize it is often the bridge between curiosity and real usage.

The strongest signal that Dusk is trying to leave the crypto sandbox is the willingness of regulated entities to name the collaboration publicly. NPEX announced on March 11, 2024 that it was preparing an application under the EU DLT Pilot Regime together with Dusk, aiming toward a stock exchange powered by Dusk technology. Then, on February 19, 2025, Dusk announced a partnership with Quantoz Payments and NPEX to bring EURQ, a MiCA compliant digital euro, onto Dusk, and Quantoz described it as three Netherlands based organizations working together, noting it as the first time an MTF licensed stock exchange would utilize electronic money tokens through a blockchain. We are seeing the hard part begin there, because real institutions move slowly and demand clarity, and that slowness is exactly why a public named step matters.

I do not think the risk section should be hidden, because privacy systems are difficult to implement safely, modular stacks introduce integration complexity, and network effects remain brutally real since issuers, liquidity, and developers cluster where activity already exists. But the emotional reason this project keeps pulling attention is that it refuses to accept a false choice: privacy or compliance. Dusk is trying to build a world where a regulated asset can move on chain with confidentiality, where proof can be produced without forced exposure, and where settlement finality can be fast enough to feel like real finance instead of a perpetual pilot. If they succeed, it becomes easier for institutions to enter open networks without fear, and it becomes easier for everyday people to access institution level assets without surrendering their personal safety to permanent public tracing, and that is the kind of progress that matters long after the loud narratives move on.

@Dusk $DUSK #dusk

Tôi đang theo dõi @Dusk với một loại sự chú ý khác vì nó không giống như một dự án được xây dựng để giành chiến thắng trong một cuộc đua ngắn ngủi thu hút sự chú ý, mà giống như một dự án được xây dựng cho một hành trình dài, nơi mục tiêu không phải là tiếng vỗ tay, mà là niềm tin, và niềm tin trong lĩnh vực tài chính chưa bao giờ được trao dễ dàng vì nó được tạo nên từ sự minh bạch, kỷ luật và các hệ thống vững chắc ngay cả khi áp lực tăng cao. Dusk bắt đầu từ năm 2018 với định hướng rõ ràng hướng đến cơ sở hạ tầng tài chính được quản lý, và họ đang xây dựng một lớp 1 coi bảo mật và tuân thủ như những đối tác thay vì kẻ thù, bởi vì thế giới của các tổ chức không thể vận hành nếu mọi giao dịch và mọi số dư đều bị lộ trước người lạ, và thế giới đó cũng không thể vận hành nếu không thể xác minh điều gì, do đó Dusk đang cố gắng tạo ra một môi trường mà sự bảo mật tồn tại mà không biến thành hỗn loạn, và các quy tắc có thể được tuân thủ mà không khiến người dùng trở thành một chiếc hộp thủy tinh. Chúng ta đang thấy nhiều cuộc thảo luận hơn về tài sản thực thế được mã hóa và thanh toán trên chuỗi, nhưng điều mà nhiều người bỏ qua là các thị trường thực tế có trách nhiệm, báo cáo, bảo vệ nhà đầu tư và các ranh giới pháp lý mà không biến mất chỉ vì thứ gì đó nằm trên blockchain, vì vậy Dusk đang hướng đến việc trở thành một chuỗi phù hợp với những thực tế đó thay vì tranh cãi với chúng.

THE MOMENT YOU REALIZE STORAGE IS ABOUT TRUST
I’m noticing that most people do not think about storage until the day it hurts, because everything feels fine when files load quickly and links work and the world stays calm, but the moment something breaks you understand that storage is not just a place where data sits, it becomes the foundation of your work, your memories, your business, and your identity online. They’re countless stories of creators losing archives, teams losing critical assets, communities losing history, and it rarely happens in a dramatic way that gives you time to prepare, it happens quietly through policy changes, pricing shifts, account limits, regional blocks, outages, or simple neglect, and if you have ever felt that sinking feeling when a file is suddenly unreachable then you already know why decentralized storage is not a trend, it is a response to a real vulnerability that keeps repeating. We’re seeing a world where more value becomes digital every year, and if the next internet is supposed to be open and fair, it becomes impossible to accept that the most important layer, the data layer, can still be controlled by a few doors that can close without warning.

WHAT WALRUS FEELS LIKE WHEN YOU EXPLAIN IT IN PLAIN WORDS
@Walrus 🦭/acc is built around a simple promise that sounds almost ordinary until you realize how rare it is, which is that large files should remain available without asking permission from a single owner, and the system should still work even when some machines fail and some operators disappear and conditions become messy like they always do in real life. I’m calling out large files on purpose because modern apps live on heavy content, including images, video, audio, documents, datasets, and the growing number of digital objects that need to exist alongside onchain logic, and they’re not practical to store directly inside a blockchain in full. Walrus focuses on blobs, which is just a clean way to describe big chunks of data that need to be stored and retrieved reliably, and if it becomes normal for applications to be both onchain and data heavy, then the ability to handle blobs reliably becomes the difference between a product that scales and a product that collapses under its own weight.

WHY WALRUS IS LINKED TO SUI AND WHY THAT HELPS BUILDERS
We’re seeing Walrus designed to use Sui as a coordination layer, and the value of that design becomes clearer when you stop thinking of storage as a pile of bytes and start thinking of storage as a living agreement between users and operators. Storage networks need a trustworthy place to record commitments, track responsibilities, and prove that data was actually accepted by the network rather than merely promised, and Sui plays that role so Walrus can stay focused on the heavy work of storing and serving data. If a system tries to do everything at once, it becomes fragile, but if responsibilities are cleanly separated, it becomes easier to build and easier to audit, and I’m seeing this separation as one of the reasons Walrus feels practical because Sui can anchor the rules and receipts while Walrus specializes in availability and retrieval.

THE ENGINE INSIDE WALRUS AND WHY IT CHANGES THE COST STORY
They’re many ways to keep data safe, but the blunt approach is to copy everything everywhere, and that becomes expensive fast, while the risky approach is to store too little redundancy and hope nothing goes wrong, and that becomes a disaster the moment the network is stressed. Walrus leans on erasure coding, and the idea is simple even if the math is sophisticated, because instead of storing a whole file in one place, the file is transformed into many pieces so the network can lose some pieces and still reconstruct the full file, which is the kind of resilience that makes decentralized storage believable. What matters most in practice is not only that a file can be reconstructed, but that recovery stays efficient when parts go missing, because real networks churn constantly as nodes go offline, hardware changes, and operators rotate, and if the recovery process is slow or bandwidth hungry, it becomes a hidden tax that destroys usability. I’m drawn to Walrus because it treats churn as normal, and it tries to make recovery and self healing part of the baseline design rather than an afterthought.

HOW STORING A BLOB BECOMES A VERIFIABLE EVENT INSTEAD OF A HOPEFUL PROMISE
When an application stores a blob in Walrus, the data is encoded into smaller pieces that are distributed across a set of storage nodes, and the nodes acknowledge what they have accepted, and those acknowledgements can be combined into a certificate that gets anchored through the coordination layer, which is a powerful shift because it turns storage into something you can prove rather than something you assume. If it becomes normal for applications to depend on decentralized storage for real user experiences, then proof matters, because users do not care about your architecture when the screen is blank, they care that content loads, and builders need a way to reason about availability with confidence. We’re seeing this certificate based thinking show up as a recurring theme in modern infrastructure, because the internet is moving from trust me to show me, and Walrus aims to operate in that world where claims are backed by verifiable evidence.

WHERE WAL FITS AND WHY IT IS MORE THAN A NAME
WAL exists to coordinate incentives in a system where incentives can easily drift apart, because users want low cost storage and high reliability, operators want fair compensation for providing capacity and bandwidth, and the broader network needs tools to select participants and punish bad behavior so the service stays dependable. They’re no serious decentralized networks that can rely on goodwill alone, and storage is especially unforgiving because the costs are continuous and the consequences of failure are immediate. If it becomes easy for low quality operators to earn rewards while delivering weak availability, then the network degrades and trust erodes, so staking and governance become part of keeping the system honest over time, and I’m describing this not as hype but as the practical reality that economics and security are tied together in decentralized infrastructure.

WHO THIS IS FOR AND WHY THE USE CASES KEEP EXPANDING
Walrus speaks to builders who need data to stay reachable, and that includes teams building rich media apps, onchain games, AI workflows, archival systems, community knowledge bases, and any product where content is the product rather than a side feature. We’re seeing the boundary between onchain logic and offchain content become thinner, because users want seamless experiences where ownership, identity, and history are provable, while the actual heavy assets remain accessible without relying on a single storage gatekeeper. If you are an entrepreneur, it becomes easier to plan long term when your critical assets are not locked into one provider, and if you are a creator, it becomes easier to build a legacy when the work you publish is not one policy update away from disappearing. They’re people who will never read a technical document, yet they will still benefit from systems like this because the outcome is simple, which is that their content stays available.

THE QUIET PROMISE THAT MAKES THIS FEEL HUMAN
I’m not interested in pretending infrastructure is romantic, but I am honest about the fact that good infrastructure protects human effort, and that is why Walrus matters when you look beyond the jargon. If it becomes normal for our lives to be recorded, created, and conducted through digital systems, then the ability to store and retrieve data without begging for access becomes a kind of dignity, because it means your work is respected enough to survive outside a single company’s mood or a single server’s uptime. We’re seeing a shift where people want systems that do not require blind trust, and Walrus is part of that shift because it aims to keep availability strong through distribution, redundancy, and verifiable commitments, and if that approach succeeds, it becomes a quiet form of freedom where you can build, publish, and grow without fearing that the ground beneath your data will suddenly vanish.

A POWERFUL CLOSING THAT STAYS REAL
They’re many projects that talk about the future, but the future is built by the systems that keep working when conditions are imperfect, and I’m watching the industry slowly learn that lesson again and again. If Walrus delivers on its promise, it becomes more than a protocol, it becomes a dependable layer that lets people trust their own work over the long term, because the real value of decentralized storage is not ideology, it is continuity, and continuity is what makes innovation possible. We’re seeing the internet move toward a world where proof replaces promises, where resilience replaces convenience, and where users finally stop accepting that losing access is normal, and if you take that seriously, then Walrus and WAL start to feel less like a token and more like a commitment to keeping human effort reachable, intact, and respected, even when everything else is unstable.

@Walrus 🦭/acc $WAL #walrus

Tôi luôn quay lại vấn đề thanh toán vì đó là nơi hy vọng hoặc trở thành hiện thực hoặc sụp đổ thành lo âu, và tôi đã chứng kiến đủ chu kỳ trong crypto để biết rằng con người có thể chịu đựng các ứng dụng chậm và giao diện cồng kềnh trong một thời gian, nhưng họ không thể chịu đựng sự bất định khi giá trị thực sự đang ở trên bàn, vì sự bất định chính là điều biến một hệ thống hứa hẹn thành một nỗi căng thẳng dai dẳng trong tâm trí. Họ không sai khi sợ hãi nỗi căng thẳng đó, bởi vì tài chính được xây dựng trên các cam kết, và các cam kết đòi hỏi một câu trả lời rõ ràng cho một câu hỏi đơn giản nhưng sâu sắc của con người: liệu nó đã thanh toán và có tính cuối cùng chưa? Nếu có tính cuối cùng, nó sẽ trở thành nền tảng để xây dựng mà không cần phải luôn cảnh giác, và nếu không, nó sẽ trở thành nơi niềm tin dần tan biến từng giao dịch một. Chúng ta đang chứng kiến ngành công nghiệp trưởng thành, không phải vì những từ ngữ trở nên thông minh hơn, mà vì những yêu cầu ngày càng khắt khe hơn, và những yêu cầu khắt khe thường là dấu hiệu đầu tiên cho thấy điều gì đó đang trở nên quan trọng.

I’m seeing a quiet fear spread through builders and creators because the internet is now made of large files that carry real value, and yet most people still store those files in places that can disappear overnight. A video that took weeks to make, a dataset collected with patience, a model artifact built through expensive compute, a game world packed with assets, a business archive that proves what happened, all of it can be erased by one outage, one policy change, or one locked account. If you have ever felt that cold moment when a file link fails right when you need it, you already know this is not only a technical issue, it becomes a trust issue, and trust is hard to rebuild once it breaks.

@Walrus 🦭/acc exists because large data needs a stronger home than a single provider can promise. They’re building a decentralized blob storage system, which in plain words means a network designed to store and serve large unstructured files across many independent nodes, so the data is not trapped in one place that can fail. Walrus is described by its builders as a decentralized secure blob store and data availability protocol, and the idea is to let applications store, read, and certify availability for blobs like images and videos in a way that is resilient even under rough network conditions. We’re seeing the project move from early public preview into deeper technical maturity, with public documentation and papers that focus on how the system behaves when things go wrong, not only when everything is calm.

The most important part of Walrus is how it treats loss, because storage fails in real life, and a serious design must assume that. Walrus uses erasure coding, which means it breaks a file into many pieces, adds redundancy in a planned way, and spreads those pieces across different storage nodes. If enough pieces remain, the original file can be reconstructed, so the network can tolerate node failures without losing the data. The Walrus research paper explains that at the core is Red Stuff, a two dimensional erasure coding protocol that aims to achieve high security with around a 4.5 times replication factor, while also focusing on efficient recovery under high churn. If the network takes damage, it becomes a system designed to heal rather than a system designed to collapse.

Walrus also matters because it treats storage as something that should be programmable and verifiable, not a black box. Their documentation explains that Walrus leverages the Sui blockchain for coordination, attesting availability, and payments, and it describes storage space as a resource on Sui that can be owned, split, merged, and transferred. Stored blobs are also represented by objects on Sui, which means smart contracts can check whether a blob is available and for how long, extend its lifetime, or optionally delete it. I’m highlighting this because it changes the emotional feeling of building, since developers can rely on visible rules and onchain checks instead of hoping the storage layer behaves. If you are building a product that must last, it becomes powerful to treat data availability as something your application can reason about directly.

When people ask what makes Walrus different, I keep coming back to one simple point. They are not trying to store everything for everyone in the same way, they are trying to store big content with a design that is optimized for blob data and real world churn, while using Sui as a control plane so the storage network can remain specialized. A Walrus blog post from June 24, 2025 describes how the lifecycle of a blob is managed through interactions with Sui, from registration and space acquisition to encoding and distribution and then generating an onchain proof of availability certificate, which helps make availability a verifiable property instead of a promise you just accept. We’re seeing a trend where data is treated like infrastructure, and Walrus is leaning into that trend with a design that prioritizes correctness under stress.

The story of the developer preview is also part of the latest timeline, and it shows how the project has been tested in public view. Mysten Labs announced Walrus and a developer preview in June 2024, and later wrote in September 2024 that the developer preview was already storing over 12 TiB of data, with events that brought developers together to build applications that use decentralized storage. I’m not saying volume alone proves reliability, but it does show that Walrus has been pushed beyond theory, and that matters because storage earns trust through use, iteration, and honest measurement. If a protocol stays in slides forever, it becomes easy to believe and easy to abandon, but when it runs in public, it becomes accountable.

WAL sits inside this system as the coordination and participation token, and while token talk can get noisy, the purpose here is straightforward. A storage network needs incentives so nodes actually store and serve data, and it needs governance so the system can evolve without breaking the social contract with users. Sources that cover Walrus describe WAL as supporting staking, governance voting, rewards, and payments related to storage activity. They’re trying to create alignment where doing the right thing for the network is the profitable thing, and doing the wrong thing becomes expensive. If the incentives are built carefully, it becomes a network that can scale without slowly drifting into fragility.

I’m also seeing why Walrus is resonating with the current wave of builders, because the needs are becoming obvious. AI teams need durable data pipelines and model artifacts. Media apps need content that does not disappear. Games need large assets that can be served reliably. Communities need archives that do not vanish because one host loses interest. Walrus positions itself as a layer that can make data markets and programmable data use possible, and it is presented as storage that can support builders who want to scale without being trapped by a single centralized storage gatekeeper. If this works as intended, it becomes a quiet backbone that many applications depend on without users even needing to know the name, and that is usually what success looks like for infrastructure.

None of this removes the reality that decentralized storage is hard, and I think honesty here is part of what makes an article like this worth reading. Performance, retrieval experience, network churn, long term economics, and governance coordination are not small problems. If Walrus succeeds, it will be because the system continues to prove itself under real conditions, because the incentives remain coherent, and because the documentation and research keep matching what the network actually does. It becomes fragile when marketing runs ahead of engineering, and it becomes strong when engineering stays visible and measurable.

I’ll end where the emotion is most real. I’m thinking about the moment someone realizes their work is gone, and how that moment feels like helplessness because you cannot bargain with a failed server or a closed account, you can only accept the loss. Walrus is trying to reduce those moments by designing storage around recovery, distribution, and verifiable availability, so data can survive the normal disasters of the internet. They’re building a world where your files do not feel like they live on borrowed time, and if that world becomes real at scale, it becomes more than storage, it becomes relief, because it lets people create and build with less fear, and it lets the internet hold what we make with the care it deserves.

@Walrus 🦭/acc $WAL #walrus

Một sự thay đổi lặng lẽ trong cách tiền muốn di chuyển
Tôi đang quan sát một sự thay đổi chậm nhưng mạnh mẽ trong cách thế giới tài chính suy nghĩ về blockchain, bởi vì giai đoạn hào hứng đang dần phai nhạt và một câu hỏi nghiêm túc hơn đang thay thế nó, một câu hỏi về an toàn, trách nhiệm, và liệu công nghệ này có thực sự phục vụ được những người quản lý tài sản của người khác hay không. Các tổ chức không phải là những người mơ mộng theo đuổi các thí nghiệm, họ là những người bảo vệ vốn, và khi họ nhìn vào các hệ thống trên chuỗi, họ không chỉ hỏi về tốc độ hay lợi suất, mà còn hỏi về mức độ phơi bày, về tính bảo mật, về việc liệu các vị trí nhạy cảm và dữ liệu khách hàng có thể tồn tại trong thế giới số mà không bị đặt dưới ánh sáng công khai vĩnh viễn hay không. Nếu tính riêng tư yếu kém, nó sẽ trở thành rủi ro, và rủi ro sẽ trở thành điều mà bất kỳ tổ chức có trách nhiệm nào cũng không thể bỏ qua, bất kể đổi mới có hấp dẫn đến đâu.

Cảm giác mà không ai muốn thừa nhận
Tôi sẽ bắt đầu bằng một cảm giác, bởi vì công nghệ chỉ chiến thắng khi nó thay đổi cách con người cảm nhận bên trong, và Web3 có một vấn đề mà nhiều người dùng cảm nhận nhưng hiếm khi giải thích, đó là nó thường cảm giác mạnh mẽ nhưng lại kỳ lạ và mong manh cùng lúc. Bạn có thể sở hữu một token, ký một giao dịch, bạn có thể thấy chuỗi xác nhận sự thật, nhưng bản chất thực sự của trải nghiệm thường nằm ở nơi nào đó khác, ẩn sau một máy chủ bình thường, ẩn sau một tài khoản riêng tư, ẩn sau một phụ thuộc lặng lẽ có thể sụp đổ bất cứ lúc nào mà không báo trước. Nếu hình ảnh biến mất, nếu các tệp ngừng tải, nếu liên kết nội dung trở nên tối tăm, người dùng sẽ không quan tâm rằng hợp đồng thông minh vẫn hoàn hảo, bởi vì thứ họ chạm vào và tin tưởng đã biến mất, và khoảnh khắc đó tạo ra một vết thương cảm xúc sắc nét nói rằng thế giới này vẫn chưa an toàn. Họ không chỉ đang xây dựng ứng dụng, họ đang yêu cầu mọi người đặt những mảnh ghép của bản thân, công việc, nghệ thuật, cộng đồng và ký ức của họ vào một hệ thống, và nếu hệ thống không thể giữ những mảnh ghép đó sống sót, thì thật khó để ai đó thực sự thư giãn và tin tưởng.

Tôi đang theo dõi thế giới tài chính thay đổi theo một cách vừa mang lại hy vọng vừa nặng nề, vì rất nhiều người mong muốn tự do từ các hệ thống onchain hiện đại nhưng họ cũng mong muốn sự an toàn mà chỉ có những quy tắc nghiêm túc, kiểm toán và trách nhiệm mới mang lại, và trong nhiều năm qua ngành công nghiệp đã hành xử như thể bạn phải chọn một bên duy nhất. Chúng ta đang chứng kiến một sự phân chia kỳ lạ khi một số hệ thống tiết lộ mọi thứ mãi mãi và gọi đó là minh bạch, trong khi những hệ thống khác thúc đẩy sự bí mật mà không có rào cản nào và gọi đó là tự do, tuy nhiên cuộc sống thực tế không được xây dựng trên cực đoan, vì cuộc sống thực tế cần sự riêng tư để bảo vệ những người bình thường và tuân thủ để bảo vệ thị trường khỏi lạm dụng. @Dusk was thành lập vào năm 2018 với mục đích mang cảm giác trung thực hiếm có, vì họ đang xây dựng một blockchain lớp 1 được thiết kế cho cơ sở hạ tầng tài chính được quản lý và tập trung vào quyền riêng tư, nơi quyền riêng tư được coi là nhu cầu của con người và tuân thủ được coi là yêu cầu không thể thương lượng, và sự kết hợp này chính xác là điều mà kỷ nguyên tài chính tiếp theo đã thiếu.