Hisho
The Smart Secretary Making Blockchain Feel Easy
Created on 25th June 2025
•
Hisho
The Smart Secretary Making Blockchain Feel Easy
The problem Hisho solves
☠️ The Problem: We Are Doomed If We Don’t Act Fast
A few years ago, we shouted:
“Web3 is the future!”
We believed. We still do. But belief isn’t adoption.
And adoption… is broken.
Here’s the truth we don’t want to hear:
Blockchain is powerful — but it’s still a stranger to the average user.
Decentralized apps? Too slow, too complex, and too far from where users actually live — on their social platforms.
We launched revolutionary tools, but the world said:
“Sorry. I’m busy on Instagram.”
🧱 We Tried. We Built. We Bled.
We dropped SocialFi… but it never reached the virality of TikTok.
We offered DeFi… but people still Googled “how to open a bank account.”
We fought the algorithms… while paying them just to be seen.
The painful irony?
Web2 users pay to use platforms that harvest their data.
Web3 builders pay users to try tools that offer them freedom.
Still, we’re called “slow.”
But now we’re fast with security, thanks to ZK.
Still, they say “it’s too hard.”
But we paid them to learn. We built tutorials, dashboards, incentives.
Yet adoption lags. Why?
Because people don’t want to leave their comfort zones.
They don’t want to “switch chains.”
They don’t want to download ten wallets.
They don’t want to click away from their Twitter DM just to verify a transaction.
🧠 Hard Truths We Learned
-
If you can’t beat them, join them — but with purpose.
-
Security means nothing if performance is poor.
-
Simplicity isn't a feature — it’s the key to the future.
💡 The Solution: Welcome to Hisho
🧙♂️ Hisho isn’t just another dApp. It’s not just another protocol.
It’s a legendary onchain agent — a guide in your DM, a bridge between worlds.
“Blockchain goes onchain, cross-chain… in your DM.”
That’s Hisho.
No more complicated UIs.
No more learning five new chains just to move tokens.
No more juggling wallets, RPCs, or obscure incentives.
What does Hisho bring?
✅ Availability – Wherever you are. On Twitter. Telegram. Discord.
✅ Simplicity – You don’t have to learn the tech. Hisho understands and processes your language to onchain and offchain operations e.g getting realtime prices, minting NFTs, staking, unstaking, claiming tokens, withdrawing tokens, transfering tokens and even getting blockchain education, events, images and analytics.
✅ Performance – Hisho agent is built with rust. A taste of modernity, scalability, speed and memory security.
✅ AI-native – Hisho understands your language by contextualising your chats using guided chain of thought to arrive at the exact information outcome you needed.
✅ Cross-chain ready – Thanks for chainlink CCIP. With the rist of CCT tokens, hisho goes cross-chain which just a chat.
🔗 Hisho is what happens when Chainlink’s vision for interoperability meets real-world AI-powered usability.
Chainlink + Hisho = The Adoption Catalyst
Chainlink showed us that trust, truth, and connection across chains is possible.
Hisho takes that dream one step further — by putting it in your daily digital life.
Hisho is Chainlink’s whisperer, bringing CCIP, VRF, Functions, Automation, Data Feeds and Data Streams not just to dApps — but to the user’s favorite platforms.
Think of it like this: “What if you could use Uniswap like you use WhatsApp?”
“What if your Discord DM could tell you your portfolio, execute swaps, and bridge tokens — securely?”
That’s not a dream. That’s Hisho.
🙌 This is How We Win
We don’t need to kill Web2.
We need to integrate it.
We don’t need to force users into blockchain.
We need to bring blockchain to them, wherever they are — in language, in interface, in soul.
That’s Hisho.
That’s now.
🔥 Final Words
“The blockchain revolution will not be downloaded.
It will be messaged to you, one DM at a time.”
The war isn’t over.
The mission hasn’t failed.
We’re just getting started.
Because we believe,
and now…
We build with Hisho.
Challenges I ran into
My Challenges were Hell!
In the process of buidling hisho, encountered several problems, from several angles and from several languages.
The frontend was easy. Thanks to nexus!
But still had problems with react!
Solidity!
Yes! the first monster I had to fight was solidity, I faced so many problems ranging from using foundry and using remix. gas estimation, external calls, low level calls, interface. abi.encodes and more.
Price Feed
The major prolem here was convertsion problem. I had to consider token decimals and the 1e8 division standard used by priceFeed to get the price of a token.
Automation and VRF
This was the big problem. In trying to create a contract that uses vrf to generate daily interest through chainlink's automation, I encountered lots of challenges. My contracts deployed but wasn't working due to gas cost on remix. I had to recheck by logics and try to modify certain implementations to use less gas.
CCIP
Finally the big guyy!, dealing with CCIP was a nightmare. It was like I having a father and a mom's responsibility! The overcomed this challene by following Dave Isbitski tutorial on CCT. I finally used the starterkit before going to chainlink CCT interface to crate my token. Learn't a lot!
Rust☠️❤️🦀
A mix of pain, satisfaction, and conviction. During my implementation of agent with rust, I really faced the following challenges!
Implementation of Bedrock runntime Model for the agent
This was a pain. I read documentation on implementation bedrock for rust. The documentation wasn't clear. I can BOLDLY say the best way for a technology to be adopted is by having multiple implantation examples. >
Multiple Examples and Demo project showcase shouldn't be underrated. It's the documentation.
Structuring of Knowledge Base
Using Pro models are great! But prompting can't overemphasised! AI understands Json structed data over Markdown prompt. It was hard for the ai model to follow my agentic guidelines. I use injected 💉 and instruction prompt in a form of CoT(Chain of Thoughts. I call it programmable chain of thought guide. My model followed all the reasoning steps to process each message and generate response either for calling tool or normal smart response to keep the user engaged.
Agentic Tooling 🔧
While there are few documentation and examples for rust, chainlink public external api was used. To make
get_price
andget_market_cap
tool. I had problems with async in rust and had to use tokio runtime for each async function since the main entry function isn't an async and await.Implementation of contract tools was a nightmare. I used ether_rs library to implement onchain tools that enables users make calls to smart contracts with just their chats.
I tried to adopt the
singleton
design pattern to prevent overhead for each function calls due to establishment of new connection. It was hard.To succesfully impement contract based tools, I restructured of files to suit my implementation.
Telegram Bot
After implementing tools, creating parsers and filters for responses to the bot was a major challenge. I 😂 had to retake my regex classes. In summary, I solved most of my problems by watching multiple tutorials, asking AI such as deepseek for what I don't understand and reading documentation(The best.
cheat😅). It was a great experience.
Tracks Applied (5)
Onchain Finance
Cross-Chain Solutions
Build the Future of Web3 x AI with Amazon Bedrock
AWS
AWS Credits for all Hackathon winners and runner ups
AWS
Avalanche Track
Avalanche

