API services: 1 / 3
PRIVATE JOURNAL LEDGER / ETCD RAFT
MyBlogChain
Different cities. One shared chain.
MyBlogChain 2 is an encrypted private journal ledger using etcd Raft. Deployment: Sydney AWS EC2, Shanghai Tencent Cloud, and my laptop in Melbourne.
Live signed chain data. Nodes report roles; animation illustrates updates and verified replica synchronization.
12 blocks, including genesis
One operation per block
Available
01 / NETWORK TOPOLOGY
A network across the Pacific
- etcd role
- etcd Leader
- Replica tip
3a8f810d…
- etcd role
- etcd Follower
- Replica tip
3a8f810d…
- etcd role
- Offline
- Replica tip
3a8f810d…
- Submit / send
- Verify / return
03 / SIGNED JOURNAL HISTORY
Latest blocks
| Height | Block hash | Record operation | Written at (UTC) | Signature |
|---|---|---|---|---|
3a8f810dbd…4792c7 | Create record | Ed25519 | ||
b3b16dd564…ff5405 | Create record | Ed25519 | ||
fdb0fee2d5…6abc35 | Create record | Ed25519 | ||
ff9664f317…5bff0e | Create record | Ed25519 |
04 / MYBLOGCHAIN 2
A private ledger, replicated.
Journal content is encrypted with AES-256-GCM. Each create, update or delete appends one SHA-256-linked, Ed25519-signed block. The authorized API services share a signing identity; etcd Raft provides crash fault tolerance.
One etcd member in each city; API service on AWS
2 of 3 communicating members; leader election is in etcd
Topology, checkpoints and signed blocks; journal content stays private
Live chain metadata · record contents remain private