Around 66,000 CVEs are expected in 2026. Most won't affect your code, but which ones will? A practical look at layered, AI-supported vulnerability triage.
For a bank, introducing autonomous coding agents is an architecture, security and governance problem. Here is how Visdom addresses data residency, machine-enforced boundaries, credential security, AI tracing, audit integrity, human oversight, code quality, test verification, organizational context and cost governance.
Large financial institutions use the public Canton Network in live systems that process hundreds of billions of dollars every day. Here are 8 distinct production use cases from financial markets — covering short-term lending, securities lending, trading, payments, and digital ownership records.
A look at the Scala Days 2026 agenda: from AI and Scala's type system to security, WebAssembly, and GPUs — the talks worth attending and why.
The most frequently asked questions about the Canton Network — answered by VirtusLab engineers who have worked alongside Digital Asset for over five years building the core Canton infrastructure.
Most of the AI-generated code already in your codebase arrived through unsanctioned tools on personal accounts. This is Shadow AI — and like shadow banking before 2008, the risk is invisible until it isn't. Here's how to govern it with risk-based triage, traceability, and Continuous Modernization.
Canton is Digital Asset's privacy-preserving ledger protocol. Unlike public blockchains, it limits transaction visibility from the start – each participant only sees what they're authorized to see. This article breaks down how Canton handles consistent state, historical integrity, and issuer trust.
AI tools work. Adoption is above 80%. And yet measurable business value remains stubbornly low. The bottleneck is not the model — it's the software delivery system around it.
A coding agent is not an AI-native SDLC. Visdom provides the control plane — context, orchestration, sandboxing, and auditability — required to turn AI-generated code into software enterprises can trust in production.
Kotlin's DeepRecursiveFunction turns deep recursion into a heap-allocated trampoline while keeping direct-style code, built on suspend functions. This post explains why that works, then builds a Scala 3 macro that does the same trick with no coroutines and no Project Loom, by rewriting a recursive method into a TailRec state machine at compile time.
Recently, Wasm is used in different areas: safely running AI-generated code, server-side applications with ultra-fast cold starts, and language-independent plugin systems. What Wasm itself can do is just a pure computation. It cannot affect the outside world directly. Things like file I/O, clocks, and networking have to go through interfaces imported from the host. So unless the host explicitly gives it access, a Wasm module cannot perform external effects. This is why Wasm is often described as a sandbox.
Alerts show symptoms, not causes. Grafana RCA workbench puts related services, infrastructure components, and telemetry on one shared timeline — so you can follow the failure chain instead of jumping between dashboards.
