Blockchain Devs Stuck on Multi-Chain Deployment
Developers building on blockchains face significant challenges coordinating and deploying code across multiple chains. This involves dealing with address management, compatibility issues, and complex architectures, leading to increased development time and potential vulnerabilities. The need for standardization and simplified deployment processes is a recurring theme.
SOURCES (60)
“Yeah, it's a really good one if you are unfamiliar with the subject. Glad it was helpful”
“Bank of England digital pound lab entered phase two. Polygon labs, nobo finance and dun & bradstreet joined to test cross border SME trade finance, one workstream on reusable credit profiles via polygon smart contracts, another on invoice factoring where exporters get paid in stablecoins and importers settle in digital pounds It's still sandboxed with no real money moving, and BOE hasn't decided if the digital pound launches at all (decision comes after 2026, needs parliament to pass”
“ETH-AVM Light Client — a trustless Ethereum→Algorand light client. Verifies real Ethereum receipts/logs on-chain via Algorand smart contracts, with an optional zero-RPC-trust mode (BLS sync-committee verification anchors the real Ethereum state root on Algorand, so you're not trusting any RPC provider's word for it) https://github.com/m-reynaldo35/eth-avm-light-client A trustless way for AI agents to confirm a transaction on eth for a predictable fee and fast confirmation times on algora”
“it's encouraging to see actual functionality being tested, but I agree that a working testnet is only one step and the real challenge is successfully delivering and sustaining it on mainnet.”
“I’m a backend/blockchain dev working mostly with TS/Node, Solidity/EVM and Rust/Solana. I’ve already done stuff around RWA tokenization, vesting/NFTs, cross-chain swaps, wallets, NFT ecosystem, etc. Now I want to build something more towards DeFi/protocol engineering , rather than projects that are basically API integrations + a smart contract. I’m also open to going completely outside my current stack like something in Rust, low-level backend/infrastructure, or a protocol I haven’t worked with”
“Fork and no account I guess, but Google login whatever. Look I've spent 110 BILLION tokens on one project. The code base is 1.5 million lines of code (with ponytail!) across multiple languages. I've used every best model out there in every which way. I could not for the LIFE of me get the last 5% done due to some insanely complex bugs. As I built over the year I've kept IMMACULATE documents about every little part and how it should work. In addition I've kept absolutely rigorous”
“BoE are not “doing this”. Chainlink are using the BoE test lab to try to demo their solution to the BoE. BoE have not contracted Chainlink to provide anything or agreed to productionize their solution.”
“I tried to make solidity devs life little easier who integrate automation in their smart contract. Honestly i don't know if there is such a tool exist or not but i thought by making easy to use tool can help developers. So the problem is that chainlink automation is gonna deprecate, instead they recommended to user their CRE. also if anyone developing smart contracts using keeper service it can be little confusing to those who are developing in local setup. like anvil. If someone is developi”
“Agreed, but we also need to make sure we don't lose the decentralization aspect, for the sake of regulation compliance.”
“I'd like to know if you chose to white-label or use a custom fork. Did the development overhead make sense? submitted by /u/ClaretTovi [link] [comments]”
“no sequencer, and that part isn’t a design choice — it’s structural. there’s no second system to sequence. the contract is an ordinary MW transaction: the multisig is the kernel signature every payment already has, the condition is an adaptor point shifted onto the nonce, the timeout is the lock_height field consensus already validates. no L2, no validators, no VM, nothing to centralize. on trusted hardware, the honest answer has a caveat and i’d rather give it than have you find it later. the c”
“According to me as well. Tokenization of real world assets is the biggest and best usecase for blockchain tech so far.”
“Hey everyone, I’ve been heads down in a 3-week sprint building out Alchemy Guild (currently submitted to the WTF!! Hackathon). It's a gasless DeFi yield protocol on Arbitrum Sepolia, and I need some fresh eyes to stress-test the contracts and poke holes in the architecture before I even think about a mainnet deployment. The Stack / Architecture: Account Abstraction (Pimlico): I wrote a background bot that taxes the protocol yield to automatically refill our Paymaster, making the entire dApp”
“Watch one real transaction on their screen instead of asking people to describe the process. Real data, live system, no slides. Described processes hide the exceptions and workarounds that break a fixed bid build later. One walkthrough per role usually surfaces more than a day of open questions. It also gives you something concrete to react to. Then bring a rough draft of the future state into the next session. People correct a wrong diagram much faster than they invent an answer. Close each ses”
“They aren't talking about transactions to send money, they are talking about tokenization of financial assets (treasuries, bonds, stocks etc). That's the use case which will dwarf all others, and as you can see from the links I shared above, it's already starting.”
Jumper dot xyz is my go to. Squid router is solid as well
“Recently found out an old coworker is working on a research project called Project Abundance and figured some of the builders here might appreciate it. It is basically a solo dev trying to build a new blockchain architecture from the ground up to solve the blockchain trilemma. What actually caught my eye is that there is zero token hype or marketing. It is just someone quietly building in Rust and writing really honest dev logs about the process. He talks a lot about compiler optimizations, buil”
“Yea I pump out working features that are QA tested at work and then I run those same loops for my side project. 🤷♂️ idk anyone that’s not working like this. To be fair I learned a substantial amount of system architecture that I personally wasn’t aware of. Get with the times or just be unemployed.”
“Agreed, still need to know technical jargon and knowledge to make the complex workings to work.”
“They aren’t just tokens representing cows, the cows are wearing tracking collars that take their vitals and all of this is recorded on the blockchain. So instead of owning a piece of paper that says “I own a cow and it lives on a farm somewhere and I hope it’s alive” you have a live proof of ownership that digitally tracks the location, health and well being of the investment. Wave of the future, Dude. 100% Electronic! -Jackie Treehorn”
“Working on Aevum Protocol — infrastructure for autonomous AI agents on Ethereum. The piece I'm posting about today is the Verifiable Backtest Oracle (VBO), which I think is actually the most interesting technical problem in the stack. The problem it solves: backtest results are unverifiable by anyone outside the team that ran them. Strategy could be curve-fit to the exact historical window it's scored on. The code shown might not be the code that actually ran. "Out-of-sample" r”
“Hi, We’re building Cradle, a proptech AI rental discovery platform token gated using payments in USDC on the Solana blockchain. Kinda like Twitter meets Airbnb but with some blockchain and AI in the loop. A few things to note: API calls are running on free Render web services so might take a while for the server to get up. Shouldn’t load for more than a minute or so in case If you run out of tokens you can only buy more using USDC and Solana wallet extensions (Phantom and Solflare) . Its on deve”
“This is very interesting, I happen to be looking for a secure wallet, for the next generation Echo OS distribution I'm working on , I will try it soon, I will give feedback after a week of using it”
“Yeah stay on ecosystem, protocols that does not leave a stack trace, probably the automated bundle.”
“Well i do have genuine expertise in that. Deployed multiple tokens and for past 3 years working on tokenization. It is a real skill.”
“Seriously, thank you for taking the time to write this out, this is hands-down the most actionable breakdown I’ve received yet. Using CodeQL's codeFlows as a trace baseline and splitting evaluation into Graph / Answers / Patches makes total sense. Also completely spot on with the product vision: anchoring the entire UI around the CodeQL alert (showing the trace path, evidence, and candidate diff together with an opt-in PR button) builds way more developer trust than auto-opening PRs blindly.”
“I used ChatGPT to help tighten the wording of the post. The project idea, hardware, and testing are my own and I’ll be building and documenting the demo myself.”
“If your goal is automation without giving us custody, that's basically the direction I ended up taking as well. Aave. Yearn, and EtherFi all have options worth looking at, but I personally prefer EtherFi because the vaults stay non custodial while handling most of the management for me.”
“I keep seeing crypto projects describe transparency through dashboards, documentation, blog posts, or promises of future reporting. But from an architectural perspective, those mechanisms still depend on someone choosing what to disclose. A system may expose its wallet balances while leaving its actual control structure difficult to understand. For example: – Are visible funds meaningful if upgrade permissions or admin controls remain opaque? – Does a multisig materially reduce trust assumptions”
“Half the time folks are just flexing their infra budget. A basic subgraph handles 90% of queries without burning cash.”
“i mean, ”shared ledger” and ”similar algorithm” could be doing a lot of work in that statement.”
“They are using Chainlink, which doesn't change much does it? It may benefit Chainlink investors, I suppose.”
Looking for an experienced Solidity/web3 engineer to help fix a current integration issue. Deadline is tight, so I only need someone who's genuinely done this before — not looking to train anyone…
“That's a solid approach - offloading everything to the client side keeps your attack surface small. Would be curious if you hit any pain points with iOS limitations or if syncing state across devices became annoying.”
Hey everyone, I’ve been working on a project that tries to solve one of the biggest issues in DeFi right now: unwarranted liquidations caused by temporary exchange flash-crashes and market noise. Most…
Hey everyone, I’ve been working on a project that tries to solve one of the biggest issues in DeFi right now: unwarranted liquidations caused by temporary exchange flash-crashes and market noise. Most…
“Agreed. The market, not the protocol brand, is the right unit of analysis. I’d put oracle design and exit liquidity ahead of governance for exactly that reason: immutability limits admin discretion, but it cannot fix a stale price or create liquidators when the market is stressed. Curator history then determines whether the vault layer adds discipline or concentration risk. The 1% slippage test is a useful next step. It just needs a defined stress window, chain, asset pair, and whether we’re mea”
“Hi everyone, I've been working on a protocol called GeoProof and wanted to get feedback from protocol and smart contract developers before moving further. The problem we're trying to solve is fairly straightforward: Blockchains are excellent at verifying digital state, but they're not designed to verify whether a real-world event actually occurred. Current approaches usually depend on GPS, timestamps, centralized APIs or oracle networks. In practice these often become single points o”
“"Which projects are doing it right?" The one that this sub hates more than haters hate themselves :D”
“One of the biggest issues in crypto is liquidity and users being spread across multiple blockchains. Cross-chain solutions are trying to solve this by allowing assets and data to move between ecosystems like Ethereum, Solana, BNB Chain, Polygon, and others. Supporters believe this could accelerate DeFi and NFT adoption, while critics point to bridge hacks and security risks. Do you think cross-chain infrastructure is the future of crypto, or are the security concerns still too big? Which project”
“Hexens kicks off July 27. Kasper Zwijsen is leading. Before he opens the repo, I want to be transparent about what the internal process actually found and fixed, and what we’re handing to him with a known-limitations flag attached. What the internal rounds caught (41 findings total): Highs (resolved): • AEVToken was missing ERC20Votes snapshot voting — DAO proposals could use current balance instead of snapshot balance, enabling flash loan attacks on governance • AevumDAO execution target had no”
“Built a pipeline that ingests every PairCreated / PoolCreated on Uniswap v2/v3/v4 and scores the token before its first block of trading. Signals: LP lock status, a simulated sell (eth_call + stateOverride), deployer lineage (funding wallet + past tokens via trace_filter), holder concentration. Five months of mainnet data: 104,767 tokens scanned, 62,321 flagged as scams (~60%). 40,953 scam pools. Buyers net-lost 30,000+ ETH to them. 422,625 distinct wallets got drained (bought, then could not se”
“Everyone talks about Ethereum, Solana, Base, and Avalanche, but I'm more interested in platforms that don't get nearly as much attention as they probably deserve, and maybe some that are better than what I just mentioned. Mainly wondering what has exceeded your guys expectations this year. submitted by /u/Quant3k [link] [comments]”
“Centralized & Permissioned Nodes 🚨 The relay nodes are not required to use algorand. P2P nodes don't use them meaning there is no dependence on any centralised infrastructure and censorship is not possible. Python as language instead of Cadence 🚨 Python has approx 15 million developers. You can also use Typescript 13 million developers Flow blockchain uses Cadence and I don't think any one else does. Its very niche and unadopted. Algo holds majority of supply 🚨 False, around 10% h”
“For all use cases and for everyone to have a time stamped, verified proof of event based record of events in the advent of the ai era. If you can’t understand why that’s important, you don’t understand what you’re invested in. If you can admit that, you’re ahead of 70% of all crypto investors.”
“Nice post! Personally I have found the best overall option to be building custom analytics pipelines with scalability and future additions in mind. It is entirely project dependent but relative to the costs you'll incur in any case when building DeFi/crypto-related projects such as servers, APIs, RPCs, etc, the cost of building and running a custom analytics pipeline is well worth the price (And in some cases can even save you money).”
“For which uses cases though and for what users? Crypto has been "positioning" for 2 decades.... Which end users are requesting these changes and will ultimately decide if they are sufficenat and have solved whatever problem they currently have?”
“Ive tried small bits of moving out of pulsechain just out of curiosity. That and me being able to read code. I definitely stay within pulsechain blockchain best layer 1 I have encountered so far. The code for other stuff is setup so bad with potential threats.”
“Been heads-down building Aevum Protocol — on-chain infrastructure that treats autonomous AI agents as first-class economic participants rather than just wallet addresses being puppeted by a script. The core problem I was trying to solve: agents that transact on behalf of users have no persistent, verifiable identity or reputation. Every agent starts from zero trust every time, and there's no on-chain record of whether an agent has behaved well historically. The stack: - AgentIdentity — on-ch”
“The problem: Single-authority customs approval is a rational bribery target. One official, one decision, predictable cost. The incentive structure is broken by design. Game theory layer: UBLP changes the incentive structure before any cryptography kicks in: - 2/3 committee threshold required (Byzantine fault tolerant) - Committee members have conflicting interests by design - Any anomalous signing pattern is visible on-chain Corrupting the system is no longer a cost-benefit calculation — it beco”