Subscribe to our daily newsletter to keep in touch with the subjects shaping our future.

DeepSeek Failed Every Single Security Test, Researchers Found

ISLAMABAD, Jan 28 (APP):Federal Minister for Finance and Revenue, Senator Muhammad Aurangzeb here Tuesday expressed the hope that the positive development in

Finance Minister hopes Single B sovereign rating

Space Banana SpaceX's latest test flight of its Starship spacecraft carried a highly unusual payload into orbit: a single banana. Footage showed the interior of the behemoth rocket being adorned with one, lonely piece of fruit. It also conveniently puts the size of the spacecraft to scale.

Starship Shoots Into Orbit With Single Banana in Cargo Hold

SpaceX's latest test flight of its Starship spacecraft carried a highly unusual payload into space in its massive hold: a single banana.

Starship Shoots Into Space With Single Banana in Cargo Hold

Quarterly revenues of $2.92 billion beat the street view of $2.90 billion. The company reported a loss per share of $6.59, including a non-cash goodwill impairment loss for the Wine and Spirits business of $2.25 billion. The Beer business achieved solid mid-single-digit net sales growth while ...

Constellation Brands Beats On Q2 Earnings, Beer Business Achieved Solid Mid-Single-Digit Sales Growth

Google spent $2.7 billion to rehire AI expert Noam Shazeer, as part of a software licensing deal with his AI startup Character.

Desperate Google Paid $2.7 Billion to Get a Single AI Researcher Back

Elon Musk has had a longstanding crush on Taylor Swift, with his tweet suggesting he could impregnate her the latest in a long string.

Elon Musk Has Been Making Sad Attempts to Woo Taylor Swift for Years, and She’s Never Responded a Single Time

Single

single

Table of Links Abstract and 1 Introduction Abstract and 1 Introduction 2 MindEye2 and 2.1 Shared-Subject Functional Alignment 2 MindEye2 and 2.1 Shared-Subject Functional Alignment 2.2 Backbone, Diffusion Prior, & Submodules 2.2 Backbone, Diffusion Prior, & Submodules 2.3 Image Captioning and 2.4 Fine-tuning Stable Diffusion XL for unCLIP 2.3 Image Captioning and 2.4 Fine-tuning Stable Diffusion XL for unCLIP 2.5 Model Inference 2.5 Model Inference 3 Results and 3.1 fMRI-to-Image Reconstruction 3 Results and 3.1 fMRI-to-Image Reconstruction 3.2 Image Captioning 3.2 Image Captioning 3.3 Image/Brain Retrieval and 3.4 Brain Correlation 3.3 Image/Brain Retrieval and 3.4 Brain Correlation 3.5 Ablations 3.5 Ablations 4 Related Work 4 Related Work 5 Conclusion 5 Conclusion 6 Acknowledgements and References 6 Acknowledgements and References A Appendix A Appendix A.1 Author Contributions A.1 Author Contributions A.2 Additional Dataset Information A.2 Additional Dataset Information A.3 MindEye2 (not pretrained) vs. MindEye1 A.3 MindEye2 (not pretrained) vs. MindEye1 A.4 Reconstruction Evaluations Across Varying Amounts of Training Data A.4 Reconstruction Evaluations Across Varying Amounts of Training Data A.5 Single-Subject Evaluations A.5 Single-Subject Evaluations A.6 UnCLIP Evaluation A.6 UnCLIP Evaluation A.7 OpenCLIP BigG to CLIP L Conversion A.7 OpenCLIP BigG to CLIP L Conversion A.8 COCO Retrieval A.8 COCO Retrieval A.9 Reconstruction Evaluations: Additional Information A.9 Reconstruction Evaluations: Additional Information A.10 Pretraining with Less Subjects A.10 Pretraining with Less Subjects A.11 UMAP Dimensionality Reduction A.11 UMAP Dimensionality Reduction A.12 ROI-Optimized Stimuli A.12 ROI-Optimized Stimuli A.13 Human Preference Experiments A.13 Human Preference Experiments A.5 Single-Subject Evaluations Tables 7 and 8 show more exhaustive evaluation metrics computed for every subject individually using 40-hours and 1-hour of fine-tuning data respectively. This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv Authors:
(1) Paul S. Scotti, Stability AI and Medical AI Research Center (MedARC);
(2) Mihir Tripathy, Medical AI Research Center (MedARC) and a Core contribution;
(3) Cesar Kadir Torrico Villanueva, Medical AI Research Center (MedARC) and a Core contribution;
(4) Reese Kneeland, University of Minnesota and a Core contribution;
(5) Tong Chen, The University of Sydney and Medical AI Research Center (MedARC);
(6) Ashutosh Narang, Medical AI Research Center (MedARC);
(7) Charan Santhirasegaran, Medical AI Research Center (MedARC);
(8) Jonathan Xu, University of Waterloo and Medical AI Research Center (MedARC);
(9) Thomas Naselaris, University of Minnesota;
(10) Kenneth A. Norman, Princeton Neuroscience Institute;
(11) Tanishq Mathew Abraham, Stability AI and Medical AI Research Center (MedARC). Authors: Authors: (1) Paul S. Scotti, Stability AI and Medical AI Research Center (MedARC); (2) Mihir Tripathy, Medical AI Research Center (MedARC) and a Core contribution; (3) Cesar Kadir Torrico Villanueva, Medical AI Research Center (MedARC) and a Core contribution; (4) Reese Kneeland, University of Minnesota and a Core contribution; (5) Tong Chen, The University of Sydney and Medical AI Research Center (MedARC); (6) Ashutosh Narang, Medical AI Research Center (MedARC); (7) Charan Santhirasegaran, Medical AI Research Center (MedARC); (8) Jonathan Xu, University of Waterloo and Medical AI Research Center (MedARC); (9) Thomas Naselaris, University of Minnesota; (10) Kenneth A. Norman, Princeton Neuroscience Institute; (11) Tanishq Mathew Abraham, Stability AI and Medical AI Research Center (MedARC).

MindEye2: Shared-Subject Models Enable fMRI-To-Image With 1 Hour of Data: Single-Subject Evaluations

Build Your Own BEP-20 Token in a Single Afternoon—No Prior Experience Needed

Table of Links Abstract and 1. Introduction Abstract and 1. Introduction 2 Methodology 2 Methodology 3 Hardware 3 Hardware 4 Software 4 Software 5 Network 5 Network 6 Consensus 6 Consensus 7 Cryptocurrency Economics 7 Cryptocurrency Economics 8 Client API 8 Client API 9 Governance 9 Governance 10 Geography 10 Geography 11 Case Studies 11 Case Studies 12 Discussion and References 12 Discussion and References A. Decentralization and Policymaking A. Decentralization and Policymaking B. Software Testing B. Software Testing C. Brief Evaluations per Layer C. Brief Evaluations per Layer D. Measuring decentralization D. Measuring decentralization E. Fault Tolerance and Decentralization E. Fault Tolerance and Decentralization 4 Software Software development is another dimension of distributed ledgers that has been associated with potential centralization [44,147,11]. Diverse software development and usage is a core element of stability and safety of distributed ledgers, as it increases resilience to catastrophic bugs in a product’s code. A vulnerability in one implementation may jeopardize a part of the system, but if the system is sufficiently decentralized, such vulnerabilities would not escalate to systemic threats. Following, we discuss the development of core blockchain software components, namely transaction validation and PoW mining (via full nodes) and management of keys and digital assets (via wallets).[7] Protocol Participation. The principal type of software in blockchain systems is the full node. Full nodes implement the ledger protocol by: i) keeping a local chain; ii) validating new transactions; iii) extending the local chain with new blocks; iv) participating in the consensus mechanism to incorporate new blocks. To analyze decentralization, we identify two resources of interest: 1) (number of) full nodes; 2) participating power (e.g., computational or stake) that is hosted on full nodes. The relevant parties are: 1) full node software implementations; 2) full node software developers. Protocol Participation. Protocol Participation. Relying on a handful of full node implementations introduces safety, liveness, and stability hazards. A bug that fails to validate correct transactions would hurt the system’s liveness, whereas accepting incorrect transactions could hurt the system’s safety and stability, e.g., via a network split or token forgery. Such bugs have been observed in Bitcoin Core and could have resulted in Denial-of-Service (DoS) attacks [75] and token forgery [48]. Implementation bugs could also threaten privacy, if nodes reveal information about message origin (e.g., IP addresses). Similar threats arise when code gets reused across different projects. Often, a new blockchain is only a “derivative”, that is a project that started by forking an existing codebase, including copyrighted information [147]. Such projects often remain unpatched, so bugs in the initial implementation tend to spill over [44]. Vulnerabilities may also arise when adapting an existing implementation in a new setting, e.g., copying Bitcoin’s code and replacing PoW with PoS [96]. Thus, widespread usage of multiple node implementations, developed by different teams, is a hallmark of a secure and reliant ecosystem. Asset Management. Distributed ledgers are mostly used for bookkeeping of digital asset transactions, so securely managing and transferring assets is a core necessity. Digital assets are typically managed by private keys and represented via addresses. The software responsible for managing keys and addresses is the wallet [100] and its principal functionalities are: i) store the user’s keys; ii) prove ownership of the assets (managed by the keys); iii) issue transactions that transfer assets to other accounts; iv) retrieve the user’s (keys’) balance and history information. Therefore, the resource of interest is the set of all assets managed via the ledger and the relevant parties are, accordingly: i) wallet implementations; ii) developers of wallet software. Asset Management. Asset Management. The wallet is a major point of security consideration, so multiple properties rely on it. A bug which e.g., corrupts the user’s keys could not only prohibit a user from transacting with their assets (liveness hazard), but forever lose access to them (stability hazard). This was demonstrated in 2017, when the “Parity” Ethereum wallet saw a vulnerability that allowed a user to take ownership of multiple assets and then lock them [89]; as a result, 300m worth of Ethereum tokens were forever lost. In another example, some Bitcoin wallets possibly displayed incorrect balance, effectively enabling a double spending attack [116]. Consequently, if a few implementations are predominantly used, a vulnerability could result in assets being unusable or stolen. Such vulnerability could also turn into a systemic point of failure, with the whole ledger becoming unusable.[8] Authors:
(1) Christina Ovezik, University of Edinburgh (c.ovezik@ed.ac.uk);
(2) Dimitris Karakostas, University of Edinburgh (dkarakos@ed.ac.uk);
(3) Aggelos Kiayias, University of Edinburgh and IOG (akiayias@ed.ac.uk). Authors: Authors: (1) Christina Ovezik, University of Edinburgh (c.ovezik@ed.ac.uk); (2) Dimitris Karakostas, University of Edinburgh (dkarakos@ed.ac.uk); (3) Aggelos Kiayias, University of Edinburgh and IOG (akiayias@ed.ac.uk). This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv available on arxiv [7] Appendix B also explores software testing. [8] A prime such example was “The DAO”, which in 2016 attracted nearly 14% of all Ethereum tokens and, when hacked, instigated a change in Ethereum’s consensus layer and a hard fork which split the network [169].

Blockchain’s Single Point of Failure? The Software Running It

I remember reading some years ago an L1’s proposal to migrate to an L2. That's where I came across the term decentralized sequencers. At the time, it seemed like an interesting but somewhat distant concept—an optimization rather than a necessity. But today, as rollups solidify their role as the dominant scaling solution for Ethereum and beyond, the importance of decentralized sequencers has grown considerably. decentralized sequencers For all the innovation that rollups bring, they still carry a significant centralization risk: most of them rely on a single, privileged sequencer. While this approach helps improve transaction speed and cost efficiency, it reintroduces some of the trust assumptions that blockchains were designed to eliminate. The debate around decentralized sequencers is not just about removing centralization for the sake of ideology; it’s about solving real bottlenecks in performance, censorship resistance, and fair transaction ordering. In this deep dive, we'll explore why sequencers matter, how decentralized sequencer networks work, the emerging designs in this space, and what challenges remain before they see widespread adoption. What is a sequencer and why does it matter? What is a sequencer and why does it matter? Sequencers play a critical role in rollup architectures. In simple terms, a sequencer is responsible for: Ordering transactions before they are posted on L1.


Providing rapid confirmations to users, even before final settlement on Ethereum.


Mitigating MEV (Maximal Extractable Value) by controlling how transactions are arranged. Ordering transactions before they are posted on L1. Ordering transactions before they are posted on L1. Providing rapid confirmations to users, even before final settlement on Ethereum. Providing rapid confirmations to users, even before final settlement on Ethereum. Mitigating MEV (Maximal Extractable Value) by controlling how transactions are arranged. Mitigating MEV (Maximal Extractable Value) by controlling how transactions are arranged. Without sequencers, rollups would function much like L1 blockchains—transactions would have to wait for finalization before they can be considered confirmed, resulting in slower user experiences. A sequencer brings the benefit of near-instant finality, making rollups feel as fast as traditional Web2 applications. Okay, but why do we need decentralized sequencers? Well, decentralized sequencers implies the opposite exists too. What's interesting is that centralized sequencers are more scalable and even faster. But its a double edged sword, its advantages in terms of scaling, comes with significant risk. Censorship – A centralized sequencer can choose which transactions to include or exclude, leading to concerns about neutrality, fair access and defeats the purpose of decentralized technology.
Single point of failure – If the sequencer goes offline, transactions cannot be processed until it comes back. While some rollups have fallback mechanisms, they are inefficient and not ideal for mainstream adoption. Censorship – A centralized sequencer can choose which transactions to include or exclude, leading to concerns about neutrality, fair access and defeats the purpose of decentralized technology. Single point of failure – If the sequencer goes offline, transactions cannot be processed until it comes back. While some rollups have fallback mechanisms, they are inefficient and not ideal for mainstream adoption. This might also seem like an unlikely scenario but it has in fact happened before. Arbitrum’s sequencer once stalled, making the network unusable for over an hour. MEV exploitation – A centralized sequencer can extract value from users through unfair transaction ordering, front-running, or sandwich attacks. MEV exploitation – A centralized sequencer can extract value from users through unfair transaction ordering, front-running, or sandwich attacks. These risks make it pertinent that L2s move towards a decentralized sequencer architecture.While a number of chains are still using centralized sequencers like Arbitrum one, optimism and base, we have seen new players like Morph adopting the decentralized sequencer model. How do decentralized sequencers work? A decentralized sequencer network, distributes the sequencing function across multiple entities, removing the reliance on a single entity. Its essentially the opposite of centralized sequencers. Its more time consuming and more expensive (in comparison with centralized sequencers) but for what it lacks, it makes up for it with: Censorship resistance – No single entity can exclude transactions.
High availability – Even if one sequencer node goes down, others can take over. This eliminates the risk of network downtime.
Fair transaction ordering – Preventing MEV abuse and ensuring a level playing field. Censorship resistance – No single entity can exclude transactions. High availability – Even if one sequencer node goes down, others can take over. This eliminates the risk of network downtime. Fair transaction ordering – Preventing MEV abuse and ensuring a level playing field. Shared Sequencing In the shared sequencing approach, multiple sequencers collaborate to process transactions in a shared mempool. The sequencers collectively determine the order of transactions and propose blocks to the L1 chain based on a consensus mechanism. Advantages: Ensures consistent transaction ordering across all sequencers
Reduces the risk of MEV exploitation through a fair ordering mechanism
Enables seamless failover in case of individual sequencer failures\ Ensures consistent transaction ordering across all sequencers Reduces the risk of MEV exploitation through a fair ordering mechanism Enables seamless failover in case of individual sequencer failures\ Challenges: Requires a robust consensus mechanism to ensure fair participation and prevent attacks
Potential for lower throughput compared to centralized sequencing due to the coordination overhead
Increased communication complexity among sequencers Requires a robust consensus mechanism to ensure fair participation and prevent attacks Potential for lower throughput compared to centralized sequencing due to the coordination overhead Increased communication complexity among sequencers Example: The Morph rollup uses a shared sequencing model based on a proof-of-stake consensus among sequencers. Example The Future of Decentralized Sequencing As the Ethereum ecosystem continues to scale and mature, the need for decentralized sequencing solutions will only grow. While the current approaches offer significant improvements over centralized sequencers, there is still room for innovation and optimization. One area of active research is the development of hybrid sequencing models that combine the benefits of different approaches. For example, a system could use shared sequencing for high-value transactions that require strong censorship resistance, while employing a more centralized approach for low-value transactions to maximize throughput. Another promising direction is the integration of privacy-preserving technologies like zero-knowledge proofs into decentralized sequencers. This could enable users to submit transactions without revealing their identities or transaction details to the sequencers, further enhancing the censorship resistance and neutrality of the system. As the technology evolves, we can expect to see more rollups and L2 solutions adopting decentralized sequencing architectures. This will not only improve the security and fairness of these systems but also bring us closer to the vision of a fully decentralized and scalable blockchain ecosystem. Conclusion Decentralized sequencers are a critical component of the Ethereum scaling puzzle. By removing the reliance on a single, privileged entity, they mitigate the risks of censorship, single points of failure, and MEV exploitation. While the current approaches have their tradeoffs and challenges, they represent a significant step towards a more resilient and trustless blockchain infrastructure. As the space continues to innovate and mature, we can expect to see more advanced and efficient decentralized sequencing solutions emerge. These developments will not only benefit Ethereum but also have far-reaching implications for the broader blockchain ecosystem, enabling new use cases and unlocking the full potential of decentralized technologies.

Rollups Are the Future—But Their Biggest Bottleneck Might Be a Single Point of Failure

A Single Point of Access or Chaos — Unlocking Non-Blocking API Gateways

How to Troubleshoot 'hostpolicy.dll' and 'singlefilehost.exe' Errors in .NET 8.0.11

Kunjamas ‘hostpolicy.dll’ ukat ‘singlefilehost.exe’ pantjasiwinak askichañax .NET 8.0.11

Com solucionar els errors "hostpolicy.dll" i "singlefilehost.exe" a .NET 8.0.11

Jak odstraňovat chyby 'hostpolicy.dll' a 'singlefilehost.exe' v .NET 8.0.11

Τρόπος αντιμετώπισης σφαλμάτων "hostpolicy.dll" και "singlefilehost.exe" στο .NET 8.0.11

Cómo solucionar los errores 'hostpolicy.dll' y 'singlefilehost.exe' en .NET 8.0.11

نحوه عیب‌یابی خطاهای «hostpolicy.dll» و «singlefilehost.exe» در NET 8.0.11

Kako otkloniti pogreške 'hostpolicy.dll' i 'singlefilehost.exe' u .NET 8.0.11

.NET 8.0.11 での「hostpolicy.dll」および「singlefilehost.exe」エラーのトラブルシューティング方法

.NET 8.0.11 හි 'hostpolicy.dll' සහ 'singlefilehost.exe' දෝෂ නිරාකරණය කරන්නේ කෙසේද?

Maitiro eku Troubleshoot 'hostpolicy.dll' uye 'singlefilehost.exe' Zvakanganisa mu.NET 8.0.11

Чӣ гуна хатогиҳои "hostpolicy.dll" ва "singlefilehost.exe" -ро дар .NET 8.0.11 бартараф кардан мумкин аст

วิธีการแก้ไขปัญหาข้อผิดพลาด 'hostpolicy.dll' และ 'singlefilehost.exe' ใน .NET 8.0.11

Table of Links Abstract and 1 Introduction 2. Related Works 2.1. 2D Diffusion Models for 3D Generation 2.2. 3D Generative Models and 2.3. Multi-view Diffusion Models 3. Problem Formulation 3.1. Diffusion Models 3.2. The Distribution of 3D Assets 4. Method and 4.1. Consistent Multi-view Generation 4.2. Cross-Domain Diffusion 4.3. Textured Mesh Extraction 5. Experiments 5.1. Implementation Details 5.2. Baselines 5.3. Evaluation Protocol 5.4. Single View Reconstruction 5.5. Novel View Synthesis and 5.6. Discussions 6. Conclusions and Future Works, Acknowledgements and References Abstract In this work, we introduce Wonder3D, a novel method for efficiently generating high-fidelity textured meshes from single-view images. Recent methods based on Score Distillation Sampling (SDS) have shown the potential to recover 3D geometry from 2D diffusion priors, but they typically suffer from time-consuming per-shape optimization and inconsistent geometry. In contrast, certain works directly produce 3D information via fast network inferences, but their results are often of low quality and lack geometric details. To holistically improve the quality, consistency, and efficiency of single-view reconstruction tasks, we propose a cross-domain diffusion model that generates multiview normal maps and the corresponding color images. To ensure the consistency of generation, we employ a multiview cross-domain attention mechanism that facilitates information exchange across views and modalities. Lastly, we introduce a geometry-aware normal fusion algorithm that extracts high-quality surfaces from the multi-view 2D representations. Our extensive evaluations demonstrate that our method achieves high-quality reconstruction results, robust generalization, and good efficiency compared to prior works Introduction Reconstructing 3D geometry from a single image stands as a fundamental task in computer graphics and 3D computer vision [12, 25, 31, 33, 35, 38, 41, 44], offering a wide range of versatile applications such as virtual reality, video games, 3D content creation, and the precision of robotics grasping. However, this task is notably challenging since it is ill-posed and demands the ability to discern the 3D geometry of both visible and invisible parts. This ability requires extensive knowledge of the 3D world. knowledge of the 3D world. Recently, the field of 3D generation has experienced rapid and flourishing development with the introduction of diffusion models. A growing body of research [5, 29, 43, 59, 63], such as DreamField [24], DreamFusion [43], and Magic3D [29], resort to distilling prior knowledge of 2D image diffusion models or vision language models to create 3D models from text or images via Score Distillation Sampling (SDS) [43]. Despite their compelling results, these methods suffer from two main limitations: efficiency and consistency. The per-shape optimization process typically entails tens of thousands of iterations, involving full-image volume rendering and inferences of the diffusion models. Consequently, it often consumes tens of minutes or even hours on per-shape optimization. Moreover, the 2D prior model operates by considering only a single view at each iteration and strives to make every view resemble the input image. This often results in the generation of 3D shapes exhibiting inconsistencies, thus, often leading to the generation of 3D shapes with inconsistencies such as multiple faces (i.e., the Janus problem [43]). There exists another group of works that endeavor to directly produce 3D geometries like point clouds [37, 41, 71, 75], meshes [16, 34], neural fields [1, 4, 7, 14, 17, 21, 25– 27, 40, 42, 61, 72] via network inference to avoid timeconsuming per-shape optimization. Most of them attempt to train 3D generative diffusion models from scratch on 3D assets. However, due to the limited size of publicly available 3D datasets, these methods demonstrate poor generalizability, most of which can only generate shapes on specific categories. More recently, several methods have emerged that directly generate multi-view 2D images, with representative works including SyncDreamer [33] and MVDream [51]. By enhancing the multi-view consistency of image generation, these methods can recover 3D shapes from the generated multi-view images. Following these works, our method also adopts a multi-view generation scheme to favor the flexibility and efficiency of 2D representations. However, due to only relying on color images, the fidelity of the generated shapes is not well-maintained, and they struggle to recover geometric details or come with enormous computational costs. To better address the issues of fidelity, consistency, generalizability and efficiency in the aforementioned works, in this paper, we introduce a new approach to the task of single-view 3D reconstruction by generating multi-view consistent normal maps and their corresponding color images with a cross-domain diffusion model. The key idea is to extend the stable diffusion framework to model the joint distribution of two different domains, i.e., normals and colors. We demonstrate that this can be achieved by introducing a domain switcher and a cross-domain attention scheme. In particular, the domain switcher allows the diffusion model to generate either normal maps or color images, while the cross-domain attention mechanisms assist in the information exchange between the two domains, ultimately improving consistency and quality. Finally, in order to stably extract surfaces from the generated views, we propose a geometry-aware normal fusion algorithm that is robust to the inaccuracies and capable of reconstructing clean and high-quality geometries (see Figure 1). We conduct extensive experiments on the Google Scanned Object dataset [13] and various 2D images with different styles. The experiments validate that Wonder3D is capable of producing high-quality geometry with high efficiency in comparison with baseline methods. Wonder3D possesses several distinctive properties and accordingly has the following contributions: • Wonder3D holistically considers the issues of generation quality, efficiency, generalizability, and consistency for 2 single-view 3D reconstruction. It has achieved a leading level of geometric details with reasonably good efficiency among current zero-shot single-view reconstruction methods. • We propose a new multi-view cross-domain 2D diffusion model to predict normal maps and color images. This representation not only adapts to the original data distribution of Stable Diffusion model but also effectively captures the rich surface details of the target shape. • We propose a cross-domain attention mechanism to produce multi-view normal maps and color images that are consistently aligned. This mechanism facilitates information perception across different domains, enabling our method to recover high-fidelity geometry. • We introduce a novel geometry-aware normal fusion algorithm that can robustly extract surfaces from the generated normal maps and color images. This paper is available on arxiv under CC BY-NC-ND 4.0 DEED license. Authors:
(1) Xiaoxiao Long, The University of Hong Kong, VAST, MPI Informatik and Equal Contributions;
(2) Yuan-Chen Guo, Tsinghua University, VAST and Equal Contributions.
(3) Cheng Lin, The University of Hong Kong with Corresponding authors;
(4) Yuan Liu, The University of Hong Kong;
(5) Zhiyang Dou, The University of Hong Kong;
(6) Lingjie Liu, University of Pennsylvania;
(7) Yuexin Ma, Shanghai Tech University;
(8) Song-Hai Zhang, The University of Hong Kong;
(9) Marc Habermann, MPI Informatik;
(10) Christian Theobalt, MPI Informatik;
(11) Wenping Wang, Texas A&M University with Corresponding authors. Table of Links Abstract and 1 Introduction Abstract and 1 Introduction 2. Related Works 2.1. 2D Diffusion Models for 3D Generation 2.1. 2D Diffusion Models for 3D Generation 2.2. 3D Generative Models and 2.3. Multi-view Diffusion Models 2.2. 3D Generative Models and 2.3. Multi-view Diffusion Models 3. Problem Formulation 3.1. Diffusion Models 3.1. Diffusion Models 3.2. The Distribution of 3D Assets 3.2. The Distribution of 3D Assets 4. Method and 4.1. Consistent Multi-view Generation 4. Method and 4.1. Consistent Multi-view Generation 4.2. Cross-Domain Diffusion 4.2. Cross-Domain Diffusion 4.3. Textured Mesh Extraction 4.3. Textured Mesh Extraction 5. Experiments 5.1. Implementation Details 5.1. Implementation Details 5.2. Baselines 5.2. Baselines 5.3. Evaluation Protocol 5.3. Evaluation Protocol 5.4. Single View Reconstruction 5.4. Single View Reconstruction 5.5. Novel View Synthesis and 5.6. Discussions 5.5. Novel View Synthesis and 5.6. Discussions 6. Conclusions and Future Works, Acknowledgements and References 6. Conclusions and Future Works, Acknowledgements and References Abstract In this work, we introduce Wonder3D , a novel method for efficiently generating high-fidelity textured meshes from single-view images. Recent methods based on Score Distillation Sampling (SDS) have shown the potential to recover 3D geometry from 2D diffusion priors, but they typically suffer from time-consuming per-shape optimization and inconsistent geometry. In contrast, certain works directly produce 3D information via fast network inferences, but their results are often of low quality and lack geometric details. Wonder3D To holistically improve the quality, consistency, and efficiency of single-view reconstruction tasks, we propose a cross-domain diffusion model that generates multiview normal maps and the corresponding color images. To ensure the consistency of generation, we employ a multiview cross-domain attention mechanism that facilitates information exchange across views and modalities. Lastly, we introduce a geometry-aware normal fusion algorithm that extracts high-quality surfaces from the multi-view 2D representations. Our extensive evaluations demonstrate that our method achieves high-quality reconstruction results, robust generalization, and good efficiency compared to prior works Introduction Reconstructing 3D geometry from a single image stands as a fundamental task in computer graphics and 3D computer vision [12, 25, 31, 33, 35, 38, 41, 44], offering a wide range of versatile applications such as virtual reality, video games, 3D content creation, and the precision of robotics grasping. However, this task is notably challenging since it is ill-posed and demands the ability to discern the 3D geometry of both visible and invisible parts. This ability requires extensive knowledge of the 3D world. knowledge of the 3D world. Recently, the field of 3D generation has experienced rapid and flourishing development with the introduction of diffusion models. A growing body of research [5, 29, 43, 59, 63], such as DreamField [24], DreamFusion [43], and Magic3D [29], resort to distilling prior knowledge of 2D image diffusion models or vision language models to create 3D models from text or images via Score Distillation Sampling (SDS) [43]. Despite their compelling results, these methods suffer from two main limitations: efficiency and consistency. The per-shape optimization process typically entails tens of thousands of iterations, involving full-image volume rendering and inferences of the diffusion models. Consequently, it often consumes tens of minutes or even hours on per-shape optimization. Moreover, the 2D prior model operates by considering only a single view at each iteration and strives to make every view resemble the input image. This often results in the generation of 3D shapes exhibiting inconsistencies, thus, often leading to the generation of 3D shapes with inconsistencies such as multiple faces (i.e., the Janus problem [43]). There exists another group of works that endeavor to directly produce 3D geometries like point clouds [37, 41, 71, 75], meshes [16, 34], neural fields [1, 4, 7, 14, 17, 21, 25– 27, 40, 42, 61, 72] via network inference to avoid timeconsuming per-shape optimization. Most of them attempt to train 3D generative diffusion models from scratch on 3D assets. However, due to the limited size of publicly available 3D datasets, these methods demonstrate poor generalizability, most of which can only generate shapes on specific categories. More recently, several methods have emerged that directly generate multi-view 2D images, with representative works including SyncDreamer [33] and MVDream [51]. By enhancing the multi-view consistency of image generation, these methods can recover 3D shapes from the generated multi-view images. Following these works, our method also adopts a multi-view generation scheme to favor the flexibility and efficiency of 2D representations. However, due to only relying on color images, the fidelity of the generated shapes is not well-maintained, and they struggle to recover geometric details or come with enormous computational costs. To better address the issues of fidelity, consistency, generalizability and efficiency in the aforementioned works, in this paper, we introduce a new approach to the task of single-view 3D reconstruction by generating multi-view consistent normal maps and their corresponding color images with a cross-domain diffusion model. The key idea is to extend the stable diffusion framework to model the joint distribution of two different domains, i.e., normals and colors. We demonstrate that this can be achieved by introducing a domain switcher and a cross-domain attention scheme. In particular, the domain switcher allows the diffusion model to generate either normal maps or color images, while the cross-domain attention mechanisms assist in the information exchange between the two domains, ultimately improving consistency and quality. Finally, in order to stably extract surfaces from the generated views, we propose a geometry-aware normal fusion algorithm that is robust to the inaccuracies and capable of reconstructing clean and high-quality geometries (see Figure 1). We conduct extensive experiments on the Google Scanned Object dataset [13] and various 2D images with different styles. The experiments validate that Wonder3D is capable of producing high-quality geometry with high efficiency in comparison with baseline methods. Wonder3D possesses several distinctive properties and accordingly has the following contributions: • Wonder3D holistically considers the issues of generation quality, efficiency, generalizability, and consistency for 2 single-view 3D reconstruction. It has achieved a leading level of geometric details with reasonably good efficiency among current zero-shot single-view reconstruction methods. • We propose a new multi-view cross-domain 2D diffusion model to predict normal maps and color images. This representation not only adapts to the original data distribution of Stable Diffusion model but also effectively captures the rich surface details of the target shape. • We propose a cross-domain attention mechanism to produce multi-view normal maps and color images that are consistently aligned. This mechanism facilitates information perception across different domains, enabling our method to recover high-fidelity geometry. • We introduce a novel geometry-aware normal fusion algorithm that can robustly extract surfaces from the generated normal maps and color images. This paper is available on arxiv under CC BY-NC-ND 4.0 DEED license. This paper is available on arxiv under CC BY-NC-ND 4.0 DEED license. available on arxiv Authors: (1) Xiaoxiao Long, The University of Hong Kong, VAST, MPI Informatik and Equal Contributions; (2) Yuan-Chen Guo, Tsinghua University, VAST and Equal Contributions. (3) Cheng Lin, The University of Hong Kong with Corresponding authors; (4) Yuan Liu, The University of Hong Kong; (5) Zhiyang Dou, The University of Hong Kong; (6) Lingjie Liu, University of Pennsylvania; (7) Yuexin Ma, Shanghai Tech University; (8) Song-Hai Zhang, The University of Hong Kong; (9) Marc Habermann, MPI Informatik; (10) Christian Theobalt, MPI Informatik; (11) Wenping Wang, Texas A&M University with Corresponding authors. Authors: Authors: (1) Xiaoxiao Long, The University of Hong Kong, VAST, MPI Informatik and Equal Contributions; (2) Yuan-Chen Guo, Tsinghua University, VAST and Equal Contributions. (3) Cheng Lin, The University of Hong Kong with Corresponding authors; (4) Yuan Liu, The University of Hong Kong; (5) Zhiyang Dou, The University of Hong Kong; (6) Lingjie Liu, University of Pennsylvania; (7) Yuexin Ma, Shanghai Tech University; (8) Song-Hai Zhang, The University of Hong Kong; (9) Marc Habermann, MPI Informatik; (10) Christian Theobalt, MPI Informatik; (11) Wenping Wang, Texas A&M University with Corresponding authors.

What Is Wonder3D? A Method for Generating High-Fidelity Textured Meshes From Single-View Images

Authors:
(1) Hanoona Rasheed, Mohamed bin Zayed University of AI and equally contributing first authors;
(2) Muhammad Maaz, Mohamed bin Zayed University of AI and equally contributing first authors;
(3) Sahal Shaji, Mohamed bin Zayed University of AI;
(4) Abdelrahman Shaker, Mohamed bin Zayed University of AI;
(5) Salman Khan, Mohamed bin Zayed University of AI and Australian National University;
(6) Hisham Cholakkal, Mohamed bin Zayed University of AI;
(7) Rao M. Anwer, Mohamed bin Zayed University of AI and Aalto University;
(8) Eric Xing, Mohamed bin Zayed University of AI and Carnegie Mellon University;
(9) Ming-Hsuan Yang, University of California - Merced and Google Research;
(10) Fahad S. Khan, Mohamed bin Zayed University of AI and Linköping University. Editor's Note: This is Part 9 of 10 of a study detailing the development of an AI model that is designed to describe images to users. Read the rest below. Table of Links Abstract and 1 Introduction
2. Related Work
3. Method
4. Data Annotation Pipeline
5. Experiments
6. Conclusion and References Supplementary Material (Part 1) A. Additional Implementation Details
B. Additional Downstream Tasks
C. Additional Qualitative Results Supplementary Material (Part 2) D. Dataset Visualization
E. Limitations and Future Work
F. Ethics and Societal Impact C. Additional Qualitative Results In this section, we provide more qualitative examples to better understand the capacity of GLaMM. C.1. Grounded Conversation Generation (GCG) Fig. 7 shows qualitative results of GLaMM finetuned on GranDf dataset. The model could produce dense captions and provide dense pixel-level groundings of the caption. C.2. Referring Segmentation Fig. 8 shows the effectiveness of GLaMM in understanding the natural language query and segmenting the corresponding objects. Note that GLaMM can also segment multiple objects via multi-round conversations. C.3. Region-level Captioning Fig. 9 shows the qualitative results of GLaMM for regionlevel understanding. Our model can generate detailed descriptions about the user-specified regions in an image. C.4. Image-level Captioning Fig. 10 shows GLaMM’s qualitative results on captioning tasks. Our model can generate dense captions for images. C.5. Conditional Image Generation Fig. 12 shows GLaMM’s seamless integration for generative tasks. We use the Stable Diffusion inpainting model stable-diffusion-xl-1.0-inpainting [41] for this task. We first generate a segmentation mask using our GlaMM model based on the user query. This segmentation mask along with the user prompt is given as the input to the Stable Diffusion inpainting model, which generates the final output. Figure 14. Dataset samples from GranDf. The figure shows the GPT4 [34] prompts used and the created dataset samples from Grandf dataset. This repurposed human-annotated dataset provides rich semantics to GLaMM for GCG task. C.6. Conversations Fig. 13 illustrates the unique functionality of GLaMM to engage in multi-purpose task conversations. GLaMM is a generic conversational model that can accept prompts in the form of text and/or region and can answer in the form of text and/or segmentation masks. Note that our model is not explicitly trained to handle such scenarios, and this behavior emerges mainly due to our pretraining on GranD dataset, where an image is presented to LMM in different contexts. This paper is available on arxiv under CC BY 4.0 DEED license. Authors: (1) Hanoona Rasheed, Mohamed bin Zayed University of AI and equally contributing first authors; (2) Muhammad Maaz, Mohamed bin Zayed University of AI and equally contributing first authors; (3) Sahal Shaji, Mohamed bin Zayed University of AI; (4) Abdelrahman Shaker, Mohamed bin Zayed University of AI; (5) Salman Khan, Mohamed bin Zayed University of AI and Australian National University; (6) Hisham Cholakkal, Mohamed bin Zayed University of AI; (7) Rao M. Anwer, Mohamed bin Zayed University of AI and Aalto University; (8) Eric Xing, Mohamed bin Zayed University of AI and Carnegie Mellon University; (9) Ming-Hsuan Yang, University of California - Merced and Google Research; (10) Fahad S. Khan, Mohamed bin Zayed University of AI and Linköping University. Authors: Authors: (1) Hanoona Rasheed, Mohamed bin Zayed University of AI and equally contributing first authors; (2) Muhammad Maaz, Mohamed bin Zayed University of AI and equally contributing first authors; (3) Sahal Shaji, Mohamed bin Zayed University of AI; (4) Abdelrahman Shaker, Mohamed bin Zayed University of AI; (5) Salman Khan, Mohamed bin Zayed University of AI and Australian National University; (6) Hisham Cholakkal, Mohamed bin Zayed University of AI; (7) Rao M. Anwer, Mohamed bin Zayed University of AI and Aalto University; (8) Eric Xing, Mohamed bin Zayed University of AI and Carnegie Mellon University; (9) Ming-Hsuan Yang, University of California - Merced and Google Research; (10) Fahad S. Khan, Mohamed bin Zayed University of AI and Linköping University. Editor's Note: This is Part 9 of 10 of a study detailing the development of an AI model that is designed to describe images to users. Read the rest below. Editor's Note: This is Part 9 of 10 of a study detailing the development of an AI model that is designed to describe images to users. Read the rest below. Editor's Note: This is Part 9 of 10 of a study detailing the development of an AI model that is designed to describe images to users. Read the rest below. Editor's Note: This is Part 9 of 10 of a study detailing the development of an AI model that is designed to describe images to users. Read the rest below. Table of Links Abstract and 1 Introduction 2. Related Work 3. Method 4. Data Annotation Pipeline 5. Experiments 6. Conclusion and References Abstract and 1 Introduction Abstract and 1 Introduction 2. Related Work 2. Related Work 3. Method 3. Method 4. Data Annotation Pipeline 4. Data Annotation Pipeline 5. Experiments 5. Experiments 6. Conclusion and References 6. Conclusion and References Supplementary Material (Part 1) Supplementary Material (Part 1) A. Additional Implementation Details B. Additional Downstream Tasks C. Additional Qualitative Results A. Additional Implementation Details A. Additional Implementation Details B. Additional Downstream Tasks B. Additional Downstream Tasks C. Additional Qualitative Results C. Additional Qualitative Results Supplementary Material (Part 2) Supplementary Material (Part 2) D. Dataset Visualization E. Limitations and Future Work F. Ethics and Societal Impact D. Dataset Visualization D. Dataset Visualization E. Limitations and Future Work E. Limitations and Future Work F. Ethics and Societal Impact F. Ethics and Societal Impact C. Additional Qualitative Results In this section, we provide more qualitative examples to better understand the capacity of GLaMM. C.1. Grounded Conversation Generation (GCG) Fig. 7 shows qualitative results of GLaMM finetuned on GranD f dataset. The model could produce dense captions and provide dense pixel-level groundings of the caption. f C.2. Referring Segmentation Fig. 8 shows the effectiveness of GLaMM in understanding the natural language query and segmenting the corresponding objects. Note that GLaMM can also segment multiple objects via multi-round conversations. C.3. Region-level Captioning Fig. 9 shows the qualitative results of GLaMM for regionlevel understanding. Our model can generate detailed descriptions about the user-specified regions in an image. C.4. Image-level Captioning Fig. 10 shows GLaMM’s qualitative results on captioning tasks. Our model can generate dense captions for images. C.5. Conditional Image Generation Fig. 12 shows GLaMM’s seamless integration for generative tasks. We use the Stable Diffusion inpainting model stable-diffusion-xl-1.0-inpainting [41] for this task. We first generate a segmentation mask using our GlaMM model based on the user query. This segmentation mask along with the user prompt is given as the input to the Stable Diffusion inpainting model, which generates the final output. Figure 14. Dataset samples from GranDf. The figure shows the GPT4 [34] prompts used and the created dataset samples from Grandf dataset. This repurposed human-annotated dataset provides rich semantics to GLaMM for GCG task. Dataset samples from GranD f . f C.6. Conversations Fig. 13 illustrates the unique functionality of GLaMM to engage in multi-purpose task conversations. GLaMM is a generic conversational model that can accept prompts in the form of text and/or region and can answer in the form of text and/or segmentation masks. Note that our model is not explicitly trained to handle such scenarios, and this behavior emerges mainly due to our pretraining on GranD dataset, where an image is presented to LMM in different contexts. This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv

This New AI Can See, Talk, and Even Edit Images in a Single Conversation

This article outlines how to transition from singletons to dependency injection in a SwiftUI app with minimal effort. If you're here, you likely already know that you should avoid singletons with various of reasons like: Hidden Dependencies: Classes rely on singletons without explicit indicators, making it harder to track app dependencies and leading to unintended coupling.
Circular Dependencies: Singletons depending on each other can create cycles, leading to initialization deadlocks as instances wait for each other.
Testing Challenges: Using singletons complicates testing and SwiftUI previews since singletons can't easily be swapped for mocks. Lack of Flexibility: Singletons make it difficult to provide different implementations for different environments (e.g., live vs. mock versions for testing). And many others. Dependency Injection To overcome most issues we can use Dependency injection (DI). Using it, swapping in a new implementation becomes much easier, as components don’t rely on a single shared instance but on protocols that can be implemented in different ways. This promotes flexibility, easier testing, and adaptability as app requirements evolve. Constructor Injection Constructor injection is a straightforward technique for injecting dependencies by passing them through initializers. While effective, it often increases the size and complexity of initializers. A common challenge with constructor injection is passing dependencies through a deep UI hierarchy. If a dependency is only needed on a specific screen but must be passed down through multiple intermediary screens, this can quickly become cumbersome. One way to handle this is by using the Coordinator pattern, which centralizes navigation and manages dependencies more efficiently. Check out this article to learn how to make it. Why Not Use @EnvironmentObject? While @EnvironmentObject simplifies dependency sharing in SwiftUI, it has limitations: It only works with ObservableObject
It doesn’t allow using protocols for implementation switching.
It only works in SwiftUI views hierarchy
It only checks for service existence when accessed, increasing the risk of unintentional omissions in views. Dependency injection with property wrappers This is similar to the @EnvironmentObject solution where the dependency management happens inside of property wrappers, but without drawbacks. DependencyContainer This small library contains only a couple files, can be copied directly into your project or integrated via SPM. Please, make sure you put a star on it if you like it. Here is the link on GitHub. Let’s create an example of the service we need to pass as a dependency. As we are assuming that we are going to make a mock for testing, we need to implement our service as a protocol. Also we make it as ObservableObject, to review additional features of the framework. import Combine

protocol DataRepository: Actor, ObservableObject {
    
    func fetchData() async throws
}

actor DataRepositoryImp: DataRepository {
    
    func fetchData() async throws {
        // do real stuff
    }
}

actor DataRepositoryMock: DataRepository {
    
    func fetchData() async throws {
        // do mocked stuff
    }
} Defining a DI container Once integrated, you’ll set up a DI container to manage your services. Each service requires a unique key. You have no limitations in creating keys with the same service type. import DependencyContainer

extension DI {
    static let data = Key<any DataRepository>()
} Next let’s create a function for registering service in DI Container. extension DI.Container {
    
    static func setup() {
        register(DI.data, DataRepositoryImp())
    }
} Then, call this function at app startup. @main
struct ExampleApp: App {
    
    @MainActor final class AppState: ObservableObject {
        
        init() {
            DI.Container.setup()
        }
    }
    @StateObject var state = AppState()
    
    var body: some Scene {
        WindowGroup {
            MainView()
        }
    }
} Injecting Dependencies The actual injection is done with several property wrappers. The most common one is @DI.Static. You just need to pass a key we defined earlier. struct MainView: View {
    
    @DI.Static(DI.data) var data
    
    var body: some View {
        Color.clear.task {
            try? await data.fetchData()
        }
    }
} The points we need to make attention to: No Need to Specify Type. As you may have noticed we don’t need to write a type here, because Swift gets the type from the key.
It’s very convenient in case you start with a concrete type for your service and later decide to use a protocol to enable mocking. You only need to update the type in the key definition. This change propagates automatically without requiring updates to any code referencing that service. Dependency Existence Checked on Initialization. The property wrapper checks that the service exists when initialized. This helps prevent accidental circular dependencies, where services might try to reference each other. The framework enforces a clear initialization order, encouraging thoughtful dependency management and avoiding deadlocks. Additional property wrappers: @DI.Observed Use this in SwiftUI views when your service is ObservableObject. Views will be updated when the service is changed. struct MainView: View {
    
    //updates the view when data is posting objectWillChange
    @DI.Observed(DI.data) var data
    
    var body: some View {
        Color.clear.task {
            try? await data.fetchData()
        }
    }
} @DI.RePublished Should be used in ObservableObject. If your service is ObservableObject, the update will be republished further by the owner of the property wrapper. struct MainView: View {
    
    final class State: ObservableObject {
        
        // Republishes the data.objectWillChange to the State.objectWillChange
        // The view will be updated
        @DI.RePublished(DI.data) var data
    }
    
    @StateObject var state = State()
    
    var body: some View {
        Color.clear.task {
            try? await data.fetchData()
        }
    }
} In addition, if you have nested services you can use a key path in property wrappers. In this case the observing logic uses the service referenced by a keypath. @DI.Static(DI.data, \.innerService) var innerService

@DI.Observed(DI.data, \.innerService) var innerService

@DI.RePublished(DI.data, \.innerService) var innerService Mocking To swap out implementations for testing or previews, you have two options: Initialize with mocked dependency
MainView(data: .init(value: DataRepositoryMock())) Replace service with mock in DI Container
DI.Container.register(DI.data, DataRepositoryMock())
    
MainView() Conclusion This guide provides a straightforward approach to adopting DI using a DependencyContainer framework and moving away from singletons, enhancing flexibility, modularity, and testability in your iOS apps. This article outlines how to transition from singletons to dependency injection in a SwiftUI app with minimal effort. singletons dependency injection minimal If you're here, you likely already know that you should avoid singletons with various of reasons like: reasons Hidden Dependencies: Classes rely on singletons without explicit indicators, making it harder to track app dependencies and leading to unintended coupling. Circular Dependencies: Singletons depending on each other can create cycles, leading to initialization deadlocks as instances wait for each other. Testing Challenges: Using singletons complicates testing and SwiftUI previews since singletons can't easily be swapped for mocks. Hidden Dependencies: Classes rely on singletons without explicit indicators, making it harder to track app dependencies and leading to unintended coupling. Hidden Dependencies: Circular Dependencies: Singletons depending on each other can create cycles, leading to initialization deadlocks as instances wait for each other. Circular Dependencies: Testing Challenges : Using singletons complicates testing and SwiftUI previews since singletons can't easily be swapped for mocks. Testing Challenges Lack of Flexibility : Singletons make it difficult to provide different implementations for different environments (e.g., live vs. mock versions for testing). Lack of Flexibility And many others. Dependency Injection Dependency Injection To overcome most issues we can use Dependency injection (DI). Using it, swapping in a new implementation becomes much easier, as components don’t rely on a single shared instance but on protocols that can be implemented in different ways. This promotes flexibility, easier testing, and adaptability as app requirements evolve. Dependency injection protocols Constructor Injection Constructor Injection Constructor injection is a straightforward technique for injecting dependencies by passing them through initializers . While effective, it often increases the size and complexity of initializers. initializers A common challenge with constructor injection is passing dependencies through a deep UI hierarchy . If a dependency is only needed on a specific screen but must be passed down through multiple intermediary screens, this can quickly become cumbersome. deep UI hierarchy One way to handle this is by using the Coordinator pattern, which centralizes navigation and manages dependencies more efficiently. Check out this article to learn how to make it. Coordinator this article this article this article Why Not Use @EnvironmentObject ? Why Not Use @EnvironmentObject ? While @EnvironmentObject simplifies dependency sharing in SwiftUI, it has limitations : @EnvironmentObject limitations It only works with ObservableObject It doesn’t allow using protocols for implementation switching. It only works in SwiftUI views hierarchy It only checks for service existence when accessed, increasing the risk of unintentional omissions in views. It only works with ObservableObject ObservableObject It doesn’t allow using protocols for implementation switching. protocols It only works in SwiftUI views hierarchy views It only checks for service existence when accessed, increasing the risk of unintentional omissions in views. existence Dependency injection with property wrappers Dependency injection with property wrappers This is similar to the @EnvironmentObject solution where the dependency management happens inside of property wrappers , but without drawbacks. @EnvironmentObject property wrappers DependencyContainer DependencyContainer This small library contains only a couple files , can be copied directly into your project or integrated via SPM . couple files SPM Please, make sure you put a star on it if you like it. star Here is the link on GitHub . link on GitHub link on GitHub link on GitHub link on GitHub Let’s create an example of the service we need to pass as a dependency. As we are assuming that we are going to make a mock for testing, we need to implement our service as a protocol. Also we make it as ObservableObject , to review additional features of the framework. ObservableObject import Combine

protocol DataRepository: Actor, ObservableObject {
    
    func fetchData() async throws
}

actor DataRepositoryImp: DataRepository {
    
    func fetchData() async throws {
        // do real stuff
    }
}

actor DataRepositoryMock: DataRepository {
    
    func fetchData() async throws {
        // do mocked stuff
    }
} import Combine

protocol DataRepository: Actor, ObservableObject {
    
    func fetchData() async throws
}

actor DataRepositoryImp: DataRepository {
    
    func fetchData() async throws {
        // do real stuff
    }
}

actor DataRepositoryMock: DataRepository {
    
    func fetchData() async throws {
        // do mocked stuff
    }
} Defining a DI container Defining a DI container Once integrated, you’ll set up a DI container to manage your services. Each service requires a unique key. You have no limitations in creating keys with the same service type . DI container unique key. service type import DependencyContainer

extension DI {
    static let data = Key<any DataRepository>()
} import DependencyContainer

extension DI {
    static let data = Key<any DataRepository>()
} Next let’s create a function for registering service in DI Container. function extension DI.Container {
    
    static func setup() {
        register(DI.data, DataRepositoryImp())
    }
} extension DI.Container {
    
    static func setup() {
        register(DI.data, DataRepositoryImp())
    }
} Then, call this function at app startup . app startup @main
struct ExampleApp: App {
    
    @MainActor final class AppState: ObservableObject {
        
        init() {
            DI.Container.setup()
        }
    }
    @StateObject var state = AppState()
    
    var body: some Scene {
        WindowGroup {
            MainView()
        }
    }
} @main
struct ExampleApp: App {
    
    @MainActor final class AppState: ObservableObject {
        
        init() {
            DI.Container.setup()
        }
    }
    @StateObject var state = AppState()
    
    var body: some Scene {
        WindowGroup {
            MainView()
        }
    }
} Injecting Dependencies Injecting Dependencies The actual injection is done with several property wrappers. The most common one is @DI.Static . You just need to pass a key we defined earlier. injection common @DI.Static key struct MainView: View {
    
    @DI.Static(DI.data) var data
    
    var body: some View {
        Color.clear.task {
            try? await data.fetchData()
        }
    }
} struct MainView: View {
    
    @DI.Static(DI.data) var data
    
    var body: some View {
        Color.clear.task {
            try? await data.fetchData()
        }
    }
} The points we need to make attention to: attention No Need to Specify Type. As you may have noticed we don’t need to write a type here, because Swift gets the type from the key.
It’s very convenient in case you start with a concrete type for your service and later decide to use a protocol to enable mocking. You only need to update the type in the key definition. This change propagates automatically without requiring updates to any code referencing that service. No Need to Specify Type. As you may have noticed we don’t need to write a type here, because Swift gets the type from the key. It’s very convenient in case you start with a concrete type for your service and later decide to use a protocol to enable mocking. You only need to update the type in the key definition. This change propagates automatically without requiring updates to any code referencing that service. No Need to Specify Type. As you may have noticed we don’t need to write a type here, because Swift gets the type from the key. No Need to Specify Type. type It’s very convenient in case you start with a concrete type for your service and later decide to use a protocol to enable mocking. You only need to update the type in the key definition. This change propagates automatically without requiring updates to any code referencing that service. concrete type protocol Dependency Existence Checked on Initialization. The property wrapper checks that the service exists when initialized. This helps prevent accidental circular dependencies, where services might try to reference each other. The framework enforces a clear initialization order, encouraging thoughtful dependency management and avoiding deadlocks. Dependency Existence Checked on Initialization. The property wrapper checks that the service exists when initialized . This helps prevent accidental circular dependencies, where services might try to reference each other. The framework enforces a clear initialization order, encouraging thoughtful dependency management and avoiding deadlocks . Dependency Existence Checked on Initialization. initialized deadlocks Additional property wrappers: @DI.Observed Use this in SwiftUI views when your service is ObservableObject . Views will be updated when the service is changed. @DI.Observed ObservableObject struct MainView: View {
    
    //updates the view when data is posting objectWillChange
    @DI.Observed(DI.data) var data
    
    var body: some View {
        Color.clear.task {
            try? await data.fetchData()
        }
    }
} struct MainView: View {
    
    //updates the view when data is posting objectWillChange
    @DI.Observed(DI.data) var data
    
    var body: some View {
        Color.clear.task {
            try? await data.fetchData()
        }
    }
} @DI.RePublished Should be used in ObservableObject . If your service is ObservableObject , the update will be republished further by the owner of the property wrapper. @DI.RePublished ObservableObject ObservableObject struct MainView: View {
    
    final class State: ObservableObject {
        
        // Republishes the data.objectWillChange to the State.objectWillChange
        // The view will be updated
        @DI.RePublished(DI.data) var data
    }
    
    @StateObject var state = State()
    
    var body: some View {
        Color.clear.task {
            try? await data.fetchData()
        }
    }
} struct MainView: View {
    
    final class State: ObservableObject {
        
        // Republishes the data.objectWillChange to the State.objectWillChange
        // The view will be updated
        @DI.RePublished(DI.data) var data
    }
    
    @StateObject var state = State()
    
    var body: some View {
        Color.clear.task {
            try? await data.fetchData()
        }
    }
} In addition, if you have nested services you can use a key path in property wrappers. In this case the observing logic uses the service referenced by a keypath. key path observing logic @DI.Static(DI.data, \.innerService) var innerService

@DI.Observed(DI.data, \.innerService) var innerService

@DI.RePublished(DI.data, \.innerService) var innerService @DI.Static(DI.data, \.innerService) var innerService

@DI.Observed(DI.data, \.innerService) var innerService

@DI.RePublished(DI.data, \.innerService) var innerService Mocking Mocking To swap out implementations for testing or previews, you have two options: Initialize with mocked dependency
MainView(data: .init(value: DataRepositoryMock())) Initialize with mocked dependency MainView(data: .init(value: DataRepositoryMock())) Initialize with mocked dependency MainView(data: .init(value: DataRepositoryMock())) MainView(data: .init(value: DataRepositoryMock())) Replace service with mock in DI Container
DI.Container.register(DI.data, DataRepositoryMock())
    
MainView() Replace service with mock in DI Container DI.Container.register(DI.data, DataRepositoryMock())
    
MainView() Replace service with mock in DI Container DI.Container.register(DI.data, DataRepositoryMock())
    
MainView() DI.Container.register(DI.data, DataRepositoryMock())
    
MainView() Conclusion Conclusion This guide provides a straightforward approach to adopting DI using a DependencyContainer framework and moving away from singletons, enhancing flexibility, modularity, and testability in your iOS apps. DependencyContainer DependencyContainer DependencyContainer DependencyContainer

How to Stop Making Singletons in Swift: A Dependency Injection Guide

Breaking Free from the Evil Singleton TL;DR: Refactor singletons to reduce coupling Problems Addressed High coupling
Difficult testability
Multi-threading issues Related Code Smells https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-vii-8dk31x0?embedable=true https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-v-evj3zs9?embedable=true https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-v-evj3zs9?embedable=true Steps Identify the singleton
Locate all references to its getInstance() method
Refactor the singleton to a standard class
Inject it as a dependency Sample Code Before public class DatabaseConnection {
    private static DatabaseConnection instance;

    private DatabaseConnection() {}

    public static DatabaseConnection getInstance() {
        if (instance == null) {
            instance = new DatabaseConnection();
        }
        return instance;
    }

    public void connect() { 
    }
}

public class Service {
    public void performTask() {
        DatabaseConnection connection = DatabaseConnection.getInstance();
        connection.connect(); 
    }
} After public class DatabaseConnection {  
    // 1. Identify the singleton 
    public void connect() { 
    }
}

public class Service {
    // 2. Locate all references to its getInstance() method.
    private DatabaseConnection connection;

    // 3. Refactor the singleton to a standard class. 
    public Service(DatabaseConnection connection) {
        // 4. Inject it as a dependency.
        this.connection = connection;
    }

    public void performTask() {
        connection.connect(); 
    }
}

DatabaseConnection connection = new DatabaseConnection();
// You can also mock the connection in your tests

Service service = new Service(connection);
service.performTask(); Type [x]Semi-Automatic Safety This refactoring is safe when you update all references to the singleton and handle its dependencies correctly. Testing each step ensures that no references to the singleton are missed. Why Is the Code Better? Refactoring away from a singleton makes the code more modular, testable, and less prone to issues caused by the global state. Injecting dependencies allows you to easily replace DatabaseConnection with a mock or different implementation in testing and other contexts. Tags Coupling Related Refactorings https://maximilianocontieri.com/refactoring-007-extract-class?embedable=true See also https://hackernoon.com/singleton-pattern-the-root-of-all-evil-e4r3up7?embedable=true https://hackernoon.com/coupling-the-one-and-only-software-designing-problem-9z5a321h?embedable=true Credits Image by PublicDomainPictures from Pixabay This article is part of the Refactoring Series. How to Improve Your Code With Easy Refactorings Breaking Free from the Evil Singleton Breaking Free from the Evil Singleton TL;DR: Refactor singletons to reduce coupling TL;DR: Refactor singletons to reduce coupling Problems Addressed High coupling Difficult testability Multi-threading issues High coupling coupling Difficult testability testability Multi-threading issues Related Code Smells https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-vii-8dk31x0?embedable=true https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-vii-8dk31x0?embedable=true https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-v-evj3zs9?embedable=true https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-v-evj3zs9?embedable=true https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-v-evj3zs9?embedable=true https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-v-evj3zs9?embedable=true Steps Identify the singleton Locate all references to its getInstance() method Refactor the singleton to a standard class Inject it as a dependency Identify the singleton Locate all references to its getInstance() method getInstance() Refactor the singleton to a standard class Inject it as a dependency Sample Code Before public class DatabaseConnection {
    private static DatabaseConnection instance;

    private DatabaseConnection() {}

    public static DatabaseConnection getInstance() {
        if (instance == null) {
            instance = new DatabaseConnection();
        }
        return instance;
    }

    public void connect() { 
    }
}

public class Service {
    public void performTask() {
        DatabaseConnection connection = DatabaseConnection.getInstance();
        connection.connect(); 
    }
} public class DatabaseConnection {
    private static DatabaseConnection instance;

    private DatabaseConnection() {}

    public static DatabaseConnection getInstance() {
        if (instance == null) {
            instance = new DatabaseConnection();
        }
        return instance;
    }

    public void connect() { 
    }
}

public class Service {
    public void performTask() {
        DatabaseConnection connection = DatabaseConnection.getInstance();
        connection.connect(); 
    }
} After public class DatabaseConnection {  
    // 1. Identify the singleton 
    public void connect() { 
    }
}

public class Service {
    // 2. Locate all references to its getInstance() method.
    private DatabaseConnection connection;

    // 3. Refactor the singleton to a standard class. 
    public Service(DatabaseConnection connection) {
        // 4. Inject it as a dependency.
        this.connection = connection;
    }

    public void performTask() {
        connection.connect(); 
    }
}

DatabaseConnection connection = new DatabaseConnection();
// You can also mock the connection in your tests

Service service = new Service(connection);
service.performTask(); public class DatabaseConnection {  
    // 1. Identify the singleton 
    public void connect() { 
    }
}

public class Service {
    // 2. Locate all references to its getInstance() method.
    private DatabaseConnection connection;

    // 3. Refactor the singleton to a standard class. 
    public Service(DatabaseConnection connection) {
        // 4. Inject it as a dependency.
        this.connection = connection;
    }

    public void performTask() {
        connection.connect(); 
    }
}

DatabaseConnection connection = new DatabaseConnection();
// You can also mock the connection in your tests

Service service = new Service(connection);
service.performTask(); Type [x]Semi-Automatic [x] Semi-Automatic [x] Safety This refactoring is safe when you update all references to the singleton and handle its dependencies correctly. Testing each step ensures that no references to the singleton are missed. Why Is the Code Better? Refactoring away from a singleton makes the code more modular, testable, and less prone to issues caused by the global state. Injecting dependencies allows you to easily replace DatabaseConnection with a mock or different implementation in testing and other contexts. Tags Coupling Coupling Related Refactorings https://maximilianocontieri.com/refactoring-007-extract-class?embedable=true https://maximilianocontieri.com/refactoring-007-extract-class?embedable=true See also https://hackernoon.com/singleton-pattern-the-root-of-all-evil-e4r3up7?embedable=true https://hackernoon.com/singleton-pattern-the-root-of-all-evil-e4r3up7?embedable=true https://hackernoon.com/coupling-the-one-and-only-software-designing-problem-9z5a321h?embedable=true https://hackernoon.com/coupling-the-one-and-only-software-designing-problem-9z5a321h?embedable=true Credits Image by PublicDomainPictures from Pixabay PublicDomainPictures Pixabay This article is part of the Refactoring Series. How to Improve Your Code With Easy Refactorings How to Improve Your Code With Easy Refactorings

Stories, News & Mentions about SINGLE

Categories

Trending Topics

Stories, News & Mentions about SINGLE

Single’s Stories on HackerNoon

Single's News & Mentions

Categories

Trending Topics