RΣIGNTΣCH retweeted
🚀 Katsina, we’re coming!
This October 31st, we’re bringing another campus activation to Katsina, connecting with Umaru Musa Yar’Adua University students and the wider Web3 community.
We’ll be talking Web3, onboarding people to Hedera, meeting local builders, and hearing what they’re working on.
📅 October 31, 2026
📍 National Library of Nigeria, Katsina Branch, Batagarawa
Register; luma.com/4h77t688
If you’re in Katsina and interested in Web3, come through. Let’s connect and grow the ecosystem together!
Also thanks to @0xKarofi for seeing this through.
Let us spread @hedera across Africa
Replying to @hedera
@hedera is expanding across Africa, not just in Nigeria and Kenya.
The goal is continent-wide: get more builders, developers, and students learning the stack, experimenting, and actually shipping projects on the network. Not limited to one or two markets.
It’s about African talent building the next wave of technology here, together, instead of waiting for it to come from somewhere else.
That’s the work right now.
RΣIGNTΣCH retweeted
Replying to @hedera
@hedera is expanding across Africa, not just in Nigeria and Kenya.
The goal is continent-wide: get more builders, developers, and students learning the stack, experimenting, and actually shipping projects on the network. Not limited to one or two markets.
It’s about African talent building the next wave of technology here, together, instead of waiting for it to come from somewhere else.
That’s the work right now.
RΣIGNTΣCH retweeted
Hedera Part 18: Why Smart Contract Compatibility Matters
A small change in blockchain architecture can have a big impact on how developers build.
Hedera has announced an important change to how smart contract calls work inside Atomic Batch transactions.
But what does this actually mean?
Atomic Batch allows supported transactions to be grouped together and processed as a single atomic operation. This can be useful when multiple actions need to succeed or fail together.
However, Hedera is changing how smart contract calls are supported within these batches.
Under the announced transition:
- Since September 2026, an Atomic Batch can contain no more than one smart contract call, and that call must be the final inner transaction.
- From March 2027, smart contract calls will no longer be supported as inner transactions within Atomic Batch.
- Atomic Batch itself is not being discontinued. Supported native Hedera service transactions remain available.
- Standalone smart contract calls are not affected by this specific change.
Why does this matter?
Smart contract execution, transaction ordering, and EVM compatibility are important considerations when designing blockchain applications. Changes to these rules can affect how developers structure their transaction flows and where application logic should live.
For builders, the practical lesson is clear:
Do not just build around today's capabilities. Understand the roadmap, review architectural dependencies, and plan for announced changes before deadlines arrive.
That is part of building responsibly in a changing Web3 ecosystem.
I’m continuing to explore Hedera by researching its technical developments and translating them into clear, practical insights for the wider community.
What do you think matters most when a network changes its transaction execution model: backward compatibility, developer experience, or long-term architecture?
Source: Hedera official announcement
hedera.com/blog/atomic-batch…
#Hedera #Hashgraph #HBAR







