# bootstrapping Published articles for bootstrapping. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Beyond Inline Values: Evolving Strata's Storage Engine DevFeed: [Beyond Inline Values: Evolving Strata's Storage Engine]() Original publisher: [Read original article]() Author: Nevin Zheng Published: 2026-06-03T00:00:00Z Content type: article Language: en Sources: [nevzheng]() Topics: [Rust](), [abstraction](), [SQL](), [olap]() Tags: [abstraction](), [block](), [bootstrapping](), [layout](), [migration](), [performance](), [repo](), [rust](), [sql](), [storage](), [storage-engine](), [write-amplification]() ### AI overview This architectural decision record proposes replacing Strata's inline value storage with a block-based abstraction. It describes the current Rust LSM storage engine and SQL layer, identifies flexibility and I/O amplification problems, compares options, and records the proposed direction. ### Source excerpt An architectural decision record: why Strata is moving from inline values to block-based storage. ## Teleport Workload Identity DevFeed: [Teleport Workload Identity]() Original publisher: [Read original article]() Author: ben@goteleport.com (Ben Arent) Published: 2024-04-11T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [SPIFFE](), [SPIRE](), [Security](), [Architecture & Design](), [Microservice](), [TLS (Transport Layer Security)](), [Zero Trust]() Tags: [api](), [bootstrapping](), [identity](), [preview](), [security](), [services](), [spiffe](), [spire](), [tls](), [x509](), [zero-trust]() ### AI overview An introduction to Teleport Workload Identity, a preview feature that bootstraps and issues identities to services across heterogeneous environments and organizational boundaries. It builds on SPIFFE and adds a SPIFFE workload API endpoint, SVID issuance, TPM server attestation, and AWS Roles Anywhere support. ### Source excerpt An introduction to Teleport Workload Identity, a preview feature for bootstrapping and issuing identities to services across heterogeneous environments. ## Static Roots: Objects with Compile-Time Constant Addresses DevFeed: [Static Roots: Objects with Compile-Time Constant Addresses]() Original publisher: [Read original article]() Author: Olivier Flückiger Published: 2024-02-05T00:00:00Z Content type: article Language: en Sources: [V8]() Topics: [V8](), [JavaScript](), [Chrome](), [JIT](), [C++]() Tags: [bootstrapping](), [c-plus-plus](), [chrome](), [javascript](), [jit](), [performance]() ### AI overview This article explains V8 static roots, which give frequently used immutable objects compile-time constant addresses in the read-only heap. It describes how V8 bootstraps that heap into a snapshot, uses pointer compression to place it predictably, and improves performance across the VM, especially for C++ code and built-in functions. ### Source excerpt Did you ever wonder where undefined, true, and other core JavaScript objects come from? These objects are the atoms of any user defined object and need to be there first. V8 calls them immovable immutable roots and they live in their own heap - the read-only heap. Since they are used constantly, quick access is crucial. And what could be quicker than correctly guessing their memory address at compile time? As an example, consider the extremely common IsUndefined API function. Instead of having to look up the address of the undefined object for reference, what if we could simply check if an object's pointer ends in, say, 0x61 to know if it is undefined. This is exactly what the V8's static roots feature achieves. This post explores the hurdles we had to take to get there. The feature landed in Chrome 111 and brought performance benefits across the whole VM, particularly speeding up C++ code and builtin functions. Bootstrapping the Read-Only Heap # Creating the read-only objects takes some time, so V8 creates them at compile time. To compile V8, first a minimal proto-V8 binary called mksnapshot is compiled. This one creates all the shared read-only objects as well as the native code of builtin functions and writes them into a snapshot. Then, the actual V8 binary is compiled and bundled with the snapshot. To start V8 the snapshot is loaded into memory and we can immediately start using its content. The following diagram shows the simplified build process for the standalone d8 binary. Once d8 is up and running all the read-only objects have their fixed place in memory and never move. When we JIT code, we can e.g., directly refer to undefined by its address. However, when building the snapshot and when compiling the C++ for libv8 the address is not known yet. It depends on two things unknown at build time. First, the binary layout of the read-only heap and second, where in the memory space that read-only heap is located. How to Predict Addresses? # V8 uses pointer compre ## Fully bootstrapping Go from source in Wolfi DevFeed: [Fully bootstrapping Go from source in Wolfi]() Original publisher: [Read original article]() Published: 2023-08-11T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Go](), [Go Language](), [Compiler](), [toolchain](), [gcc](), [C++](), [backdoor]() Tags: [backdoor](), [binaries](), [bootstrapping](), [c-plus-plus](), [gcc](), [go](), [provenance](), [source](), [supply-chain](), [toolchain](), [wolfi]() ### AI overview The article explains how to fully bootstrap Go from source in Wolfi to improve provenance and reduce trust risks associated with pre-built binaries. It describes using the C++-based gcc-go or gollvm implementations to build the official Go toolchain without requiring an existing Go compiler. ### Source excerpt Dive into fully bootstrapping Go from source in Wolfi, paving the way for secure, independent development. ## Fully bootstrapping Java from source in Wolfi DevFeed: [Fully bootstrapping Java from source in Wolfi]() Original publisher: [Read original article]() Published: 2023-06-02T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Java](), [openjdk](), [supply-chain-security](), [chainguard](), [Compiler](), [Programming](), [gcc]() Tags: [bootstrapping](), [chainguard](), [chainguard-images](), [compiler](), [distribution](), [eclipse-compiler-for-java](), [gcc](), [gnu-linux](), [java](), [jdk](), [linux](), [openjdk](), [programming](), [programming-languages](), [provenance](), [security](), [software](), [software-supply-chain](), [software-supply-chain-security](), [supply-chain-security](), [wolfi]() ### AI overview Chainguard describes how it is fully bootstrapping Java from source in Wolfi. The process builds a chain of OpenJDK packages with provenance extending from source code to final binary packages, using GNU Classpath, GNU Compiler for Java, and the Eclipse Compiler for Java to overcome historical bootstrapping dependencies. ### Source excerpt Learn how Chainguard engineers created a chain of OpenJDK packages to provide full provenance from pure source code for the entire Java ecosystem in Wolfi. ## The Gadget Decomposition in FHE DevFeed: [The Gadget Decomposition in FHE]() Original publisher: [Read original article]() Published: 2021-12-11T13:57:25Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [FHE](), [homomorphic encryption](), [Cryptography](), [Computing](), [data](), [Code](), [GitHub]() Tags: [bootstrapping](), [core](), [encryption](), [fhe](), [gadget-decomposition](), [group-theory](), [homomorphic-encryption](), [learning-with-errors](), [linear-algebra](), [lwe](), [mathematics](), [matrix](), [number-theory](), [operations](), [programming](), [python]() ### AI overview A tutorial on gadget decomposition in fully homomorphic encryption (FHE). It explains how GSW and related schemes use random noise, how homomorphic operations increase that noise, why bootstrapping is needed, and how gadget decomposition helps limit noise growth. ### Source excerpt Lately I've been studying Fully Homomorphic Encryption, which is the miraculous ability to perform arbitrary computations on encrypted data without learning any information about the underlying message. It's the most comprehensive private computing solution that can exist (and it does exist!). The first FHE scheme by Craig Gentry was based on ideal lattices and was considered very complex (I never took the time to learn how it worked). Some later schemes (GSW = Gentry-Sahai-Waters) are based on matrix multiplication, and are conceptually much simpler. ## Content Security Policy for Single Page Web Apps DevFeed: [Content Security Policy for Single Page Web Apps]() Original publisher: [Read original article]() Author: Square Engineering Published: 2016-05-19T16:11:00Z Content type: tutorial Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Single-page application (SPA)](), [Web app](), [Security](), [Web Development](), [Vulnerabilities](), [Web]() Tags: [bootstrapping](), [csp](), [engineering](), [javascript](), [security](), [vulnerabilities](), [web](), [web-apps]() ### AI overview This tutorial explains how Square Cash implemented Content Security Policy on cash.me, including an iterative deployment process for identifying allowed sources and reducing policy violations. It describes how CSP restricts resource loading and connections, blocks inline scripts, helps mitigate some cross-site scripting and browser-based threats, and reports violations. ### Source excerpt Deploying comprehensive CSP that supports template bootstrapping.