<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ahmed Ali on Medium]]></title>
        <description><![CDATA[Stories by Ahmed Ali on Medium]]></description>
        <link>https://medium.com/@0xAhmedAli?source=rss-ff2c9ae5d5a3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gGE8cO2_URBb6qey2PVH1g.jpeg</url>
            <title>Stories by Ahmed Ali on Medium</title>
            <link>https://medium.com/@0xAhmedAli?source=rss-ff2c9ae5d5a3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:44:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@0xAhmedAli/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ Beyond Collapse: Escaping the Western Economic Trap Through Sufficiency Zones]]></title>
            <link>https://medium.com/@0xAhmedAli/beyond-collapse-escaping-the-western-economic-trap-through-sufficiency-zones-0ac06f3bc48a?source=rss-ff2c9ae5d5a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/0ac06f3bc48a</guid>
            <category><![CDATA[geopolitics]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[ethical-finance]]></category>
            <category><![CDATA[decentralized-finance]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Ahmed Ali]]></dc:creator>
            <pubDate>Wed, 04 Jun 2025 19:26:29 GMT</pubDate>
            <atom:updated>2025-06-04T19:27:34.017Z</atom:updated>
            <content:encoded><![CDATA[<h2>Beyond Collapse: Escaping the Western Economic Trap Through Sufficiency Zones</h2><h3>Part1: Towards a Decentralised Islamic and Ethical based financing infrastructure</h3><blockquote>When survival depends on the system, the system becomes the cage.</blockquote><h3><strong>⚠️ The Problem: Fragile Systems in an Age of Permanent Crisis</strong></h3><p>We live in an age of permanent crisis – economic volatility, supply chain breakdowns, climate shocks, and geopolitical tremors.</p><p>These aren’t random disruptions. They’re the logical outcomes of a system designed not for resilience, but for control.</p><p>At the center of this fragility is the <strong><em>Western-led global economic model – </em></strong>a system that operates through debt, dependence, and centralization.</p><p>It thrives on fragility because a fragile world is easier to govern through fear.</p><h3><strong>🏗️ The Current Model: How the Western Economic System Operates</strong></h3><p>The Western economic structure is engineered to <strong><em>extract</em></strong>, not empower. Its architecture prioritizes financial capital over human well-being and favors efficiency over stability.</p><h3><strong>🔧 Core Components of the Western Model:</strong></h3><ul><li><strong><em>Debt-Based Growth</em></strong>: Everyone – nations, businesses, individuals – is trapped in a perpetual debt cycle.</li><li><strong><em>Export Dependence</em></strong>: Local economies are designed for global markets, not community needs.</li><li><strong><em>Centralized Infrastructure</em></strong>: Food, energy, transport, and digital systems are externally owned.</li><li><strong><em>Financial Hegemony</em></strong>: Institutions like BlackRock, Vanguard, IMF, and the World Bank dictate economic reality.</li><li><strong><em>Monopoly Tech</em></strong>: Digital life is mediated by corporate surveillance platforms.</li><li><strong><em>Crisis Leverage</em></strong>: Each disaster becomes a new excuse for deeper control.</li></ul><p>This system was not built to survive crises. It was built to <strong><em>use</em></strong> them.</p><h3><strong>🧨 The Cracks Are Showing: Challenges of the Western Model</strong></h3><p>Despite its power, the Western model is crumbling under its own weight.</p><ul><li><strong><em>Fragility</em></strong> : Hyper-efficiency has made systems brittle and vulnerable.</li><li><strong><em>Loss of Sovereignty</em></strong>: Nations are reduced to clients of global capital.</li><li><strong><em>Ethical Collapse</em></strong>: Profit overrides justice, culture, and community.</li><li><strong><em>Social Fragmentation</em></strong>: Atomized individuals replace interdependent communities.</li><li><strong><em>Coercive Recovery</em></strong>: Every economic shock is met not with renewal, but with tighter control.</li></ul><p>This isn’t dysfunction. It’s design.</p><h3>🌱 The Alternative: Introducing the Sufficiency Zone Model (SZM)</h3><p>The Sufficiency Zone Model is not just an alternative economic plan – it’s a <strong><em>civilizational blueprint.</em></strong></p><p><strong><em>It begins from below: from the land, the ethics, and the community. It does not wait for reform. It starts where you stand.</em></strong></p><h4>🏡 What Is a Sufficiency Zone?</h4><p>A <strong><em>Sufficiency Zone</em></strong> is a local, self-regenerating community ecosystem that:</p><ul><li>Meets its own food, energy, and essential needs</li><li>Operates without interest, speculative debt, or external ownership</li><li>Builds on shared values, ethical trade, and local governance</li><li>Trades horizontally with other zones – without relying on empire-scale logistics**</li></ul><p>It is resilient by design. It is cooperative by structure. And it is the <strong><em>nightmare scenario for fragile empires.</em></strong></p><h4>🧩 How Sufficiency Zones Address the Systemic Challenges</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*9MmApCksP_JRZJnmBxgk9A@2x.jpeg" /></figure><h4>🏘️ Intra-Zone &amp; 🌍 Inter-Zone Integrity: Building Multi-Layered Resilience</h4><p><strong><em>Resilience is not isolation. It’s integrity</em></strong>. The Sufficiency Zone Model strengthens both internal structures and regional cooperation.</p><h4><strong>🏘️ Intra-Zone (Local) Strategies:</strong></h4><ul><li>Food Sovereignty: Community-supported agriculture, seed libraries, permaculture.</li><li>Energy Autonomy: Solar microgrids, biogas, decentralized water systems.</li><li>Ethical Governance: Shura councils, trust-based agreements, collective decision-making.</li></ul><h4>🌍 Inter-Zone (Regional) Collaboration:</h4><ul><li>Trade Networks: Surplus exchange between zones, outside of hegemonic systems.</li><li>Knowledge Sharing: Skills, systems, blueprints for decentralized tools and structures.</li><li>Shared Defense: Coordinated resistance to coercion by financial or political empires.</li></ul><h4>📊 Comparative Analysis: Western Model vs. Sufficiency Zones</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*PZJB4CmO11x1wzvab-ieMg@2x.jpeg" /></figure><p><strong><em>✅ The Takeaway: Build Lifeboats, Not Dependencies</em></strong></p><p>The empire cannot tolerate people who survive without it.</p><p>Sufficiency Zones are <strong><em>lifeboats before the flood</em></strong>, not after. They are practical, scalable, and deeply ethical responses to a system engineered for collapse.</p><p>They do not require permission.</p><p>They require <strong><em>discipline, community, and a clear ethical spine</em></strong></p><p>Once begun, they are unstoppable.</p><h4>📣 Final Call</h4><p>You don’t have to dismantle the empire. Just **stop depending on it**.</p><p>Start small. Start local. Start now.</p><p>What would a Sufficiency Zone look like in your community? Share your vision in the comments below.</p><p>This blogpost was based on ideas and concepts discussed by Shahid Bolsen in his mini lectures about sufficiency zones. Refer to this playlist below for more details.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=http%3A%2F%2Fwww.youtube.com%2Fembed%2Fvideoseries%3Flist%3DPLEFyjccPY4koCg1QzA03XpyUpikFIagXp&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fplaylist%3Fapp%3Ddesktop%26list%3DPLEFyjccPY4koCg1QzA03XpyUpikFIagXp&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FjhK_b_8WjRg%2Fhqdefault.jpg%3Fsqp%3D-oaymwEXCOADEI4CSFryq4qpAwkIARUAAIhCGAE%3D%26rs%3DAOn4CLBwYmryKx8mbF8ks5hPIUtWKwAnjg%26days_since_epoch%3D20243&amp;type=text%2Fhtml&amp;schema=youtube" width="853" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/777473513446610f5ebe0b65b8352e30/href">https://medium.com/media/777473513446610f5ebe0b65b8352e30/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0ac06f3bc48a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ocean Integration: fitchain — Providing Secure On-Premise Compute]]></title>
            <link>https://blog.oceanprotocol.com/ocean-integration-fitchain-secure-on-premises-compute-59f43a944266?source=rss-ff2c9ae5d5a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/59f43a944266</guid>
            <category><![CDATA[homepage]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[contracts]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[Ahmed Ali]]></dc:creator>
            <pubDate>Tue, 11 Dec 2018 07:57:17 GMT</pubDate>
            <atom:updated>2018-12-11T07:57:17.111Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ocean Integration: fitchain — Providing Secure On-Premise Compute</h3><p>We are excited to announce the integration of <a href="https://fitchain.io/">fitchain</a> with Ocean Protocol. Read further for technical details on the plumbing for integration via <a href="https://blog.oceanprotocol.com/exploring-the-sea-service-execution-agreements-65f7523d85e2">Service Execution Agreements</a> (SEA). This blog post is co-authored by <a href="https://medium.com/u/68468a2d58be">Francesco Gadaleta</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dJ8a7j56IYaJf16LCR-8Og.jpeg" /><figcaption>Sailing into Ocean [credits: <a href="https://medium.com/u/6c175db80c87">Kwinten Crauwels</a>]</figcaption></figure><h3>How it works</h3><p><a href="https://fitchain.io/">fitchain</a> is a decentralized network that allows <em>model providers </em>(e.g. data scientists) to train their models on data provided by <em>data owners</em>. The computation is performed remotely by the data provider themselves or by a delegated actor — referred to as <em>compute provider.</em> This is an execution pattern that relies upon data isolation, as opposed to purely on data encryption, to help secure the data in-situ.</p><p>Traditional machine learning pipelines also rely on testing and validating the models after training. Such a validation step is usually performed by data scientists who “promise” to be ethical in testing their models with so called <a href="https://en.wikipedia.org/wiki/Cross-validation_(statistics)">out-of-sample</a> data (OOS); that is, data that is different from the set of observations used for training. As a matter of fact, testing a model on the same training dataset will inflate its accuracy, making the entire process not only useless, (because models will not generalise to unseen observations) but technically fraudulent.</p><p>In the fitchain network additional actors make sure that this “undesired” behaviour (or inexperience) of data scientists is detected and eventually stopped, thus impeding the trained model’s tradablility within a marketplace. Examples of these types of actors are <em>Gossipers</em> and <em>Verifiers.</em></p><p>In order to simplify the explanation, below are all the actors involved in the complex task of training a machine learning model in a decentralized and untrustworthy fashion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eCZDkLao9cpbZtla0WLXOQ.png" /><figcaption><strong>Table 1:</strong> Describing the actor-task and staking mechanism in fitchain.io</figcaption></figure><p>In the last column of Table 1, it is indicated whether an actor stakes in the system before proceeding. Some actors are required to stake once per available slot. One slot represents how much computation capacity an actor could provide for the specific task. For instance, a CP with a powerful GPU, could train multiple models at once; similarly a Verifier could verify multiple models; and a Gossiper could broadcast and replicate logs for multiple models, provided there is sufficient network bandwidth and storage. <br>Generally speaking,</p><ul><li>Gossipers stake in order to participate in the election (a <a href="https://en.wikipedia.org/wiki/Round-robin_scheduling">Round-Robin</a> like election schedule, still prone to 51% attack) to <em>gossip</em> in a dedicated channel, which is created every time a new model is trained.</li><li>Verifiers contribute to a secure <a href="https://en.wikipedia.org/wiki/Commitment_scheme">commit-reveal scheme</a> to avoid the front-running attack, and therefore have to stake before getting elected to a verification game.</li><li>Compute provider (CP) must stake to generate transactions during model training. This stake aids in preventing indefinite generation of forged transactions that might lead to DoS attacks. Each CP is in charge of staking based on number of available slots.</li><li>Data provider (DP) stakes until model training is complete.</li><li>Consumers don’t really stake, but they lock payments that will be released after all conditions have been proven by the network.</li></ul><h4>Gossipers game</h4><p>When a new model starts the computation task, a new gossiper channel is created by the <a href="https://github.com/fitchain/fitchain-contracts">fitchain Ethereum contracts</a>. In such a network, a number of gossipers will broadcast the transaction logs produced by the CP that are addressed to the MP through a <a href="https://hackernoon.com/difference-between-sidechains-and-state-channels-2f5dfbd10707">state channel</a>. Without such a network the transaction log would become hard to dispute, as there would only be two actors actively involved, namely CP and MP. Moreover, if one of the two actors either disconnected or misbehaved (e.g. by intentionally hiding transactions) it would become impossible to restore such transactions without starting the training process again. This would be prohibitive in some cases (e.g. model training against extremely large datasets) and could be very expensive and time consuming to re-instantiate.</p><blockquote>In contrast, gossipers are in charge of receiving logs, signing them as acknowledged and broadcasting them to their neighbours according to a <a href="http://parallels.nsu.ru/~chebotarev/docs/kademlia.pdf">kademlia-like protocol</a> defined by fitchain.</blockquote><p>The end of training is flagged by a special transaction called End-of-Training (EoT). A gossiper who receives the EoT transaction and has stored all transactions from the beginning of training can provide a proof to the network. Proofs are submitted by a certain number of gossipers to the smart contract that will set model.isTrained = true as soon as consensus is reached. We call such a proof the <strong>proof-of-training</strong> (PoT).</p><h4>Verifiers game</h4><p>The purpose of the PoT is only to prove that a model has been trained, provided that CP did not forge such transactions without actually training any model. As mentioned, trained models still require a verification process with test data leveraging data that was not used by CP during training. It is extremely difficult to prevent CPs from injecting low-quality data or fake data during the training process, due to the fact that training occurs privately and in an isolated fashion. This task has exactly the same difficulty as in the traditional case of hiring a data scientist who is forging results, with the only difference being that such a data scientist would be fired or prosecuted if such a behaviour went detected.</p><p>To combat this type of fraudulent activity, fitchain makes the life of malicious CPs difficult by:</p><ol><li>Requesting a copy of the Merkle tree of the data claimed as the training dataset when the data is published;</li><li>Requesting the Merkle root of each data batch used during model training <br>(CP will automatically submit such information just by using a genuine <a href="http://fitchain.io/"><em>fitchain-pod</em></a>);</li><li>Implementing a data-reveal mechanism to inspect training data, anytime after the model has been trained.</li></ol><blockquote>Verifiers are actors who perform the model verification game by testing models with external, domain-specific datasets, possibly curated by domain-experts (e.g. Ocean data curators).</blockquote><p>It is the task of the v<em>erifiers</em> to fetch trained models and curated test datasets, and then performing off-chain computation to assess the accuracy/error of such models. Obviously, in order to perform verification, verifiers use resources like CPU/GPU and network bandwidth. For this reason they get rewarded by the network, provided consensus is reached.</p><p>Only after a verification game is completed will the model be flagged as verified (model.isVerified = true ) and ready to be shipped to the consumer.</p><h3>fitchain Service Execution Agreement</h3><p>As mentioned in the previous blog posts <a href="https://blog.oceanprotocol.com/oep-11-service-agreements-63421ca76d9f">introducing Ocean’s service agreements</a> and Ocean’s <a href="https://blog.oceanprotocol.com/exploring-the-sea-service-execution-agreements-65f7523d85e2">Service Execution Agreement</a> (SEA), service agreement is meant to be a definition of each actor’s expectations and obligations in order to reduce future conflicts. This definition specifies communication mechanisms, dispute resolution and the common strategies or actions that every rational actor is obligated to meet.</p><h4>fitchain SEA Template</h4><p>fitchain SEA is an Ocean based SEA template that is defined by a set of service conditions with a <em>dependency model</em> that glues them together. Each condition is associated with one or more on-chain proof. The below figure shows a sample fitchain SEA template including <em>the minimal viable conditions</em> to consume fitchain services in Ocean.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zmG2rSxSR6JturAPxCi3WQ.png" /><figcaption><strong>Figure 1:</strong> fitchain Ocean SEA Template (minimal viable conditions)</figcaption></figure><p>The compute conditions contract is in charge of the fulfillment of one condition, as is the access control contract (performed via <a href="https://blog.oceanprotocol.com/secure-on-chain-access-control-for-ocean-protocol-38dca0af820c">secret store</a>). On the other end, the fitchain conditions contract is in charge of fulfillment of three conditions. All these contracts are predefined and deployed in the Ocean network.</p><p>This sample template doesn’t include dispute resolution (on the level of the verification), and secure computation conditions; however, please note that the modular design of the Ocean SEAs can support future upgrades.</p><p>The SEA life cycle is defined by three phases:</p><p><strong>SEA Definition Phase</strong></p><p>Ocean SEAs provide the basic primitives to define the conditions, as well as the dependency model, of a SEA template. These primitives include the link between the condition and its fulfillment, and the definition of the dependency model. The link is interpreted as a condition <strong><em>key</em></strong> (or Id) which<strong> </strong>is defined as follows:</p><ul><li>Hash(smartContractAddress, functionSignature(selector), dependencyConditionsKeys(ifExist)).</li></ul><p>This means that the condition key is hardcoded with a specific function fingerprint (<a href="https://solidity.readthedocs.io/en/v0.4.25/abi-spec.html#function-selector-and-argument-encoding">solidity function selector</a>) in a smart contract. This is the only authorized function that is in charge of handling the condition fulfillment. Therefore, a smart contract can handle one or more conditions by defining multiple fulfillment functions.</p><p>Figure 2 shows how a dependency model is constructed for an arbitrary Ocean SEA template:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*7VXQxglU_8l7SFwZbsJgRg.png" /><figcaption><strong>Figure 2:</strong> Dependency bits array for an arbitrary Ocean’s SEA template</figcaption></figure><p>The dependency model is embedded or encoded in the template in terms of dependency bits array. Each condition in this array is represented by 2-bits. The 1st bit refers to the dependency condition index and the 2nd bit refers to the timeout flag. For instance, if we have 5 conditions, we need 2 x 5 bits to represent the condition dependency in an array of five elements. So by using bitwise operations, Ocean SEA contracts can easily check the dependency representation and decide whether the current fulfillment function is eligible to fulfill the current condition or not.</p><p>This approach has two advantages:</p><ul><li>It preserves the on-chain storage by compressing the dependency flags into a couple of bits; and,</li><li>It enables Ocean SEA to piggyback more features in the dependency model for the next releases.</li></ul><blockquote>The template can be defined once, and consumed many times. Thus, new service providers have the option to develop their own templates by adding new conditions, or bundling the predefined conditions. However, they can also use a predefined template directly by assigning the template ID to their services.</blockquote><p><strong>SEA Execution Phase</strong></p><p>In this phase, the actors sign the agreement and push it on-chain. Then the Ocean SEA contract verifies the signatures and notifies actors to start the game. During the setup, the service provider will be asked to submit the input values and timeout values (also signed values) that are required for condition fulfillments, including <a href="https://github.com/oceanprotocol/OEPs/blob/master/7/did-method-spec.md">asset/service DIDs</a>, price, consumer address, providers, publisher addresses, etc. At that point, the conditions of the template are instantiated by generating <strong>new condition Instances =</strong> Hash(conditionKey, inputsValueHash) , where the input value’s hash represents all the associated inputs for the condition in the fulfillment function. Therefore, if a malicious actor tries to cheat by passing an invalid input to the fulfillment function, the function will reconstruct an invalid condition instance ID and the Ocean SEA smart contract will revert the call with an error message.</p><p>And where the input values are stored? Simply, they are defined in the service/asset DID document. This <a href="https://github.com/oceanprotocol/OEPs/blob/master/11/ddo.example.json">DID document</a> describes the off-chain representation of the SEA template, the conditions and their associated inputs values. The DID document provides a detailed description for serving data assets by data providers in Ocean.</p><p><strong>SEA Termination Phase</strong></p><p>Ocean’s SEA template should be designed to terminate. This implies that we have two types of termination: fulfilled and unfulfilled agreements. Some key features are:</p><ul><li>As a rational service provider, you will be incentivized to have a higher rank by fulfilling SEAs as much as you can. Moreover, you have the right to write your own conditions (i.e specific identity).</li><li>As a rational consumer, is it important to get your job done as soon as possible. Also, by consuming services, you are curating service agreements. This implies the service quality will increase.</li></ul><h4>Enforcing fitchain SEA in Ocean</h4><p>Figure 3 summarizes the way that data scientists consume the fitchain service through Ocean by signing a service agreement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ipr7x8Ge8nP1XBHj" /><figcaption><strong>Figure 3:</strong> Enforcing Ocean-fitchain SEA</figcaption></figure><p>On the Ocean side, we essentially have three actors:</p><ul><li>Data-Scientist — acts as model provider and consumer;</li><li>fitchain Service Provider — acts as data provider and compute provider;</li><li>Ocean Witnesses — elected actors who are in charge of witnessing the proofs by reference in fitchain.</li></ul><p>Actors are obligated to follow the below steps (i.e. the <em>happy path</em>):</p><ul><li>A data scientist chooses data and compute assets, and a SEA template through a fitchain marketplace (Ocean registered marketplace).</li><li>Data-scientist signs SEA template with values then sends the signed message to the fitchain service provider (SP).</li><li>fitchain SP accepts the request by instantiating a new Ocean SEA on-chain.</li><li>Actors will be notified about the instantiated conditions by listening to the events from the <a href="http://github.com/oceanprotocol/keeper-contracts">Ocean SEA contract</a>.</li><li>Data-scientist locks the payment in the reward contract to start the game, then submits the algorithm to the SP service endpoint.</li><li>At that point, both parties (the data scientist and the SP) are obligated to cooperate in order to fulfill the data integrity check of the submitted algorithm. Thus, the data scientist will calculate the hash of the submitted algorithm, sign it and submit the signed hash (only signature) to the compute conditions contract. If the SP received the same algorithm, he will be able to fulfill the condition by sending the hash of the submitted algorithm.</li><li>Now the work is delegated to the fitchain SP who, in turn, will train the model in the fitchain network, where gossipers will be elected to submit the PoT. Similarly, the verifiers submit the verification proof. Finally, the SP commits the PoT and the verification proof reference IDs on the Ocean side.</li><li>Ocean witnesses use the model Id (service agreement Id on the Ocean side) and the committed proof IDs to check PoT, and the verification proof on the fitchain side. They then commit votes on the Ocean side.</li><li>If both conditions model.isTrained and model.isVerified are true, the SP will grant the data scientists access to the results via <a href="https://blog.oceanprotocol.com/secure-on-chain-access-control-for-ocean-protocol-38dca0af820c">Ocean’s secret store</a>.</li><li>Finally, the reward function is triggered by the SP, where it evaluates the conditions status and releases the payment if all the conditions are met.</li></ul><p><strong>fitchain SEA Integration</strong></p><p>As shown in Table 2, by design, an Ocean SEA is based on an <a href="https://en.wikipedia.org/wiki/Event-driven_architecture">event-driven architecture</a> where every new condition should be associated with an <em>off-chain (software module) handler</em>. A handler basically subscribes to an on-chain condition event(s) and takes the corresponding on-chain or off-chain action(s). These modules are plugged into the Ocean network interface component (Squid <a href="https://github.com/oceanprotocol/squid-py">Python</a>, <a href="https://github.com/oceanprotocol/squid-js">JS</a>, <a href="https://github.com/oceanprotocol/squid-java">Java</a>) which in turn facilitates the interaction with the <a href="https://github.com/oceanprotocol/keeper-contracts/">keeper contracts</a>. The key features of such modules are that they are modular, encapsulated, and loosely coupled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BS_Ih--UIhE4yuiGY_PJ5A.png" /><figcaption><strong>Table 2:</strong> fitchain Integration (feature matrix)</figcaption></figure><p>With that said, additional implementations are required in order to complete the integration. We summarize this below:</p><ul><li>Implementing one contract (<a href="https://github.com/oceanprotocol/keeper-contracts/blob/develop/contracts/SLA/FitchainConditions.sol">fitchain conditions contract</a>) that fulfills both the PoT and the verification proof by reference, which takes place from the Ocean protocol side.</li><li>The same applies to the off-chain modules that handle the condition events and enforce the integrity of proofs from fitchain’s side.</li></ul><blockquote>The key point is that Service Agreements in Ocean are usually defined by stakeholders or the community who are involved in the game. Therefore, the role of Ocean SEAs is to provide the means to describe and operate/execute the agreements and give the power to the community to develop their own conditions. We are looking forward for the next Ocean sailors.</blockquote><p><em>Thanks to </em><a href="https://medium.com/u/9104a5aaeb71"><em>Don Gossen</em></a><em>, </em><a href="https://medium.com/u/86da257a59b6"><em>Dimitri De Jonghe</em></a><em>, </em><a href="https://medium.com/u/8ab281366479"><em>Aitor Argomániz</em></a> <em>, </em><a href="https://medium.com/u/299e78046434"><em>Samer Sallam</em></a><em>, </em><a href="https://medium.com/u/f1e17af9a3ea"><em>Fang Gong</em></a><em>, </em><a href="https://medium.com/u/7cb369a906d7"><em>John Enevoldsen</em></a><em>, </em><a href="https://medium.com/u/6c175db80c87"><em>Kwinten Crauwels</em></a><em>, </em><a href="https://medium.com/u/43c527adde71"><em>Sebastian Gerske</em></a></p><h4>Useful Links</h4><ul><li>fitchain Ethereum Contracts: <a href="https://github.com/fitchain/fitchain-contracts">https://github.com/fitchain/fitchain-contracts</a></li><li>fitchain Verifiers: <a href="https://github.com/fitchain/verifier">https://github.com/fitchain/verifier</a></li><li>Keeper Contracts: <a href="https://github.com/oceanprotocol/keeper-contracts/">https://github.com/oceanprotocol/keeper-contracts/</a></li><li>Introducing the Ocean Protocol Service Agreements: <a href="https://blog.oceanprotocol.com/oep-11-service-agreements-63421ca76d9f">https://blog.oceanprotocol.com/oep-11-service-agreements-63421ca76d9f</a></li><li>Exploring the SEA: Service Execution Agreements: <a href="https://blog.oceanprotocol.com/exploring-the-sea-service-execution-agreements-65f7523d85e2">https://blog.oceanprotocol.com/exploring-the-sea-service-execution-agreements-65f7523d85e2</a></li><li>On-chain Access Control in Ocean Protocol network: <a href="https://blog.oceanprotocol.com/secure-on-chain-access-control-for-ocean-protocol-38dca0af820c">https://blog.oceanprotocol.com/secure-on-chain-access-control-for-ocean-protocol-38dca0af820c</a></li><li>Ocean DID Specification: <a href="https://github.com/oceanprotocol/OEPs/blob/master/7/did-method-spec.md">https://github.com/oceanprotocol/OEPs/blob/master/7/did-method-spec.md</a></li><li>Kademlia: A Peer-to-peer Information System Based on the XOR Metric <a href="http://parallels.nsu.ru/~chebotarev/docs/kademlia.pdf">http://parallels.nsu.ru/~chebotarev/docs/kademlia.pdf</a></li></ul><p>We hope you are ready to dive in — check out <a href="https://github.com/oceanprotocol/dev-ocean">Dev-Ocean</a> to get a sense of what we’ve been working on, and fire all your technical questions in <a href="https://gitter.im/oceanprotocol/Lobby">our Gitter chatroom</a>.</p><p>Follow <strong>Ocean Protocol</strong> on <a href="https://twitter.com/oceanprotocol">Twitter,</a> <a href="https://t.me/joinchat/GUyxrE0Hi154D0NrlOqLFg">Telegram</a>, <a href="https://www.linkedin.com/company/ocean-protocol/">LinkedIn</a>, <a href="https://www.reddit.com/r/oceanprotocol/">Reddit</a>, <a href="https://github.com/oceanprotocol">GitHub</a> &amp; <a href="https://oceanprotocol.com/newsletter/">Newsletter</a> for project updates and announcements.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59f43a944266" width="1" height="1" alt=""><hr><p><a href="https://blog.oceanprotocol.com/ocean-integration-fitchain-secure-on-premises-compute-59f43a944266">Ocean Integration: fitchain — Providing Secure On-Premise Compute</a> was originally published in <a href="https://blog.oceanprotocol.com/">Ocean Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>