You've seen the Nexus API. Now see what it powers.
Live Cardano DeFi market data: real candles, a real DEX order book, top traders by wallet, and volume with the bots filtered out.
๐ Try it now: https://t.co/A1cMgIVo8C
๐ Early access is open today: https://t.co/L3yPWBk8H1
Powered by $GERO
@emurgo_io@YoroiWallet@phillip_pon
Where can we find the rationale behind your NO vote on the BloxBean Java Tools Maintenance proposal?
With ~980M voting power, your NO vote has significantly impacted the proposalโs chances of reaching the required threshold. It would be helpful to understand the reasoning behind this decision.
#Cardano #ada $ada
We say we want enterprise adoption... yet maintaining the tooling that enables it remains a tough sell.
~USD 100k for 1.5 FTEs maintaining projects already used in the ecosystem.
So far, the voting results for the BloxBean proposal (Intersect) don't look great.
https://t.co/i9EFttPaAE
#Cardano #ada $ada
3 more days to go, and only 35% Yes votes so far.
If you're using these tools, please help spread the word.
If you haven't voted yet, please take a look at the proposal and compare it with similar ecosystem maintenance proposals before deciding.
Original ask: ~USD 100k for maintaining the core BloxBean Java tools (1.5 FTEs). At current ADA price, that's now roughly 72k USD.
#Cardano #ada $ada
We say we want enterprise adoption... yet maintaining the tooling that enables it remains a tough sell.
~USD 100k for 1.5 FTEs maintaining projects already used in the ecosystem.
So far, the voting results for the BloxBean proposal (Intersect) don't look great.
https://t.co/i9EFttPaAE
#Cardano #ada $ada
Not sure who needs to see this, but it's been fun learning complex topics with AI while building tools for developers.
https://t.co/I5ruwg5xYC
https://t.co/2FEjOaiCKY
Still a WIP. The end-to-end examples are working, but need some cleanup and better docs. Coming soon...
Disclaimer: Always read the disclaimer. ๐
#Cardano #ada $ada
Recent Scarf analytics (Maven central) for Cardano Client Lib over the last 3 months.
The screenshots speak for themselves: worldwide usage, growing adoption, and developer community.
#Cardano#ada $ada
We say we want enterprise adoption... yet maintaining the tooling that enables it remains a tough sell.
~USD 100k for 1.5 FTEs maintaining projects already used in the ecosystem.
So far, the voting results for the BloxBean proposal (Intersect) don't look great.
https://t.co/i9EFttPaAE
#Cardano #ada $ada
Thanks to the DReps who have voted YES so far for the BloxBean Java Tools Maintenance Proposal.
Still evaluating the proposal or haven't voted yet?
Here's a quick overview of what the proposal funds ๐
https://t.co/KPkIzvI0u8
#Cardano#ada $ada
You are right that when maintainers become internalized within an organization, I can understand the concern. But I think there is a difference between supporting an existing community project and creating a new project internally.
Most of the core BloxBean projects were not created inside CF. They existed before and are supported today because they are used in critical products. Of course, there are some new projects in the BloxBean repository that were started as individual efforts and not as part of any CF initiative.
Regarding the "build internally" point, I may be misunderstanding, but if part of the concern is overlap between projects such as BloxBean and Scalus/Lantr, I don't necessarily see that as a bad thing.
Within CF, teams use many community tools and libraries. It depends on the team, the use case, and the language stack. My team happens to be mostly Java developers, so naturally we use Java tooling more heavily. Likewise, if we get a request from an external team that is primarily Scala focused, we point them toward Scalus. I have personally been a big supporter of Scalus since its early days.
We also try to reuse community projects whenever it makes sense. For example, Yaci Store uses Scalus for transaction evaluation, and we recently started using Scalus ledger-rule module for transaction validation as well.
At the same time, some overlap is natural. BloxBean is primarily focused on Java developers, while Scalus is primarily focused on Scala developers. Different developer communities often need similar capabilities, but exposed in ways that fit their language and tooling.
A simple example is Spring Boot. Spring Boot gives Java developers an opinionated and easy-to-use framework, but underneath it supports many different dbs, messaging systems, caches, and other technologies. Developers can choose what works best for them while using a common programming model.
And Spring Boot is not the only option. There is Quarkus, Micronaut, and others. They overlap in many areas, but that choice and diversity are generally seen as a strength of the Java ecosystem.
Ideally, we would like to see something similar in Cardano. Reuse and collaborate where possible, but also allow different developer communities to build the tools that work best for them.
And you know we can always jump on a call and discuss it if there is any confusion :)
Thanks @adamKDean for highlighting the proposal.
Just to clarify, BloxBean and CF are separate.
BloxBean started in 2020 as an independent opensource effort. Projects like Cardano Client Lib, Yaci, and the early versions of Yaci Store were maintained for several years without any Catalyst funding, mostly through personal time and community contributions.
Since I joined CF in 2023, the Java ecosystem has benefited significantly from CF's support. In fact, I don't think we would have reached the current level of maturity without it. CF deserves a lot of credit for helping sustain and grow these projects.
That said, BloxBean remains an independent project with its own roadmap, and community.
This proposal is not about replacing CF support. It's about adding some extra capacity and helping make the project more sustainable in the long run.
Opensource projects are generally healthier when they are not dependent on a single source of support, and the additional funding would help us move faster on community requested work such as full Blockfrost API compatibility.
Ultimately, it's up to the community to decide whether that additional support is needed, but I wanted to clarify the relationship between CF and BloxBean.
Hidden ballots for the duration of the voting period, it's now possible on #Cardano ! Give it a try with this demo vote on mainnet: https://t.co/WH2YtDGbbS
Thanks to the DReps who have voted YES so far for the BloxBean Java Tools Maintenance Proposal.
Still evaluating the proposal or haven't voted yet?
Here's a quick overview of what the proposal funds ๐
https://t.co/KPkIzvI0u8
#Cardano#ada $ada
Last year's funding helped us expand the team and accelerate work on full Blockfrost API compatibility for Yaci Store, alongside ongoing maintenance of the existing tools.
We now have strong coverage across the API surface, and the first preview release is coming soon.
Progress tracker
https://t.co/Bm6sn5t78H
#Cardano #ada $ada
GM, if you're a dApp developer on @Cardano and you have (very) large @awscloud or cloud bills, I'd like to talk about it and see if there's anything that can be done to reduce costs.
Big news: we've partnered with the Brazilian Olympic Committee (@timebrasil) to transform Olympic sport with public blockchain, IoT, and AI.
The three-year roadmap aims to position COB as the global benchmark in sports innovation.
The best part? It's all powered by Cardano. โก๏ธ