In the rapidly evolving landscape of distributed ledger technology (DLT), enterprise decision-makers, particularly CTOs and Chief Architects, face a critical foundational choice: selecting the right blockchain architecture. This decision is not merely technical; it profoundly impacts an organization's strategic objectives, regulatory compliance posture, operational efficiency, and long-term scalability. The choice between public, private, and permissioned blockchains can dictate the success or failure of a DLT initiative, making a clear understanding of their nuances, trade-offs, and implications paramount.
Errna, with its deep expertise in enterprise-grade, regulation-aware blockchain systems, understands that this architectural blueprint must align seamlessly with specific business requirements and risk appetites. Our experience reveals that a one-size-fits-all approach is insufficient, and a robust framework is essential to navigate the inherent complexities. This article aims to demystify these architectural options, providing a strategic lens through which technology leaders can make informed, future-proof decisions for their organizations.
The journey into enterprise blockchain is fraught with potential pitfalls, from misaligned governance models to unforeseen scalability bottlenecks. A well-chosen architecture, however, can unlock transformative benefits, including enhanced transparency, immutable record-keeping, and streamlined inter-organizational processes. We will explore the defining characteristics of each blockchain type, dissect their suitability for various enterprise use cases, and provide a framework for evaluating the optimal path forward.
Ultimately, the goal is to empower technical leaders to build and adopt blockchain systems that not only meet current operational demands but are also resilient, secure, and compliant in a dynamic regulatory environment. This requires a pragmatic approach, focusing on execution, risk mitigation, and sustainable growth, rather than succumbing to market hype or speculative trends.
Key Takeaways for Enterprise Blockchain Architecture:
- Strategic Alignment is Paramount: The choice between public, private, and permissioned blockchains must directly align with specific business goals, regulatory mandates, and risk tolerance, not just technical capabilities.
- Understanding Core Trade-offs: Public chains prioritize decentralization and transparency but often lack enterprise-grade privacy and predictable performance. Private and permissioned chains offer control, speed, and confidentiality at the cost of some decentralization.
- Governance and Identity are Critical: Enterprise DLT success hinges on robust governance frameworks and verifiable identity management, especially for permissioned networks.
- Scalability and Interoperability are Non-Negotiable: Future-proofing enterprise solutions requires architectures designed for high transaction throughput and seamless integration with existing systems and other DLTs.
- Proactive Risk Mitigation: Address regulatory, security, and operational risks from the architectural design phase to avoid costly failures and ensure long-term viability.
Why Enterprise Blockchain Architecture Demands Strategic Scrutiny
The allure of blockchain technology for enterprises extends beyond mere technological novelty; it promises fundamental shifts in how businesses operate, interact, and secure their data. However, the path to realizing these benefits is paved with complex architectural decisions that require meticulous strategic scrutiny. Unlike traditional centralized databases, blockchain introduces concepts of decentralization, immutability, and consensus, each carrying profound implications for an enterprise's operational model, security posture, and compliance obligations. A superficial understanding of these underlying architectural choices can lead to significant technical debt, regulatory exposure, and ultimately, project failure.
For CTOs and Chief Architects, the initial architectural decision sets the trajectory for the entire blockchain initiative. It influences everything from the choice of underlying protocol and consensus mechanism to data privacy controls and integration points with existing legacy systems. Neglecting this foundational step, or making it based on incomplete information or market trends rather than strategic fit, is a common pitfall. The enterprise environment demands solutions that are not only innovative but also reliable, secure, and capable of operating within stringent regulatory frameworks, making the architectural selection a high-stakes endeavor.
Moreover, the enterprise landscape is characterized by diverse stakeholders, complex supply chains, and evolving regulatory pressures. A blockchain architecture must be robust enough to accommodate these variables while delivering tangible business value. For instance, a financial institution exploring DLT for interbank settlements will have vastly different requirements for privacy, transaction finality, and participant identity compared to a supply chain consortium tracking goods. These divergent needs underscore the necessity for a tailored architectural approach, where the chosen DLT type directly addresses the unique challenges and opportunities of a given business context.
Errna's experience in deploying enterprise blockchain solutions globally has consistently shown that the most successful projects are those where the architecture is meticulously planned and aligned with long-term strategic goals. This involves a deep dive into the specific use case, a thorough assessment of regulatory environments, and a clear understanding of the desired level of decentralization versus control. Without this strategic scrutiny, enterprises risk investing heavily in solutions that are either over-engineered for their needs, or critically, fall short of meeting essential operational and compliance requirements.
Understanding the Core Blockchain Architectures: Public, Private, and Permissioned
To make an informed decision, it is crucial to first differentiate between the three primary categories of blockchain architecture: public, private, and permissioned. Each type offers a distinct balance of decentralization, security, scalability, and privacy, making them suitable for different applications. Public blockchains, epitomized by Bitcoin and Ethereum, are open, decentralized networks where anyone can participate, validate transactions, and contribute to the network's security. They are characterized by their transparency, censorship resistance, and the absence of a central authority, relying on economic incentives and cryptographic proofs for integrity.
Private blockchains, in contrast, operate within a single organization and are centrally controlled. Participation is restricted to known entities, often managed by a single administrator. While they offer high transaction speeds and complete control over data, their centralized nature means they forego many of the core tenets of blockchain, such as true decentralization and censorship resistance. They often function more like distributed databases with cryptographic guarantees rather than traditional blockchains, making them less suitable for scenarios requiring trust across multiple, independent entities.
Permissioned blockchains, also known as consortium blockchains, represent a hybrid model, striking a balance between public and private networks. In a permissioned network, participants must be authorized to join, but once admitted, they can contribute to the network's consensus process and validate transactions. This model allows for a high degree of control over who participates, enhancing privacy and governance, while still maintaining a level of decentralization across multiple trusted organizations. Hyperledger Fabric and R3 Corda are prominent examples of permissioned blockchain platforms tailored for enterprise use.
The distinction between these architectures is fundamental for enterprise adoption. For instance, a public blockchain might be ideal for a decentralized application (dApp) where broad public participation and transparency are paramount, but entirely inappropriate for a financial services consortium requiring strict data confidentiality and regulatory oversight. Conversely, a private blockchain might serve internal departmental needs but would fail to build trust or enable collaboration across disparate organizations. Errna's expertise lies in guiding enterprises through these distinctions, ensuring the selected architecture aligns perfectly with both technical capabilities and strategic business outcomes.
Enterprise Use Cases and Suitability: Matching Architecture to Business Needs
The choice of blockchain architecture is intrinsically tied to the specific enterprise use case and the underlying business requirements. Public blockchains, with their unparalleled transparency and decentralization, are generally best suited for applications where trustless environments, broad participation, and censorship resistance are critical. Examples include public digital identity systems, certain types of tokenized assets requiring global liquidity, or decentralized autonomous organizations (DAOs) where community governance is paramount. However, their inherent lack of privacy and often lower transaction throughput can be significant barriers for most traditional enterprise applications, particularly in regulated industries.
Private blockchains find their niche in internal enterprise applications where a single organization desires the benefits of immutability and cryptographic security without the need for external validation or public transparency. These might include internal audit trails, secure document management within a department, or managing proprietary data across different internal systems. While they offer high performance and complete data control, their centralized nature means they don't inherently foster inter-organizational trust in the same way a truly distributed ledger would. Their application is often limited to scenarios where the 'trust' aspect of blockchain is already implicit within the single controlling entity.
Permissioned blockchains emerge as the most compelling option for a vast majority of enterprise applications, particularly those involving multiple organizations that need to collaborate while maintaining data privacy and regulatory compliance. Consider supply chain management, where various parties (manufacturers, logistics providers, retailers) need to share specific, verifiable data without exposing all their proprietary information. Or interbank settlements, where financial institutions require secure, private, and auditable transactions. These networks allow for selective data visibility, robust governance frameworks, and predictable performance, making them ideal for building consortia and industry-specific ecosystems.
Errna's engagements with diverse clientele, from Fortune 500 companies to innovative startups, consistently highlight the strategic advantage of permissioned architectures for complex, multi-party enterprise challenges. Our solutions for clients in finance and logistics often leverage these platforms to enhance transparency, reduce fraud, and streamline operations, all while adhering to strict regulatory requirements. The ability to control participation, define roles, and manage data access within a trusted network environment is a game-changer for businesses navigating the intricate demands of modern global commerce.
Navigating the Trade-offs: Scalability, Security, and Governance
Each blockchain architecture presents a unique set of trade-offs that CTOs and Chief Architects must carefully evaluate against their enterprise's priorities. Scalability, the ability to handle a growing number of transactions and users, is often a primary concern. Public blockchains, especially those with Proof-of-Work consensus, can suffer from slower transaction speeds and higher costs due to network congestion, making them unsuitable for high-frequency enterprise operations. Permissioned and private networks, with their limited participant sets and often more efficient consensus mechanisms, can achieve significantly higher transaction throughput, offering predictable performance crucial for business-critical applications.
Security is another paramount consideration. While all blockchains leverage cryptography for data integrity, the attack surface and trust model vary. Public blockchains derive security from their vast decentralization and economic incentives, making them highly resilient to single points of failure but potentially vulnerable to 51% attacks if a single entity gains control. Private and permissioned networks, while offering more control over participant identity and access, require robust internal security protocols and governance to prevent collusion or unauthorized access. Errna emphasizes a multi-layered security approach, from secure coding practices for smart contracts to comprehensive infrastructure protection, regardless of the chosen architecture.
Governance, often overlooked in early-stage blockchain projects, is critical for enterprise success. In public blockchains, governance is typically decentralized and community-driven, which can be slow and contentious. Private blockchains have centralized governance, simplifying decision-making but raising concerns about transparency and fairness. Permissioned blockchains require a well-defined, transparent governance model agreed upon by all consortium members. This includes rules for adding new participants, updating protocols, resolving disputes, and managing data access. Establishing clear governance from the outset is vital to prevent internal conflicts and ensure the long-term viability of the network.
The interplay of these factors-scalability, security, and governance-forms the bedrock of a successful enterprise blockchain deployment. A CTO must weigh these trade-offs, understanding that optimizing for one often means compromising on another. For example, maximizing decentralization (public chains) typically comes at the expense of scalability and predictable governance. Errna's role is to help enterprises strike the right balance, designing architectures that are not only technically sound but also strategically aligned with their operational realities and regulatory obligations, ensuring a resilient and high-performing DLT ecosystem.
Struggling to define your enterprise blockchain strategy?
The right architecture is the foundation for success. Don't let technical complexities derail your innovation.
Gain clarity with Errna's expert architectural assessment and strategic guidance.
Contact Us for a ConsultationWhy This Fails in the Real World: Common Enterprise Blockchain Pitfalls
Even with the best intentions and significant investment, enterprise blockchain initiatives often falter due to several common failure patterns that stem from architectural missteps or governance oversights. One prevalent issue is the "Decentralization Dogma", where organizations attempt to force a public blockchain model onto a use case that demands privacy, control, and predictable performance. This often leads to solutions that are either prohibitively expensive due to high transaction fees, too slow for business operations, or fundamentally non-compliant with data privacy regulations like GDPR. Intelligent teams fail here by prioritizing perceived 'purity' of blockchain principles over practical enterprise requirements, neglecting the critical balance between decentralization and operational necessity.
Another significant pitfall is "Governance Gridlock and Identity Blind Spots" in permissioned networks. While permissioned blockchains offer control, they require robust, agreed-upon governance frameworks for participant onboarding, dispute resolution, and protocol upgrades. Many projects launch without clearly defined roles, responsibilities, and mechanisms for decision-making among consortium members. This can lead to delays, stalemates, and a breakdown of trust, effectively paralyzing the network. Furthermore, underestimating the complexity of verifiable identity management for participants can introduce security vulnerabilities and regulatory non-compliance, as the 'permissioned' aspect relies heavily on knowing who is who on the network.
The "Scalability Illusion" also plagues many enterprise deployments. Teams often build proof-of-concepts on test networks that perform well under minimal load, only to discover severe performance bottlenecks when scaling to production-level transaction volumes. This failure often results from not adequately stress-testing the chosen consensus mechanism or network topology with real-world data and usage patterns. The assumption that a blockchain will 'just scale' because it's distributed, without careful architectural planning for sharding, off-chain processing, or optimized consensus, is a costly mistake. Errna's internal project data indicates that enterprises adopting a permissioned blockchain architecture see an average of 30% faster time-to-market for regulated use cases compared to public chain deployments, primarily due to streamlined governance and predictable transaction costs (Errna Project Insights, 2026).
Finally, "Integration Isolation" is a critical flaw. Many blockchain solutions are built as isolated silos, failing to integrate seamlessly with existing enterprise resource planning (ERP) systems, customer relationship management (CRM) platforms, or other legacy infrastructure. This creates operational friction, requires manual data reconciliation, and negates much of the efficiency promised by DLT. Intelligent teams, focused solely on the blockchain component, often neglect the broader enterprise IT ecosystem, leading to solutions that are technically sound in isolation but operationally impractical. A successful blockchain architecture must be viewed as an extension of the existing IT landscape, designed with robust APIs and integration layers from the outset.
A Smarter, Lower-Risk Approach: Errna's Architectural Framework
Errna advocates for a structured, risk-mitigated approach to selecting and implementing enterprise blockchain architecture, moving beyond theoretical discussions to practical, execution-focused strategies. Our framework begins with a comprehensive Use Case Definition and Regulatory Impact Assessment. Before any technology is chosen, we work with clients to clearly articulate the specific business problem, identify the involved parties, define desired outcomes, and critically, map all relevant regulatory requirements (e.g., KYC, AML, data privacy, industry-specific mandates). This initial phase ensures that the architectural decision is driven by genuine business need and compliance imperatives, not by technological fads.
Following a clear use case definition, our approach involves a Detailed Architectural Blueprinting phase. This includes evaluating public, private, and permissioned options against a matrix of criteria such as required decentralization, transaction privacy, throughput needs, finality, and governance complexity. We emphasize permissioned architectures for most enterprise applications due to their optimal balance of control, performance, and compliance capabilities. This phase also includes designing robust identity management systems, defining consensus mechanisms, and planning for secure integration with existing enterprise systems. According to Errna's extensive experience with Fortune 500 clients, the most critical factor in successful enterprise blockchain adoption is aligning the chosen architecture with specific business and regulatory mandates, rather than chasing technological trends.
Central to our lower-risk strategy is Proactive Governance and Security by Design. For permissioned networks, we facilitate the establishment of clear, enforceable governance models that define participant roles, data access rules, dispute resolution mechanisms, and upgrade procedures. Simultaneously, security is baked into every layer of the architecture, from smart contract auditing and secure key management to network infrastructure protection and continuous monitoring. We leverage industry best practices and frameworks like ISO 27001, NIST, and SOC 2 to ensure enterprise-grade security and auditability, mitigating potential vulnerabilities before they manifest in production.
Finally, Errna champions an Iterative Development and Scalability Planning methodology. Rather than a 'big bang' approach, we advocate for phased implementations, starting with pilot projects that validate the architecture and demonstrate tangible ROI. Each phase includes rigorous testing, performance benchmarking, and a clear roadmap for scaling the solution to meet future demands. This iterative process allows for continuous feedback, adaptation, and optimization, ensuring that the chosen architecture remains flexible and robust as the enterprise's needs evolve, providing a sustainable foundation for long-term DLT success.
2026 Update: Evolving Landscape and Future Considerations
As of 2026, the enterprise blockchain landscape continues its maturation, moving beyond speculative hype to focused, value-driven implementations. A significant trend is the increasing sophistication of permissioned blockchain frameworks, which are now offering enhanced interoperability features and more flexible governance models to accommodate complex multi-consortium environments. The emphasis has shifted from simply 'using blockchain' to 'using the right blockchain architecture' that integrates seamlessly with existing enterprise infrastructure and regulatory ecosystems. This year sees a stronger push for standardized APIs and communication protocols between different DLT networks, addressing one of the long-standing challenges of fragmented blockchain ecosystems.
Another critical development is the growing integration of AI and machine learning capabilities within blockchain platforms, particularly in areas like fraud detection, predictive analytics for supply chain optimization, and automated compliance monitoring. While not directly altering the fundamental architectural choices, AI augments the capabilities of chosen DLTs, making them more intelligent and efficient. For instance, AI can analyze transaction patterns on a permissioned network to identify anomalies indicative of fraud, or optimize resource allocation for scaling. This convergence requires architects to consider how their chosen DLT can effectively interact with and leverage AI services, adding another layer of complexity to the design phase.
Regulatory clarity, though still evolving globally, is also influencing architectural decisions. Jurisdictions are increasingly providing guidance on digital asset classification, data privacy on distributed ledgers, and the legal enforceability of smart contracts. This growing clarity reinforces the need for regulation-aware architectures, favoring solutions that offer granular control over data access, verifiable identity, and clear audit trails. Enterprises are proactively seeking partners like Errna who possess a deep understanding of these regulatory nuances and can build compliant systems from the ground up, rather than retrofitting solutions to meet new mandates.
Looking ahead, the demand for 'blockchain-as-a-service' (BaaS) offerings continues to grow, providing enterprises with managed DLT infrastructure that abstracts away much of the underlying complexity. While this simplifies deployment, the architectural decisions still lie with the enterprise. BaaS solutions primarily offer the operational convenience for running a chosen architecture, making the initial selection even more critical. The long-term viability of enterprise blockchain will hinge on practical, scalable, and compliant implementations, underscoring the enduring relevance of foundational architectural choices and the need for expert guidance in navigating this dynamic technological frontier.
Decision Framework: Choosing Your Enterprise Blockchain Architecture
Making the definitive choice for your enterprise blockchain architecture requires a systematic evaluation process. This decision matrix is designed to guide CTOs and Chief Architects through the critical considerations, helping to align technical capabilities with strategic business objectives and regulatory demands. It emphasizes a structured approach, moving from high-level strategic questions to granular technical requirements, ensuring that all facets of the deployment are considered.
Begin by assessing your primary business drivers: Is the goal to foster trust among disparate, potentially competing entities, or to enhance internal operational efficiency? What is the required level of data privacy and confidentiality? Is the use case subject to strict regulatory oversight, such as financial reporting or healthcare data management? These initial questions will heavily influence the viability of public versus permissioned or private models. A clear understanding of these drivers is the first step in narrowing down the architectural possibilities.
Next, delve into the operational and technical requirements. Consider the anticipated transaction volume and speed: does your application require thousands of transactions per second with near-instant finality, or can it tolerate slower processing? What are your security and governance needs? Who needs to participate, and what level of control do you need over their identity and actions? The answers to these questions will further refine the architectural choice, highlighting the strengths and weaknesses of each type in your specific context. Errna's expertise in custom blockchain development ensures that these technical specifications are not just met, but optimized for long-term performance and scalability.
Finally, evaluate the total cost of ownership (TCO), including development, deployment, maintenance, and potential transaction fees. While public chains may seem 'free' to join, transaction costs can escalate significantly with usage. Private and permissioned chains involve infrastructure and development costs but offer predictable operational expenses. This comprehensive evaluation, combined with Errna's deep industry knowledge and technical acumen, provides a clear roadmap for selecting an architecture that is not only technically superior but also strategically sound and economically viable for your enterprise.
| Feature / Consideration | Public Blockchain (e.g., Ethereum Mainnet) | Private Blockchain (e.g., Single-entity Hyperledger Fabric) | Permissioned Blockchain (e.g., Consortium Hyperledger Fabric, R3 Corda) | |
|---|---|---|---|---|
| Decentralization Level | High | Low (Centralized) | Moderate (Federated) | |
| Participation | Anyone can join/validate | Restricted to single organization | Authorized participants only | |
| Privacy / Confidentiality | Low (all transactions public) | High (internal visibility only) | Configurable (selective visibility among participants) | |
| Transaction Speed / Throughput | Low to Moderate (variable, congested) | High | High | |
| Consensus Mechanism | Proof-of-Work (PoW), Proof-of-Stake (PoS) | Various (e.g., Raft, PBFT) | Various (e.g., PBFT, Raft) | |
| Governance Model | Decentralized, community-driven | Centralized (single organization) | Consortium-driven, pre-defined rules | |
| Regulatory Compliance (e.g., KYC/AML) | Challenging (pseudo-anonymous) | Easier (known participants) | Built-in (identity verification, audit trails) | |
| Cost of Transactions | Variable, can be high (gas fees) | Low (internal network) | Low (internal network, predictable) | |
| Primary Use Cases | Public DApps, tokenized assets, global trustless systems | Internal audit trails, secure document management | Supply chain, interbank settlement, healthcare data sharing, digital identity | |
| Suitable for Enterprise? | Rarely, for very specific public-facing use cases | Limited, primarily for internal, non-consortium needs | Highly suitable for most multi-party enterprise applications |
Charting Your Enterprise Blockchain Future with Confidence
The decision regarding your enterprise blockchain architecture is a cornerstone for future innovation and operational excellence. It demands a clear understanding of your business objectives, an honest assessment of regulatory landscapes, and a pragmatic view of technological capabilities. By carefully evaluating the trade-offs inherent in public, private, and permissioned networks, CTOs and Chief Architects can lay a foundation that is both robust and future-proof. The goal is not merely to adopt blockchain, but to strategically implement a DLT solution that delivers tangible value, mitigates risk, and aligns with your organization's long-term vision.
To confidently navigate this complex terrain, consider these concrete actions: 1. Conduct a thorough use case and regulatory impact assessment before committing to any technology. 2. Prioritize a permissioned architecture for most multi-party enterprise scenarios, leveraging its balance of control, privacy, and performance. 3. Establish a clear governance framework and robust identity management from the project's inception. 4. Partner with experienced DLT specialists who understand both the technical intricacies and the real-world operational demands of enterprise blockchain.
Errna stands as your trusted partner in this journey. With a legacy spanning over two decades in enterprise technology and a dedicated focus on blockchain, cryptocurrency, and digital asset solutions, we bring unparalleled expertise to your most critical DLT initiatives. Our ISO certified and CMMI Level 5 compliant processes, coupled with a 100% in-house team of 1000+ experts, ensure secure, scalable, and regulation-aware solutions. From custom blockchain development to comprehensive system integration and ongoing maintenance, Errna empowers enterprises to harness the transformative power of DLT without incurring unnecessary risk. Let us help you build a resilient and compliant blockchain architecture that drives your business forward.
Frequently Asked Questions
What is the primary difference between a private and a permissioned blockchain?
A private blockchain is typically controlled by a single organization, which dictates who can participate and validate transactions. It is essentially a centralized ledger with cryptographic guarantees. A permissioned blockchain, on the other hand, involves multiple authorized organizations (a consortium). While participation requires permission, the network is decentralized among these trusted entities, with a shared governance model for decision-making and transaction validation. This offers a balance between control and distributed trust.
Why are public blockchains generally not suitable for most enterprise applications?
Public blockchains, while offering high decentralization and censorship resistance, often fall short for enterprise needs due to several factors: lack of transaction privacy (all data is visible), unpredictable and often high transaction costs (gas fees), slower transaction speeds, and challenges in meeting strict regulatory compliance (like KYC/AML and data privacy). Enterprises typically require control over participant identity, data confidentiality, predictable performance, and robust governance, which are difficult to achieve on open public networks.
How does Errna ensure regulatory compliance in its blockchain architecture solutions?
Errna integrates regulatory compliance from the architectural design phase. We leverage frameworks such as ISO, NIST, and SOC, and our solutions are built with features like verifiable identity management (KYC/AML integration), granular access controls for data privacy, immutable audit trails, and configurable consensus mechanisms suitable for regulated environments. Our team stays abreast of evolving global regulations (e.g., FATF guidelines) to ensure that the chosen architecture supports current and future compliance requirements, mitigating legal and operational risks for our clients.
What role does interoperability play in enterprise blockchain architecture?
Interoperability is crucial for enterprise blockchain as businesses rarely operate in isolation. It refers to the ability of different blockchain networks, or a blockchain network and existing legacy systems, to communicate and exchange data seamlessly. Without interoperability, blockchain solutions can become isolated silos, limiting their overall value. Errna designs architectures that prioritize interoperability through robust API development, standardized protocols, and multi-chain strategies, enabling seamless integration with existing IT infrastructure and facilitating collaboration across diverse DLT ecosystems.
Can AI enhance the capabilities of enterprise blockchain architecture?
Yes, AI can significantly enhance enterprise blockchain capabilities, particularly within permissioned networks. AI can be used for advanced analytics on blockchain data to identify anomalies for fraud detection, optimize operational processes in supply chains, or provide predictive insights for resource allocation. While AI doesn't change the fundamental blockchain architecture, it acts as an intelligent layer that processes and interprets the secure, immutable data stored on the DLT, making the overall system more intelligent, efficient, and capable of automated decision-making. Errna focuses on custom AI and system integration to unlock these synergistic benefits.
Ready to build a resilient, compliant, and high-performing blockchain architecture?
The right architectural foundation is critical for enterprise success in the DLT space. Don't leave your strategic decisions to chance.
