TL;DR: Cardano founder Charles Hoskinson says he is personally developing a programming language that combines transaction intents, proof-carrying data and Groth16 proofs.

Charles Hoskinson is returning to the keyboard. The Cardano founder says he is working directly on a new programming language with Input Output Global engineer Lucas Rosa, aimed at making complex blockchain actions easier to express and verify.

His description brings together three ideas. Transaction intents describe what a user wants to achieve without forcing them to specify every execution step. Proof-carrying data attaches evidence that a computation or action meets certain rules. Groth16 proofs are compact cryptographic proofs that can be checked efficiently.

In principle, those pieces could give Cardano developers another way to build applications that coordinate actions and verify results without putting every underlying calculation on-chain.

There is a major caveat: Hoskinson has not publicly released a finished specification, a name for the language or a timetable for general developer access. A social-media announcement about work in progress is not a new production programming environment.

Cardano already supports tools such as Plutus and Aiken, while the separate Midnight privacy network uses its own developer tooling. A new language would have to demonstrate practical advantages, workable security and a developer experience good enough to encourage adoption.

The idea is ambitious. The unanswered question is how it moves from Hoskinson’s description to publicly reviewable code that builders can actually use.

Written by the News Desk and edited by Samuel Rae.

TL;DR: Cardano founder Charles Hoskinson says he is personally developing a programming language that combines transaction intents, proof-carrying data and Groth16 proofs.

Charles Hoskinson is returning to the keyboard. The Cardano founder says he is working directly on a new programming language with Input Output Global engineer Lucas Rosa, aimed at making complex blockchain actions easier to express and verify.

His description brings together three ideas. Transaction intents describe what a user wants to achieve without forcing them to specify every execution step. Proof-carrying data attaches evidence that a computation or action meets certain rules. Groth16 proofs are compact cryptographic proofs that can be checked efficiently.

In principle, those pieces could give Cardano developers another way to build applications that coordinate actions and verify results without putting every underlying calculation on-chain.

There is a major caveat: Hoskinson has not publicly released a finished specification, a name for the language or a timetable for general developer access. A social-media announcement about work in progress is not a new production programming environment.

Cardano already supports tools such as Plutus and Aiken, while the separate Midnight privacy network uses its own developer tooling. A new language would have to demonstrate practical advantages, workable security and a developer experience good enough to encourage adoption.

The idea is ambitious. The unanswered question is how it moves from Hoskinson’s description to publicly reviewable code that builders can actually use.

Written by the News Desk and edited by Samuel Rae.

• OpenZeppelin has launched TRON-specific versions of its smart contract libraries, upgrade tooling and Contracts Wizard.
• The stack supports TRC-20 tokens, upgradeable contracts, role-based permissions and passkey authentication.
• The tools are audited, but OpenZeppelin still recommends project-specific review and testing before production deployment.

**ID:** B25-03

**Site:** Bitcoinist

**Status:** READY

**Author:** Bitcoinist Editorial Team

**Focus Keyword:** OpenZeppelin

**Image Keyword:** TRON

**Category:** Technology

**Tags:** OpenZeppelin, TRON, Smart Contracts, Security, Developers

**Primary Source:** https://www.openzeppelin.com/news

TRON Gets More Than A Port Of The Contracts Library

The release includes audited building blocks for token contracts, access control and upgradeable architecture.

OpenZeppelin has also introduced TRON-focused upgrade plugins covering TronBox, Hardhat and Foundry workflows.

Its Contracts Wizard can generate TRON-compatible contract boilerplate, while an MCP server supports AI-assisted development.

The suite also takes account of network-specific features.

Upgradeable contracts can use UUPS patterns and TRC-1967 proxies, while passkey-based account systems can use secp256r1 signatures.

Where TRON supports the relevant native precompile, the tooling uses it directly.

Where it does not, OpenZeppelin says the contracts can fall back to Solidity-based verification.

Security Infrastructure Matters More As TRON Expands Beyond Transfers

TRON is already heavily used for stablecoin settlement, particularly USDT.

The network is now trying to support a wider range of DeFi, payments and application infrastructure.

That increases the value of standardized development tools.

A large part of smart contract security comes from not reinventing common components unnecessarily.

Token logic, upgrade patterns and role-management systems have all produced expensive failures when developers build them badly from scratch.

OpenZeppelin’s libraries are intended to give teams tested primitives instead.

The company says its broader contracts infrastructure has supported $37 trillion in transferred value and that its security teams have completed more than 900 engagements.

That history does not make every TRON application automatically secure.

OpenZeppelin itself makes that clear.

Projects still need to review dependencies, validate storage layouts, configure permissions correctly and test the exact application being deployed.

But the new integration reduces the amount of security-critical infrastructure TRON developers need to invent themselves.

For a network increasingly trying to position itself as a serious financial settlement layer, that is useful plumbing to have.

*This article was written by the News Desk and edited by [Samuel Rae](https://bitcoinist.com/author/samuelrae/).*