A static webpage is a blob of HTML,CSS, and JS that doesn’t change whenever a user loads a page. This is different than traditional websites, because there is no database, no dynamic rendering on a server, and the page is easily cacheable in a content delivery network. This architecture is known as a JAM — Stack, and the most popular host is Github Pages.

Install/Source Code: https://github.com/antsankov/go-live
Website: https://antsankov.gitbook.io/go-live/

Here are some examples of static webpages:

  • A Jekyll project can be compiled locally into static HTML…

Compromise is not about losing. It is about deciding that the other person has just as much right to be happy with the end result as you do.

A number of notable things happened last week on the ETC community call. First of all the community chose to reject ProgPoW. This is important because it is clear that this horrendous algorithm is a direct attack on the network by forcing it on substandard cryptography built by the CSW goon-squad. Good riddance!

When it comes to cryptography simpler = better. Less attack surface.

However, we were not able to achieve clear community support for ECIP-1049. Why was this? …

This is a Chinese translation of my talk given at the 2019 ETC Summit in Vancouver. Thank you ETCC! Video of talk is at bottom, source: https://github.com/etcconsortium/ETCSummit/blob/master/ETC%20Summit%202019%20the%20second%20day%20agenda%20(October%204).pdf

Here is a question: Imagine you have three Ethereum miners, and a group of users broadcasting transactions.

Miner A can do 400 megahashs a second (MH/S) and has a latency of .1 seconds to the the users, Miner B can do 700 MH/S and has a latency of 3 seconds, and Miner C that can produce 1,100 MH/S and has a latency of 9 seconds.

Which farm will most likely mine the transactions first? (answer at bottom)

The most important part to understanding cryptocurrency mining is that every hash operation is just as likely to be the correct answer to…

Since publishing ECIP-1049 (here) as a response to the 51% attack I have received quite a bit of input and questions. I have also opened up a pull request to multi-geth to create Astor (here), an Ethereum testnet that will use Keccak256 as its proof of work method. If you agree with this article, or just want to learn more about how consensus works in Ethereum, I would appreciate any help. My goal is to have the testnet running by January 2020. Read first article in series (here)

Question (courtesy of Phyro): “Why does the amount of hashes matter to…

On 2019–01–05, Ethereum Classic (ETC) was 51% attacked. What this means is that attackers sent over 40,000 ETC to an exchange, traded it for Bitcoin, withdrew that Bitcoin, and then released a chain with more accumulated hashpower that gave them back the 40k ETC. This double-spend will forever live on in the Ethereum Classic blockchain as a battlescar and will not be forked out or reversed.

Ethereum Classic Improvement Proposal 1049 is a response to this security breach. It argues for changing ETC’s proof of work algorithm from Ethash, to Keccak256. …

DISCLAIMER: Perform this at your own risk. This article is solely for academic purposes and the purpose is to help you better understand how Bitcoin/forks work.

This tutorial will show you how to split BCH from BSV, so that you can send one to an exchange without worrying about losing them both. When I say WAIT FOR THIS TO CONFIRM it is absolutely necessary to wait for a block to be mined, this can take up to an hour per transaction. DO NOT GO FAST, YOU CAN LOSE YOUR COINS.


It’s been a little over five months since I last wrote about Proof of Weak Hands (P3D) and a picture of the contract balance is worth a 1000 words:

Everything that happens once can never happen again. But everything that happens twice will surely happen a third time. — Paulo Coelho

If you are unfamiliar with the rules of the P3D game, I suggest you check out my first article which explains them. As you can see, the price has exploded since then, validating the fact that more and…

The Oracle of Delphi.

One of the many criticisms of the usefulness of smart contracts is known as the Oracle Problem. Plainly put, because a smart contract has no knowledge of reality it has to rely on a truth source, aka “an oracle” for it to receive external data. The “problem” is that while the execution of the contract may be trustless, as Jimmy Song puts it “A smart contract that trusts a third party removes the killer feature of trustlessness.” I believe this is wrong for a number of reasons:

Most importantly- the framing of the “oracle problem” as a problem for smart…

Alexander Tsankov

https://antsankov.com : Pushing boundaries

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store