# Bitcoin Published articles for Bitcoin. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Search results are sending people to fake Bitrefill checkouts DevFeed: [Search results are sending people to fake Bitrefill checkouts]() Original publisher: [Read original article]() Author: Stefan Dasic Published: 2026-09-15T08:40:22Z Content type: news Language: en Sources: [Malwarebytes]() Topics: [Cryptocurrency](), [Bitcoin](), [Website]() Tags: [bitcoin](), [cryptocurrency](), [fraud](), [payments](), [phishing](), [qr-code](), [scam](), [scams](), [search](), [threat-intel]() ### AI overview Fake Bitrefill checkout pages are appearing in search results and copying the company's branding and payment flow. They persuade victims to send cryptocurrency to scammer-controlled addresses, with no goods delivered and little chance of recovering the payment. ### Source excerpt Fake Bitrefill checkout pages are appearing in search results and tricking people into sending cryptocurrency directly to scammers. ## Teravolt looks to cannibalize older industries to meet AI power demand DevFeed: [Teravolt looks to cannibalize older industries to meet AI power demand]() Original publisher: [Read original article]() Author: Thomas Claburn Published: 2026-09-14T13:45:00Z Content type: article Language: en Sources: [www.theregister.com - Articles]() Topics: [Artificial Intelligence](), [datacenter](), [Bitcoin]() Tags: [ai](), [ai-and-ml](), [artificial-intelligence](), [bitcoin](), [datacenter](), [electricity-grid](), [energy](), [infra]() ### AI overview Teravolt is considering repurposing Bitcoin farms, aluminum smelters, and other older infrastructure as datacenters to help meet growing AI power demand. ### Source excerpt Bitcoin farms, aluminum smelters, and other old infra is more lucrative to repurpose as a datacenter ## Revolut falls for fake government requests, hands over customer data DevFeed: [Revolut falls for fake government requests, hands over customer data]() Original publisher: [Read original article]() Author: Connor Jones Published: 2026-09-14T11:26:00Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [Cybercrime](), [Security]() Tags: [bitcoin](), [customer](), [cyber-crime](), [data](), [phishing]() ### AI overview Revolut handed over passports, selfies, and transaction histories after attackers used fake government requests and claimed responsibility for a crime while demanding 10,000 Bitcoin. ### Source excerpt Passports, selfies, transaction histories exposed as self-proclaimed culprits demand 10,000 Bitcoin ## The State of AI-Enabled Malware August 2026: From Brand Abuse to Agentic Execution DevFeed: [The State of AI-Enabled Malware August 2026: From Brand Abuse to Agentic Execution]() Original publisher: [Read original article]() Author: Sara McBroom Published: 2026-08-25T10:00:57Z Content type: article Language: en Sources: [Unit 42]() Topics: [Malware](), [Artificial Intelligence](), [Security](), [Endpoint Security & XDR](), [VirusTotal](), [dataset](), [data](), [ChatGPT](), [ransomware](), [Cryptocurrency]() Tags: [agentic](), [ai](), [analysis](), [article](), [backdoor](), [bitcoin](), [code](), [cryptocurrency](), [data](), [dll-hijacking](), [malware](), [ransomware](), [research](), [sandbox](), [security](), [threat-research](), [virustotal]() ### AI overview Unit 42 analyzes 405 malware samples incorporating AI through mechanisms such as brand impersonation, LLM-generated code, and agentic execution loops. The research finds that most samples remain proof-of-concept or sandbox activity, while existing behavioral detection, cloud sandboxing, and endpoint analytics can detect the threats that reach operational environments. ### Source excerpt Explore Unit 42 research on AI-enabled malware. Learn how existing behavioral detection and endpoint analytics stop AI-authored code before execution. The post The State of AI-Enabled Malware August 2026: From Brand Abuse to Agentic Execution appeared first on Unit 42. ## Not-so-anonymous telemetry: The @injectivelabs/sdk-ts backdoor DevFeed: [Not-so-anonymous telemetry: The @injectivelabs/sdk-ts backdoor]() Original publisher: [Read original article]() Author: Sebastian Obregoso, Christophe Tafani-Dereeper, Eslam Salem Published: 2026-07-09T00:00:00Z Content type: news Language: en Sources: [Datadog Security Labs]() Topics: [backdoor](), [SDKs](), [Blockchain](), [Malware](), [Git](), [npm](), [Bitcoin](), [TypeScript](), [servers](), [ci](), [Prettier]() Tags: [backdoor](), [bitcoin](), [blockchain](), [ci](), [code](), [git](), [github](), [http](), [malware](), [server](), [telemetry](), [typescript]() ### AI overview A malicious commit briefly compromised the Injective blockchain's @injectivelabs/sdk-ts npm package by disguising a credential-stealing backdoor as telemetry code. The malware captured wallet mnemonic seed phrases and private keys, encoded them, and exfiltrated them through HTTP requests to a remote endpoint before the code was reverted. ### Source excerpt A malicious commit disguised as SDK telemetry briefly compromised @injectivelabs/sdk-ts, exfiltrating wallet mnemonics and private keys. ## Security Week 2609: новые варианты атак ClickFix DevFeed: [Security Week 2609: новые варианты атак ClickFix]() Original publisher: [Read original article]() Author: Kaspersky\_Lab ("Лаборатория Касперского") Published: 2026-02-24T15:15:01Z Content type: news Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [ClickFix](), [Security](), [Threat Research]() Tags: [bitcoin](), [clickfix](), [dns](), [javascript](), [microsoft](), [nslookup](), [security](), [tag-9fe8963de219](), [zip]() ### AI overview The article reviews two recent ClickFix attack studies. One variant uses nslookup to retrieve part of a malicious script from a controlled DNS server, downloads a ZIP archive, and installs ModeloRAT through VBS persistence. Another uses social engineering and JavaScript pasted into the Swapzone.io browser interface to replace Bitcoin wallet addresses and divert cryptocurrency. ### Source excerpt На прошлой неделе опубликовано сразу два новых исследования об атаках типа ClickFix, в которых пользователя так или иначе мотивируют самостоятельно выполнять вредоносный код в командной строке. Команда Microsoft Threat Intelligence поделилась чуть более сложным, чем обычно, вариантом атаки, продемонстрированном на скриншоте ниже. Как правило, команда, которую злоумышленники заставляют запустить, содержит адрес, с которого загружается и выполняется вредоносный скрипт. Вероятно, для того чтобы усложнить детектирование атаки в корпоративном окружении и продлить жизнь вредоносной инфраструктуре, в этот простой сценарий вставлен еще один шаг: обращение к контролируемому DNS-серверу. От имени пользователя происходит обращение к DNS-серверу c использованием утилиты nslookup, запрашиваются данные для домена example.com. Из полученных в ответ данных выделяется строка NAME:, которая и содержит вторую часть вредоносного скрипта. Он, в свою очередь, напрямую скачивает ZIP-архив с набором вредоносных программ. На финальной стадии один из VBS-скриптов прописывается в автозапуск и на компьютер жертвы устанавливается троянская программа ModeloRAT. Это далеко не самый изощренный вариант атаки ClickFix. Ранее та же Microsoft сообщала о нетривиальной тактике, предусматривающей намеренное выведение из строя браузера путем установки вредоносного расширения под видом адблокера. Читать далее ## Recovering/undeleting short deleted files in 50 SLOC of pure C, any filesystem supported. DevFeed: [Recovering/undeleting short deleted files in 50 SLOC of pure C, any filesystem supported.]() Original publisher: [Read original article]() Published: 2025-10-13T22:00:00Z Content type: tutorial Language: en Sources: [Dennis Yurichev]() Topics: [C](), [OpenSSH](), [Linux](), [SQLite](), [Bitcoin](), [Cryptography]() Tags: [bitcoin](), [bug](), [c](), [encryption](), [files](), [filesystem](), [linux](), [openssh](), [private-key](), [sqlite]() ### AI overview This article presents a small pure-C utility for recovering short deleted files by scanning storage for known file headers or boundary strings. It describes recovering data from Linux ext4 SSDs, virtual-machine images, and RAM save files, and notes that deleted OpenSSH keys and Bitcoin wallets may be identifiable. It recommends secure deletion and filesystem encryption to reduce recovery risk. ### Source excerpt Recovering/undeleting short deleted files in 50 SLOC of pure C, any filesystem supported. ## Blog: Track the Bitcoin transactions with Falco DevFeed: [Blog: Track the Bitcoin transactions with Falco]() Original publisher: [Read original article]() Published: 2024-03-13T00:00:00Z Content type: tutorial Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [Bitcoin](), [WebSocket](), [Blockchain](), [Monitoring]() Tags: [bitcoin](), [falco](), [helm](), [kubernetes](), [plugin](), [websocket]() ### AI overview This tutorial presents a Falco plugin that receives Bitcoin transactions from a public WebSocket stream and shows how to install it, configure its default rules, and monitor transaction events in real time. ### Source excerpt The number of plugins available for Falco continues to grow thanks to our wonderful community. Thank you all for your help! You can find the list of available plugins here. The vast majority of plugins developed allow Falco to ingest logs from different sources and raise alerts when suspicious elements are identified by its rules. In order to show that any event stream can be a source if you have the right plugin, and to have something fun to show users during my talks, I developed a Falco plugin to track Bitcoin transactions. How does it work? I discovered the site https://www.blockchain.com/ exposes a public flux, accessible via a websocket, by subscribing to it you can retrieve transactions carried out on the blockchain in real time. This is perfect for a Falco plugin as it allows you to test the ingestion of events via a websocket, and serve as a basis for other plugins. I am not going to describe the internal workings of the plugin here, nor how it was developed. If you are interested, you can look at the code here. Alternatively, read our documentation explaining how to create a plugin from A to Z: https://falco.org/docs/concepts/plugins/developers-guide/how-to-develop/. Default rules The plugin comes with its default set of rules, we will use them as a working example. You are free to play with it for your own needs, such as monitoring suspicious movements of your wallet. You can find the Falco rules file provided here. Installation of the plugin We will see the 3 classic ways to install the plugin: via sources with falcoctl in kubernetes via Helm Via sources The prerequisites are: Golang >= 1.19 make Falco >= 0.36 Git We will start by installing download the sources, build and install the plugin: git clone https://github.com/Issif/bitcoin-plugin.git cd bitcoin-plugin sudo make install We will create a falco.yaml file containing: plugins: - name: bitcoin library_path: /usr/share/falco/plugins/libbitcoin.so init_config: '' open_params: '' load_plugins: [bitcoi ## Devconnect Scholars Program - Ethereum Stories from Istanbul and Beyond DevFeed: [Devconnect Scholars Program - Ethereum Stories from Istanbul and Beyond]() Original publisher: [Read original article]() Author: Next Billion Published: 2024-02-29T00:00:00Z Content type: opinion Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Resilience](), [Protocol (disambiguation)](), [Blockchain]() Tags: [africa](), [backend](), [banking](), [bitcoin](), [blockchain](), [community](), [devconnect](), [diversity](), [ecosystem](), [ethereum](), [geography](), [india](), [innovation](), [iran](), [java](), [network](), [networks](), [next-billion](), [perspectives](), [program](), [resilience]() ### AI overview The article presents stories from participants in the Devconnect Scholars Program, describing how broader geographic and demographic representation can strengthen Ethereum's resilience, security, and community. It profiles scholars from India, Iran, and Kenya and their work in research, education, smart contracts, and open-source projects. ### Source excerpt Ethereum is growing, and diversity of human participation creates resilience throughout the ecosystem. The Devconnect Scholars Program is one small effort that aims to create resilience through community diversity. Better representation across human geography and demographics leads to diverse experiences and new perspectives that help the Ethereum protocol serve the... ## Ultimate Go: Advanced Engineering Episode 20 DevFeed: [Ultimate Go: Advanced Engineering Episode 20]() Original publisher: [Read original article]() Published: 2023-01-27T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Data structures](), [Transactions](), [HTTP](), [REST API](), [servers]() Tags: [account-balance](), [bitcoin](), [blockchain](), [blockchain-rest-api](), [blockchain-state](), [data-structure](), [ethereum](), [genesis-block](), [genesis-record](), [go-blockchain](), [how-to](), [http](), [rest-api](), [state](), [transactions](), [video]() ### AI overview This video demonstrates how to launch a blockchain node, define an in-memory database for account information, manage blockchain state, and access the blockchain over HTTP through a REST API. ### Source excerpt Introduction In episode 19, Bill designed and implemented the data structure for an account on his blockchain. This type will have a nonce field to ensure incoming transactions are valid and performed in order. Since the database will be stored in memory and not on disk, the balances in these accounts are reconstructed with information from previous transactions and the genesis block. In this video, Bill takes all the theories discussed in this series and applies them by launching his first blockchain node. Bill starts by defining a database type that will house all the account information on his blockchain with the initial values populated by the genesis record. Once he is finished, Bill will add a new package named state and, as the name implies, it will manage the state on his blockchain. Watch and learn how to launch a blockchain node and interface with it over HTTP. ## Defining and Validating Blockchain Transactions in an In-Memory Accounting Database DevFeed: [Defining and Validating Blockchain Transactions in an In-Memory Accounting Database]() Original publisher: [Read original article]() Published: 2023-01-24T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Transactions](), [data](), [Ethereum]() Tags: [bitcoin](), [blockchain](), [blockchain-transaction](), [code](), [data](), [ethereum](), [factory-function](), [function](), [go-blockchain](), [how-to](), [implementation](), [learn](), [reference](), [transactions](), [types](), [video]() ### AI overview This video explains how to define and validate transaction types for a blockchain's in-memory accounting database. It covers the transaction data type, field design, validation methods, nonce tokens, and a transaction factory function, with concepts borrowed from Ethereum for reference. ### Source excerpt Introduction In episode 17, Bill began to design an in-memory accounting database that will store the account balances on his blockchain. To build this database, Bill will add a memory pool on each node that stores a list of public addresses with their respective balances. The balances on these addresses are reconstructed by reading the previous transaction records found on his blockchain. In this video, Bill will define the types of transactions his blockchain will support. The first step Bill takes is to define the transaction data type and give a full walkthrough of the reasoning behind the fields he chose for this data type. Next, he'll define methods for this type that will validate a transaction. While writing this code, Bill will borrow a few concepts from Ethereum to build a reference implementation. Watch to learn how transactions are managed on the blockchain and how to define one on your blockchain. ## Ultimate Go: Advanced Engineering Episode 19 -- Defining a Blockchain Account Data Structure DevFeed: [Ultimate Go: Advanced Engineering Episode 19 -- Defining a Blockchain Account Data Structure]() Original publisher: [Read original article]() Published: 2023-01-24T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Blockchain](), [Data structures](), [Ethereum](), [Transactions]() Tags: [account](), [bitcoin](), [blockchain](), [data-structure](), [data-type](), [design](), [engineering](), [ethereum](), [factory-function](), [go](), [go-blockchain](), [how-to](), [learn](), [transactions](), [video]() ### AI overview This video explains how to define a user account type for a blockchain in Go. It covers the account data structure, the design rationale, and a factory function for initializing an account. ### Source excerpt Introduction In episode 18, Bill defined the Go type that will represent a transaction and implemented the methods to validate one. While developing the transaction type, Bill states that he'll be borrowing concepts from Ethereum to ensure that he's building a reference implementation. Bill's transaction type has a field named nonce, similar to Ethereum, that ensures transactions are executed in order. The nonce value of the last transaction is stored in his accounting database and later compared for additional verification. ## Ultimate Go: Advanced Engineering Episode 17 DevFeed: [Ultimate Go: Advanced Engineering Episode 17]() Original publisher: [Read original article]() Published: 2023-01-19T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Transactions](), [Database]() Tags: [account](), [account-balance](), [accounting](), [bitcoin](), [blockchain](), [database](), [ethereum](), [go-blockchain](), [in-memory-database](), [memory-pool](), [transactions]() ### AI overview This video tutorial continues a blockchain engineering series by implementing account-balance tracking. It designs an in-memory accounting database and uses a memory pool to store account balances, following earlier transaction-verification work. ### Source excerpt Introduction In episode 16, Bill implemented additional means of verification for his blockchain's transactions. The first update he made was to verify if a transaction is destined for his blockchain by reading the first byte of the signature. The next one Bill made was to recalculate the public address from a signature and compare it with the from field of the transaction to verify if the request is valid. While building this, Bill demonstrates how a user's private key transforms into their public address. ## Ultimate Go Episode 16: Adding Transaction Validation and Security to a Blockchain DevFeed: [Ultimate Go Episode 16: Adding Transaction Validation and Security to a Blockchain]() Original publisher: [Read original article]() Published: 2023-01-17T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Security](), [Go Language]() Tags: [bitcoin](), [blockchain](), [engineering](), [ethereum](), [go](), [go-blockchain](), [iam](), [identity](), [identity-management](), [learn](), [private-key](), [protocol](), [public-address](), [secure-blockchain](), [security](), [validation](), [verification]() ### AI overview This video explains how to add validation mechanisms to blockchain nodes. It covers checking a transaction's destination, verifying signature rules defined by the protocol, and calculating a user's address from a transaction signature. ### Source excerpt Introduction In episode 15, Bill architected a solution to ensure all the users on his blockchain were given a unique identifier. His approach consisted of essentially leveraging the randomness of a user's private key to ensure each identifier is unique. A disadvantage Bill pointed out with this is that a user may forget their private key and ultimately lose access to their account. To circumvent this issue, Bill proposed the usage of a mnemonic, that is composed of 12 to 24 words, to act as the private key since it's simpler to keep track of and hard to guess. ## Ultimate Go: Advanced Engineering Episode 15 DevFeed: [Ultimate Go: Advanced Engineering Episode 15]() Original publisher: [Read original article]() Published: 2023-01-12T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Transactions](), [Ethereum]() Tags: [bitcoin](), [blockchain](), [digital-signature](), [ecdsa](), [ethereum](), [generate](), [go-blockchain](), [library](), [private-key](), [public-address](), [public-key](), [transactions]() ### AI overview This video tutorial explains how to derive a blockchain user's unique address from a public key recovered from a transaction signature. It covers reading the public key, validating the transaction's origin, and generating the user's address using Go Ethereum library functions. ### Source excerpt Introduction In episode 14, Bill architected a solution to digitally sign the transactions on his blockchain. His solution retrieved the private key by : loading private key data from disk, parsing the key data and returning the ECDSA private key. The private key is then used to generate the signature of a transaction. While writing the code to perform this functionality, Bill highlighted how a blockchain node can use a transaction's signature to extrapolate the public key. ## Creating Ethereum Digital Signatures with Go DevFeed: [Creating Ethereum Digital Signatures with Go]() Original publisher: [Read original article]() Published: 2023-01-11T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Blockchain](), [Ethereum](), [Transactions](), [Library]() Tags: [bitcoin](), [blockchain](), [code](), [digital-signature](), [ecdsa](), [ethereum](), [go](), [go-blockchain](), [library](), [private-key](), [public-key](), [signed-data](), [transactions]() ### AI overview A video tutorial demonstrating how to create Ethereum digital signatures with Go. It covers private ECDSA keys, signing objects, loading private keys from disk, decoding Ethereum signatures, and deriving public keys using the Go Ethereum library. ### Source excerpt Introduction In episode 13, Bill discussed the idea of adding salt to a hash and how modern crypto-currency blockchains use it to better interpret requests sent to nodes. He continued by defining a function called stamp that embeds a salt within a hash. While writing the function, Bill stated that he would use keccak256 as it's the same algorithm used by Ethereum to generate hash values. Bill will use the APIs provided with Go Ethereum to generate a keccak256 hash. He plans on reusing the stamp function in the future to digitally sign transactions performed on his blockchain. ## Ultimate Go: Advanced Engineering Episode 13 DevFeed: [Ultimate Go: Advanced Engineering Episode 13]() Original publisher: [Read original article]() Published: 2023-01-11T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Go Language](), [Algorithm](), [Security](), [Ethereum](), [API](), [Transactions]() Tags: [algorithm](), [bitcoin](), [blockchain](), [data-stamping](), [digital-signature](), [digital-signatures](), [ethereum](), [go](), [go-blockchain](), [hash](), [hexademical](), [how-to](), [keccak256](), [salt](), [security](), [video]() ### AI overview This video tutorial explains how to add a salt value to transaction hashes, implement the keccak256 algorithm in Go, and use transaction stamping in a blockchain. It also discusses digital signatures and related security issues. ### Source excerpt Introduction In episode 12, Bill laid out his strategy to handle data hashing on his blockchain. The first step he took was to create a package to handle the cryptographical aspects of his blockchain. After that, he wrote a hash function that met the requirements outlined in his strategy. This function took transaction data as a parameter and returned a hexadecimal representation of the hash. To implement this function, Bill imported packages from the Go standard library and Ethereum API. ## Ultimate Go: Advanced Engineering Episode 12 DevFeed: [Ultimate Go: Advanced Engineering Episode 12]() Original publisher: [Read original article]() Published: 2023-01-04T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [data](), [Blockchain](), [Algorithm](), [Ethereum](), [Library](), [Code]() Tags: [algorithm](), [bitcoin](), [blockchain](), [code](), [ethereum](), [go](), [go-blockchain](), [hash](), [hashing](), [hex-value](), [hexademical](), [standard-library](), [video]() ### AI overview This video tutorial explains how to hash a transaction in Go using packages from the standard library and the Ethereum Go library. It also discusses the desired properties of a hashing function and the role of cryptographic signatures and public-key recovery in a decentralized blockchain. ### Source excerpt Introduction In episode 11, Bill highlighted the issue of identity verification and provided a solution to this problem. The solution proposed was to cryptographically sign a transaction to verify its authenticity. Bill chose to implement a solution making use of the Elliptic Curve Digital Signature Algorithm (ECDSA) as the public key can be extracted from a signature. Although a small distinction, the ability to re-compute a public key is essential in a decentralized and distributed environment. ## Defining Go Types and Loading Blockchain Settings from JSON DevFeed: [Defining Go Types and Loading Blockchain Settings from JSON]() Original publisher: [Read original article]() Published: 2023-01-03T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [JSON](), [Blockchain](), [data](), [Ethereum]() Tags: [bitcoin](), [blockchain](), [blockchain-asset](), [clean-code](), [code](), [data-structure](), [data-type](), [ethereum](), [genesis-record](), [go](), [go-blockchain](), [go-types](), [json](), [load](), [types](), [video]() ### AI overview This video explains how to define Go types for a blockchain's genesis record and load the blockchain's settings from a JSON file. It also discusses choosing suitable built-in types for struct fields, including limitations of uint64. ### Source excerpt Introduction In episode 9, Bill introduced the idea of the genesis record and its role in his blockchain. As a recap, the genesis record will be used to customize the settings of his blockchain. The approach Bill takes here is similar to how Ethereum operates because he is storing the record in JSON format. In this video, Bill starts by defining the Go types his blockchain will use. The first type he defines will represent the genesis record. This type will be populated by the data found in the genesis record and will ensure Bill reaps all the benefits of using strongly typed language. Before he proceeds with the next type definition, he highlights the possible limitations he can encounter by using type uint64. Watch to learn how to write idiomatic and durable Go code that will load your blockchain's settings from disk. ## Ethereum Identity Verification with ECDSA for a Decentralized Blockchain DevFeed: [Ethereum Identity Verification with ECDSA for a Decentralized Blockchain]() Original publisher: [Read original article]() Published: 2023-01-03T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Ethereum](), [Go Language]() Tags: [bitcoin](), [blockchain](), [blockchain-asset](), [digital-signature](), [distributed](), [ecdsa](), [ecdsa-encryption](), [encryption](), [ethereum](), [ethereum-authentication](), [genesis-record](), [go-blockchain](), [identity](), [identity-management](), [verification]() ### AI overview This video tutorial explores how Ethereum confirms user identity and explains how ECDSA can verify transaction authenticity without relying on a central key store. ### Source excerpt Introduction In episode 10, Bill dove into the technical implementation of his genesis record and defined a custom Go type representing the record. While doing so, he provided an in-depth look at the reasoning behind the fields he included.. After declaring this type, Bill wrote a function that loads the genesis record from disk and onto memory. His function will use the standard library encoding/json package to load JSON data from a hard-coded file path. ## Ultimate Go: Advanced Engineering Episode 9 DevFeed: [Ultimate Go: Advanced Engineering Episode 9]() Original publisher: [Read original article]() Published: 2022-12-20T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Go Language](), [Bitcoin](), [Ethereum]() Tags: [bitcoin](), [blockchain](), [blockchain-asset](), [build](), [building](), [code](), [concepts](), [engineering](), [ethereum](), [genesis](), [genesis-json](), [genesis-record](), [go](), [go-blockchain](), [implement](), [introduction](), [project](), [project-layout](), [reuse](), [standard-library]() ### AI overview This video tutorial covers the initial layout of a blockchain project in Go, including creating a genesis record and explaining its role. It also introduces fundamental blockchain verifications. ### Source excerpt Introduction In episode 8, Bill wanted to build a blockchain in Go and began to lay the groundwork for the project. Go is a good choice because its standard library has the necessary network and cryptographical functionality required to build a blockchain. Unlike the previous segment, Bill plans to use this blockchain to manage accounts and balances with hypothetical assets. Bill will reuse concepts from ethereum, bitcoin and the previous segment of the series to implement this blockchain. ## Securing private keys with a high-performance, threshold signature-based protocol DevFeed: [Securing private keys with a high-performance, threshold signature-based protocol]() Original publisher: [Read original article]() Author: Chris Hager Published: 2021-07-21T00:00:00Z Content type: article Language: en Sources: [Chris Hager]() Topics: [Security](), [ECDSA](), [Bitcoin](), [Ethereum](), [API keys](), [client](), [servers]() Tags: [api](), [bitcoin](), [blockchain](), [client](), [cryptography](), [ecdsa](), [ethereum](), [mpc](), [security](), [server](), [threshold-signatures]() ### AI overview The article explains a threshold-signature protocol for securing private keys through collaborative signing. It describes splitting a key into secret shares, requiring multiple parties to cooperate, and using client/server controls for limits, revocation, and rotation. The approach applies to blockchains using ECDSA and EdDSA, including Bitcoin and Ethereum. ### Source excerpt This post is about the paper "Improving security for users of decentralized exchanges through multiparty computation", by Robert Annessi and Ethan Fast. The paper introduces an effective algorithm for secure, collaborative signature generation using threshold signatures, and an API-key based client/server protocol that allows user-specific limits and restrictions as well as key revocations and rotations. The method supports all blockchains that use ECDSA and EdDSA signatures, which includes Bitcoin, Ethereum and the majority of popular cryptocurrencies. ## What the Twitter Hack Revealed About Common Company Security Flaws DevFeed: [What the Twitter Hack Revealed About Common Company Security Flaws]() Original publisher: [Read original article]() Author: info@goteleport.com (Virag Mody) Published: 2020-11-11T00:00:00Z Content type: opinion Language: en Sources: [Teleport]() Topics: [X (Twitter)](), [Social engineering](), [account](), [Virtual Private Network](), [Logging]() Tags: [attacks](), [bitcoin](), [credentials](), [logging](), [post-mortem](), [social-engineering](), [techniques](), [twitter](), [vpn]() ### AI overview This commentary examines the 2020 Twitter hack, arguing that the incident exposed security weaknesses common across companies. It describes credential theft through impersonation and social engineering, followed by access to an internal account-management tool and Bitcoin scam messages. ### Source excerpt The Twitter hack was not orchestrated by a nation state. Twitter was hacked by an average teenager who was too young to have his own driver's license. ## The History of Casper - Chapter 2 DevFeed: [The History of Casper - Chapter 2]() Original publisher: [Read original article]() Author: Vlad Zamfir Published: 2016-12-07T21:58:58Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Security](), [Protocol (disambiguation)](), [Bitcoin]() Tags: [bitcoin](), [protocol](), [research](), [research-development](), [security](), [strategy]() ### AI overview Chapter 2 recounts research into game theory and economic security for proof-of-stake in 2014. It explains how the bribing attacker model informed a solution to long-range attacks and discusses incentive compatibility, security deposits, slashing conditions, and Nash equilibria. ### Source excerpt This chapter describes the game theory and economic security modelling we were doing in the Fall of 2014. It recounts how the "bribing attacker model" led our research directly to a radical solution to the long range attack problem.... [Next page]()