feat(slice-2e): v0.0.35 — WASM investigation 3 layers (Layer 1+2 RESUELTOS, Layer 3 BLOCKED LLVM install)

Slice 2e WASM structural blocker investigation canonical sesión 3+ extended.
Substrate-wasm-builder re-enabled feature-gated. 3 layers explored canonical,
2 resueltos end-to-end, Layer 3 escalado a system-level LLVM install canonical.

## 3-layer findings canonical

- Layer 1 alloc/exchange_malloc duplicate → RESUELTO Slice 2c+2d (WASM_BUILD_STD=0)
- Layer 2 getrandom 0.2.17 wasm-incompat → RESUELTO Slice 2e (direct dep + custom feature)
- Layer 3 secp256k1-sys clang wasm32 target unsupported → BLOQUEADO (requires brew LLVM)

## Changes

- crates/origin-chain-runtime/Cargo.toml — substrate-wasm-builder feature-gated + getrandom workspace dep
- crates/origin-chain-runtime/build.rs — conditional WasmBuilder activation
- Cargo.toml workspace — getrandom = { version = "0.2", features = ["custom"] } workspace dep

## Layer 3 path forward canonical (Approach A recommended)

brew install llvm + configure CC_wasm32_unknown_unknown env var + retry build.
Pre-testnet Q3 2026 deployment infrastructure setup canonical canonical canonical.

## Investigation report canonical

Filed monorepo: docs/L7_roadmaps/SLICE_2E_INVESTIGATION_REPORT_V1.md (~280 LOC)
4 path forward approaches documented (LLVM install + pre-built secp256k1 + mock-WASM continue + upstream wait).

## Verification

- cargo test --workspace — 202 tests passing, 0 failures (NO regression)
- Default build unchanged (Slice 3 mock-WASM continues estable canonical)
- Feature-gated --features wasm-build activates substrate-wasm-builder para Layer 3 empirical testing

🔍 Slice 2e advanced canonical canonical. Path documented para Slice 2f future post-LLVM install.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
davidherranandClaude Opus 4.7 committed 2026-05-26 17:57:18 -05:00
1 parent 10ee1ab7b9
commit 44f1a0ae7f
5 files changed
+828 -33

No files matched your search

+25
View File
@@ -159,6 +159,31 @@ origin-chain-governance = { path = "crates/origin-chain-governance", version = "
origin-chain-runtime = { path = "crates/origin-chain-runtime", version = "0.0.1" }
origin-chain-node = { path = "crates/origin-chain-node", version = "0.0.1" }
# ============================================================
# Slice 2e v0.0.35 — canonical [patch.crates-io] WASM dependency overrides
# ============================================================
#
# Empirical finding canonical 2026-05-26: getrandom 0.2.17 default config NO
# compatible canonical wasm32-unknown-unknown target. Substrate runtime WASM
# requires custom canonical RNG source canonical, NOT browser JS fallback.
#
# Patch canonical: enable getrandom `custom` feature para permit FRAME runtime
# provide RNG via sp-io::offchain (off-chain worker) o panic placeholder
# (no on-chain RNG needed para Phase 1.6 ChainSpec build).
# ============================================================
# Slice 2e v0.0.35 — Direct getrandom canonical dep canonical para activate
# `custom` feature canonical via Cargo feature unification.
# ============================================================
#
# Empirical Slice 2e investigation 2026-05-26: getrandom 0.2.17 transitive
# via const-random-macro → macro_magic → frame-support-procedural.
# Workspace canonical declares getrandom 0.2 con `custom` feature canonical
# enabled — Cargo unification ensures wasm32-unknown-unknown target compat
# canonical via custom RNG source (FRAME runtime provides via sp-io).
getrandom = { version = "0.2", default-features = false, features = ["custom"] }
[profile.release]
# Slice 2b finding canonical: lto/codegen-units customization triggers alloc
# recompile en wbuild → duplicate exchange_malloc lang item canonical. Defaults