Coinbase Developer Platform’s Post

Calling all #blockchain & #web3 #developers! The YAR developer documentation is now open to everyone. Today, we are releasing a crucial system update that will propel the entire world to the web3 adoption. With YAR #dev docs, you can build #multichain #DEX, #DAO, #RWA, and #DeFi projects, as well as web3-native #payment #gateways, #crypto #billing systems, #GameFI #monetization systems, etc. This week, we will be announcing the start of the first cohort of the YAR Pioneer Program and are excited to invite all startups and entrepreneurs in need of #crosschain onboarding to join us on this new journey. Powered by YAR DAO, the YAR Pioneers Program is an empowering initiative designed to nurture and accelerate the growth of promising cross-chain projects. By offering comprehensive resources, mentorship, and unparalleled access to the YAR ecosystem, we aim to foster a community of pioneers driving innovation in the blockchain space. Stay tuned and follow us for more updates. https://lnkd.in/dMceeiQq

Calling all #blockchain & #web3 #developers! The YAR developer documentation is now open to everyone. Today, we are releasing a crucial system update that will propel the entire world to the web3 adoption. With YAR #dev docs, you can build #multichain #DEX, #DAO, #RWA, and #DeFi projects, as well as web3-native #payment #gateways, #crypto #billing systems, #GameFI #monetization systems, etc. This week, we will be announcing the start of the first cohort of the YAR Pioneer Program and are excited to invite all startups and entrepreneurs in need of #crosschain onboarding to join us on this new journey. Powered by YAR DAO, the YAR Pioneers Program is an empowering initiative designed to nurture and accelerate the growth of promising cross-chain projects. By offering comprehensive resources, mentorship, and unparalleled access to the YAR ecosystem, we aim to foster a community of pioneers driving innovation in the blockchain space. Stay tuned and follow us for more updates. https://lnkd.in/dMceeiQq

Recently, there's been an insane trend and demand for staking assets from custody. However, custodians natively support staking a limited number of assets and are not in a hurry to expand their support. On the other hand, some custodians support a so-called Raw Signing feature, which allows signing any transaction on behalf of the asset holder within the custodian. I wrote a technical article with an example of how to stake ATOM tokens from Fireblocks (who is the one of the most famous custodians) , which might interest some colleagues and partners to better understand the concept of Raw Signing and how to use it for staking assets. Interestingly, with the help of our Platform API, you can perform stake/unstake operations without even touching the blockchain or blockchain-specific SDKs.

If you enjoy delving into new codebases related to distributed systems, you might find go-ethereum intriguing. I've written a blog that offers a code walkthrough of Ethereum, providing a head start in understanding the go-ethereum codebase. Check it out here: https://lnkd.in/gPNHhgGS. Feedback and suggestions are welcome! #distributedsystems #golang #ethereum #codewalkthrough #blockchain #txpool #transaction

Hey there! So, after getting some awesome feedback from one of my readers, I figured it's high time I give you all a proper intro to this blog post. Let's dive in! Okay, picture this: in today's world, money is pretty much under the thumb of 𝒈𝒐𝒗𝒆𝒓𝒏𝒎𝒆𝒏𝒕𝒔, right? They can just print more money whenever they feel like it, and bam! 𝑰𝒏𝒇𝒍𝒂𝒕𝒊𝒐𝒏 hits us. Plus, our individual cash holdings are usually scribbled down in some book or stored in a centralized server. But guess what? Those systems are like sitting ducks for manipulation since they're controlled by just a handful of folks. Now, imagine if we could spread out those records across a bunch of servers all over the globe, each controlled by different peeps. It's like having a safety net for our money, right? But hold up a sec! How do we keep all those records in sync and avoid any messy conflicts? Enter 𝒕𝒓𝒂𝒏𝒔𝒂𝒄𝒕𝒊𝒐𝒏𝒔! Every person has their own account, and when we move money around, it's called a transaction. Each transaction gets a thumbs-up from the sender's secret key, keeping things legit. But here's the kicker: we've gotta run these transactions one after the other, in the same order, on every single server. But who's calling the shots here? That's where consensus comes into play. 𝐂𝐨𝐧𝐬𝐞𝐧𝐬𝐮𝐬 is all about getting everyone to agree on the order of transactions. And to keep things fair, we need to elect a 𝒍𝒆𝒂𝒅𝒆𝒓 who'll propose that order. But here's the twist: we switch up the leader regularly to dodge any centralization issues. We give all the servers a task, and whoever finishes first gets the leader's hat for a while. But hey, what if someone tries to pull a fast one? Like hosting a server and rigging the code to give themselves a boatload of cash? That's where 𝑩𝒚𝒛𝒂𝒏𝒕𝒊𝒏𝒆 𝒇𝒂𝒖𝒍𝒕 𝒕𝒐𝒍𝒆𝒓𝒂𝒏𝒄𝒆 kicks in, my friends! In simpler terms, we've gotta make sure our system can handle sneaky attacks through majority of honest nodes. Now, here's a big question: why do we even need thousands of blockchains? Isn't 𝑩𝒊𝒕𝒄𝒐𝒊𝒏 doing the job just fine? Well, sure, Bitcoin's great for moving money around, but 𝑬𝒕𝒉𝒆𝒓𝒆𝒖𝒎 stepped in with a whole new ball game. They said, "Hey, why not use blockchains for more than just cash transfers?" And bam! Suddenly, we're talking about complex programs, lending, stablecoins—you name it! Everyone's trying to level up the blockchain game, pushing the boundaries with scalability, consensus mechanisms, privacy—you name it! And hey, just so you know, even though all these servers are running the same software, each blockchain has its own flavor. Like in Ethereum, you've got multiple clients coded in different languages, from Golang to Rust to Java. So, in this blog, I'm gonna take you through the code of the 𝑮𝒐𝒍𝒂𝒏𝒈 client. Strap in, folks—it's gonna be one heck of a ride! #distributedsystems #ethereum #golang #blockchain #consensus #bitcoin #financialsystems #scalability

Not all emails from Satoshi Nakamoto contained in this repository from Martti Malmi (https://lnkd.in/dRJKdBRx) are unpublished. Take, for example, the link below. #bitcoin #cryptocurrency #sirius #iris #satoshi #nickszabo https://lnkd.in/dR65QSTx

Hey blockchain devs 👋 Just delved into advanced Solidity concepts and recently grasped the idea of upgradability. I explored proxy patterns for implementing upgradable smart contracts and penned a blog about it to provide an overview of how proxy smart contracts function. Feel free to check it out and share your suggestions for enhancements. If you're keen on learning more about the proxy pattern, drop a comment, and I'll create a video on it to share with you. #Blockchain #Solidity #SmartContracts #ProxyPattern

If you want to know more about proxy patterns checkout this post

The Inter-Blockchain Communication Protocol (IBC) is an end-to-end, connection-oriented, stateful protocol for reliable, ordered, and authenticated communication between heterogeneous blockchains arranged in an unknown and dynamic topology. IBC is a protocol that allows blockchains to talk to each other. Chains that speak IBC can share any type of data as long as it's encoded in bytes, enabling the industry’s most feature-rich cross-chain interactions. IBC is secure and permissionless. The protocol realizes this interoperability by specifying a set of data structures, abstractions, and semantics that can be implemented by any distributed ledger that satisfies a small set of requirements. IBC can be used to build a wide range of cross-chain applications that include token transfers, atomic swaps, multi-chain smart contracts (with or without mutually comprehensible VMs), cross-chain account control, and data and code sharding of various kinds.

🚨 Update on Cadence 1.0 Migration 🚨 At the beginning of this year, the Flow Blockchain announced the migration to Cadence 1.0, and we have been diligently preparing for it. However, three weeks ago, we received news that the migration had been postponed, and as of now, there is no confirmed date for when it will take place. https://lnkd.in/dsw55jhe This delay is problematic for us because we now have to maintain an additional environment, adding to our operational overhead. Moreover, the documentation is currently a mix of Cadence 0.42 and Cadence 1.0, leading to confusion and inefficiencies. We've encountered instances where neither version worked as expected, and the solutions were only available on Discord if specifically asked for. While I appreciate Discord as a modern forum, this should be an exception, not the norm. Despite the challenges, now we are waiting for a final date and it's getting more confusing. I want to emphasize that I am not placing blame on anyone. However, effective communication is always crucial. It's about time to provide some clarity because our businesses are waiting. Flow Blockchain #CadenceMigration #FlowBlockchain #TechUpdates #BlockchainDevelopment #EffectiveCommunication