-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
Describe the change
Body:
Hello Tempo team π
Iβm currently running a Tempo testnet node on a Raspberry Pi 5 (ARM64) and wanted to share my experience and confirm my participation as a contributor.
Setup summary
- Hardware: Raspberry Pi 5 (8GB RAM) + SSD
- OS: Ubuntu 24.04 LTS (ARM64)
- Mode: Execution + consensus
- Service: Managed via systemd (auto-restart, headless-ready)
- RPC: Enabled and responding on 127.0.0.1:8545
- Consensus: Node successfully initializes, joins epochs, and participates in ceremony flow
Notes from the process
- Encountered storage consistency checks and unwind during initial sync (expected behavior after interruptions).
- Consensus key handling and permissions were critical; once properly configured, the node stabilized.
- ARM64 on Raspberry Pi performs well once disk and restart policies are tuned.
Current status
- Node is running continuously
- Consensus initialized and active
- RPC responsive
- Preparing for long-term uptime to support the testnet
Iβm happy to provide:
- logs or metrics
- ARM-specific feedback
- reproducible steps if helpful for documentation or other contributors
Thanks for the work on Tempo β looking forward to continuing participation and supporting the testnet.
Best,
Tempo Testnet Contributor
Additional context
No response
Cloud963
Metadata
Metadata
Assignees
Labels
No labels