StakeSquid/ethereum-rpc-docker
1
0
Fork 0
Code Issues Pull Requests 3 Packages Projects Releases Wiki Activity
5,120 Commits 52 Branches 0 Tags
d43ed4a098c2bba4d2fc073c66deddf35cb96b14
Commit Graph
13 Commits
Author SHA1 Message Date
claude d43ed4a098 plasma: fix trusted_peers object shape for plasma-consensus 1.1.0 
Convert trusted_peers from TOML array-of-tables format ([[network.trusted_peers]])
to object format ([network.trusted_peers.0], [network.trusted_peers.1], etc.)
to match the schema expected by plasma-consensus 1.1.0.

The array-of-tables format was causing fatal errors on rpc-de-27:
  Error: Invalid config schema: Schema compliance: 'Invalid Toml config file.
  /tmp/non-validator.toml [...] is not of type "object"'

Mirrors the existing bootstrap_nodes structure which already uses numbered keys.
Preserves all three peer entries unchanged.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
 2026-09-28 10:19:30 +00:00
claude 43c800e430 plasma: restore trusted_peers to mainnet non-validator.toml 
Restore the [[network.trusted_peers]] array-of-tables that was silently
dropped during the 0.15.0->1.1.0 config-schema migration (PR #89).

The trusted_peers entries ensure the observer can connect to the Plasma
mainnet bootstrap nodes even with trusted_only=true.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
 2026-09-28 08:26:49 +00:00
claude 123f4cd696 Bump prysm to v7.1.8 
Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
 2026-09-28 05:06:06 +00:00
claudeandMistral Vibe fd73721e33 plasma: bump plasma-consensus to v1.1.0 with config schema migration 
- Bump plasma-consensus node version from 0.15.0 to 1.1.0
- Update non-validator.toml schema: replace [validators.N] with [network.bls_peer_ids] + [chain.static_committee.N]
- Add [chain.aquila] section with mainnet activation_height=33300000
- Convert [[network.bootstrap_nodes]] to indexed [network.bootstrap_nodes.N] tables
- Remove deprecated [[network.trusted_peers]] section
- Regenerate compose files with new config

BREAKING: Requires in-place consensus-DB migration. Downgrade to 0.15.0 is unsupported after first 1.1.0 start.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
 2026-09-27 23:10:18 +00:00
claude f1adbf7210 deploy: regenerate compose from vibe-node main 87606b9799ab 2026-09-24 15:35:32 +00:00
claude dc27f33384 plasma-mainnet: regenerate compose with IP env and --nat flag for observer 2026-09-24 12:49:05 +00:00
claude 7daf0ca6ea plasma: pin trusted bootstrap peers for mainnet observer 
Add trusted_peers configuration with observer-cs-1, observer-cs-4,
observer-cs-9 to fix P2P peering issue. Set trusted_only=true.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
 2026-09-24 12:42:08 +00:00
claude a8a8986305 deploy: regenerate compose from vibe-node main 2c123e09150c 2026-09-11 07:16:37 +00:00
claude dd059dfa1e deploy: regenerate compose from vibe-node main 02930ac0a52b 2026-09-11 06:32:40 +00:00
claude 6a19dc91e1 deploy: regenerate compose from vibe-node main e1cb79cc7707 2026-07-19 08:52:47 +00:00
claude db81e62c73 plasma: add testnet compose + assets (reth + plasma-consensus) 
Canonicalize plasma-testnet so the tracked compose adopts the same
volume/service names as the de-32 hand-written override (rpc_plasma-
testnet-reth-pruned-trace-{execution,consensus,jwt}). Also refresh
mainnet observer sed to be chain-agnostic.
 2026-07-19 04:15:45 +00:00
claude 14b3d70125 deploy: regenerate compose from vibe-node main e5b8e344f927 2026-07-13 16:58:03 +00:00
claude ba410ba7f6 plasma: vendor mainnet chain assets (genesis, non-validator config, validator keys) 2026-07-13 16:34:23 +00:00