/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

blog.blockstream.com
| | blog.willcosgrove.com

What will follow is a walk-through of bitcoin's circular lifecycle as it gets transacted from person to person. Because of the circular nature, there's not an ideal starting point, because you must always know what came before to truly make sense... | Will Cosgrove | I'm bad at writing these things
20.8 parsecs

Travel
| |
| | parsiya.net

[AI summary] The text provides an in-depth overview of blockchain technology, covering its core concepts, applications, platforms, limitations, and misconceptions. It explains how blockchain operates, including transaction processing, consensus mechanisms, and smart contracts. The document also explores various blockchain platforms like Bitcoin, Ethereum, and Hyperledger projects, highlighting their unique features and use cases. It addresses common limitations, such as energy consumption, scalability issues, and trust challenges, while emphasizing the importance of cryptographic security and user responsibility in managing private keys. The text concludes by summarizing the key points and encouraging further feedback for improvement.
21.4 parsecs

Travel
| |
| | www.wpsoftware.net

[AI summary] This technical article explains a mathematical method to simulate Bitcoin covenants and transaction introspection by abusing the algebra of Schnorr signatures and a hypothetical CAT opcode.
14.3 parsecs

Travel
| |
| | rog3rsm1th.github.io

The Okamoto-Uchiyama cryptosystem is a semantically secure, asymmetric encryption algorithm. It was first introduced in 1998 by Tatsuaki Okamoto and Shigenori Uchiyama. The method is additive-homomorphic, which means that the plaintexts are added by multiplying two ciphertexts. It is therefore not necessary to decrypt the ciphertexts in order to be able to operate on the plaintexts. While searching for implementations of this algorithm on github, I realized that there were only two rough implementations.
32.2 parsecs

Travel
|