# golang blockchain Published articles for golang blockchain. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Smart Contracts Using Solidity and Go: Basic Contract DevFeed: [Smart Contracts Using Solidity and Go: Basic Contract]() Original publisher: [Read original article]() Published: 2022-12-21T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Solidity](), [Ethereum](), [Go Language](), [Programming](), [API]() Tags: [blockchain](), [ethereum](), [go](), [go-blockchain](), [golang-blockchain](), [how-to](), [programming-language](), [smart-contract](), [tests]() ### AI overview A tutorial on using Go to create and test basic Solidity smart contracts for Ethereum. It explains how smart contracts expose APIs and manage mutable storage on a blockchain, then focuses on testing a contract API against a simulated Ethereum node. ### Source excerpt Introduction I made it my mission in 2022 to learn everything I could about blockchain and as the year ends, I feel like I accomplished my goal. Love it, hate it, or don't want to know nothing about it, I think it's important to push your opinions aside and understand how this technology works. Even with the current collapse of several large crypto companies in 2022, blockchain isn't going to disappear. Bitcoin and Ethereum are here to stay. If anything, this past year has shown how entrenched blockchain has become in the world and in people's lives. ## Ultimate Go Episode 6: Blockchain Consensus Algorithms DevFeed: [Ultimate Go Episode 6: Blockchain Consensus Algorithms]() Original publisher: [Read original article]() Published: 2022-12-16T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Algorithms](), [Security](), [data]() Tags: [algorithms](), [blockchain](), [consensus](), [consensus-algorithm](), [distributed](), [go-blockchain](), [golang-blockchain](), [poa](), [pos](), [pow](), [proof-of-authority](), [proof-of-work](), [security]() ### AI overview This video explains why proof of work can be inefficient as a blockchain grows, focusing on duplicated computation and energy consumption. It introduces proof of stake and proof of authority as alternative consensus algorithms and discusses their role in maintaining valid data in a distributed database. ### Source excerpt Introduction In the last video, Bill left off talking about proof of work (PoW) algorithms. In a distributed and decentralized environment, PoW used to be the gold standard for a node to participate equitably in a Blockchain. However, with PoW as the number of nodes on the Blockchain increases, the amount of energy waste increases. This is because each node is performing the same computationally heavy calculation and only one node's energy usage is leveraged to write the next block. ## Ultimate Go: Advanced Engineering Episode 5 DevFeed: [Ultimate Go: Advanced Engineering Episode 5]() Original publisher: [Read original article]() Published: 2022-12-16T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Databases](), [Replication]() Tags: [atomic](), [consensus](), [consensus-algorithm](), [cryptographically-auditable](), [database](), [distributed](), [engineering](), [go-blockchain](), [golang-blockchain](), [poa](), [pos](), [pow](), [proof-of-authority](), [proof-of-work]() ### AI overview This video explains how to use blockchain concepts to design a distributed, auditable, synchronized, and scalable database for a dependency manager. It focuses on atomic writes, consensus, and a proof-of-work algorithm, while also discussing the inefficiency of proof of work and the emergence of proof of stake and proof of authority. ### Source excerpt Introduction In case you missed episode 4, Bill attempted to integrate current database sharing solutions to solve the "database ownership" problem his dependency manager faces. He tried providing copies of the database, implementing a load balancer and replication. While performing these experiments, Bill identified the qualities his dependency manager's database needs to have for users to trust it. He closed episode 4 by stating that his dependency manager needs a database that is distributed, cryptographically auditable, synchronized and scalable. By implementing this Bill hoped to provide greater transparency for his dependency manager. ## Ultimate Go: Advanced Engineering Episode 3 -- Adding a Cryptographic Audit Trail to a Dependency Manager Database DevFeed: [Ultimate Go: Advanced Engineering Episode 3 -- Adding a Cryptographic Audit Trail to a Dependency Manager Database]() Original publisher: [Read original article]() Published: 2022-12-14T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Database](), [audit trail](), [audit]() Tags: [audit](), [audit-trail](), [cryptographic-audit](), [cryptographically-auditable](), [database](), [genesis-record](), [go-blockchain](), [golang-blockchain](), [hash-algorithms](), [hashing](), [record-chaining](), [trust]() ### AI overview This video explains how to add a previous-record hash to a dependency manager database, chaining records into a cryptographic audit trail. Recomputed hashes can reveal database changes, while the genesis record has no previous hash. ### Source excerpt Introduction In episode 2, Bill designed a database for his dependency manager to enable Go developers to have reproducible,durable and secure builds. This database will house the hash value for each of the dependencies stored. During runtime, these hash values are compared with the dependencies a user has locally. Bill's tool makes this comparison to make sure the user has the right version of the dependency. Each team making use of Bill's dependency manager will have access to its database, however, his database lacked any means to reliably perform audits. ## Sharing Control of a Dependency Manager's Database DevFeed: [Sharing Control of a Dependency Manager's Database]() Original publisher: [Read original article]() Published: 2022-12-14T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Database]() Tags: [audits](), [data-ownership](), [data-rights](), [database](), [gatekeeping](), [go-blockchain](), [golang-blockchain](), [load-balancing](), [master](), [privacy](), [replication](), [sharding](), [slave](), [sqlite]() ### AI overview This episode explores different methods for sharing control of a dependency manager's database. It examines the benefits, drawbacks, bottlenecks, and disadvantages of each approach, and explains why these methods fall short of solving the database ownership problem. ### Source excerpt Introduction In episode 3, Bill needed to figure out how to share ownership of his dependency manager's database in a secure and efficient manner. Bill is the only stakeholder with full access to his dependency manager's database. That is, he is the only person with the ability to mutate the database. This is problematic because he can freely edit the database which will make it harder for other users to confidently perform audits. And as a result, reduce the perceived transparency of his dependency manager. ## Ultimate Go: Advanced Engineering Episode 2 DevFeed: [Ultimate Go: Advanced Engineering Episode 2]() Original publisher: [Read original article]() Published: 2022-12-13T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Dependency management](), [Blockchain](), [Algorithm](), [Command-line interface](), [Database]() Tags: [algorithm](), [blockchain](), [cli](), [database](), [dependency-management](), [go](), [go-blockchain](), [golang-blockchain](), [hash-algorithms](), [hash-collision](), [hashing](), [sha-256](), [sha256]() ### AI overview This video tutorial explains how dependency management in Go relates to reproducible builds, blockchain hashing, and trust in a centralized dependency database. It introduces hashes as distributed identifiers, explains collisions, and discusses the use of SHA-256 to reduce collision risk. ### Source excerpt Introduction In episode 1, Bill finished by describing the dependency management conundrum Go faced in its early days. Prior to the Go team providing the module system, developers were on their own to find a solution. Engineers in the Go community did propose different solutions, but there was no general consensus on which tool to use for dependency management. In this video, Bill will begin to architect a solution to the reproducible build problem. By doing so, you will learn how blockchain hashing works and then Bill will share how centralizing this dependency database will cause other problems. One of these problems is people eventually losing trust in the database because only one stakeholder, Bill, can make changes to it without a means for users to detect the change. He closes this segment with an important question, "how do we establish trust for this CLI's database?" ## Blockchain Concepts Explained Through Go Modules and Software Build Problems DevFeed: [Blockchain Concepts Explained Through Go Modules and Software Build Problems]() Original publisher: [Read original article]() Published: 2022-12-12T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [P2P](), [Database](), [Go Language]() Tags: [blockchain](), [build-blockchain-from-scratch](), [cryptographically-auditable](), [database](), [digital-wallet](), [ecdsa](), [engineering](), [ethereum](), [genesis-file](), [go](), [go-blockchain](), [golang-blockchain](), [p2p]() ### AI overview This video introduces blockchain concepts, including its append-only and transparent database model, cryptographic auditability, and peer-to-peer network structure without a central authority. It explains these ideas through reproducible, durable, and secure software builds and the Go module system. ### Source excerpt Introduction In this video, Bill will introduce the concepts of what a blockchain is, the benefits of a blockchain, and the network environment it operates in. Bill describes a blockchain as a single, append-only, transparent, publicly available and cryptographically auditable database. Blockchains operate using a peer to peer (p2p) network with no single node designated as the central authority. To better understand what all that means, Bill begins to work through a familiar problem of creating reproducible, durable, and secure builds that software teams face. It's a real problem the Go team eventually solved with the new module system. As Bill uncovers different problems that present themselves, he introduces different blockchain concepts that can help provide a solution. ## Practical Uses Of Blockchain Technology DevFeed: [Practical Uses Of Blockchain Technology]() Original publisher: [Read original article]() Published: 2022-06-06T00:00:00Z Content type: article Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [blockchain technology](), [Dependency management](), [Database](), [Cryptography](), [Code]() Tags: [blockchain](), [blockchain-signature-verification](), [blockchain-technology](), [build-blockchain-from-scratch](), [cryptographically-auditable](), [cryptography](), [database](), [dependency-management](), [digital-wallet](), [distributed](), [ecdsa](), [ethereum](), [genesis-file](), [go-blockchain](), [golang-blockchain](), [verification]() ### AI overview The article explains practical uses of blockchain technology, focusing on a dependency-management verification system. The proposed system hashes code retrieved from a version-control system and compares it with a database record to detect changes. Cryptographic auditing and append-only records are presented as ways to make the database verifiable. ### Source excerpt Introduction A blockchain is an integrated solution of different computer science problems in the form of a single, append-only, publicly available, transparent, and cryptographically auditable database that runs in a distributed and decentralized environment. I've heard many times that blockchain is a technology looking for a problem to solve. I disagree with that assessment because the tech and computer science behind blockchain has practical uses in everyday engineering problems. One use of this technology that comes to mind is a dependency management verification system. ## Blockchain In Go: Part IV: Fraud Detection DevFeed: [Blockchain In Go: Part IV: Fraud Detection]() Original publisher: [Read original article]() Published: 2022-05-05T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [audit trail](), [Go Language](), [Database](), [Code]() Tags: [audit-trail](), [blockchain](), [blockchain-signature-verification](), [build-blockchain-from-scratch](), [cryptographic-audit](), [digital-wallet](), [ecdsa](), [ethereum](), [fraud](), [fraud-detection](), [genesis-file](), [go](), [go-blockchain](), [golang-blockchain](), [hash](), [storage](), [verification]() ### AI overview This fourth post in a series explains how the Ardan blockchain detects forgery or changes to blocks and transaction data. It describes the cryptographic audit trail formed by block-header fields, including hashes linking each block to the previous one, so a node can verify its local blockchain copy and detect mismatches. ### Source excerpt Introduction In the first three posts, I explained there were four aspects of a blockchain that this series would explore with a backing implementation provided by the Ardan blockchain project. Digital accounts with electronic signatures and verification Transaction distribution and synchronization between computers Redundant storage and consensus by different computers Detection of any fraud to past transactions The first post focused on how the Ardan blockchain provides support for digital accounts, signatures, and verification. The second post focused on transaction distribution and synchronization between different computers. The third post, focused on how the Ardan blockchain handles consensus between different computers which results in the redundant storage of the blockchain database. In this fourth post, I will focus on how the Ardan blockchain can detect forgery or changes to the underlying blocks and transaction data. ## Blockchain In Go: Part III: Redundant Storage And Consensus DevFeed: [Blockchain In Go: Part III: Redundant Storage And Consensus]() Original publisher: [Read original article]() Published: 2022-04-19T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Go Language](), [Databases](), [Transactions]() Tags: [availability](), [blockchain](), [blockchain-consensus-protocol](), [build-blockchain-from-scratch](), [consensus](), [database](), [digital-wallet](), [ethereum](), [go](), [go-blockchain](), [golang](), [golang-blockchain](), [proof-of-work](), [storage](), [transactions](), [verification]() ### AI overview The third article in a series explains how the Ardan blockchain project handles consensus between computers and uses that process for redundant storage of the blockchain database. It introduces proof of work and proof of stake, discusses safety versus liveness, and notes the consensus approaches used by Bitcoin and Ethereum. ### Source excerpt Introduction In the first two posts, I explained there were four aspects of a blockchain that this series would explore with a backing implementation provided by the Ardan blockchain project. Digital accounts with electronic signatures and verification Transaction distribution and synchronization between computers Redundant storage and consensus by different computers Detection of any fraud to past transactions The first post focused on how the Ardan blockchain provides support for digital accounts, signatures, and verification. The second post focused on transaction distribution and synchronization between different computers. In this third post, I will focus on how the Ardan blockchain handles consensus between different computers which results in the redundant storage of the blockchain database. ## Blockchain In Go: Part II: Transaction Distribution and Synchronization DevFeed: [Blockchain In Go: Part II: Transaction Distribution and Synchronization]() Original publisher: [Read original article]() Published: 2022-03-08T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Transactions](), [Go Language](), [API](), [REST API](), [Concurrency](), [Cache](), [HTTP](), [JSON]() Tags: [api](), [blockchain](), [build-blockchain-from-scratch](), [cache](), [digital-wallet](), [distribution](), [ethereum](), [go](), [go-blockchain](), [golang-blockchain](), [http](), [implementation](), [json](), [mempool-blockchain](), [network](), [project](), [rest-api](), [series](), [synchronization](), [transactions]() ### AI overview This second article in a blockchain series explains how the Ardan blockchain distributes and synchronizes transactions between nodes. It describes submission through a wallet, storage in an in-memory mempool, signaling through a goroutine, and propagation to other nodes. It also introduces the HTTP-based REST API used for wallet and node communication. ### Source excerpt Introduction In the first post, I explained there were four aspects of a blockchain that this series would explore with a backing implementation provided by the Ardan blockchain project. Digital accounts with electronic signatures and verification Transaction distribution and synchronization between computers Redundant storage and consensus by different computers Detection of any fraud to past transactions The first post focused on how the Ardan blockchain provides support for digital accounts, signatures, and verification. In this second post, I will focus on transaction distribution and synchronization between different computers (blockchain nodes). ## Blockchain In Go: Part I: Digital Accounts, Signatures and Verification DevFeed: [Blockchain In Go: Part I: Digital Accounts, Signatures and Verification]() Original publisher: [Read original article]() Published: 2022-02-12T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Go Language](), [Code](), [Ethereum]() Tags: [blockchain](), [blockchain-signature-verification](), [build-blockchain-from-scratch](), [code](), [digital-wallet](), [ecdsa](), [ethereum](), [genesis-file](), [go](), [go-blockchain](), [golang-blockchain](), [implementation](), [introduction](), [verification]() ### AI overview This tutorial series introduces the Ardan blockchain project, a Go reference implementation intended for learning rather than production use. Part I explains how the project supports digital accounts, electronic signatures, and verification, using Ethereum as a reference. ### Source excerpt Introduction This is the first post in a series that will explore the semantics and implementation details of the Ardan blockchain project. The code is a reference implementation of a blockchain and not intended to mirror any specific blockchain in use today. Even though the code has been engineered with production level coding standards, I wouldn't use this project for anything more than learning. I am using the Ethereum project as a reference and have taken inspiration from that code. I'm hoping that understanding the code inside the Ardan blockchain will give you enough knowledge to understand the code that runs Ethereum.