Dave's banner
Dave's profile picture

Dave

@ItsDave_ADA26,009 subscribers

Cardano SPO - Search for DAVE stake pool. Cardano DRep - $drep@itsdave_ada I rarely check DM'S.

Shorts

For almost a year, I have been building a simpler and more dependable way for applications to respond to activity on Cardano. Today, I am incredibly proud to release OgmiosDotnet.BlockchainEvents v1.0.0. BlockchainEvents is an open source transaction filtering, pub sub and event delivery layer for Cardano. It connects to Ogmios, evaluates every transaction against completely customisable rules, and emits only the activity an application has chosen to receive as standard CloudEvents. The rule engine can be shaped around almost any requirement. An application or applications can listen for activity involving a particular address, asset, policy, smart contract, governance action, treasury withdrawal, metadata value or DEX transaction. Builders can also create entirely new rules around their own domain logic. A project can operate one BlockchainEvents instance and allow many different applications to subscribe to the specific Cardano events they care about. A wallet could subscribe to address activity. A governance platform could subscribe to proposals and votes. A DEX service could subscribe to swaps involving selected assets or contracts. The blockchain connection, transaction processing and event infrastructure are shared, while each application receives its own relevant stream of events. This can remove considerable duplication across a project, reduce infrastructure costs and give development teams one dependable event layer to build around. Consumers can be as simple as an HTTP endpoint. When a transaction satisfies a rule, BlockchainEvents transforms it into a CloudEvent and automatically posts it to the subscribed application. Events can also be consumed through gRPC and server sent events. This allows applications to use Cardano data exposed through Ogmios without installing an Ogmios SDK, tracking a particular SDK version, maintaining their own WebSocket connection or implementing the chain sync protocol themselves. Delivery is backed by a durable queue. When a consumer becomes unavailable, its events remain waiting. Once the application returns, delivery resumes automatically. Applications can restart, deploy or experience a temporary outage without immediately losing the Cardano activity produced while they were offline. It is also extremely fast. During a full local Docker stress test, the pipeline processed more than 1,100 transactions per second through the rule engine, CloudEvents transformation, pub sub and durable queue, with approximately one millisecond p99 processing latency and zero failed emissions. The entire stack can be deployed through Docker across cloud providers, infrastructure providers and self hosted environments, while the underlying queue and delivery architecture remains abstracted from the applications using it. This project was funded through Catalyst Fund 14 after receiving 197 million ADA in yes votes across 420 votes cast. I am deeply grateful to everybody who voted for the proposal, followed the development, tested the releases, shared feedback or supported both me and this project over the past year. A great deal of work has gone into reaching this point, and I am genuinely excited to see what Cardano builders create with it. Further technical details, reliability results and the Minswap implementation are included below. Repository: Release: The possibilities from here are endless, this brings industry standard event driven architecture right to Cardano.

For almost a year, I have been building a simpler and more dependable way for applications to respond to activity on Cardano. Today, I am incredibly proud to release OgmiosDotnet.BlockchainEvents v1.0.0. BlockchainEvents is an open source transaction filtering, pub sub and event delivery layer for Cardano. It connects to Ogmios, evaluates every transaction against completely customisable rules, and emits only the activity an application has chosen to receive as standard CloudEvents. The rule engine can be shaped around almost any requirement. An application or applications can listen for activity involving a particular address, asset, policy, smart contract, governance action, treasury withdrawal, metadata value or DEX transaction. Builders can also create entirely new rules around their own domain logic. A project can operate one BlockchainEvents instance and allow many different applications to subscribe to the specific Cardano events they care about. A wallet could subscribe to address activity. A governance platform could subscribe to proposals and votes. A DEX service could subscribe to swaps involving selected assets or contracts. The blockchain connection, transaction processing and event infrastructure are shared, while each application receives its own relevant stream of events. This can remove considerable duplication across a project, reduce infrastructure costs and give development teams one dependable event layer to build around. Consumers can be as simple as an HTTP endpoint. When a transaction satisfies a rule, BlockchainEvents transforms it into a CloudEvent and automatically posts it to the subscribed application. Events can also be consumed through gRPC and server sent events. This allows applications to use Cardano data exposed through Ogmios without installing an Ogmios SDK, tracking a particular SDK version, maintaining their own WebSocket connection or implementing the chain sync protocol themselves. Delivery is backed by a durable queue. When a consumer becomes unavailable, its events remain waiting. Once the application returns, delivery resumes automatically. Applications can restart, deploy or experience a temporary outage without immediately losing the Cardano activity produced while they were offline. It is also extremely fast. During a full local Docker stress test, the pipeline processed more than 1,100 transactions per second through the rule engine, CloudEvents transformation, pub sub and durable queue, with approximately one millisecond p99 processing latency and zero failed emissions. The entire stack can be deployed through Docker across cloud providers, infrastructure providers and self hosted environments, while the underlying queue and delivery architecture remains abstracted from the applications using it. This project was funded through Catalyst Fund 14 after receiving 197 million ADA in yes votes across 420 votes cast. I am deeply grateful to everybody who voted for the proposal, followed the development, tested the releases, shared feedback or supported both me and this project over the past year. A great deal of work has gone into reaching this point, and I am genuinely excited to see what Cardano builders create with it. Further technical details, reliability results and the Minswap implementation are included below. Repository: Release: The possibilities from here are endless, this brings industry standard event driven architecture right to Cardano.

33,140 views

Videos

ItsDave_ADA's profile picture

Self Disclosure Privacy using ZK Proofs, Demonstrated & Executed Directly on Cardano Preview I built a demo where a customer buys a beer and proves they are 18 or over, without ever showing their ID. No name. No birth year. No photo. Just maths. Two beers were ordered. Two separate transactions. The same proof, reused, no re-verification needed. The blockchain recorded "age verified" both times. That's all it knows. No name. No address. No date of birth. No photo. No personal data of any kind. This runs entirely and directly on Cardano. No sidechains. No L2s. No off-chain verification. The ZK proof is checked by the Plutus V3 validator itself, on-chain, using Groth16. And this isn't just for bars, it works for shops, website signups, any age-restricted service. One credential, reused anywhere. Self disclosure means you choose what to share, and in this case, the customer chose to share nothing except "yes, I'm old enough, give me a nice cold beer." 🍺 Massive shout out to everybody involved in the below! Aiken smart contract language on Cardano (please don't judge my Aiken... I know it's bad 😂) ak-381 by Modulo-P, Groth16 SNARK verification library for BLS12-381 on Aiken Circom + snarkjs, ZK circuit design and proof generation MeshSDK, transaction building and wallet management Blockfrost, blockchain data provider A basic demo to set the stage for further privacy enhancements that can occur directly on Cardano. Self disclosure privacy on Cardano Cheers Cardano 🍻🍻 Beer 1 Beer 2

Dave

21,523 views • 4 months ago

ItsDave_ADA's profile picture

Ouroboros "short" Leios Protoyping simulation & visualisation work in progress demonstrated by Duncan Coutts. Full P2P network running Leios Visualisation. You can see 100 different nodes and messages flowing between them all, with representation of Input Blocks (Top left, Endorsement Blocks (20 seconds In these increment), Votes (20 seconds in these increment as the pipeline hits a vote stage) You can see the votes continue to burst at roughly 20 seconds, input blocks also increase, the smoothness of message flows to reduce these bursts is something Duncan details they are working on to improve as-well as resource usage. Input Blocks (IB) - These blocks contain the raw transaction data submitted by users to the blockchain. Endorsement Blocks (EB) - These blocks reference multiple Input Blocks and are used by nodes to validate and vote on the readiness of transactions for inclusion in the blockchain. Votes- Nodes cast votes to achieve consensus on the state of the ledger, enhancing the speed of transaction finality. I believe this is completely off-chain so does not incur transaction costs (Someone keep me honest please) Keep an eye on the diffusion latency chart, as Duncan mentions this is very important, this refers more to time taken for propagation of information across the network I believe. This was an extract from a larger demonstration, really exciting, massive credit to the team working on this. It's going to be extremely impactful to Cardano and I will share as much as I can about it, I really like seeing these visualisations especially during a prototyping stage. What I find interesting is that the visualisation vote count is so much it slows down the browser rendering. Great work! web3innovationnerds & Duncan Coutts what a demonstration that was., keep them coming!

Dave

57,107 views • 1 year ago

ItsDave_ADA's profile picture

I have been building a visualisation platform that maps activity across Cardano. The objective is simple. Transparency. When information is clear and accessible it strengthens the entire ecosystem. The platform is already showing how powerful that visibility can be and it continues to improve as more data is integrated. I have successfully traced the direction of genesis funds across the blockchain end to end. The focus of the work however has increasingly turned toward Emurgo and will continue to target Emurgo.. Whether I release the tool publicly is still something I am considering carefully. In the past I built AI systems over Cardano data and chose not to release them. The reason was simple. I did not want something powerful to be turned into a weapon that hunts for minor negatives inside what is otherwise one of the most important technological and innovative blockchains built in this space, and a result of years of hard work. I have no interest in fuelling drama. My intention has always been to present Cardano for what it actually is. A blockchain built through years of research and engineering, driven by the founding entities IOHK and the Cardano Foundation, and supported by people who genuinely care about the system including Charles and many others who have given years of effort to build it. That remains true regardless of some recent comments directed toward me in spaces. Those were disappointing, and did actually upset me being completely honest, also they missed the wider context of what I have been doing and I feel discounted my care for Cardano. However transparency works both ways. I will not ignore behaviour that undermines the principles Cardano governance is supposed to protect. Emurgo, a founding entity, is accumulating a rapidly increasing share of voting power through Yoroi DRep delegations. Many users appear completely unaware that this is happening. The interface suggests things along the lines of gaining rewards by delegating voting power to Yoroi as a DRep. What many users do not realise is that they are delegating governance influence directly to the same organisation that operates the wallet ,and worst still think they need to delegate to Yoroi to get their ADA rewards! I have received countless direct messages from affected users who did not understand what they had delegated. In several cases language barriers appear to make the situation worse, particularly for users outside the English speaking community. At present Yoroi and Emurgo, which are effectively the same entity in this context, represent roughly 17 percent of all voting power. That share is rising quickly. Based on the recent rate of growth it is not unreasonable to see this exceeding 50 percent within a few years if nothing changes. Governance concentration on that scale is not healthy for a system designed around distributed decision making. Cardano’s credibility depends on users understanding where their voting power sits and being able to move it freely to representatives who actually reflect their interests. The goal of the platform was never to show how much a founding entity spent or to cause drama. The goal was to show the decisions a founding entity made and how those decisions shaped the blockchain in an era of governance

Dave

17,020 views • 4 months ago

No more content to load