<?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 Orcfax on Medium]]></title>
        <description><![CDATA[Stories by Orcfax on Medium]]></description>
        <link>https://medium.com/@orcfax?source=rss-1066f8932e47------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CJoV7U-akexPwXlwC9xXmQ.jpeg</url>
            <title>Stories by Orcfax on Medium</title>
            <link>https://medium.com/@orcfax?source=rss-1066f8932e47------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:52:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@orcfax/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[Orcfax Architecture Audit Post-Mortem: From External Review to Operational Auditability]]></title>
            <link>https://medium.com/@orcfax/orcfax-architecture-audit-post-mortem-from-external-review-to-operational-auditability-a59bdea32200?source=rss-1066f8932e47------2</link>
            <guid isPermaLink="false">https://medium.com/p/a59bdea32200</guid>
            <category><![CDATA[cardano]]></category>
            <category><![CDATA[orcfax]]></category>
            <category><![CDATA[audit]]></category>
            <dc:creator><![CDATA[Orcfax]]></dc:creator>
            <pubDate>Tue, 05 May 2026 18:16:59 GMT</pubDate>
            <atom:updated>2026-05-05T18:16:59.372Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2CmrQZbdT_q1By1cOuqiHw.png" /></figure><p>Orcfax was built around a demanding standard: real-world data should not only be published on-chain, it should be independently verifiable after publication. Orcfax’s architecture publishes real-world data to Cardano smart contracts in Cardano’s eUTXO-native format, while preserving audit-log packages that document how each fact statement was collected, validated, and published.</p><p>Through Project Catalyst Fund 12, Orcfax undertook a two-part architecture audit covering both its on-chain and off-chain systems. TxPipe was selected for the on-chain audit and signed a contract for services in August 2024; BlinkLabs was selected for the off-chain audit and signed a contract in September 2024.</p><p>This post-mortem reviews the audit process, scope changes, timeline changes, audit outcomes, lessons learned, and next steps.</p><h3>Why Orcfax pursued the audit</h3><p>Blockchain oracles are critical parts of a blockchain ecosystem as they allow for the use of trustless data in smart contracts which underpin user services. Ensuring that oracle’s build and maintain robust infrastructure gives integrators and their users the peace of mind that they need in order to continue building and leveraging the Cardano blockchain. For these reasons, it is imperative that blockchain oracles have their infrastructure audited by external parties in order to maintain these assurances.</p><p>For Orcfax, the audit was not only a security exercise. It was an opportunity to test whether the project’s architecture, documentation, operational practices, and evidence-management approach aligned with its larger mission: providing independently verifiable, permanently archived, and provably auditable smart contract data.</p><h3>Audit scope</h3><p>The audit was split into two complementary tracks.</p><h3>On-chain audit: TxPipe</h3><p>TxPipe audited Orcfax-publish, the component of the Orcfax oracle protocol that provides on-chain data for users to consume in their applications. The <a href="https://docs.orcfax.io/f12-audit#milestone-3">final TxPipe report</a> states that the review considered scenarios where attackers might exploit validators to lock or steal funds, along with risks such as unauthorized asset addition, hidden market creation, interoperability disruption with other Plutus scripts, double satisfaction, and minting-policy vulnerabilities.</p><p>The TxPipe report describes Orcfax-publish as the mechanism through which users publish on-chain data called fact statements. These statements are created as Fact Statement UTxOs locked into the FactStatement script. Validity is proven through an FS token, and the statement must be signed by a protocol-trusted entity called the Notary. The report also describes two global administrative UTxOs: the Constitution, which defines the Notary, and the Fact Statement Pointer, which points to the current Fact Statement script hash and supports migration to a new version if needed.</p><h3>Off-chain audit: BlinkLabs</h3><p>BlinkLabs reviewed Orcfax’s off-chain architecture through a SOC2-style system and controls lens. The resulting system description defines Orcfax’s audited architecture as the people, off-chain processes, and technologies used to develop, deploy, operate, and support Orcfax’s oracle-related services. Areas emphasized included access management, authentication, backup, encryption, firewalls, incident response, logging, monitoring, network configuration, risk management, software development, system tests, and vendor management.</p><p>This assessment culminated in the publication of the <a href="https://docs.google.com/document/d/">Orcfax system description</a> which addresses design choices concerning the above and clarifies audit scope boundaries.</p><h3>Change management and timeline</h3><p>The audit required two material change-management steps.</p><p>First, Orcfax submitted a <a href="https://drive.google.com/file/d/1qG7G55PcxXYJl4rweV9BPe2-cF5lnnPY/view?usp=drive_link">budget-allocation change</a> request after learning that the division of labor between auditor and client was different from the original assumption. The original proposal expected the majority of work and cost to sit with the auditors, using a 67:33 ratio between auditor effort and Orcfax effort. After onboarding with BlinkLabs and clarifying the SOC2-style evidence process, Orcfax revised that understanding to a 20:80 ratio, with the majority of effort falling to Orcfax. The approved deliverables and total project budget did not change.</p><p>The same change request documented the negotiated audit contracts: TxPipe’s on-chain audit contract was $18,500 worth of ADA at $0.3529, equal to 52,423 ADA, while BlinkLabs’ off-chain audit contract was $15,000 worth of ADA at the same rate, equal to 42,505 ADA. The combined audit contract total was 94,928 ADA.</p><p>Second, Orcfax submitted a <a href="https://drive.google.com/file/d/1n_uSGB_08tmg5NXBOzBtuu6iSgRusTZq/view?usp=sharing">timeline change request</a>. The original schedule expected Milestone 3 in November 2024, Milestone 4 in December 2024, Milestone 5 in January 2025, and the Final Milestone in February 2025. The revised schedule moved those dates to November 2025, December 2025, January 2026, and February 2026, respectively. The change request stated that the approved deliverables were not changing; the purpose was strictly to realign the timeline with the reality of the project’s progress.</p><p>The revised timeline was driven in part by the first change-request process, which took approximately six months from initiation to publication on the milestone portal. Our team explained that the project was not delayed because of abandonment or procrastination, but because transparency and accountability processes had to be completed before remaining milestones could be submitted on a realistic schedule.</p><h3>TxPipe findings and Orcfax response</h3><p>TxPipe’s final report listed four findings. All four were <strong>Info-level</strong> findings. TxPipe defines Info items as pieces of information beneficial to the dApp creator that are not necessarily issues and do not necessarily require resolution.</p><h4>ORC-301: Forbid Fact Statement UTxOs with staking credential</h4><p>TxPipe observed that Fact Statement UTxO staking credentials are left to the creator, which means Fact Statement UTxOs may not all share the same address. TxPipe recommended ensuring that all FS outputs in the Publish Statements transaction have their stake credential set to None.</p><p>Orcfax acknowledged the finding. The team’s public response noted that integrators filtering by address could miss UTxOs with different stake credentials, but that integrators can filter by payment credential instead, which Orcfax considers the preferred method.</p><h4>ORC-302: Extremely contracted names for validators and types</h4><p>TxPipe found that acronyms used for validators and main type names added difficulty when reading and navigating the code. It recommended expanded names such as Constitution, FactStatement, and FactStatementPointer or FSPointer.</p><p>Orcfax acknowledged the readability concern while weighing it against the practical value of consistent acronym usage in technical documentation and code.</p><h4>ORC-303: Fact Statement Pointer contract scope</h4><p>TxPipe noted that the Fact Statement Pointer contract is not explicitly connected to the main Fact Statement contract. It functions as a long-term governance or administration component that can point to the active Fact Statement script. TxPipe recommended removing the FSP-related contract from the audited codebase so that the repository scope is clearly defined as the first version of the Fact Statement contract.</p><p>Orcfax disagreed with removing the FSP from scope because the FSP remains integral to the current design. At the same time, Orcfax recognized that as the protocol continues decentralizing, the FSP and similar components should eventually be controlled by a decentralized model rather than a single entity.</p><h4>ORC-304: Sub-optimal cost for FS Collect transactions</h4><p>TxPipe identified a possible optimization for FS Collect transactions. The report explains that, when collecting a Fact Statement, the spend validator checks that FS validity tokens are burned. Because the script hash is obtained from the input list, this work may be repeated for each collected fact, making CPU and memory budget proportional to the number of inputs. TxPipe proposed several alternatives, including storing the own hash in the FS datum or using a separate withdraw script to perform the burn check once.</p><p>Orcfax found the proposal interesting but concluded that more testing would be needed to determine whether reduced collect costs would be worth any increase in publish transaction size or reduction in maximum outputs.</p><h3>TxPipe outcome</h3><p>The on-chain audit concluded without Critical, Major, or Minor findings. The four findings were advisory Info-level observations, all acknowledged. Orcfax decided not to immediately remediate them because doing so could disrupt integrators or introduce unnecessary risk through refactoring. The team will reevaluate the findings when a future on-chain service update is needed.</p><h3>BlinkLabs findings and Orcfax response</h3><p>The BlinkLabs review evolved into a substantial SOC2-style evidence process. After an initial review, BlinkLabs requested evidence showing Orcfax’s ability to meet <a href="https://docs.google.com/spreadsheets/d/1Nw4GTlWgLN5p5LQA6lK0nvtV7N5i75M-/edit?usp=sharing&amp;ouid=103992507632211357751&amp;rtpof=true&amp;sd=true">SOC2-related requirements</a>, which amounted to nearly 200 items, including policies that needed to be drafted or amended. Orcfax responded by organizing the work into evidence batches, with a policy workstream developed in parallel.</p><p>The submitted evidence batches were accepted by BlinkLabs. Batch one, batch two, and batch three were each accepted as satisfactory, with BlinkLabs requesting and receiving additional evidence where needed. By Milestone 5, both Orcfax audits had concluded successfully, and the BlinkLabs work culminated in the system description required under ReqID 2990.</p><p>The uploaded system description shows that this process materially matured Orcfax’s operating model. It documents Orcfax’s control environment, system boundaries, risk assessment processes, monitoring activities, records management, subservice organizations, complementary user entity controls, and recent significant changes made during the audit period.</p><h3>What changed because of the audit</h3><p>The system description and TxPipe report show the concrete result of the work completed. On-chain, integrators and users of integrating DApps, can now verify that the underlying Orcfax data has been produced by an external review process. Off-chain, Orcfax formalized and standardized its internal policy corpus, including production-impacting change management, access-controlled systems, backup-related retention and disposal practices, risk reassessment triggers, and security baselines for encryption, malware protection, firewalls, patching, and vulnerability evaluation. Operational changes included a document retention and disposal register, a workflow for policy and procedure changes, further network hardening, more consistent DevOps procedures, audit and assurance of SSH and MFA access where applicable, and a staff handbook.</p><p>The BlinkLabs process also clarified Orcfax’s operational boundaries. Orcfax controls code repositories, release workflows, operational documentation, access management for production systems, production infrastructure configuration, incident response, monitoring, and remediation. Orcfax does not control integrator environments, the underlying Cardano or Arweave networks, or the underlying security and availability of third-party providers such as DigitalOcean, Kupo, or Ogmios.</p><h3>Key lessons learned</h3><h4>1. On-chain and off-chain audits require different methods</h4><p>The TxPipe audit was appropriately focused on validators, UTxO behavior, minting policies, transaction structures, and on-chain protocol mechanics. The BlinkLabs audit was appropriately focused on infrastructure, people, policies, evidence, monitoring, access governance, and operational controls. Splitting the audit into two workstreams allowed each auditor to evaluate the system according to the right risk model.</p><h4>2. Off-chain audit readiness is mostly evidence work</h4><p>The BlinkLabs audit showed that off-chain infrastructure review is not just a technical walkthrough. It requires a company to prove what it does, where responsibilities sit, how systems are governed, how records are retained, how access is granted and revoked, how monitoring works, and how incidents would be handled.</p><h4>3. Stability is a valid remediation decision</h4><p>The TxPipe findings were useful, but they were advisory. Orcfax’s decision not to immediately remediate Info-level findings reflects a mature operational tradeoff: in production systems relied on by integrators, unnecessary refactoring can introduce new risk.</p><h4>4. Documentation is part of the security model</h4><p>ORC-302 reinforces that names, acronyms, and documentation conventions affect how safely integrators and reviewers can understand a system. For an oracle provider, documentation is not merely explanatory; it shapes how the system is consumed, verified, and trusted.</p><h4>5. Auditability must be practiced internally</h4><p>Orcfax’s external product promise is auditability: fact statements should be backed by durable evidence of collection, validation, and publication. The BlinkLabs process applied the same expectation inward. Orcfax had to demonstrate that its own infrastructure and operations could be described, bounded, evidenced, and reviewed.</p><h3>Next steps</h3><p>Orcfax treats the completion of these audits as the beginning of a more mature audit-readiness cycle. Our team has documented the TxPipe Info-level findings as advisory items, which should continue to be reviewed as system changes are made in the future.</p><p>Orcfax has also committed to improving integrator-facing documentation, especially around payment-credential filtering, Fact Statement discovery, chain-indexer assumptions, FSP purpose, and terminology.</p><p>Policies which has resulted from this experience have been set for review periodically depending on their scope.</p><p>Finally, our team is sharing this document and the milestone breakdown on our docs in order to share our audit experience with the Cardano ecosystem in the hope that it can benefit other Cardano dApps seeking to have their own solutions audited.</p><h3>Closing reflection</h3><p>The audit process confirmed something central to Orcfax’s identity: trustworthy oracle data depends on more than on-chain publication. It depends on collection discipline, validation logic, transparent infrastructure, durable records, operational controls, and the ability for others to verify what happened.</p><p>TxPipe’s audit strengthened Orcfax’s understanding of its on-chain protocol and produced four advisory findings for future consideration. BlinkLabs’ audit pushed Orcfax to formalize the operational evidence, policies, boundaries, and monitoring practices that support the off-chain systems behind the oracle.</p><p>Together, these audits helped Orcfax move from claiming auditability as a product feature to demonstrating auditability as an organizational practice. The result is a stronger foundation for the next phase of Orcfax: a more transparent, resilient, and verifiable oracle service for Cardano builders.</p><p>Our Catalyst closeout report can be found <a href="https://docs.google.com/document/d/19ev8v16T0qpM2Yto1XKZw-zzBQiPuxa0NxUs5umFu_0/preview?tab=t.0#heading=h.12qadggcch0e">here</a>, with the <a href="https://youtu.be/X9h6wrXwdaw?si=E0M6oCWjKqZfD98y">closeout video</a>, and a <a href="https://x.com/orcfax/status/2038144340191580391?s=20">public announcement</a> was made on X.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a59bdea32200" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcement: Orcfax Operational Mode]]></title>
            <link>https://medium.com/@orcfax/announcement-orcfax-operational-mode-10c271b6f72c?source=rss-1066f8932e47------2</link>
            <guid isPermaLink="false">https://medium.com/p/10c271b6f72c</guid>
            <dc:creator><![CDATA[Orcfax]]></dc:creator>
            <pubDate>Fri, 27 Mar 2026 14:41:17 GMT</pubDate>
            <atom:updated>2026-03-27T14:41:17.945Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L9uF4cZxgxVKyJs4AK30CA.png" /></figure><p>After four years of focused R&amp;D and community engagement in the Cardano ecosystem, the Orcfax project has reached a critical turning point.</p><p>Due to a combination of market conditions and funding shortfalls, we are announcing a transition in our operational structure and leadership.</p><h3>The Funding Reality</h3><p>Despite our best efforts to secure a sustainable future, Orcfax is currently unfunded. We benefited from our 2023 ISPO, 2023 Token Launch, 2024 Catalyst funding, and 2025 BuilderDAO sponsorship. These enabled us to carry out research and development into launching high-quality oracle infrastructure on Cardano and Arweave.</p><p>However, we have been unsuccessful in recent Catalyst rounds and its current re-structuring and pause comes at a really bad time for us, and many other projects. That said, the three primary factors that have now impacted the Orcfax runway are:</p><h4>* BuilderDAO</h4><p>Orcfax was a successful recipient of funding from the Cardano Builder DAO’s first funding cycle. This funding enabled Orcfax to supply free-to-use oracle feeds to the Cardano ecosystem. It was intended to shift the Cardano oracle paradigm, freeing cash-strapped integrators from paying for feeds themselves.</p><p>The pilot was a success and the Orcfax feeds saw incredible gains across its target KPIs. However, in the face of an increasingly competitive funding landscape for Cardano projects, we were not approved for a second round of BuilderDAO funding. This was a vital requirement to allow the Orcfax team to continue providing free-to-use feeds to the ecosystem, while simultaneously allowing the use of remaining reserve funds for continued development. Support from the BuilderDAO initiative will conclude at the end of March.</p><h4>* Market Adoption</h4><p>The Orcfax oracle successfully launched on Cardano mainnet in September 2023. We worked with community partners to develop an upgrade to our idiomatic v1 in September 2024. Since that time, the expected exponential growth of the Cardano DeFi ecosystem, a key requirement in our business plan, has not materialized. Total Value Locked (TVL) is a fraction of competing chains.</p><p>This lack of growth in TVL has meant that most Cardano projects are unable or unwilling to pay for independent oracle feeds, opting instead for free single-source APIs. It’s only when there is a failure in those services that they understand the value of dedicated, third-party oracle feeds and have started a dialog with us.</p><p>While careful budget management of reserves allowed Orcfax to continue with R&amp;D and expand service offerings up until now, the lack of further investment and market adoption now means we cannot simultaneously run the current operational Orcfax solution and continue R&amp;D, which includes work on the L2 data validator network.</p><h4>* Pyth oracle on Cardano</h4><p>We had been working for months with a major Cardano DeFi platform on integrating Orcfax feeds and had a signed SLA for feed payments. However, this deal fell through when their team revealed that they will switch to using Pyth feeds instead.</p><p>We are disappointed that official Cardano entities have chosen to sponsor external projects like Pyth, while requests for cooperation from the two long-running Cardano native oracle projects (Orcfax and Charli3) have gone unanswered.</p><p>Having a third oracle solution enter Cardano was not necessarily a dealbreaker for Orcfax. However, more deliberate dialog and a collaborative assessment of oracle requirements unique to Cardano with IOG and/or the Cardano Foundation and its own founding oracle projects should have been the first step.</p><p>A collaborative approach to addressing the data provision needs on Cardano would have helped us to build a stronger ecosystem and maintain all three solutions for diversity, instead the ecosystem finds itself in a situation where it runs the risk of losing proven native solutions and centralizing on a single data provider.</p><h3><strong>Transition to Operational Mode</strong></h3><p>Due to the current funding reality described above, Orcfax will switch to Operational Mode effective immediately. This switch will affect the following areas and is designed to strategically cut costs while new funding options continue to be explored.</p><ul><li><strong>R&amp;D and Maintenance:</strong> All research, platform enhancements, ITN development and system maintenance have been halted; work that is connected with ongoing Catalyst funding is scheduled for completion by the end of March.</li><li><strong>Availability: </strong>Current services and feeds remain available for the time being, and business relations activities continue actively as we seek alternative funding.</li><li><strong>Open Source:</strong> To ensure our work to date continues to provide value, the entire Orcfax technical stack has been open-sourced, allowing the Cardano and oracle community to benefit from our R&amp;D. See <a href="https://github.com/orcfax">https://github.com/orcfax</a></li><li><strong>Wind-down Notice:</strong> In preparation for the possibility that new funding mechanisms are not found, <strong>we are preparing for a wind-down of the Orcfax network by July 31</strong>. We will continue to update the community and partners on our operations timeline to allow existing users sufficient time to migrate.</li></ul><h3>Leadership Change</h3><p>As the project enters this new phase, there will be a transition in leadership:</p><ul><li>Peter Van Garderen is stepping down as CEO and will assume a company director role.</li><li>Christian Koch, who has served as Product Owner and Head of Business Relations for two years, will take over as CEO.</li></ul><h3>Final Deliverables</h3><p>Before entering operational mode, our team is completing two final tasks:</p><ol><li><strong>Custom Feed Demo:</strong> We are preparing a demo application to illustrate how custom, non-price oracle feeds can be deployed using Orcfax infrastructure to accommodate a number of emergent markets for oracles (eg. AI provenance, RWA valuations, etc.).</li><li><strong>ODAPI:</strong> While our on-demand price publication API was opened for testing by ITN validators, we unfortunately lacked the runway for a full market release.</li></ol><h3>About Orcfax</h3><ul><li><a href="http://orcfax.io/">orcfax.io</a></li><li><a href="http://explorer.orcfax.io/">explorer.orcfax.io</a></li><li><a href="http://docs.orcfax.io/">docs.orcfax.io</a></li><li><a href="http://github.com/orcfax">github.com/orcfax</a></li><li><a href="http://x.com/orcfax">x.com/orcfax</a></li><li><a href="http://medium.com/@orcfax">medium.com/@orcfax</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10c271b6f72c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Orcfax Update #26]]></title>
            <link>https://medium.com/@orcfax/orcfax-update-26-8c74294b51c1?source=rss-1066f8932e47------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c74294b51c1</guid>
            <category><![CDATA[cardano]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[orcfax]]></category>
            <dc:creator><![CDATA[Orcfax]]></dc:creator>
            <pubDate>Tue, 17 Mar 2026 20:38:05 GMT</pubDate>
            <atom:updated>2026-03-17T20:38:05.739Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Orcfax Update #26<br></strong>March 17, 2026</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UPLcwYHZotqTZzLNpwfxrg.png" /></figure><h3><strong>Developments</strong></h3><ul><li><strong>Orcfax On-Demand API (ODAPI)</strong> <br>The ODAPI application has completed end-to-end testing and is open for community beta testing.</li><li><strong>CNT Collector</strong> <br>The CNT collector repository is being open-sourced, more details will be shared soon.</li><li><strong>Consensus (Melon)</strong> <br>Work on the Melon consensus algorithm continues toward the end-of-month target.</li></ul><h3><strong>Catalyst</strong></h3><ul><li>Milestone submissions for Subbit and Audit are pending for review.</li></ul><h3><strong>Business &amp; Partnerships</strong></h3><ul><li><strong>Custom Feeds MVP</strong> <br>The team is building toward a custom feeds MVP by end of March. The MVP targets off-chain to on-chain data publication with weather data as the reference use case.</li><li><strong>Builder DAO Application</strong> <br>Our application did not pass this Builder DAO round 2. Thanks to everyone who took the time to vote for us.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*GU1pqFRyYDWX_8nxiLVP2g.png" /></figure><h3>Community</h3><ul><li><strong>CNT Article</strong><br>An article highlighting the CNT collector has been published last week. Read it here:</li></ul><p><a href="https://medium.com/@orcfax/orcfaxs-gold-standard-for-cardano-native-token-cnt-pricing-d047064beb3d">Orcfax’s Gold Standard for Cardano Native Token (CNT) Pricing</a></p><p><strong>Orcfax</strong></p><p>The Oracle of Record</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c74294b51c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Orcfax’s Gold Standard for Cardano Native Token (CNT) Pricing]]></title>
            <link>https://medium.com/@orcfax/orcfaxs-gold-standard-for-cardano-native-token-cnt-pricing-d047064beb3d?source=rss-1066f8932e47------2</link>
            <guid isPermaLink="false">https://medium.com/p/d047064beb3d</guid>
            <category><![CDATA[orcfax]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[dex]]></category>
            <category><![CDATA[cardano]]></category>
            <dc:creator><![CDATA[Orcfax]]></dc:creator>
            <pubDate>Thu, 12 Mar 2026 15:17:42 GMT</pubDate>
            <atom:updated>2026-03-12T15:17:42.241Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eTo-k2KVFRW7FeumQgOhkA.png" /></figure><p>In the fast-moving world of Cardano DeFi, price discovery is often the Achilles’ heel of smart contracts. For the rich ecosystem of Cardano Native Tokens (CNT), many platforms rely on single-source external APIs that can be manipulated or go offline. To help advance decentralization on Cardano, Orcfax has pioneered an on-chain first approach to CNT pricing.</p><h3>Why On-Chain is the Only Source of Truth</h3><p>For Cardano Native Tokens, the most accurate price isn’t found on any single one exchange — it’s found within the combined liquidity pools of DEXs like Minswap, Wingriders, SundaeSwap, and others.</p><p>Orcfax’s unique CNT solution doesn’t just “check the price”; it performs a <strong>Liquidity-Weighted Analysis</strong>. By monitoring block-by-block transactions across multiple geo-dispersed nodes, Orcfax ensures that the data your smart contract receives is a true reflection of the entire ecosystem’s liquidity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RfEnNA7pzgJSZ0GX2Tarng.png" /></figure><h3>The Orcfax Virtual Pool Advantage</h3><p>To eliminate the risks of price manipulation in low-liquidity pools, Orcfax utilizes an industry-first <strong>Virtual Pool </strong>liquidity method.</p><ul><li><strong>Two-Level Triangulation:</strong> Nodes compare data across multiple DEXs and then reach a consensus across the validator network.</li><li><strong>Manipulation Resistance:</strong> By aggregating liquidity into a “virtual pool,” outliers and “flash-skewed” prices are filtered out.</li><li><strong>Verification, Not Trust:</strong> Every price publication is backed by an archived audit trail on Arweave. We don’t just provide data; we provide <strong>proof</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4zhEBMIDzC6IKdyi.jpg" /></figure><h4><strong>About Orcfax</strong></h4><p>The Orcfax oracle solution launched by offering current exchange rate feeds (e.g. ADA-USD) that queried multiple Centralized Exchanges (CEX) APIs and triangulated accurate prices.</p><p>Orcfax then expanded to offer a unique solution for querying and reporting Cardano Native Token (CNT) prices by leveraging Decentralized Exchanges (DEX) and liquidity pools directly from the Cardano blockchain itself. This CNT breakthrough demonstrated something simple: on Cardano, the most accurate method to execute price discovery for native tokens is to look directly on-chain, inside DEX liquidity pools and their per-block transactions.</p><p>Orcfax’s CNT feeds, currently use five geo-dispersed, full Cardano nodes that each do their own liquidity pool analysis and reach a consensus via the Orcfax Validator that triggers the on-chain publication of CNT prices. Each publication is attached to a publicly-accessible, archived audit trail package on the Arweave storage network.</p><p>And Orcfax will open-source this CNT tool so that it can be inspected for security, quality, and as collaborative building blocks for other projects; keep watch for another announcement where we announce the open sourcing of this resource.</p><h4><strong>Advantages of the Orcfax CNT solution</strong></h4><p>The virtual liquidity solution can remove the risk associated with low liquidity DEXes, which can be skewed and manipulated by participants, or single data-sources which can be taken offline or frozen. Instead, Orcfax replaces traditional risks with price accuracy and reliability. New liquidity pools are added as necessary to ensure that the virtual liquidity pool remains reflective of real-time, on-chain activity.</p><p>The Orcfax CNT feed solution provides builders with uncompromising access to reference inputs that don’t need to be trusted, they can be verified at publication.</p><p>Users of these services will be able to see that their service providers have developed robust solutions that no longer implement smart contracts which trust an API response, and instead implement contracts which leverage a publicly verifiable fact statement embedded in the ledger.</p><p>Records are maintained on the Arweave L0 storage solution, and can be downloaded via the Orcfax Explorer or any Arweave gateway. And because the whole process is documented and archived for public use, all kinds of use cases can benefit.</p><h4><strong>Working with Orcfax</strong></h4><p>As Cardano blockchain’s oracle of record, Orcfax provides decentralized data solutions for its users. If you are integrating oracle data into something that carries risk (e.g. financial, operational, or regulatory) we’d love to talk to you.</p><p>The Orcfax oracle solution and CNT feeds have been designed for organizations that value data integrity, compliance alignment, and full auditability of oracle processes. Orcfax doesn’t just provide data, we provide proof. That makes for a higher-quality feed and a better security model for Cardano DeFi and beyond.</p><p>Do you have a CNT you want listed on Orcfax so that it can be leveraged in smart contract transactions? Either on mainnet, preprod, or preview? While we recommend that your CNT is hosted by more than one DEX, we support single LP CNTs as well. Reach out and let us know,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7iaXLUVS5243JI85" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d047064beb3d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Orcfax Update #25]]></title>
            <link>https://medium.com/@orcfax/orcfax-update-25-bdd1871d076a?source=rss-1066f8932e47------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdd1871d076a</guid>
            <category><![CDATA[cardano]]></category>
            <category><![CDATA[orcfax]]></category>
            <dc:creator><![CDATA[Orcfax]]></dc:creator>
            <pubDate>Fri, 30 Jan 2026 21:04:28 GMT</pubDate>
            <atom:updated>2026-01-30T21:04:28.062Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>January 2026</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zz5bqxi_QX62X26xCKZ8Vg.png" /></figure><p>Here’s your bi-weekly Orcfax update, covering recent developments, ITN progress, Catalyst milestones, business strategy, and community activity.</p><h3><strong>Developments</strong></h3><ul><li><strong>CNT Collector &amp; Indexer Upgrades<br></strong> A major review of the collector refactor is underway, bringing Orcfax closer to fully open-sourcing the pipeline end-to-end.</li><li><strong>Orcfax On-Demand API / Subbit <br></strong>The Orcfax On-Demand API is getting closer to launch for testing. Integrators will be able to request real-time price feeds and fact statements exactly when needed. Each request is published on-chain in a single flow. Pricing is strictly pay-per-use, without subscriptions. We are onboarding integrators for the Orcfax On-Demand API. Builders interested in access should contact us</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f0CUa_wuS8XS0gbX" /></figure><ul><li><strong>Consensus Research<br></strong>Work continues on the consensus milestone. Scope is being tightened to to align with the ITN needs.</li></ul><h3><strong>Catalyst</strong></h3><ul><li>Milestone four of the audit track was approved. Work continues on the next milestone and testimonial requirements for submit.</li></ul><h3><strong>Business &amp; Partnerships</strong></h3><ul><li><strong>Custom Feeds &amp; RWAs<br></strong>Our team took the time to explore custom feeds during multiple meeitngs. Work begins on a minimal reference example — “widget data” — to demonstrate custom off-chain to on-chain workflows.</li><li><strong>New Integrator(s) <br></strong>We got big news to share, keep an eye on our socials next week.</li></ul><h3>Community</h3><ul><li><strong>Hello, Charles?!<br></strong>We asked for Charles support for native Cardano oracles! Lets make sure he knows about Orcfax and our offerings.</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//x.com/orcfax/status/2013589543971115269&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/e743501d0d95aec50639abc78a5a0880/href">https://medium.com/media/e743501d0d95aec50639abc78a5a0880/href</a></iframe><p><strong>Orcfax</strong></p><p>The Oracle of Record</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdd1871d076a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Orcfax Update #24]]></title>
            <link>https://medium.com/@orcfax/orcfax-update-24-f62fed03c781?source=rss-1066f8932e47------2</link>
            <guid isPermaLink="false">https://medium.com/p/f62fed03c781</guid>
            <category><![CDATA[orcfax]]></category>
            <category><![CDATA[cardano]]></category>
            <category><![CDATA[oracle]]></category>
            <dc:creator><![CDATA[Orcfax]]></dc:creator>
            <pubDate>Tue, 06 Jan 2026 10:22:34 GMT</pubDate>
            <atom:updated>2026-01-06T10:22:34.163Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2qQTYYtY_ss5pDgcN1Imsw.png" /></figure><p>Here’s your bi-weekly Orcfax update, covering recent developments, consensus progress, ecosystem integrations, business strategy, and community activity.</p><p><strong>Developments 🧪</strong></p><ul><li><strong>CNT Collector Refactor &amp; Dynamic Loading</strong><br>The fully refactored CNT collector is now running on preview. Dynamic pair loading is live, allowing feed updates without redeploying the collector.</li><li><strong>Network Stability &amp; Fork Mitigation</strong><br>A recent Cardano fork caused several geographically distributed nodes to become stuck on an incorrect block. Recovery actions were executed, the incident was documented, and new safeguards are being implemented.</li><li><strong>Consensus &amp; P2P</strong><br>The consensus milestone continues to advance. Design work for a P2P protocol is underway. Validator activity thresholds and participation rules are being explored as the foundation for future decentralized operation.</li><li><strong>ODAPI Integration</strong><br>Wallet login and end-to-end submit flows are being connected with the ODAPI interface, progressing ODAPI toward a functional release.</li></ul><h3><strong>Catalyst 🧭</strong></h3><ul><li>It’s been a long road, but we’re pleased to conclude the catalyst funded R&amp;D project, Orcfax staking: rewarding good behavior. You can read the close-out report in the link below:</li></ul><p><a href="https://milestones.projectcatalyst.io/projects/1200179/milestones/4">Project Catalyst - Milestone Module</a></p><ul><li>Additional audit batches are awaiting feedback from Blink Labs.</li></ul><h3><strong>ITN 🚀</strong></h3><ul><li>Work continues on validator-behavior modeling and network reliability definitions, core prerequisites for a future ITN. Explorations include daily validator tracking, consensus participation metrics, and improved monitoring.</li></ul><h3><strong>Business &amp; Partnerships 🤝</strong></h3><ul><li><strong>SLA Nearing Completion</strong><br>The SLA with an upcoming integrator is in final legal review!</li><li><strong>Custom Data Feeds</strong><br>The team aligned on custom feeds as a potential next product. This accommodates arbitrary fact statements, such as weather, scientific measurements, or other RWA-style claims, defined by the customer and validated by the Orcfax network. A small prototype is targeted for early in the new year.</li></ul><h3><strong>Community 🌐</strong></h3><ul><li><strong>A word from our CEO<br></strong>Peter shared an update with the community in our discord server, read it here:<strong> </strong><a href="https://discord.com/channels/918870284331802674/1060285881174466601/1451306427560759552">https://discord.com/channels/918870284331802674/1060285881174466601/1451306427560759552</a></li><li><strong>+200.000 FACTs milestone</strong></li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//x.com/orcfax/status/2003086015141990472&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/0cb5c8c999ae90c5f3dda1e5eec258c0/href">https://medium.com/media/0cb5c8c999ae90c5f3dda1e5eec258c0/href</a></iframe><p>See you next update!</p><p><strong>Orcfax<br>The Oracle of Record</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f62fed03c781" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Orcfax Update #23]]></title>
            <link>https://medium.com/@orcfax/orcfax-update-23-e84222fbecaa?source=rss-1066f8932e47------2</link>
            <guid isPermaLink="false">https://medium.com/p/e84222fbecaa</guid>
            <category><![CDATA[cardano]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[orcfax]]></category>
            <dc:creator><![CDATA[Orcfax]]></dc:creator>
            <pubDate>Mon, 08 Dec 2025 20:23:07 GMT</pubDate>
            <atom:updated>2025-12-08T20:23:39.973Z</atom:updated>
            <content:encoded><![CDATA[<p>December 2025</p><p>Here’s your bi-weekly Orcfax update, covering recent developments, Catalyst and audit progress, ITN, business, and community activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bxvt6toP4WcsYuRwTunGMQ.png" /></figure><h3><strong>Developments 🧪</strong></h3><p><strong>CNT Refactor<br></strong>The CNT indexing refactor is nearing completion. The work introduces a pluggable configuration system that allows dynamic feed updates without requiring software releases.</p><p><strong>DEX &amp; Token-Pair Criteria<br></strong>Criteria for adding and removing DEXes and token pairs in the CNT collector are being formalized and will be added to Orcfax documentation.</p><h3><strong>Catalyst 🧭</strong></h3><p>Audit Batch 2 has been submitted and reviewed. Batch 3 is nearly complete. Staking and consensus closeout reporting is underway.</p><h3><strong>ITN 🚀</strong></h3><p><strong>Consensus </strong><br>Consensus development continues with a focus on libp2p integration and preparation for eventual ITN deployment. Internal reporting on staking, consensus, and validator flows is being consolidated for publication.</p><p><strong>Open-sourcing CNT collector</strong><br>Work continues toward open-sourcing the remainder of the Orcfax stack, including the CNT collector and the validator.</p><h3><strong>Business &amp; Partnerships 🤝</strong></h3><p><strong>Infrastructure Risk Review<br></strong>Centralized cloud hosting remains a concern. Our team is testing Iagon to evaluate whether their compute offering meets decentralization and risk-mitigation requirements.</p><p><strong>Chainlink &amp; Competitive Positioning<br></strong>Internal analysis reaffirmed Orcfax’s advantage: full data-flow traceability absent in major oracle networks. This remains a differentiator for synthetic assets, stablecoins, and RWA platforms.</p><h3><strong>Community 🌐</strong></h3><p><strong>Oracle-based orderbook on Cardano<br></strong>While0x shared the first order-book oracle transaction on mainnet! Powered by orcfax oracles.</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//x.com/while0x1/status/1993524074459677062&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/3daf8cb1f23dc712acdef4403f962b16/href">https://medium.com/media/3daf8cb1f23dc712acdef4403f962b16/href</a></iframe><p><strong>BuilderDAO update</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//x.com/orcfax/status/1994700593374360024&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/fa86402237d2c86410ede87817e1a4ac/href">https://medium.com/media/fa86402237d2c86410ede87817e1a4ac/href</a></iframe><p><strong>Orcfax</strong></p><p>The Oracle of Record</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e84222fbecaa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Orcfax Update #22]]></title>
            <link>https://medium.com/@orcfax/orcfax-update-22-d46dff66dac2?source=rss-1066f8932e47------2</link>
            <guid isPermaLink="false">https://medium.com/p/d46dff66dac2</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[orcfax]]></category>
            <category><![CDATA[cardano]]></category>
            <dc:creator><![CDATA[Orcfax]]></dc:creator>
            <pubDate>Tue, 04 Nov 2025 07:36:10 GMT</pubDate>
            <atom:updated>2025-11-04T07:38:14.814Z</atom:updated>
            <content:encoded><![CDATA[<p><em>November 4, 2025</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_RXm4GlSm9cHYbahBokBZg.png" /></figure><p>Here’s your bi-weekly Orcfax update, covering recent developments, Catalyst progress, ITN milestones, business strategy, and community activity.</p><h3>Developments 🧪</h3><p><strong>CNT Collector Refinement</strong> <br>Characterization tests are nearly complete, bringing the CNT collector close to open-source readiness.</p><p><strong>Arweave Fallback Implementation<br></strong>Following an AWS outage earlier this month, the team is implementing an Arweave fallback mechanism that pings multiple gateways at random before publishing data. This ensures more resilient data transfers and reduces single-vendor dependency.</p><p><strong>ODAPI<br></strong>Work continues on refining ODAPI for on-demand data delivery.</p><p><strong>Lightweight Explorer &amp; RWA Research<br></strong>Our team discussed developing a lightweight on-chain explorer for verifiable data, extending beyond price feeds to Real World Assets (RWA), decentralized identifiers (DID), and verifiable claims.</p><h3>Catalyst 🧭</h3><p><strong>Fund 15 Strategy</strong> <br>Our team is preparing for Fund 15 under new rules limiting proposals per project, focusing on consensus and staking.</p><h3>ITN 🚀</h3><p><strong>DAO Community Ecosystem Repository<br></strong>The ITN issues repository is being reworked into a <em>DAO community ecosystem repository</em> to provide better transparency and community reporting for the validators.</p><p><strong>Peer-to-Peer<br></strong>Early design discussions continue around a peer-to-peer archival network, decentralizing data validation and storage.</p><h3>Business &amp; Partnerships 🤝</h3><p><strong>Fluid Integration<br></strong>Fluid integrated Orcfax on Mainnet and will start to support IAG and DJED for their V3 lending product.</p><p><strong>Exploring New Infrastructure<br></strong>Following the AWS outage, the team is evaluating decentralized compute alternatives and exploring new collaborations for redundancy and performance improvements.</p><p><strong>RWA &amp; Cross-Chain<br></strong>Research continues into Arweave as a long-term partner for archival and metadata services. This aligns with Orcfax’s broader strategy to position itself as a cross-chain archival oracle network, bridging Cardano and storage ecosystems like Arweave.</p><h3>Community 🌐</h3><p><strong>Brand Kit Released<br></strong>The updated Orcfax Brand Kit is live, completing the brand refresh project. It aligns all visuals, UI, and content style under the “Oracle of Record” identity.</p><p>Thanks for following along with Orcfax.</p><p>See you next update.</p><p><strong>Orcfax<br></strong><em>The Oracle of Record</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d46dff66dac2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Orcfax Update #21]]></title>
            <link>https://medium.com/@orcfax/orcfax-update-21-8a55c3610c0a?source=rss-1066f8932e47------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a55c3610c0a</guid>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[orcfax]]></category>
            <category><![CDATA[cardano]]></category>
            <dc:creator><![CDATA[Orcfax]]></dc:creator>
            <pubDate>Wed, 15 Oct 2025 21:24:16 GMT</pubDate>
            <atom:updated>2025-10-15T21:24:16.374Z</atom:updated>
            <content:encoded><![CDATA[<p><em>October 15, 2025</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4M3OHbenGgn_lKJe2uKDMA.png" /></figure><p>Here’s your bi-weekly Orcfax update, covering recent developments, Catalyst milestones, ITN plans, business progress, and community highlights.</p><h3>Developments 🧪</h3><ul><li><strong>CNT Collector Expansion:<br></strong>Our team finalized continuity tests on the CNT collector, preparing it for open-sourcing.</li><li>Ten new pricefeeds for the DAO have been launched on mainnet last week. 10 More are coming soon.</li><li><strong>Monitoring and Infrastructure: <br></strong>We<strong> </strong>improved the monitoring layer, improving the alarms and updating CNT collector configuration to support multiple DEX security policies.</li><li><strong>ODAPI Progress:<br></strong>We completed Phase One of the ODAPI specification, creating a web interface for testing ODAPI endpoints.</li><li><strong>+40 Feeds on Preview:<br></strong>We pushed 46 oracle feeds in a single transaction. Our bundling mechanism makes oracle feeds affordable and customizable, built for Cardano DeFi.</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//x.com/orcfax/status/1975922126029808082&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/472ebe0b785db9b1fb62f5cf3aea6d3f/href">https://medium.com/media/472ebe0b785db9b1fb62f5cf3aea6d3f/href</a></iframe><h3>Catalyst 🧭</h3><ul><li><strong>BuilderDAO Feeds:<br></strong>The BuilderDAO feeds are now live on mainnet! We will add 10 more free-to-use feeds in the coming weeks.</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//x.com/orcfax/status/1975210750491660590&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/4bfecd3aa4f6535ddd7047fcdd42c63e/href">https://medium.com/media/4bfecd3aa4f6535ddd7047fcdd42c63e/href</a></iframe><h3>Business &amp; Partnerships 🤝</h3><ul><li><strong>Reafino Integration:<br></strong>Reafino successfully tested SmartPlay, a verifiable randomness game contract powered by Orcfax price feeds.</li></ul><h3>Community 🌐</h3><ul><li><strong>Summit Attendance:<br></strong>A few of our team members will attend the Cardano Summit in Berlin.</li></ul><p><strong>Thanks for following along with Orcfax.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a55c3610c0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Orcfax Update #20]]></title>
            <link>https://medium.com/@orcfax/orcfax-update-20-e8df89d36503?source=rss-1066f8932e47------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8df89d36503</guid>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[orcfax]]></category>
            <category><![CDATA[cardano]]></category>
            <dc:creator><![CDATA[Orcfax]]></dc:creator>
            <pubDate>Thu, 25 Sep 2025 17:25:12 GMT</pubDate>
            <atom:updated>2025-09-25T17:39:42.909Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>September 26, 2025</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0jFAVx8jwsLJlAcgswbzqQ.png" /></figure><p>Here’s your bi-weekly Orcfax update, covering recent developments, Catalyst progress, ITN milestones, business strategy, and community activity.</p><h3>Developments 🧪</h3><ul><li><strong>Orcfax V2:</strong> We’re preparing a V2 release of our CNT product with improved reliability, unit tests, and open sourcing.</li><li><strong>Feed Expansion:</strong> Builder DAO-funded feeds are being prepared for mainnet.</li><li><strong>Bundled Transactions:</strong> On preview, Orcfax published <strong>25 feeds in a single transaction</strong>, reducing costs and streamlining dApp integration.</li><li><strong>Fact Archiving:</strong> Fixes were implemented for archival package handling, ensuring all fact statements are published even if retries are required. Explorer updates now show clear error states for missing archives.</li></ul><h3>Builder DAO &amp; Catalyst 🧭</h3><ul><li><strong>Audit &amp; Milestones:</strong> Catalyst Milestone 3 was approved.</li><li><strong>Builder DAO:</strong> Funding secured for 10 feeds. KPIs (transactions, active users, TVS) will be tracked over six months to unlock the second tranche.</li><li><strong>Third Eye Labs Proposal:</strong> Indigo’s dev team proposed to build an open-source smart contract that consumes Orcfax Fact Statements and publishes the latest validated price data for DeFi builders. Make sure to vote for their catalyst proposal!!</li></ul><h3>ITN 🚀</h3><ul><li><strong>Phase 2 Progress:</strong> CNT V2 collectors are in testing, validator refactors are complete, and “Echonet Collect” for P2P networking being discussed.</li></ul><h3>Business &amp; Partnerships 🤝</h3><ul><li><strong>Fluid Integration:</strong> Fluid shared their integration roadmap and publicly endorsed Orcfax’s multi-oracle approach.</li></ul><h3>Community 🌐</h3><ul><li><strong>Publications &amp; Threads:</strong> Our recent article <em>“Why Cardano Oracles Aren’t Chainlink Clones”</em> has sparked wide discussion. Tweets highlighted Orcfax’s design: Fact Statements, integrator-driven freshness rules, and bundling innovations.</li><li><strong>ClarityDAO Spotlight:</strong> ClarityDAO featured Orcfax as a project highlight, recognizing our transparent and auditable feeds.</li><li><strong>Summit Attendance:</strong> Orcfax team members will attend the Cardano Summit in Berlin.</li></ul><p>Thanks for following along with Orcfax.</p><p>See you in the next update.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8df89d36503" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>