Web3 Devs Fighting Broken Blockchain Tooling

“[Feature Request] Native Bitcoin Core Integration for Wallet Synchronization Summary Add an option to connect Bitcoin Safe directly to a user's local Bitcoin Core node for wallet synchronization and transaction verification. <br Motivation Bitcoin Core users don't need to connect to other nodes via Bitcoin Safe to get blockchain information. <br Possible Implementation Approaches Option 1 (Direct Core RPC / BDK Integration): Query blockchain data directly from the user's Bitcoin Core node via RP”

“Thanks! Yes, it's draft acceptance. Not plain MTP: V4.1 ships its own draft head (DSpark), and the engine verifies up to 5 drafted tokens per step. Mean tokens per step (greedy, 512-token replies, counting the 1 token the main model always adds): Prose: 1.98 (58% of drafts accepted), 59 tok/s Code: 3.60 (68%), 85 tok/s JSON: 4.73 (80%), 104 tok/s Task eval: agreed, not run yet. It's next on my list: gsm8k + IFEval with lm-eval-harness. The full model doesn't fit on two Sparks, so the”

“I’m the solo dev of txMonitor . It sends push alerts when an XRP Ledger wallet you watch sends or receives funds, or when its security settings change (Regular Key, multisig, master key). Who I’m looking for: anyone with an XRP wallet (Xaman, Ledger, exchange withdrawal address, anything). You only add the public address. No keys, no seed. What I’d love from you: Add a wallet and tell me if onboarding was confusing Send yourself a small payment and tell me how fast the alert arrived An honest Pl”

“What it is: a mobile app that watches XRP Ledger addresses and sends push notifications for payments and security-relevant account changes. Why: on the XRPL, a common move after someone compromises a wallet is to set a Regular Key so they keep control. Most people never notice until it’s too late. I wanted an alert the moment it hits the ledger. Stack: Expo / React Native, Apollo GraphQL, a Node backend listening to the ledger, OneSignal for pushes, Firebase for analytics and crash reporting. Wh”

“Use https://conflux.finance/ next time, they have a gas fees integrator in the bridge and cheapest prices, it's ultimately the place to swap and bridge [re: swapping tokens across different blockchain networks and i'm stuck halfway]”

“Agreed, token approvals are easy to overlook. Checking permissions and revoking unused ones is a simple step that can help reduce risk. [re: What Frustrated You Most When Using DeFi?]”

“Token approvals were the part many beginners underestimate because a transaction can succeed while leaving ongoing permission behind. A good first-use checklist is: verify the network and contract, simulate or test with a small amount, set a tight slippage limit, and review or revoke approvals afterwards. [re: What Frustrated You Most When Using DeFi?]”

“An on-chain basket can reduce single-token selection, but it adds issuer, custody, liquidity and rebalancing risk. Before choosing one, verify the product is still live, what backs each token, redemption mechanics, fees and whether market liquidity can hold near net asset value. I’d compare those before comparing past returns. [re: Any "index fund" style token for a top-10 or top-20 basket?]”

“the no-loops-over-3-days bit is the real headline imo. most 2-bit quants i've tried start repeating themselves once the agent loop runs long [re: Qwen Flash Next potential SOTA Q2 nobody talks about]”

“True, but if we can't fix that we're basically just rebuilding bank intranets with extra steps. [re: Does private tokenization fragment RWA liquidity?]”

“clicked the link and it's just an ip address, not touching that. but the idea sounds useful if it actually surfaces the stuff morpho buries, especially borrower health and liquidatable debt. that's the kind of thing you only find out about after you're already down bad question 3 is the real one, alerts would be useful if they're not pinging me every time a whale sneezes. i'd set a threshold and forget it [re: I’m building a risk-monitoring dashboard for Morpho vaults—would t”

“The honeypot check alone makes this worth a look, too many people just ape into tokens without even checking if they can sell. Joined the group, will kick the tires on some Solana garbage coins I've been tracking. [re: RugRadar – check crypto tokens for scam & rug-pull red flags (need 12 testers, will test yours back)]”

“I’m not gonna rely on something that is actually 1000 times more expensive. It’s NOT sustainable. Period. People are burning $3000 worth of tokens while paying $20 a month. The bill is coming. [re: Linus Torvalds: I don't understand this whole idiotic concept of "don't use AI for X".]”

“Most people treat keeping assets in their own wallet as total control by default. But in volatile markets like meme coins, where tracking liquidity pools manually is practically impossible, the temptation is to delegate the constant checks to an automated setup. Holding your keys and granting execution permissions are two very different things. Read-only tracking for contract events or wallet activity carries almost no downside. The boundary blurs the moment you tie those checks to automatic app”

“use 1 hot wallet/burner for testing new apps, fund it with enough so you can test. use if for everything testing. DO NOT use a hot wallet (software wallet with seed phrase you write down) as your main wallet. That's way more likely to lose you all your coins then any burner would help you. [re: Is a burner wallet worth the hassle?]”

“Evm::transact consumes Recovered<TxEnvelope , so every simulation entry point has to construct the signed transaction domain type and mark it recovered without a signature: The repo itself does this dance in three places: the evm2 test helpers, the EEST harness — which pulls in alloy rpc types eth and drives TransactionRequest::build consensus tx plus a five arm TypedTransaction match just to produce a RecoveredTxEnvelope from loose fields — and the fuzzer in cli/src/fuzzer/case.rs , which repea”

“I like that you're letting people test it with sample data too. Makes it easier to get feedback before committing to importing real transactions. Curious to see how it develops. [re: Looking for ether.fi cardholders to test a spending dashboard (no sign-up, your file stays on your device)]”

“https://solanabeach.io/ 400ms with 680 validators. [re: Vitalik Says Ethereum's ZK Speed Race Is Won and Priority Shift Fully to Security]”

“The worst part is having money on a chain and still being broke because you can't pay the gas fee [re: swapping tokens across different blockchain networks and i'm stuck halfway]”

“Btw, is anyone going to fix the Litecoin Uptime Tracker? There was a massive outage and reorg on April 25, 2026 due to that consensus bug. AI keeps hallucinating its uptime because of it. [re: Happy Cake Day Litecoin 🎂]”

I’ve been working on a tool for finding unclaimed crypto across bridges, and while digging through the data, I came across some numbers I thought were worth sharing. Across official bridges between…

“The 10% fee on top of usage costs is the part that would make me pause, not the trust issue. For side projects just testing an idea, every dollar matters and that markup eats into the experiment budget fast. Could see it working if you bundled in something like aggregated rate limits or a dead simple way to track which project is burning the most cash, that shared usage view is the real hook for me [re: I'm building DreamTune Labs to give AI side projects one shared balance across models and too”

“eth call style simulation needs the transaction environment validation checks off: nonce, sender balance, fee charging, base fee, block gas limit, priority fee, EIP 3607, and chain ID. Because these are runtime EvmFeatures , every consumer strips the same eight bits by hand after Version::new . We keep three such copies downstream and the list is easy to get subtly wrong — dropping EIP3607 while keeping the rest, for instance, changes which transactions a simulator accepts without anyone noticin”

“So move from Taproot to Native Segwit still err?? [re: Coinbase: Working Together on Bitcoin’s Post-Quantum Readiness]”

“yes they do, have you even read the protocol? there is a master key so it's not decentralised at all. Read the fucking smart contract or have AI explain it to you. Stop being so gullible and start doing your own research. https://github.com/AcronymFoundation/anvil-contracts ?@title Collateral Vault providing authorized Collateralizable contracts access to collateral via the ICollateral interface. * * @notice Approved Collateralizable contracts may reserve, claim, modify, pool, and release co”

“Smart contract exploits get most of the attention, but plenty of wallet drains still come down to pretty basic scams that trick people into clicking, copying, or sharing something they shouldn’t. I’ve seen the ~65% figure mentioned, and the common attack methods are surprisingly low tech. One example is address poisoning, where scammers send tiny amounts to your wallet so a lookalike address appears in your transaction history. It’s easy to copy the wrong one later without noticing. Fake Zoom in”

“Looking at the images here, there is zero attempt at security here from the ledger team. They’re using an MCU (ST MCU with Cortex M4 core) that doesn’t have any meaningful security features (ie, no secure boot, no differentiation between trusted and user mode operation - features the newer Cortex M33 core supports and newer ST parts implement). So there’s no way to guarantee that the software running on this has not been tampered with.There is no physical tamper detection either. No tamper pads”

“12 people have tried it so far. one of them got stuck at the deposit step because the test usdc button was sitting up in the top corner and he couldn't find it. didn't see that coming, glad someone said it. it's a perp dex on solana where the order book is public but your position size and liq price aren't. devnet only, test funds, takes about 5 min. open a trade, close it, and tell me what felt off, even small stuff. PRIVORA - BUILD ON SOLANA submitted by /u/Big_Resi”

“Between public node operators stealth-gating eth_getLogs behind archive tiers, arbitrary chunk-size caps, multi-chain cursor re-winds, and front-running bots eating standard arbitrage strategies alive, building scalable apps on transparent EVM chains feels like a constant battle against infrastructure debt. When you look at why these failure modes happen, public mempools exposing transaction intent, lack of native state confidentiality, and fragmented cross-chain bridging, it highlights why arch”

I've been working on a tool called FreeMyFund because I noticed that people can sometimes leave funds unclaimed after bridging to another chain, and figuring out how to get them back isn't…

“I made a short tutorial showing the full flow of a first blockchain transaction in TypeScript: create testnet wallets, build a payment, autofill the transaction, sign locally, submit it, and verify the validated result. The example uses XRPL and xrpl.js, and I also explain Fee, Sequence, LastLedgerSequence, tesSUCCESS, and delivered_amount. I made the video myself. If you work on blockchain dev and like end-to-end walkthroughs, it may still be useful even if you do not use XRPL day to day. Video”

“Personally, I skipped time windows and matched on-chain instead, any wallet that touched a quest contract or claimed a KOL referral NFT before staking counted, and aggregator routing stopped mattering, since the wallet history shows it anyways [re: Attribution for stakers when half of them come through aggregators]”

“It warns you that the wallet is restricted. It won't allow a withdrawal. [re: Using Lighter dex to determine if a wallet is clean]”

“Maybe not every wallet, but I definitely think more should offer it. I've been using Tangem for a couple of years and love having different features in one app instead of constantly moving funds around. They're also introducing payments with Tangem Pay, which I'm pretty excited about. It's nice to actually use crypto for everyday purchases rather than just hold it 😅 [re: Should every crypto wallet have a built-in payment feature?]”

“no, and the reason is attack surface. a wallet’s job is to hold keys and sign things, and every feature you bolt on is more code between your seed and the world. the clean separation is a hardware signer, a minimal interface, and a separate spending pot you accept is hot [re: Should every crypto wallet have a built-in payment feature?]”

submitted by /u/GeologistNo5580 [link] [comments]

“Does it make sense to get this with all the hacks going on? Will this absolutely secure me? My post must have 100 characters. submitted by /u/KillALil [link] [comments]”

“im watching the OOBE Steve Capital Management protocol to better manage these issues. [re: How do AI agents drain crypto wallets?]”

“Being able to verify a transfer on a block explorer is useful. It still doesn't show whether the issuer holds enough shares or whether you have any right to redeem them. Those need their own evidence. [re: Trading tokenized stocks isn't the same as owning stocks]”

“This is probably one of the biggest UX problems in DeFi right now. Bridging, approvals, wallet switching and gas management can turn simple actions into a whole workflow. That’s also why simpler crypto use cases, like buying gift cards directly with crypto , can feel so much more practical - less setup, less friction, and a clear end result. [re: why does moving crypto have to be a part time job]”

“feels like this creates a weird incentive where launching child tokens becomes the main use case for holding the parent. thats fine until the child launches slow down and the parent loses its bid. circular demand is fragile tbh [re: Soo Pump communities can launch their own mini economies now]”

“If it's tokenized staking you can just send everything to a newly generated address on the same device/private key. But yeah, we need some solutions on the baselayer. Which they are already working on anyway. These problems are really only for people with 50+BTC worth of tokens. As it takes an enormous amount of calculation power, they'll obviously go for the biggest wallets. And Satoshi has a bunch of 50BTC addresses. [re: Europol urges early action to protect cryptocurrencies and sensi”

“tossing a bit into a liquidity pool on a new L2 that's still in testnet, mostly out of curiosity. the incentives are laughable but the tech underneath is slick, so i'm in purely for the chaos. keeping the rest parked in a boring stablecoin vault until something cracks. [re: Weekly DeFi discussion. What are your moves for this week?]”

“Exactly, Just because transactions are onchain does not mean everyone should be able to see what you're doing with your money. [re: Would you be comfortable with anyone tracking your tokenized stock portfolio?]”

“If sending $100 requires someone to understand networks, gas fees, seed phrases and transaction approvals, the UX still isn't there 😂. Security shouldn't depend on every user being a cybersecurity expert. Better warnings, readable transaction previews and safer recovery options would make a real difference. [re: Crypto has a problem we keep calling “user error” instead of actually fixing.]”

“Interesting, thanks for the correction. Seems in both cases, the lesson is not to take a code from anywhere trusting that it's legit, but instead, generate one ourselves. I guess the next little arms race is figuring out which 'random generator' a user sourced their code from. Time to break out the lava lamps. [re: At this point, does “Not your keys, not your coins” still hold? It seems almost safer to leave your crypto on an exchange.]”

“Someone in this sub did a token check / audit. Notion has a very high burn rate. Claude / chatgpt can link to it. I personally use chatgpt. Claud is great but it's was hitting limits [re: Smallest / cheapest LLM available in Notion right now?]”

“I agree with you that institutions would need privacy features to take tokenized stocks seriously. There are some solutions that tackle this. But the bigger question is whether they can offer enough privacy without compromising compliance, since regulators still need some visibility. I think options like private RFQs and shielded transactions help with privacy, alongside proper compliance controls. Injective is working on both. Its recent Meridian upgrade introduced compliance controls for regul”

“Authorized reseller or not, a middleman between a hardware wallet manufacturer and end user is an additional vector for tampering. I'm not saying its OK that an approved vendor is apparently compromised, only that personally, I'd take pause and assess that risk before transferring $6.6mil to my hardware wallet. That said, Ledger has been a shit company for some years now and should be responsible for returning the bitcoin to this user. I'm sure a lawsuit is incoming. [re: After $86M”

“There are technical steps these electronics manufacturers can take to reduce risk tho. Ledger is the worst offender, because the user literally cannot verify anything at all, and is 100% forced to trust Ledger. Open sourcing the device and building steps to allow cryptographic verification of secure enclave and runtime would make these attacks a lot harder. [re: Trader Loses $6.6 Million in Bitcoin After Buying New Ledger Wallet]”

“The problem with this license change is that it is unenforceable, now that developers believe they can vibe-code their own.Only a matter of time until we see "OpenWarden", just like we saw the migration from Redis to Valkey.But let's be honest. "enshittification" here really means "I don't want to pay for my tools and I want it completely for free forever."Just look at the reactions towards the single UI change made in Firefox on HN [0] and already the complaints are there. Even if you charge yo”

“Yeah- we know. The guy trying to kickstart applications, on SOL and SUI, was trying to create a token and NFTs and some DeFi applications with each car. It’s still being built- as far as we know that’s not been abandoned but they’re redesigning the car to look more like the original DeLorean so it has been delayed. The partnership with Litecoin is different. They’ll accept Litecoin in payments for the cars They’re planning on starting a new Litecoin treasury 3. We have a treasury rn (LiteStrateg”

“I've been building a small Python tool that watches a wallet on BSC, Base, Ethereum, Polygon and Arbitrum and tries to answer "who is behind this transfer" instead of just showing what moved. The heuristics are simple on purpose: - Freshly funded wallet: the sender was created or funded recently, and the funding source looks like a private wallet rather than an exchange - Dormant wallet: no activity for 14+ days, then it suddenly sends - Coordinated buys: several wallets buy the sa”

“I'd prioritize security assumptions, oracle reliability and how the system behaves under extreme market conditions. Those problems become much harder once real money is involved. It's also worth studying the differences between DeFi infrastructure and products such as Moon's crypto price markets, since the custody and settlement models can create very different risks. [re: What Technical Challenges Should You Solve Before Building a DeFi Platform?]”

“quick context: this is devnet only. you connect a wallet, deposit test funds, place an order, and the fill shows public while the position stays private. if you want to try it, ask and i'll share the link [re: started building a perp dex on solana where your position isn't public, here's where it is now]”

“I think the infrastructure will stay crypto-native, while most user-facing products get absorbed into familiar fintech apps. Most people probably won’t care about vaults or settlement layers as long as payments and lending work smoothly. The challenge is keeping risks transparent even when the blockchain is hidden. Do you think fintechs will expose on-chain details for users who want more control? [re: Is DeFi Moving From Yield Products to Real Financial Infrastructure?]”

“That’s a fair point. The bigger change might be how people access DeFi rather than where the yield comes from. If users can benefit without managing wallets or understanding protocols, adoption could look very different. Do you think this will make DeFi more accessible or just harder for users to see the risks? [re: Is DeFi Moving From Yield Products to Real Financial Infrastructure?]”

“@AllRespondents: which tool you're using to perform those checks? Thanks. [re: What do you actually check before touching a token youve never traded before?]”

I got tired of staring at block explorers, so I built a small Python bot that watches a wallet and tells me who is buying, not just what. For every transfer it…