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)
“Centralized systems are going to be slow to adopt, but they will eventually adopt, and are in fact starting to adopt now, SKY protocol being one of the main networks being used by institutions. So while your information may have some correct facts, it is…”
“sorry about that :( But the code writing is much much closer to me than post writing :)”
“ICP is already doing what he plans to do. Chain key cryptography is the way. He said so himself before about ICP…”
“The thing I'd design for first is proving the watcher is still alive. I run a scheduled job that reads contract state on Base, and the failure that actually bites isn't a bad threshold, it's the job quietly dying or the RPC handing back a stale block. The user gets silence and reads it as "I'm fine." Someone upthread got liquidated by automation that failed exactly when it mattered, and that's usually the shape of it. Cheap things that help: a heartbeat on a schedul”
“Problem The generator and the host must agree on which field in each collection holds the block number. Today nothing carries that information from one to the other. Each side keeps its own copy, and they're kept in agreement only by hand. Generator side. Each chain's converter declares the mapping at runtime through DocumentGroup.BlockNumField ( pkg/chains/chains.go ). The mapping differs per collection: number on the Block doc, blockNumber on Transaction / Log / AccessListEntry / BlockSignatur”
“I have been working on a decentralized discussion board that is currently live on Polygon mainnet. I wanted to share it here because a big chunk of it is smart contract-based and I think the infrastructure might be something you find interesting to poke at. The short version of the architecture: Settlement layer: an upgradeable EIP-2535 Diamond on Polygon. It holds the governance token, reward distribution (POL + USDC), sub-forum registry (each sub-forum is deployed as its own minimal-proxy clon”
“I have recently gotten into EVM development using Foundry. Since it is CLI based I built a simple UI wrapper around it to manage the node and inspect transactions that I produce via the local dev node when it is running. I want to expand the utility of the tool to be a general transaction inspector for EVM based chains. Would be good compared to web based transaction inspectors in terms of privacy and having access to the local anvil node. I find it useful as not being an expert dev and wanting”
Hey ethdev, we've been working on Shinzō, a decentralized indexing system, and just opened our public testnet for Ethereum. Posting here because we want honest technical criticism and real feedback. The problem…
“What u/vladeta said works, add it twice under different names. One thing to watch from running this across a bunch of client stores: nothing tells you which store a tool call actually hit. We've had a global config quietly win over the project one and pull from the wrong shop. No error, just wrong numbers. So have Claude run a quick shop name query on each connection before any report and print it at the top. Cheap, and it catches the mixup every time. And if he mostly looks at one region at”
“I've been building an Ethereum JSON-RPC proxy to fix mediocre providers and allow node RPC to be tuned for different RPC workloads. I'd like to hear what you're building, how you are using RPC, and what you wish you could do with the RPC api/providers to make your apps better. submitted by /u/yachtyyachty [link] [comments]”
“also: if there’s no vote account or validator hardware, treat it as an economic participation tier, not Solana consensus infra. Different category, different risks.”
“Interesting to see Casper become the first non-EVM chain to plug into the T-REX setup. Maintaining compliance checks while moving assets across chains is a massive engineering hurdle, so it'll be worth watching how the ERC-7786 messaging holds up during this testnet phase.”
“India is reportedly piloting blockchain infrastructure to tokenize its $620B corporate bond market, with settlement using the RBI’s wholesale digital rupee. From Japan exploring tokenized securities to Hong Kong and Singapore building digital-asset infrastructure, Asia is increasingly moving beyond pilots and into real-world financial markets. The next phase of tokenization may be built in Asia. submitted by /u/cSigmaFinance [link] [comments]”
“Been building this for about a year. Started as a Telegram bot for sniping tokens and turned into a full web and mobile platform. The problem: trading across Solana, Ethereum, Base, and BSC meant a different tool, wallet, and chart for every chain. Charts that took 5+ seconds to load. Bots that made you paste contract addresses like it's 2021. So I built one place that does all of it. Real-time charts, holder data, copy trading off top wallets, and non-custodial wallets so I never touch anyo”
“I’m building a small authorization layer for Ethereum/Base applications and would value feedback on the API design. The problem I’m trying to solve is repeated wallet/token authorization logic in application backends: policy → verify wallet/onchain state → entitlement Current rules include: wallet allowlist ERC-20 balance ERC-721 ownership/balance ERC-1155 balance AND / OR composition One design decision I’m especially interested in feedback on is failure semantics. A wallet that conclusively fa”
“AI was used first to help me set everything up, and then i asked it to summarize what we did and help me draft this question, english isnt my first language so its easier for me to ask ai to write it - but its completly my own question and not for spam or anything, i actually want the answers to this”
“Hey everyone, I’m learning Web3 and researching blockchain/wallet intelligence. For people who actively track wallets, whale movements, DeFi activity, or on-chain data: What tools do you currently use? What’s something you wish those tools did better or could automate for you? Not selling anything. I’m trying to understand the problems people actually have before building anything. submitted by /u/PandaTemporary8433 [link] [comments]”
“Depth, without hesitation, and here is the reasoning. For certificates you have closed the full loop: Renew, Deploy, Reload, Verify, with approval gates and rollback. That is a lifecycle engine, and it is the rare part. Adding integrations for other asset types without that loop would recreate the thing you correctly diagnosed in your own post: alerting that still leaves someone with the actual work. An alert without an owner and a next action is scheduled anxiety, and breadth of connectors just”
“Compliance adds a little complexity, but very do-able. Authentication via Entra (Think Oauth or SAML). Agent calls can be covered with ZDR. Code to pull data from other apps runs internally. Existing cyberinsurance likely covers it, though I'm expecting all the insurers are going to add AI risk to their premiums on the next renewal.”
If you know nano, you will know it must be here 🙂 . Thanks!
If you know nano, you will know it must be here 🙂 . Thanks!
“the "who decided that" part is interesting to me. is the provenance tracking automatic or does the agent need to be prompted to record decisions? because imo thats the part that breaks down first in practice”
Dynamic workflows have it investigate and branch off in creative ways
“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.”
“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.”