Hello, markovianprotocol.com/log has been on the testing list since July. We'd like to be considered for a staging list when smaller logs can move up. Since enrolling we've built the surface out; everything below is live and checkable: - Quorum-gated publication: /checkpoint serves only checkpoints cosigned by at least 4 of our 7 pinned witnesses, each cosignature cryptographically verified before publication. The policy is machine-readable at https://log.markovianprotocol.com/policy (c2sp.org/tlog-policy). - Offline proof bundles per leaf at /proof/<index> (c2sp.org/tlog-proof). - c2sp.org/tlog-tiles static tiles, RFC 9942 COSE receipts at /receipt/scitt/<index>, and hourly OpenTimestamps anchoring of the checkpoint bytes, with anchor roots checked against self-validated Bitcoin headers (state at /anchor). - A public hash-only submission door: POST /submit takes a sha256 and returns a receipt with proof URLs; nothing but 32 bytes of hash ever enters the log. Browser drag-and-drop version at https://markovianprotocol.com/log.html. - A standing open-source monitor (https://github.com/MarkovianProtocol/log-monitor) that verifies the log signature, every cosignature against pinned keys, consistency from its last head, and recomputes the root from served leaves, hourly. Anyone can run their own copy against us. - Dense-sequence completeness streams inside the log, so a reader can verify statements were not withheld, not just unaltered. We also run a witness on the test witness table (witness.markovianprotocol.com) and cosign whisper.online's log. Our declared rate stays 24 add-checkpoints/day. What would you need from us for a staging move? Thanks, Colin Winter Markovian Protocol — hello@markovianprotocol.com