@Knowledge_JOi
iAccount based inNigeria!
About this account
- Account based in
- Nigeria
- Connected via
- Nigeria App Store
! X says this location may be affected by a proxy or VPN.
Account-level information from X, not a live location or the device used for a specific post.
Full stack web & blockchain developer
Onchain
Joined July 2019
- Tweets971
- Following558
- Followers643
- Likes20.5K
Knowledge retweeted
We went to the biggest marketplace in Africa to talk about @gamdom
It was a tough task but what is a tougher task than @stevewilldoit getting @gamdom to #1
Here is our entry for the #gamdom100k challenge
Sign up with on with @gamdom
1love❤️ @gamdom_beekay @kingadukes
Knowledge retweeted
We just submitted NimDares for the @nimiq Apps Competition Cycle 2.
What if saying “I’ll do it” actually cost you something?
NimDares lets you:
→ Create a measurable dare
→ Stake NIM behind it
→ Complete the goal
→ Submit proof
→ Get your stake back or get slashed if you quit
You can go Solo, challenge friends in Team rooms, or join a public Arena.
I had an argument with a friend the other day and we decided to settle it with a dare. Whoever walks over 100 steps first wins.
Instead of just saying “okay, bet”, we could create the dare on NimDares, both stake some NIM, and actually have something on the line.
The interesting part: the app doesn't blindly trust the UI.
Your stake has to be verified on-chain before a dare becomes active, and settlement only happens after a proof verdict.
We also built screenshot-based verification and a GitHub proof adapter for developer commitments.
Built with Nimiq Pay + Next.js + Gemini.
This one was a fun problem to engineer around: incentives, proof, escrow, and real on-chain state all in one Mini App.
Try NimDares:
nimdares.vercel.app
Code:
github.com/Saber1Y/NimDares
Full demo: youtu.be/1uijncjvNTQ
#Nimiq #NimiqPay #BuildOnNimiq
Built w/@Knowledge_JO
CC: @nimiq @miniappscomp
This video is larger than Cloudflare's 512 MB cache, so it can't be played through. More donations are needed to cover a larger cache. Donate
We’re definitely taking this beyond the comp
We’re building NimDares in public for the @miniappscomp competition with @Nimiq.
NimDares basically turns personal commitments into on-chain dares inside Nimiq Pay. The user flow is simple:
1. Create a commitment and define clear acceptance criteria.
2. Choose a verifier, such as AI vision, GitHub, or Strava.
3. Select a stake and approve the native Nimiq Pay payment sheet.
4. The NIM stake moves into escrow on testnet.
5. Submit proof before the deadline.
6. Verification determines the outcome.
7. Winners receive their payout. Failed commitments are routed into the slash pool or charity destination.
NimDares has three modes:
> Solo
A private commitment between you and yourself. Complete the goal and reclaim your stake. Fail to provide valid proof and the stake is slashed.
> Team
A private room shared through an invite code. Each participant funds their own seat, submits individual proof, and valid participants share the slashed pot.
> Arena
A public commitment room listed for anyone to join. Participants compete under the same criteria, deadline, escrow, and verification rules.
The testnet build now includes native Pay funding, real NIM escrow transactions, AI/API verification, room mechanics, automatic settlement, payouts, and slash-pool routing.
We’re looking for early testers to try the full flow and give honest feedback on the payment experience, proof submission, and room design.
More progress and testnet demos coming soon.
@miniappscomp @Nimiq #BuildInPublic #Nimiq
Knowledge retweeted
We’re building NimDares in public for the @miniappscomp competition with @Nimiq.
NimDares basically turns personal commitments into on-chain dares inside Nimiq Pay. The user flow is simple:
1. Create a commitment and define clear acceptance criteria.
2. Choose a verifier, such as AI vision, GitHub, or Strava.
3. Select a stake and approve the native Nimiq Pay payment sheet.
4. The NIM stake moves into escrow on testnet.
5. Submit proof before the deadline.
6. Verification determines the outcome.
7. Winners receive their payout. Failed commitments are routed into the slash pool or charity destination.
NimDares has three modes:
> Solo
A private commitment between you and yourself. Complete the goal and reclaim your stake. Fail to provide valid proof and the stake is slashed.
> Team
A private room shared through an invite code. Each participant funds their own seat, submits individual proof, and valid participants share the slashed pot.
> Arena
A public commitment room listed for anyone to join. Participants compete under the same criteria, deadline, escrow, and verification rules.
The testnet build now includes native Pay funding, real NIM escrow transactions, AI/API verification, room mechanics, automatic settlement, payouts, and slash-pool routing.
We’re looking for early testers to try the full flow and give honest feedback on the payment experience, proof submission, and room design.
More progress and testnet demos coming soon.
@miniappscomp @Nimiq #BuildInPublic #Nimiq
Big ups Dedust
CPMM v2: new pools on DeDust🔸
Yesterday marked three years since we began building DeFi in TON — creating user-friendly and valuable products for both users and builders.
Over the past few months, we’ve been working on a new type of liquidity pool — more rewarding for token creators while remaining just as convenient for traders. Today’s release addresses one of the key challenges for all liquidity providers: separating trading fees from the core LP position.
The current model presents two main issues: it's hard to track how much you've actually earned, and token creators have no way to receive trading fees from locked liquidity.
The new CPMM v2 pools solve both. Fees are collected and claimed separately — even if the liquidity is permanently locked. For now, this applies only to tokens migrated from our Uranus launchpad on @x1000_finance, but very soon it will be available for any token directly in the DeDust interface.
Another key feature is the Creator Fee — a portion of the fee credited to the specified address and available to claim. It works like a tax, but without the need for a custom token contract and the compatibility issues that usually come with it. The address is set when the pair is created, and for now, this setup can only be done by us upon prior agreement.
Sincerely,
DeDust Team🔸
TON vs Solana in 2025 — no fluff, just facts.
Average fee last 7 days:
→ TON: $0.008–$0.03
→ Solana: $0.02–$0.25 (spikes to $2+ during memes)
Peak TPS (real mainnet, not testnet):
→ TON: 104,715 (Oct 2025)
→ Solana: ~3,000 sustained (65k was a 2021 stress test)
Dev language:
→ TON: Tact (Rust-like, safe) or FunC
→ Solana: Rust only (memory bugs = millions lost)
Built-in distribution:
→ TON: 900M Telegram users, 1-click Mini Apps
→ Solana: …Phantom wallet download
New to TON? Here’s the one concept that makes everything click:
Sharding = TON splits itself into thousands of mini-chains (“shardchains”) that process transactions at the same time.
Result → 100,000 + TPS today, not “someday”.
Ethereum vs TON Blockchain: A quick intro & key differences! 🚀
Ethereum: The OG smart contract platform launched 2015 by Vitalik Buterin. Powers DeFi, NFTs, DAOs. Uses Proof-of-Stake (PoS) since 2022. #Ethereum
TON: The Open Network, originally by Telegram (Durov bros). Designed for mass adoption, super-fast & low-cost txns. Also PoS. #TON 🧵
Ecosystem & Adoption
Ethereum: Massive dev community, $400B+ TVL, EVM standard. Most dApps live here.
TON: Telegram-native (800M+ users), mini-apps, TON Wallet in TG. Growing fast in games (Notcoin) & payments.
💎 Introduction to TON Blockchain.
In today’s video, I briefly went over TON’s history, what makes it different from other chains, and it’s focus on fine user experience.
TON Smart contract development 101
On Ethereum, contract A can retrieve the state of contract B by calling its getter functions.
On @ton_blockchain, every contract is closed. Meaning contract A cannot call contract B’s functions including its getter functions.
The only way to read the state of contract B is to send a message from contract A. Contract B then forwards back the requested data included in a message.
To build on @ton_blockchain :
- Go through the documentation - docs.ton.org
- Learn Func/Tact
- Work with blueprint SDK for development and testing
- Use tonconnect for integration with react apps
Literally, you can start from here and build crazy stuff.