I built a fully decentralized chat app using GunDB with P2P messaging, end-to-end encryption, and zero servers.
Try the live demo: https://t.co/tX9OcLrx48
#Web3#DApp#GunDB#P2P#DecentralizedWeb#BuildInPublic
@ernDju Main concern isn't reentrancy here, it's trust and accounting.
The oracle has huge power, there's no dispute mechanism, and I'd replace transfer() with call(). Also consider zeroing payment state after payout/refund to reduce future accounting risks
@mira97300@VerityChainLabs That’s the direction Web3 needs honestly.
Combining AI analysis, on-chain reputation, transparency, and decentralized verification could help users evaluate risk before interacting with protocols instead of after exploits happen
@ShieldifyMartin@jpmorgan Exactly why security has to go beyond smart contracts now.
Better signer isolation, hardware wallets, multisigs, transaction simulation, approval delays, and stricter operational procedures are becoming just as important as audits
@SawaSwapHQ A good approach is starting small.
Use caps, limited liquidity, timelocks, and test the protocol with lower TVL first. Scale security and liquidity as the protocol proves itself
@sultanabaniks Solidity if you want to get into EVM, DeFi, and smart contracts faster.
Rust if you want lower-level systems knowledge and ecosystems like Solana.
I’d say start with Solidity, then pick up Rust later
@TammyBuilds Agree to an extent. Writing Solidity is easy, understanding what the EVM actually does with storage, calldata, delegatecall, and gas is the real shift.
That’s usually where security bugs start making sense too
@FB6917511963698 That’s why security can’t rely only on static analysis or formal verification.
You still need threat modeling, economic analysis, invariant testing, and real-world exploit simulations to validate the actual design assumptions
@DecentraMindDML Exactly. A lot of DeFi failures start before deployment, not after it.
If the protocol economics, admin control, or oracle assumptions are weak, no amount of frontend polish will save it
@AbhinavCha73015 Return values and balance assumptions.
A lot of integrations assume ERC20s behave perfectly, but some tokens don’t return bools, some take fees, and some rebase unexpectedly. That’s usually the first red flag I check
@AbhinavCha73015 Yeah, update order bugs are nasty because everything looks fine until the accounting drifts.
Seen staking contracts where users could deposit right before reward updates and earn rewards they never actually accrued. Tiny ordering mistake, huge payout impact
@CryptoBoil True, TWAP helps a lot, but on its own it’s still not enough.
I found combining it with oracle validation and deviation checks makes a big difference, especially against more sustained manipulation attempts.
Oracle manipulation is still one of the easiest ways to break DeFi.
Built a lending protocol and drained it via DEX price manipulation
Fixed with:
- TWAP
- Oracle validation
- Deviation checks
- LTV
How are you mitigating oracle risk?👇
https://t.co/iQcog6A0z1
#DeFi#Solidity