{"data":{"data":{"id":1,"attributes":{"createdAt":"2023-04-06T19:54:43.345Z","updatedAt":"2023-10-13T11:41:22.516Z","publishedAt":"2023-05-31T23:54:59.988Z","link_headline":"Join the team","recent_news_headline":"Recent
\nNews","auto_update_articles":true,"footer":{"id":1,"small_print":"© 2023 Dusk. All Rights Reserved.","padding":null,"headline":"Regulated And Decentralized Finance.","navigation":{"data":{"id":2,"attributes":{"UUID":"website-footer","createdAt":"2023-04-06T19:53:59.785Z","updatedAt":"2023-06-22T11:36:39.116Z","publishedAt":"2023-06-01T00:16:22.627Z","menus":{"data":[{"id":5,"attributes":{"UUID":"website-footer-first","createdAt":"2023-04-06T19:46:27.557Z","updatedAt":"2023-06-22T11:34:08.394Z","publishedAt":"2023-06-01T00:14:48.967Z","title":"Footer First Menu","menu_items":{"data":[{"id":8,"attributes":{"title":"News","href":"/news","description":"

Stay up to date with all the latest Dusk news

","createdAt":"2023-04-06T19:21:17.157Z","updatedAt":"2023-06-01T00:13:15.246Z","publishedAt":"2023-06-01T00:13:15.240Z","logo":{"data":null}}},{"id":5,"attributes":{"title":"Newsroom","href":"/newsroom","description":null,"createdAt":"2023-04-06T18:07:19.816Z","updatedAt":"2023-07-05T14:23:16.670Z","publishedAt":"2023-06-01T00:14:44.033Z","logo":{"data":null}}},{"id":1,"attributes":{"title":"Careers","href":"/careers","description":null,"createdAt":"2023-04-06T18:05:00.429Z","updatedAt":"2023-06-01T00:14:39.682Z","publishedAt":"2023-06-01T00:14:39.676Z","logo":{"data":null}}},{"id":2,"attributes":{"title":"Contact","href":"/contact","description":null,"createdAt":"2023-04-06T18:06:14.421Z","updatedAt":"2023-06-01T00:14:35.489Z","publishedAt":"2023-06-01T00:14:35.480Z","logo":{"data":null}}}]}}},{"id":6,"attributes":{"UUID":"website-footer-second","createdAt":"2023-04-06T19:49:36.355Z","updatedAt":"2023-06-22T11:35:39.058Z","publishedAt":"2023-06-01T00:15:08.666Z","title":"Footer Second Menu","menu_items":{"data":[{"id":22,"attributes":{"title":"Telegram","href":"https://t.me/DuskNetwork","description":null,"createdAt":"2023-04-06T19:33:14.868Z","updatedAt":"2023-06-01T00:13:50.323Z","publishedAt":"2023-06-01T00:13:50.318Z","logo":{"data":null}}},{"id":17,"attributes":{"title":"Discord","href":"https://discord.com/invite/dusknetwork","description":null,"createdAt":"2023-04-06T19:26:24.221Z","updatedAt":"2023-06-01T00:15:03.508Z","publishedAt":"2023-06-01T00:15:03.501Z","logo":{"data":null}}},{"id":23,"attributes":{"title":"Twitter","href":"https://twitter.com/duskfoundation","description":null,"createdAt":"2023-04-06T19:33:32.989Z","updatedAt":"2023-06-01T00:13:55.625Z","publishedAt":"2023-06-01T00:13:55.619Z","logo":{"data":null}}}]}}},{"id":8,"attributes":{"UUID":"website-footer-third","createdAt":"2023-06-22T11:35:17.075Z","updatedAt":"2023-06-22T11:36:42.946Z","publishedAt":"2023-06-22T11:36:42.941Z","title":"Footer Third Menu","menu_items":{"data":[{"id":24,"attributes":{"title":"LinkedIn","href":"https://www.linkedin.com/company/dusknetwork/","description":null,"createdAt":"2023-04-06T19:33:58.600Z","updatedAt":"2023-06-01T00:14:59.245Z","publishedAt":"2023-06-01T00:14:59.239Z","logo":{"data":null}}},{"id":26,"attributes":{"title":"YouTube","href":"https://www.youtube.com/c/DuskNetwork","description":null,"createdAt":"2023-04-06T19:34:40.813Z","updatedAt":"2023-06-01T00:13:59.800Z","publishedAt":"2023-06-01T00:13:59.795Z","logo":{"data":null}}},{"id":25,"attributes":{"title":"Reddit","href":"https://www.reddit.com/r/dusknetwork","description":null,"createdAt":"2023-04-06T19:34:19.625Z","updatedAt":"2023-06-01T00:13:45.537Z","publishedAt":"2023-06-01T00:13:45.531Z","logo":{"data":null}}}]}}},{"id":9,"attributes":{"UUID":"website-footer-forth","createdAt":"2023-06-22T11:36:16.065Z","updatedAt":"2023-06-22T11:36:46.266Z","publishedAt":"2023-06-22T11:36:46.262Z","title":"Footer Forth Menu","menu_items":{"data":[{"id":29,"attributes":{"title":" Binance","href":"https://www.binance.com/en","description":null,"createdAt":"2023-06-22T11:32:14.820Z","updatedAt":"2023-06-22T11:32:57.637Z","publishedAt":"2023-06-22T11:32:57.632Z","logo":{"data":{"id":285,"attributes":{"name":"binance.svg","alternativeText":null,"caption":null,"width":101,"height":21,"formats":null,"hash":"binance_af2dff8df0","ext":".svg","mime":"image/svg+xml","size":2.09,"url":"https://dusk-cms.ams3.digitaloceanspaces.com/binance_af2dff8df0.svg","previewUrl":null,"provider":"aws-s3","provider_metadata":null,"createdAt":"2023-06-22T11:32:10.155Z","updatedAt":"2023-06-22T11:32:10.155Z"}}}}},{"id":32,"attributes":{"title":"KuCoin","href":"https://www.kucoin.com/","description":null,"createdAt":"2023-06-22T11:33:33.760Z","updatedAt":"2023-06-22T11:33:37.151Z","publishedAt":"2023-06-22T11:33:37.145Z","logo":{"data":{"id":287,"attributes":{"name":"kucoin.svg","alternativeText":null,"caption":null,"width":87,"height":21,"formats":null,"hash":"kucoin_ea796fe108","ext":".svg","mime":"image/svg+xml","size":6.48,"url":"https://dusk-cms.ams3.digitaloceanspaces.com/kucoin_ea796fe108.svg","previewUrl":null,"provider":"aws-s3","provider_metadata":null,"createdAt":"2023-06-22T11:32:10.297Z","updatedAt":"2023-06-22T11:32:10.297Z"}}}}},{"id":31,"attributes":{"title":" Huobi","href":"https://www.huobi.com/en-us/","description":null,"createdAt":"2023-06-22T11:33:14.371Z","updatedAt":"2023-06-22T11:33:15.445Z","publishedAt":"2023-06-22T11:33:15.439Z","logo":{"data":{"id":288,"attributes":{"name":"huobi.svg","alternativeText":null,"caption":null,"width":75,"height":21,"formats":null,"hash":"huobi_ea9430d460","ext":".svg","mime":"image/svg+xml","size":2.9,"url":"https://dusk-cms.ams3.digitaloceanspaces.com/huobi_ea9430d460.svg","previewUrl":null,"provider":"aws-s3","provider_metadata":null,"createdAt":"2023-06-22T11:32:10.302Z","updatedAt":"2023-06-22T11:32:10.302Z"}}}}},{"id":30,"attributes":{"title":" Gate.io","href":"https://www.gate.io/","description":null,"createdAt":"2023-06-22T11:32:52.552Z","updatedAt":"2023-06-22T11:32:53.820Z","publishedAt":"2023-06-22T11:32:53.814Z","logo":{"data":{"id":286,"attributes":{"name":"gateio.svg","alternativeText":null,"caption":null,"width":91,"height":21,"formats":null,"hash":"gateio_e1483328ce","ext":".svg","mime":"image/svg+xml","size":5.82,"url":"https://dusk-cms.ams3.digitaloceanspaces.com/gateio_e1483328ce.svg","previewUrl":null,"provider":"aws-s3","provider_metadata":null,"createdAt":"2023-06-22T11:32:10.282Z","updatedAt":"2023-06-22T11:32:10.282Z"}}}}}]}}},{"id":7,"attributes":{"UUID":"footer-small-print-menu","createdAt":"2023-04-06T19:50:14.347Z","updatedAt":"2023-06-01T00:15:46.972Z","publishedAt":"2023-06-01T00:15:46.966Z","title":"Small Print Menu","menu_items":{"data":[{"id":9,"attributes":{"title":"Privacy Policy","href":"/privacy-policy","description":null,"createdAt":"2023-04-06T19:21:38.953Z","updatedAt":"2023-06-01T00:15:44.137Z","publishedAt":"2023-06-01T00:15:44.132Z","logo":{"data":null}}},{"id":28,"attributes":{"title":"Terms of Use","href":"/terms-of-use","description":null,"createdAt":"2023-04-06T19:50:30.107Z","updatedAt":"2023-06-01T00:15:39.971Z","publishedAt":"2023-06-01T00:15:39.966Z","logo":{"data":null}}}]}}}]}}}}},"articles":{"data":[{"id":114,"body":"

Today is an incredibly exciting day, as we can announce our first 2 milestones on the road to mainnet, the Citadel SDK and Rusk VM 2.0, are both delivered! The delivery of the Citadel SDK and Rusk VM 2.0 mark the first two deliverables for the timely and successful delivery of mainnet.

Both are huge achievements for the team, and the community can be proud of the work that is being done.

Not to mention the fact that both are ground-breaking firsts for the blockchain industry!

The Rusk VM 2.0 will make Dusk the only ZK-friendly Layer One capable of supporting confidential smart contracts, while Citadel is the first decentralized and private identity tool capable of performing KYC in a way that is both compliant and private.

Let’s have a look at what is being shipped, and then go into a deep dive on what each deliverable is, why it was needed, and how it fits into the wider Dusk ecosystem and mission.

Rusk VM 2.0 - a privacy-friendly virtual machine for powerful use cases

Rusk VM 2.0 is the first virtual machine that can natively support privacy preserving smart contracts, while also allowing for ultra lite clients with the instant, trustless sync up of nodes and wallets.

It solves many problems faced by other blockchains, and is the foundational piece of our broader mission.

Libraries

See the code for yourself!

Rusk

Piecrust

VM and smart contracts tutorial

Key points

The Rusk VM 2.0 is ZK-friendly and can support natively deployed confidential smart contracts, both for institutional users and individual developers.
It manages storage infinitely better than competitors, and clients can sync up almost instantly downloading one block, rather than taking days/weeks/months/years to download the entire blockchain.
It is up to 500% faster than its predecessor (Rusk VM 1.0) and scales infinitely.

—-------------------

The Citadel SDK - KYC Redesigned

Next up, we have the Citadel SDK, our decentralized, privacy-friendly licensing tool, which is especially designed for know-your-customer (KYC) and anti-money-laundering (AML) needs. If we want on-chain, decentralized finance, we need an on-chain, decentralized identity tool. That tool is Citadel.

Citadel is both more efficient than current identity solutions, is specially built to be privacy-friendly and to fit into decentralized systems, and paves the way for business adoption of DLT.

Libraries

Check out the code for yourself!

Citadel

Moat

Citadel Wiki with tutorial

Key points

Citadel makes Dusk the first Layer One to have an out-of-the-box identity protocol.
Even better, it’s ZK-based and privacy-preserving.
It allows anyone - be it an institution, a DEX, or a subscription service - to provide (or deny) access to services without revealing the details of the user.
It facilitates the onboarding of regulated finance by allowing institutions to perform their checks, while keeping a users’ data private, and being compatible with blockchain.
It is a huge improvement on the current system, being more efficient and saves time and resources.

Get to know Rusk VM 2.0 and Citadel

Want to know more about both of these innovative products? Keep reading, and get a deeper understanding of what both of these products are, how they work, and why they solve a myriad of problems.

A Deeper Dive: The Rusk VM 2.0

The Rusk VM 2.0 is our novel, and groundbreaking, virtual machine that will power not only the Dusk infrastructure, but all of our partners who build on top of us, and secure billions if not trillions of dollars worth of assets. This is the second iteration of our virtual machine and brings with it a lot of improvements and benefits over its predecessor.

It is the foundational piece of a financial system that is decentralized, private, and permissionless.

This is where it gets a bit technical! There are 3 layers that make up the virtual machine: Web Assembly, Piecrust, and the Rusk nodes, with “Rusk VM 2.0” being the term that refers to all 3 of these layers.

Web Assembly is the base layer, and executes transactions. However, it knows nothing about blockchain, so Piecrust is the next layer and “teaches” Web Assembly about blockchain. Piecrust, however, knows nothing about zero-knowledge, so Rusk VM 2.0 makes it possible to transact in a way that is privacy-friendly.

Why was the Rusk VM 2.0 necessary?

One of the hardest things about crypto is cutting through the noise, so while it may appear that there are many privacy-friendly projects out there, most (if not all) are built on top of existing systems, either as applications or as Layer Twos.

This wasn’t good enough for us; we needed infrastructure that met our needs, and thus we needed a Layer One that was privacy-friendly from the beginning, and that used zero-knowledge proofs not to scale existing blockchains, but to provide privacy. This is not possible when building on top of a system that wasn’t designed for privacy, the information leaks somewhere.

Secondly, we found other VMs out there to have long-term difficulties when it came to storage and scalability and we foresee that many will have issues further down the line. As such it was necessary for us to build our own virtual machine from scratch in order to ensure that Dusk is always easy to use and doesn’t suffer from memory or scalability issues.

What is Rusk VM 2.0?

Rusk makes Dusk the only Layer One blockchain capable of deploying natively privacy-preserving smart contracts.

Privacy and compliance are built in from the ground up, enabling real real-world assets to not only be tokenized on-chain, but to be natively issued on-chain, thus ushering in a new, decentralized form of finance that is faster, more efficient, and more effective.

This is the first step in our journey towards becoming the first decentralized financial market infrastructure (FMI) for regulated assets, that is capable of replacing vast amounts of outdated processes and middlemen, and make financial assets, capital, and most importantly, opportunities for financial freedom and inclusion, available to all.

The problems Rusk solves

Rusk is faster, more scalable, and more private than anything that exists out there.

Private

It is privacy-friendly and allows for the deployment of confidential smart contracts. This means that anyone can deploy smart contracts that preserve users’ privacy, be it a stock market exchange or an anonymous developer building a DEX.

This opens up so many possibilities, as privacy is now the standard and the default, not the exception or the modification.

Infinitely better memory storage

The Rusk VM 2.0 is also leaps and bounds ahead when it comes to memory and state management.

The challenge most blockchains face is that when a new client wants to join the network, as a node provider for example, they have to sync up to the network. This has meant downloading every single block the blockchain has produced, all the way back to the genesis block.

This takes a long time! Weeks, months, and in the future, years.

With the Rusk VM 2.0, new joiners to the network only have to download the latest block, and are instantly caught up with the entire blockchain.

This makes it so much easier to participate in the network and is a revolutionary way to manage “state bloat” that would otherwise make it all but impossible for new clients to join the network.

Up to 500% faster than before

The new VM is also fast, much faster, than its previous iteration performing up to 5x more transactions per block than its predecessor. While testing it was also found that improvements do not scale linearly, but infinitely.

Complex proofs have to be generated in order to generate ZKPs and confirm the transactions, and to have sped the processing so much is a huge achievement. We now have the foundations for a Layer One blockchain that is fast and private.

A Deeper Dive: Get to Know Citadel

Why was Citadel necessary?

Citadel was needed both to bridge regulated finance on-chain, and to improve the KYC process more broadly. With Citadel it is possible to verify someone’s credentials without needing to know who they are.

It’s an amazing application of zero-knowledge proof cryptography, where your proof acts as a pass that either opens the door to a service, or it doesn’t, but no personal information is shared.

This is a huge win for privacy, decentralization, and the onboarding of the trillion dollar market of real-world assets. We also see regulations like this start to creep into DeFi with DEXs starting to require KYC.

What is Citadel?

Citadel is a privacy-preserving, decentralized licensing tool that has a number of exciting applications. It essentially issues a pass or access card (known as a “proof”) that can be used to prove that you have the right to use services or products, without having to reveal your identity or personal information.

The experience of using it is much like using a building pass; if you have the authorization to enter a room, the door will open when you present your key. If you don’t, then it doesn’t.

Citadel can be used for KYC, subscription services, and a whole host of other things. If you need to have a way of verifying who can access your platform, due to paying a membership fee or being of the right age or not from a banned jurisdiction, Citadel does this for you in a way that is private, decentralized, and on-chain.

The problems Citadel solves

More efficient

The current approach to KYC is clunky and inefficient, with enterprises spending billions to replicate a process that has already been done. This inefficiency costs money, prevents competition by making it hard for new and innovative firms to enter the market, and puts users at risk due to sharing their information so widely.

With Citadel, you provide your details once, for example to your bank, and are then issued with a license which you can use to access other services and products. It’s like getting a pass card, and rather than having to share your details, you just swipe your card.

Private

Instead of having to share who you are, you share your proof which proves no more and no less than that you are able to access these services.

There is no reason to continually leak information when all a provider needs to know is that you can access their services. Citadel preserves your privacy while allowing you to interact with regulated assets, while also making it easy for enterprises, institutions, or lone wolf developers to create services that are compliant.

This is groundbreaking, for institutions who no longer have to spend billions verifying information that has already been verified, and for users who don’t want to have to give their data to everyone when all they need to prove is that they are over a certain age, or from a certain jurisdiction.

Compliant

In order to deal in regulated, real-world assets, organizations must comply with regulations. Citadel meets the requirements of the EUDI directive for digital wallets, and thus makes it easy for everyone to be compliant while enjoying the benefits of blockchain.

Without this tool, protocols and institutions will either not be compliant, or they will have to rely on outdated KYC methods which are highly centralized, expensive, do not integrate well with blockchain, and do preserve users’ privacy.

Beyond KYC

Citadel is not only for KYC, although that is a strong use case. Citadel can also be used for subscription services, memberships, tickets, even digital identities.

The Road Ahead

Both Citadel and the Rusk VM 2.0 set a new standard in blockchain technology. Prioritizing privacy and efficiency, these are both 2 vital tools to enabling decentralized finance at its highest level, with the potential of decentralizing and increasing access to traditional financial tools, slashing costs, and opening up the economy.

The unique blend of privacy, decentralization, and solutions to the toughest problems facing institutions and blockchains alike, makes Citadel and the Rusk VM 2.0 not only two achieved milestones for us, but two groundbreaking additions to the blockchain and finance space.

","slug":"citadel-and-rusk-shipped","createdAt":"2023-11-28T14:35:59.041Z","updatedAt":"2023-12-05T17:29:50.914Z","publishedAt":"2023-11-28T16:13:37.125Z","locale":"en","custom_publishedAt":null,"spotify_link":null,"youtube_id":null,"heading":"Citadel SDK & Rusk VM 2.0: Mainnet Deliverables are Shipped","image":{"id":491,"name":"Citadel_SDK__Rusk_VM_2.0_.png","alternativeText":"Citadel SDK and Rusk VM 2.0 are shipped","caption":"Citadel SDK and Rusk VM 2.0 are shipped","width":1920,"height":1080,"formats":{"large":{"ext":".png","url":"https://dusk-cms.ams3.digitaloceanspaces.com/large_Citadel_SDK_Rusk_VM_2_0_3dcea3dffe.png","hash":"large_Citadel_SDK_Rusk_VM_2_0_3dcea3dffe","mime":"image/png","name":"large_Citadel_SDK__Rusk_VM_2.0_.png","path":null,"size":445.09,"width":1000,"height":563},"small":{"ext":".png","url":"https://dusk-cms.ams3.digitaloceanspaces.com/small_Citadel_SDK_Rusk_VM_2_0_3dcea3dffe.png","hash":"small_Citadel_SDK_Rusk_VM_2_0_3dcea3dffe","mime":"image/png","name":"small_Citadel_SDK__Rusk_VM_2.0_.png","path":null,"size":107.34,"width":500,"height":281},"medium":{"ext":".png","url":"https://dusk-cms.ams3.digitaloceanspaces.com/medium_Citadel_SDK_Rusk_VM_2_0_3dcea3dffe.png","hash":"medium_Citadel_SDK_Rusk_VM_2_0_3dcea3dffe","mime":"image/png","name":"medium_Citadel_SDK__Rusk_VM_2.0_.png","path":null,"size":247.93,"width":750,"height":422},"thumbnail":{"ext":".png","url":"https://dusk-cms.ams3.digitaloceanspaces.com/thumbnail_Citadel_SDK_Rusk_VM_2_0_3dcea3dffe.png","hash":"thumbnail_Citadel_SDK_Rusk_VM_2_0_3dcea3dffe","mime":"image/png","name":"thumbnail_Citadel_SDK__Rusk_VM_2.0_.png","path":null,"size":26.53,"width":245,"height":138}},"hash":"Citadel_SDK_Rusk_VM_2_0_3dcea3dffe","ext":".png","mime":"image/png","size":302.58,"url":"https://dusk-cms.ams3.digitaloceanspaces.com/Citadel_SDK_Rusk_VM_2_0_3dcea3dffe.png","previewUrl":null,"provider":"aws-s3","provider_metadata":null,"folderPath":"/","createdAt":"2023-11-28T14:22:45.144Z","updatedAt":"2023-11-28T14:22:45.144Z"},"author":{"id":3,"first_name":"Jade","last_name":"Doherty","role":"Marketing Specialist","twitter_handle":null,"linkedin_handle":"jade-doherty-a12b7977","github_handle":null,"createdAt":"2023-04-25T13:03:31.178Z","updatedAt":"2023-10-09T09:45:04.880Z","publishedAt":"2023-05-24T10:26:47.773Z","full_name":"Jade Doherty","bio":"Jade has a strong background in copywriting and content creation and has previously written for a global humanitarian and meditation organization, as well as various blockchains and crypto companies. She sees a lot of similarities between crypto and meditation; both are very cool but no one really knows what’s going on or what these words and concepts mean! ","email":null,"author_bio":null,"image":{"id":407,"name":"_DSC3674.jpg","alternativeText":null,"caption":null,"width":3433,"height":3433,"formats":{"large":{"ext":".jpg","url":"https://dusk-cms.ams3.digitaloceanspaces.com/large_DSC_3674_fe47cc4314.jpg","hash":"large_DSC_3674_fe47cc4314","mime":"image/jpeg","name":"large__DSC3674.jpg","path":null,"size":49.33,"width":1000,"height":1000},"small":{"ext":".jpg","url":"https://dusk-cms.ams3.digitaloceanspaces.com/small_DSC_3674_fe47cc4314.jpg","hash":"small_DSC_3674_fe47cc4314","mime":"image/jpeg","name":"small__DSC3674.jpg","path":null,"size":14.96,"width":500,"height":500},"medium":{"ext":".jpg","url":"https://dusk-cms.ams3.digitaloceanspaces.com/medium_DSC_3674_fe47cc4314.jpg","hash":"medium_DSC_3674_fe47cc4314","mime":"image/jpeg","name":"medium__DSC3674.jpg","path":null,"size":29.49,"width":750,"height":750},"thumbnail":{"ext":".jpg","url":"https://dusk-cms.ams3.digitaloceanspaces.com/thumbnail_DSC_3674_fe47cc4314.jpg","hash":"thumbnail_DSC_3674_fe47cc4314","mime":"image/jpeg","name":"thumbnail__DSC3674.jpg","path":null,"size":2.75,"width":156,"height":156}},"hash":"DSC_3674_fe47cc4314","ext":".jpg","mime":"image/jpeg","size":515.24,"url":"https://dusk-cms.ams3.digitaloceanspaces.com/DSC_3674_fe47cc4314.jpg","previewUrl":null,"provider":"aws-s3","provider_metadata":null,"folderPath":"/5/38","createdAt":"2023-10-09T09:43:22.911Z","updatedAt":"2023-10-09T09:43:22.911Z"}},"article_cats":[{"id":6,"name":"Community","createdAt":"2023-05-08T10:49:29.123Z","updatedAt":"2023-05-24T10:27:34.729Z","publishedAt":"2023-05-24T10:27:34.722Z"},{"id":3,"name":"Research & Development","createdAt":"2023-04-06T21:13:20.021Z","updatedAt":"2023-05-24T10:27:22.602Z","publishedAt":"2023-05-24T10:27:22.580Z"}]},{"id":113,"body":"

Our development planning features a Release Cycle of three weeks, providing a consistent stream of updates to the community, developers, and businesses relying on Dusk technology.

The publicly available Dusk Network GitHub contains over 18 active repositories, each focused on a different technical subject. Progress in each is ongoing and can be followed in real-time. The Release Cycle process is currently applied to some of our most active repositories.

Release Cycle Update Summary

During the most recent 3 week Release Cycle, the Rusk repository has seen significant progress. Developments include enhancements, such as license contract methods, block detection, timing of block acceptance, refining consensus mechanisms, and optimizing components. Notably, issues like adding a prover feature to Rusk, resolving test block inconsistencies, and enhancing security in the OutOfSync state have been addressed successfully.

In the Piecrust segment, a test implemented during dusk-network/rusk#1125 revealed a root display discrepancy between sessions with erroring calls and those with successful calls. This highlights an important aspect of system behavior under different conditions.

For Wallet-Core, the focus has been on introducing features for offline transaction signing, improving log, warning, and error handling, and updating WebAssembly in continuous integration tests, all aimed at bolstering security and testing efficiency. The resolution of issues pertaining to error reporting and transaction verification between wallet-core and rusk is a notable achievement.

The Plonk repository's recent updates include proposals to improve code modularity and error handling, particularly in the component_mul_generator. The absence of closed issues suggests ongoing efforts to tackle these new challenges.

The Schnorr repository underwent changes with multiple issues opened and closed, focusing on naming conventions, documentation updates, and refinements in the signature and proof systems.

Lastly, the Dusk-PKI repository has been deprecated, with all keys now integrated into either dusk-schnorr or phoenix-core, streamlining the Dusk Network ecosystem.

Overall, these updates demonstrate a strong commitment to advancing our blockchain infrastructure with a focus on security, efficiency, and system robustness towards our Mainnet in 2024.

For the community's benefit, we have divided our repositories in 3 categories, main, libraries and other. Below you will find a selection of some (but not all) of the work that is being done in our repositories, including recent advancements.

$\"release_cycle_2023.png\"$

Main Repositories

Rusk

The Dusk's Smart Contract Platform.

Update Summary

In the past three weeks, the Rusk repository has seen notable developments.

Among the opened issues, key focuses include renaming the License Contract's noop method, addressing missing block detection, investigating block acceptance timing, refining consensus mechanisms, and optimizing components by removing specific dependencies.

A number of issues have been closed, including the addition of a prover feature for rusk, resolution of non-deterministic behavior in test blocks, improved security and stability in the OutOfSync state and fallback procedure, and the successful addition of various features like deterministic winning certificates and enhanced API documentation.

Opened

Rename License Contract noop method to request_license #1151

Missing block detection #1150

Investigate block acceptance timing #1149

Consensus: accept block from single Agreement #1148

Remove anyhow from http handler #1146

Allow rusk to be prover-only #1144

Remove phoenix-core from rusk-recovery #1139

Remove phoenix-core from stake-contract #1138

node: Maintain a set of eligible provisioners of previous epoch/block #1124

Change block's finality definition #1118

Add failed_iterations fields #1116

Document API #1114

Single vote for iteration #1109

Closed

Add prover feature for rusk #1145

Test blocks are not deterministic #1141

Add clippy check for smart contracts #1140

Add hash header to the CRS-via-HTTP api #1135

Remove rusk-recovery binaries #1128

node: Improve security and stability of OutOfSync state and fallback procedure #1127

Add rusk-recovery capability to rusk #1126

CRS is not cached properly #1121

Enrich Rusk ABI and License Smart Contract with a method to provide PLONK setup #1119

Start iteration from 0 instead of 1#1117

Add Deterministic winning certificate #1115

Introduce prev_certificates #1108

Shortcircuit timed out iterations #1107

node: Request missing blocks if node enters on_idle state #1103

Piecrust

Piecrust is a Rust workspace containing two crates, piecrust and piecrust-uplink, that together form the WASM virtual machine for running, handling and creating Dusk smart contracts.

Update Summary

During the implementation of dusk-network/rusk#1125, a test was added that makes an erroring call, and then subsequently executes another call. Another session is then instantiated that only runs successful calls, which then displays a different root than before.

Opened issues

Inconsistent root after erroring calls #296

Closed issues

In the past 3 weeks, no issues were closed in the piecrust repository.

Libraries

Wallet-CLI

Library providing functionalities to create wallets compatible with Dusk Network

This library is used to implement the official Dusk CLI wallet.

Update Summary

Wallet-CLI v0.20.1 was released on November 22nd. Introducing the following changes:

Added

Add spending_keys to wallet impl [#218]

Opened issues

interactive stake-allow doesn't work #222

Closed issues

Implement a method to get the SSK from another module #218

Wallet-core

A WASM library to provide business logic for Dusk wallet implementations.

Update Summary

Three new issues have been opened in the past three weeks. These include requests to add a feature enabling offline transaction signing (#96), the provision of handles for log, warnings, and errors (#95), and the compilation of fresh WebAssembly (wasm) during integration tests on Continuous Integration (CI) (#94). These issues collectively indicate a focus on enhancing security, error management, and testing procedures within the Wallet Core library.

On the closed issues front, two matters have been successfully addressed. The first involves the addition of error reporting and hooks for handling errors (#97), while the second pertains to resolving a concern where transactions created by the current wallet-core could not be verified on the rusk side (#84).

Opened issues

Add a way to offline sign transactions #96

Provide handles for log, warnings and errors #95

Compile fresh wasm when running integration tests on CI #94

Closed issues

Add error reporting and hooks for onerror #97

Current wallet-core creates transactions which cannot be verified on rusk side #84

Plonk

This is a pure Rust implementation of the PLONK proving system over BLS12-381

This library contains a modularised implementation of KZG10 as the default polynomial commitment scheme.

Update Summary

In the recent updates to the Plonk repository, two new issues have been opened in the past three weeks. The first issue (#788) proposes the separation of the component_mul_generator into two distinct methods, one for G and one for G_prime. The second issue (#787) suggests making the component_mul_generator infallible, emphasizing a focus on code modularity and error handling within the Plonk repository.

During this period, no issues have been closed, indicating that the development team is actively addressing new concerns and enhancements without recent resolutions in the Plonk repository.

Opened issues

separate component_mul_generator into two methods, one for G and one for G_prime #788

make component_mul_generator infallable #787

Closed issues

In the past 3 weeks, no issues were closed in the plonk repository.

Other

Citadel

This repository contains the implementation of Citadel, a protocol that integrates a self-sovereign identity system into the Dusk blockchain. An academic paper with further details about the protocol can be found here.

It also contains Shelter, a version of Citadel meant for non-Blockchain use cases. Documentation on this version will be provided soon.

Update Summary

No new issues were opened for Citadel, and one was closed (#87) to ensure that if the session fails the session verify doesn’t panic. It has been updated to return boolean instead of panicking.

Opened

No issues opened in the last 3 weeks.

Closed

Add a non-panicking method for verifying session #87

Poseidon252

Reference implementation for the Poseidon Hashing algorithm.

Update Summary

Two new issues have been opened. The first issue (#108) proposes the removal of the \"Note\" prefix from \"NoteSecretKey\" and \"NotePublicKey,\" suggesting a refinement in naming conventions. The second issue (#225) involves the addition of a failing test to address incorrect openings, indicating a proactive approach to testing and ensuring the reliability of the codebase.

On the closed issues front, one matter has been successfully addressed. Issue #188 involved the utilization of component_boolean in the merkle opening circuit.

Opened

Remove Note prefix from NoteSecretKey and NotePublicKey #108

Add failing test for incorrect opening #225

Closed

Use component_boolean in the our merkle opening circuit #188

Schnorr

The Schnorr signature algorithm, given its namesake by its creator Claus Schnorr, is a digital signature scheme which provides a simple method of creating short signatures.

The implementation has been created using the Poseidon hash function, the paper for which can be found here.

For a reference to the algorithm, please see the docs.

Update Summary

There were a lot of updates to Schnorr in the past 3 weeks, with Schnorr v0.16.0 being released on November 22nd. Introducing the following changes:

Added

Update README with keys structure [#104]
Add documentation to the new key structs [#105]

Changed

Change the NotePublicKey tuple struct to directly be a tuple with two fields [#111]
Change double and single signature creation to be a method on NoteSecretKey [#81]
Rename internal key_variants module to signatures [#96]
Rename the signatures method to_witness to append [#99]
Update benchmarks to latest version of plonk [#94]
Update test structure [#94]
Move PublicKeyPair from DoubleSignature to public_keys [#95]
Rename keys: NoteSecretKey -> SecretKey, NotePublicKey -> PublicKey [#108]

Removed

Hide (Double)Signature::new() from the public API [#81]

Opened issues

Find a better name for PublicKeyPair #110

Rename crate to jubjub-schnorr #109

NotePublicKey derivation, signing and verification must also work with a custom Generator G #107

Closed issues

Remove Note prefix from NoteSecretKey and NotePublicKey #108

Change NotePublicKeyPair single field tuple struct to have two fields #111

Add docs to new key modules #105

Update README #104

Deprecate PublicKeyPair #95

Rename methods to_witness to append #99

Update benchmarks and zk tests #94

Change module name key_variants to signatures #96

Refactor Signature and Proof to be more consistent to bls12_381-sign #81

Dusk-pki

PKI stands for Public Key Infrastructure. This repository has been created so there's a unique library that holds the types and functions required to perform keys operations.

Update Summary

The Dusk-PKI depository is being deprecated. All keys moved into either dusk-schnorr or phoenix-core.

Opened

There were no issues opened in the last 3 weeks.

Closed issues

Add deprecated badge for crates.io #88

Deprecate this repo #79

In A Nutshell: Release Cycle planning

As you can see, development is continuous and this list is not exhaustive. For example, minor issues and advancements concerning the Kadcast element have also been opened and resolved. The complete series of repositories can be found on GitHub.

Breakthrough developments will receive a separate spotlight, such as our latest deployment of Daylight. Thank you very much for your understanding and feedback as we continue to find the best way to provide the community with transparency and development information.

Release Cycle development planning has been adopted by major companies including Google, Mozilla, and during the development of products such as Ubuntu, Kubernetes, and many more. The reason for this is clear: Release Cycle planning improves the predictability of software development for developers and the community alike.

For a more detailed explanation of the concept (along with frequently asked questions) please scroll down to the bottom of this article.

The above noted additions/changes to the repository can be followed on GitHub, for further details on their status and their function in the stack.

FAQ

We’ve included a small FAQ section below to make sure the community understands our intention with Release Cycles.

What is Release Cycle planning?

Release Cycle planning means that developmental updates are published at consistent intervals on GitHub; in the case of Dusk Network, every three weeks. These releases describe the latest additions, changes, fixes, and assets added to the tech stack by the development team.

Dusk Network currently has over 18+ active repositories on GitHub, each repository covering a different technical project. Release Cycle planning has not yet been applied to all repositories; the current focus on a single GitHub repository for clarity does not mean there are no ongoing developmental efforts occurring in other areas.

Does being featured in a Release mean Deployment?

The Release Cycle updates does not mean immediate deployments on our testnet. It is a release detailing additions, changes, and fixes to the repositories that we are ready to share with the public. All released content is considered stable, consistent, reviewed, and cross-checked with other repositories.

Are Release Cycle updates a spotlight for major deliverables?

No. The Release Cycle approach is strictly a way to provide a consistent shape for publication of our work in the clearest terms possible. They are not deadlines to be made, nor are they tied to specific development sprints. Release Cycle updates aim to raise attention with the community, and give proper coverage to, publishable GitHub releases. Major deliverables will be given their proper publication in dedicated articles.

About Dusk Network

Dusk Network is the privacy blockchain for financial applications. A new standard for compliance, control, and collaboration. Our mission is to enable any size enterprise to collaborate at scale, meet compliance requirements and ensure that personal and transaction data remains confidential.

In the past Release Cycle we have seen various updates and improvements across multiple Dusk GitHub repositories. In the Rusk repository, significant progress has been made in enhancing the transfer contract by migrating it to utilize the dusk-merkle tree. This upgrade not only resolves problems related to defining a proper tree walk but also simplifies the process. Additionally, several new issues have been opened and closed, addressing concerns such as enabling fallback procedures, decoding blocks with multiple transactions, and resolving compatibility issues.

Moving on to the Piecrust repository, version 0.6.0 has been released, introducing changes and additions to the piecrust and piecrust-uplink crates. Notably, the implementation now includes an Event struct, improved debugging capabilities, and adjustments to event handling.

In the Wallet-cli repository, version 0.16.0 has been released, focusing on updates related to Note's key and cache. This release tackles issues such as changing the cached Note's key to be the nullifier instead of the hash and updating the cache for all possible addresses simultaneously.

Plonk saw the release of version 0.14.1, which introduces circuit compression capabilities through the Compiler::compress and Compiler::decompress functions.

Shifting our focus to the Citadel repository, several noteworthy developments have taken place. New issues were opened, including the design and implementation of the Citadel request authoring process, while existing issues regarding compute parameters, local state removal, and code reuse were successfully resolved.

Merkle repository saw the implementation of custom serialization for Opening and poseidon_merkle::Opening, with an associated issue opened to address this functionality.

In Poseidon252, version 0.30.1 was released, fixing the missing rkyv feature, and closed issues encompassed the addition of a sponge framework and benchmarks for poseidon opening.

The Schnorr repository released version 0.13.0, incorporating updates to dusk-pki, dusk-poseidon, and dusk-plonk dependencies. Lastly, Dusk-PKI version 0.12.0 was released, featuring updates to dusk-poseidon and rust-toolchain dependencies.

These updates reflect the ongoing efforts and progress within the Dusk ecosystem. Developers are actively addressing issues, improving code efficiency, and enhancing functionality across various repositories. As the network continues to evolve, these updates pave the way for a more robust and efficient Dusk protocol, benefiting developers and users alike.

","slug":"release-cycle-update-29","createdAt":"2023-11-23T14:04:15.741Z","updatedAt":"2023-12-01T09:56:14.976Z","publishedAt":"2023-11-23T14:04:18.835Z","locale":"en","custom_publishedAt":null,"spotify_link":null,"youtube_id":null,"heading":"Dusk | Release Cycle #29","image":{"id":487,"name":"rc29.png","alternativeText":"Release Cycle Update #29","caption":"Release Cycle Update #29","width":1920,"height":1080,"formats":{"large":{"ext":".png","url":"https://dusk-cms.ams3.digitaloceanspaces.com/large_rc29_91a3e0ab41.png","hash":"large_rc29_91a3e0ab41","mime":"image/png","name":"large_rc29.png","path":null,"size":413.14,"width":1000,"height":563},"small":{"ext":".png","url":"https://dusk-cms.ams3.digitaloceanspaces.com/small_rc29_91a3e0ab41.png","hash":"small_rc29_91a3e0ab41","mime":"image/png","name":"small_rc29.png","path":null,"size":92.28,"width":500,"height":281},"medium":{"ext":".png","url":"https://dusk-cms.ams3.digitaloceanspaces.com/medium_rc29_91a3e0ab41.png","hash":"medium_rc29_91a3e0ab41","mime":"image/png","name":"medium_rc29.png","path":null,"size":220.63,"width":750,"height":422},"thumbnail":{"ext":".png","url":"https://dusk-cms.ams3.digitaloceanspaces.com/thumbnail_rc29_91a3e0ab41.png","hash":"thumbnail_rc29_91a3e0ab41","mime":"image/png","name":"thumbnail_rc29.png","path":null,"size":20.89,"width":245,"height":138}},"hash":"rc29_91a3e0ab41","ext":".png","mime":"image/png","size":367.83,"url":"https://dusk-cms.ams3.digitaloceanspaces.com/rc29_91a3e0ab41.png","previewUrl":null,"provider":"aws-s3","provider_metadata":null,"folderPath":"/","createdAt":"2023-11-23T13:54:09.403Z","updatedAt":"2023-11-23T13:54:09.403Z"},"author":{"id":50,"first_name":"Yannick","last_name":"Planteijdt","role":"Marketing Specialist","twitter_handle":"planteijdt","linkedin_handle":"yannick-planteijdt","github_handle":"DePlant01","createdAt":"2023-12-01T09:14:11.204Z","updatedAt":"2023-12-01T09:47:56.561Z","publishedAt":"2023-12-01T09:47:56.553Z","full_name":"Yannick Planteijdt","bio":null,"email":null,"author_bio":null,"image":{"id":493,"name":"yannick.png","alternativeText":null,"caption":null,"width":500,"height":500,"formats":{"thumbnail":{"ext":".png","url":"https://dusk-cms.ams3.digitaloceanspaces.com/thumbnail_yannick_c25a04cc4f.png","hash":"thumbnail_yannick_c25a04cc4f","mime":"image/png","name":"thumbnail_yannick.png","path":null,"size":22.51,"width":156,"height":156}},"hash":"yannick_c25a04cc4f","ext":".png","mime":"image/png","size":59.55,"url":"https://dusk-cms.ams3.digitaloceanspaces.com/yannick_c25a04cc4f.png","previewUrl":null,"provider":"aws-s3","provider_metadata":null,"folderPath":"/5/38","createdAt":"2023-12-01T09:47:48.300Z","updatedAt":"2023-12-01T09:47:48.300Z"}},"article_cats":[{"id":6,"name":"Community","createdAt":"2023-05-08T10:49:29.123Z","updatedAt":"2023-05-24T10:27:34.729Z","publishedAt":"2023-05-24T10:27:34.722Z"}]},{"id":112,"body":"

Introducing Our New CMO, Emanuele Carboni

Some of you might have noticed a new name in the Discord and a new face in photos. Who is this mystery man?

Today, I’m pleased to officially introduce you to Emanuele Carboni, and tell you more about who he is, why he’s involved with Dusk, and why now was the right time for him to come out from behind-the scenes.

Emanuele, a self-described \"serial entrepreneur, strategic board member, and investor\" was an early investor in Dusk.

He’s been a very good friend of co-founders Emanuele Francioni and Fulvio Venturelli for years, and has been attached to Dusk for a long time, and today we are thrilled to introduce him as our new Chief Marketing Officer and board member.

A Duskie from the beginning!

Emanuele is no stranger to Dusk and he’s been involved behind-the-scenes for some time. His journey with us began as an early investor, and someone who saw potential in our vision when we were taking our initial steps, and who was interested in using Dusk to power his own long-running real-estate business.

He saw that blockchain would be a key technology in the future, and believed in Emanuele Francioni as a person who had the vision and technical know-how to create something valuable, useful, and worth being part of.

From an Investor to an Integral Team and Board Member

Reflecting on his early belief in Dusk, Emanuele Carboni says \"I always believed Dusk was more than just another blockchain. It’s one of the only - if not the only - blockchains capable of onboarding the huge market of traditional finance. I saw Dusk as being able to provide a solution to the inefficiencies in finance, and I wanted to be part of it”

Emanuele Carboni brings with him a wealth of experience, having founded and exited the largest gaming platform in Italy. His digital marketing agencies have been game-changers, creating strategies that have generated hundreds of millions for clients. This isn't just experience; it's a track record of excellence and success in scaling companies and growing them to dominate their industry.

As our new CMO Emanuele will lead the push to make Dusk a recognized name in decentralized and traditional finance, while as a board member he will work closely to make key decisions, advise on strategy, and be the non-technical, more business-focused member of the board.

He is also a seasoned investor, making sizable, multi-million dollar investments in companies like Google and Meta, to name a few.

Why Emanuele Carboni, Why Now?

You might be wondering, why Emanuele and why now?

Now is the perfect time for Emanuele to take on a more operational role, both for us and him.

As we edge closer to launching our mainnet, we find ourselves in need of someone who not only understands marketing but who understands Dusk, and who is able to make Dusk the go-to protocol for the $100+ trillion dollar securities market.

Emanuele's expertise in digital marketing, scaling businesses, and taking a big market share is unparalleled, and his connection to our core values makes him the perfect fit for us. With so many successful ventures and companies to his name, he’s seen it all. Succeeding in some of the most competitive industries around, he knows marketing and business inside out.

So, we are incredibly happy to have him join us at this significant and important point in our journey. We want everyone to know about Dusk, and Emanuele is the man to make that happen.

Having dominated the gaming industry in Italy, and with so much experience across different business sectors, Emanuele knows what institutions need, what the press needs, and what retail investors need, and is skilled at communicating the complexity but also the value of Dusk to different people.

Emanuele himself was looking for a new challenge. Having comfortably retired a few years ago, he found himself missing the dynamism and challenges of the business world. \"I realized retirement wasn't for me. I need the challenge and the fight that marketing brings, so when Emanuele Francioni suggested to me that I take on the role of CMO I was excited,\" he shared with me.

CEO Emanuele Francioni says “I am excited to have one of my most trusted friends and advisors working with me, side-by-side to bring the Dusk vision to fruition. I have known Emanuele for many years, and value his perspective and experience. He brings shrewd business acumen, the willingness to take risks, and enthusiasm for numbers. He is what we need at this point in our journey, and I hope you’ll join me in welcoming him to the team”.

Welcome aboard, Emanuele. Here's to new beginnings and to writing a future that's as dynamic and successful as your past!

","slug":"welcome-new-CMO-emanuele-carboni","createdAt":"2023-11-16T10:27:17.834Z","updatedAt":"2023-11-16T10:33:07.815Z","publishedAt":"2023-11-16T10:28:31.526Z","locale":"en","custom_publishedAt":null,"spotify_link":null,"youtube_id":null,"heading":"Welcome to Dusk Emanuele Carboni","image":{"id":478,"name":"welcome carboni.png","alternativeText":"Dusk is please to welcome Emanuele Carboni as our new CMO","caption":"Dusk is please to welcome Emanuele Carboni as our new CMO","width":1920,"height":1080,"formats":{"large":{"ext":".png","url":"https://dusk-cms.ams3.digitaloceanspaces.com/large_welcome_carboni_18cc040d4b.png","hash":"large_welcome_carboni_18cc040d4b","mime":"image/png","name":"large_welcome carboni.png","path":null,"size":430.85,"width":1000,"height":563},"small":{"ext":".png","url":"https://dusk-cms.ams3.digitaloceanspaces.com/small_welcome_carboni_18cc040d4b.png","hash":"small_welcome_carboni_18cc040d4b","mime":"image/png","name":"small_welcome carboni.png","path":null,"size":105.71,"width":500,"height":281},"medium":{"ext":".png","url":"https://dusk-cms.ams3.digitaloceanspaces.com/medium_welcome_carboni_18cc040d4b.png","hash":"medium_welcome_carboni_18cc040d4b","mime":"image/png","name":"medium_welcome carboni.png","path":null,"size":238.66,"width":750,"height":422},"thumbnail":{"ext":".png","url":"https://dusk-cms.ams3.digitaloceanspaces.com/thumbnail_welcome_carboni_18cc040d4b.png","hash":"thumbnail_welcome_carboni_18cc040d4b","mime":"image/png","name":"thumbnail_welcome carboni.png","path":null,"size":26.72,"width":245,"height":138}},"hash":"welcome_carboni_18cc040d4b","ext":".png","mime":"image/png","size":220.45,"url":"https://dusk-cms.ams3.digitaloceanspaces.com/welcome_carboni_18cc040d4b.png","previewUrl":null,"provider":"aws-s3","provider_metadata":null,"folderPath":"/","createdAt":"2023-11-16T10:06:25.100Z","updatedAt":"2023-11-16T10:06:25.100Z"},"author":{"id":3,"first_name":"Jade","last_name":"Doherty","role":"Marketing Specialist","twitter_handle":null,"linkedin_handle":"jade-doherty-a12b7977","github_handle":null,"createdAt":"2023-04-25T13:03:31.178Z","updatedAt":"2023-10-09T09:45:04.880Z","publishedAt":"2023-05-24T10:26:47.773Z","full_name":"Jade Doherty","bio":"Jade has a strong background in copywriting and content creation and has previously written for a global humanitarian and meditation organization, as well as various blockchains and crypto companies. She sees a lot of similarities between crypto and meditation; both are very cool but no one really knows what’s going on or what these words and concepts mean! ","email":null,"author_bio":null,"image":{"id":407,"name":"_DSC3674.jpg","alternativeText":null,"caption":null,"width":3433,"height":3433,"formats":{"large":{"ext":".jpg","url":"https://dusk-cms.ams3.digitaloceanspaces.com/large_DSC_3674_fe47cc4314.jpg","hash":"large_DSC_3674_fe47cc4314","mime":"image/jpeg","name":"large__DSC3674.jpg","path":null,"size":49.33,"width":1000,"height":1000},"small":{"ext":".jpg","url":"https://dusk-cms.ams3.digitaloceanspaces.com/small_DSC_3674_fe47cc4314.jpg","hash":"small_DSC_3674_fe47cc4314","mime":"image/jpeg","name":"small__DSC3674.jpg","path":null,"size":14.96,"width":500,"height":500},"medium":{"ext":".jpg","url":"https://dusk-cms.ams3.digitaloceanspaces.com/medium_DSC_3674_fe47cc4314.jpg","hash":"medium_DSC_3674_fe47cc4314","mime":"image/jpeg","name":"medium__DSC3674.jpg","path":null,"size":29.49,"width":750,"height":750},"thumbnail":{"ext":".jpg","url":"https://dusk-cms.ams3.digitaloceanspaces.com/thumbnail_DSC_3674_fe47cc4314.jpg","hash":"thumbnail_DSC_3674_fe47cc4314","mime":"image/jpeg","name":"thumbnail__DSC3674.jpg","path":null,"size":2.75,"width":156,"height":156}},"hash":"DSC_3674_fe47cc4314","ext":".jpg","mime":"image/jpeg","size":515.24,"url":"https://dusk-cms.ams3.digitaloceanspaces.com/DSC_3674_fe47cc4314.jpg","previewUrl":null,"provider":"aws-s3","provider_metadata":null,"folderPath":"/5/38","createdAt":"2023-10-09T09:43:22.911Z","updatedAt":"2023-10-09T09:43:22.911Z"}},"article_cats":[{"id":6,"name":"Community","createdAt":"2023-05-08T10:49:29.123Z","updatedAt":"2023-05-24T10:27:34.729Z","publishedAt":"2023-05-24T10:27:34.722Z"},{"id":2,"name":"Business","createdAt":"2023-04-06T21:12:53.820Z","updatedAt":"2023-05-24T10:27:38.039Z","publishedAt":"2023-05-24T10:27:38.029Z"}]}]},"link_button":{"id":36,"label":"EXPLORE CAREERS","href":"/careers","variant":"primary","size":"large","rounded":false,"icon":"mdi:arrow-right"}}},"meta":{}}}

Get in touch with Dusk