Front-end developer has worked with our design team to implement an entirely overhauled website, while our developers are updating the documentation to include Vasil support upgrades we plan to add to our core services in this quarter.

Front-end work:

• Buttons are done minus animation
• Basic structure is done
• Basic blocks plus CSS (titles, descriptions, images with logo shapes border) are done
• Completing everything except content
• This involved a complete overhaul of charli3.io as well as we update branding

Documentation: -Glossary and terms defined -Pre vasil documentation complete -Post vasil documentation blocked

We launched a data feed for ADA/USDT that updates hourly and is verified by 5 nodes on mainnet. The team is working diligently to scale up to five feeds next and to implement the Vasil features. In the spirit of Agile and continuous innovation, we decided to launch without full Vasil compatibility. Our expectation is that 5 feeds and full Vasil support (consumable EUTXOs) will be implemented within the next 15-90 days.

We launched a data feed for ADA/USDT that updates hourly and is verified by 5 nodes on mainnet. The team is working diligently to scale up to five feeds next and to implement the Vasil features. In the spirit of Agile and continuous innovation, we decided to launch without full Vasil compatibility. Our expectation is that 5 feeds and full Vasil support (consumable EUTXOs) will be implemented within the next 15-90 days.

MVP and community price feeds are just about ready to launch. Documentation for integration is complete and ready for publishing. Website is being developed and on track to release on target. We are likely to be delayed on the Node Feed portal until Jan 2023 as per our other reports.

As per our last few reports, we were waiting on Vasil HF. Now that it is upon us, our team is preparing to launch our MVP hopefully before the next reporting period!

We have 5+ node feeds running successfully and passed our security testing. These are enough to launch community price feeds.

Our team is working diligently to deliver our core solution, community price feeds, then the developer portal including SDK and node feeds in that order.

Our team is working diligently to deliver our core solution, community price feeds, then the developer portal including SDK and node feeds in that order.

Our team is working diligently to deliver our core solution, community price feeds, then the developer portal including SDK and node feeds in that order.

Our core development team is currently fully focused on refactors due to vasil upgrades and additionally the launch of community feeds. The developer portal work will remain less than 20% of their time. This may cause us to delay launch, but for the time being we believe we are on track still. Building the team required to deliver the project is on track (minus the haskell developers needed for content creation guidance and SDK development are sidetracked at the moment).

The project deliverable is free community price feeds. This deliverable is contingent on our core service being live on mainnet. Our team is taking additional time to refactor for Vasil features and conduct thorough security testing. We are not rushing our testing to deliver this project. ETA is next 1-3 months. Catalyst funds are sitting in wallet awaiting launch to subsidize feeds. We may swap to stablecoin to preserve value if the delay will continue past August. Thank you for your patience, C3 Team.

The project deliverable is free community price feeds. This deliverable is contingent on our core service being live on mainnet. Our team is taking additional time to refactor for Vasil features and conduct thorough security testing. We are not rushing our testing to deliver this project. ETA is next 1-3 months. Catalyst funds are sitting in wallet awaiting launch to subsidize feeds. We may swap to stablecoin to preserve value if the delay will continue past August. Thank you for your patience, C3 Team.

We've solidified our project plan internally and begun contracting the teams/resources required to start the first phase (project lead, UI/UX team, front-end developer).

In other words, we've been interviewing and hiring full-speed!!

Next phase of the project includes preliminary website mockups, initial documentation creation, and SDK design planning.

This is a continuation of fund7 project 700122 – We've delayed our launch due to some changes for the hard fork and to increase additional security testing pre-launch. July 11th is our ambitious launch date.

We've completed 98% of the project plan, but delayed our launch for the reasons noted in the above question.

Glad to kick off!

This is a precursor to our Fund8 proposal and both projects "end date" are on the launch of the price feeds between June 15-July 15.

This is a continuation of our fund7 proposal. The funds will sit in a wallet awaiting launch of our price feeds. Our estimated launch of price feeds is delayed until June 15 - July 15.

There is still a potential risk to the May 15th target date because of PAB integration issues. A MVP proof of concept for May 15th is very likely, but that doesn't mean users are ready to consume the data – the funds obviously won't be used until the active public starts using feeds. All funds are being held in the wallet until live users and projects can use it.

Since last report:

• Internal polling of over 15+ Cardano projects for what feeds would be most valuable
• Internal assessment in what feeds would be possible to provide
• Twitter poll to 46k users to collect sentiment on which price feed pairs are most desirable

Outcome of our vote and likely first price pairs available:

ADA/BTC ADA/ETH ADA/DJED (or other stable coin)

The likely voting mechanism to determine the data feeds we will launch to the community is Twitter.

We currently have 45k twitter followers. We will be raising awareness of our twitter vote to drive as much traffic from the Cardano developer community as possible.

Although non developers may corrupt the integrity of the vote, we anticipate all the data feeds to launch eventually. In fund8, we have a proposal for the Developer Portal which will likely be a much better environment to hold the vote.

See; https://cardano.ideascale.com/c/idea/400771/

All that said, we expect 1k+ votes through the twitter poll. We're open to feedback on using a better mechanism for voting; there is a balance between targeting developers (e.g. on Discord) and maximizing inclusivity (e.g. twitter) that are our team is navigating in executing the final vote.