  davidherranandClaude Opus 4.7
|
a2925f67b9
|
feat(node): Phase 1.6+ Slice 3 — ChainSpec builder canonical mock-WASM fallback v0.0.13
Real ChainSpec JSON builder canonical via mock-WASM fallback pattern. Avanza
Origin Chain sin esperar Slice 2c WASM_BINARY resolution canonical (Larihana
pending). Own minimal JSON builder canonical via serde_json puro vs sc-chain-spec
dep canonical (43/44.0.0 trae sc-network mismatch + cid 0.9.0 yanked core2).
Deliverables canonical:
- crates/origin-chain-node/src/chain_spec.rs NEW (240 LOC) — 3 builder fns
(development/local_testnet/mainnet) + load_spec alias resolver + serialize_chain_spec
- crates/origin-chain-node/src/main.rs — new BuildSpec subcommand + build_spec fn
- crates/origin-chain-node/Cargo.toml — Slice 3 dep block canonical doc
- Cargo.toml workspace — sc-chain-spec investigation findings registered
Output JSON canonical compatible con Substrate-canonical sc_chain_spec::GenericChainSpec
schema (12-field structure). Mock WASM hex = "0x" placeholder canonical mientras
Slice 2c land canonical real WASM_BINARY via substrate-wasm-builder.
Verification canonical end-to-end:
- cargo check workspace verde 0.60s
- 10/10 chain_spec tests canonical pass + 75+ workspace tests canonical no regression
- cargo build --release origin-chain-node 2.28s clean
- build-spec --chain dev|local|mainnet|--raw all functional canonical
- BM V2 mainnet allocation verified: 400M+250M+150M+150M+50M = 1B OGC canonical
- Existing subcommands (version, list-presets, print-preset, info) NO REGRESSION
Phase 1.6+ progress: Slices 1+2+2b+3 ✅, Slice 2c WASM pending Larihana,
Slice 4 full sc-service requires Slice 2c canonical resolution.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
2026-05-22 07:54:57 -05:00 |
|
|
davidherranandClaude Opus 4.6
|
8a24a86ee6
|
feat(node): Phase 1.6+ Slice 1 — origin-chain-node CLI canonical v0.0.10
origin-chain-node binary canonical funcional con 4 sub-comandos:
- version (default canonical)
- list-presets (3 genesis presets disponibles)
- print-preset <id> (JSON-serialized RuntimeGenesisConfig)
- info (full runtime metadata canonical)
## Output canonical print-preset development verified
Alice SS58 address: 5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY
✅ matches exactly Substrate well-known canonical — hardcoded bytes son
bit-perfect compatible con polkadot-js + subkey ecosystem canonical.
## Decisión empírica documentada: WASM_BINARY DEFERRED a Slice 2 (v0.0.11)
substrate-wasm-builder requiere TODAS las deps no_std-compatible. origin-
chain-types actualmente usa std::String/Vec directly + thiserror 1.0 sin
no_std. Refactor scope substantial (5-10+ files affected) merece DC propio
y Slice dedicado canonical. CLI canonical opera correcto sin WASM execution
porque genesis presets serializables natively canonical.
## Workspace deps añadidos Phase 1.6+ (most Slice 4 deferred)
- substrate-wasm-builder 26.0.1 (Slice 2)
- sc-cli 0.51.0, sc-service 0.50.0, sc-executor 0.42.0 (Slice 4)
- sc-network 0.49.1, sc-consensus 0.48.0 (Slice 4)
- sc-consensus-aura 0.49.0, sc-consensus-grandpa 0.34.0 (Slice 4)
- sc-transaction-pool 39.0.0, sc-client-api 39.0.0 (Slice 4)
- sc-basic-authorship 0.49.0, sc-telemetry 28.1.0, sc-offchain 44.0.0 (Slice 4)
- jsonrpsee 0.24.3, substrate-frame-rpc-system 43.0.0 (Slice 4)
- pallet-transaction-payment-rpc 43.0.0 (Slice 4)
- clap 4.5.13 (USED v0.0.10 canonical)
- futures 0.3.31 (Slice 4)
Workspace declarations preparan canonical para Slice 4 sin re-declarar
cuando se necesite ramp up canonical.
## Roadmap Phase 1.6+ multi-slice canonical
- Slice 1 (v0.0.10 ESTA): CLI skeleton + preset listing ✅
- Slice 2 (v0.0.11): WASM_BINARY canonical + no_std refactor
- Slice 3 (v0.0.12): real sc_service::ChainSpec builder canonical
- Slice 4 (v0.0.13+): full sc-service (consensus + RPC + networking)
## Build + tests
- cargo build --release 8.22s warm cache
- cargo test --workspace ~63 tests passing
- Binary functional: cargo run --bin origin-chain-node {version|list-presets|
print-preset <id>|info}
## Filosofía canonical incorporada
Doc main.rs: "el CLI canonical es la primera ventana del barquero al mundo".
list-presets canonical = transparency canonical: las 3 distribuciones
posibles canonical están a la vista canonical, BM V2 incluida canonical
materializando David canon 2026-05-14 "la libertad infinita acota solo donde
empieza la del otro".
Refs: CHARON_ROADMAP_V1 Phase 1.6+, sub-decisión empírica WASM_BINARY defer
to Slice 2, sub-decisión empírica sc-service defer to Slice 4
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
2026-05-20 21:10:39 -05:00 |
|
|
davidherranandClaude Opus 4.6
|
2f47654418
|
feat(workspace): Phase 1.1 — runtime + node scaffolding v0.0.2
Charon sesión 1 continuación. Phase 0.4 → Phase 1.1 ship canonical.
## origin-chain-runtime crate (Phase 1.1)
- Re-exports canonical traits + types desde origin-chain-types (single-crate
surface para runtime consumers)
- RuntimeConfig marker (será reemplazado por Substrate Config traits Phase 1.2)
- RUNTIME_VERSION = 1 constante (bump per Substrate upgrade)
- Docs Phase 1 milestones (1.1 → 1.7) + Substrate version pin pending DC
## origin-chain-node binary (Phase 1.6 placeholder)
- main() prints scaffold notice + canonical frase Charon
- Hardware target documented: Pi 5 + NVMe SSD minimum (CHN-1)
- Smoldot light client noted as separate Phase 2+ crate
## Workspace
- 8 crates total (was 6): added origin-chain-runtime + origin-chain-node
- 44 tests passing workspace-wide
- Build release clean
- cargo run --bin origin-chain-node verified working
## Notes
- Aún sin deps Substrate. Phase 1.2 (pallet_aura + pallet_grandpa) será el
primer slice que pulls Substrate framework + bumps rust toolchain.
- Polkadot SDK version pin canónica vendrá vía DC complementaria a
ORIGIN_CHAIN_FOUNDATION_V1 cuando Phase 1.2 inicie.
Refs: Charon Roadmap V1 Phase 1.1, CHN-1, BM V2 §1.1
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
2026-05-20 07:44:26 -05:00 |
|