A witness for Loops account migrations
When an account moves between Loops servers, both servers sign what happened. This Transit checks those signatures, records the keys that made them and adds each step to a public, append-only log. It never sees videos or profiles, only the signed intent and receipt, so a move stays verifiable even after either server rotates its keys or goes offline.
Look up a migration
Paste the intent JWS or its SHA-256 hash. Records are only shown to people who already hold the intent.
Use this Transit
Add http://transit.loopsplatform.com
to the Transit list in your Loops admin migration settings. A move is witnessed here when both servers list this Transit.
Both servers must show it in their NodeInfo, which Loops does automatically once it is in the list.
Signing keys
| Key ID | Status | Since |
|---|---|---|
No signing key yet. The operator needs to run php artisan transit:key:generate. |
||
Audit the log
- GET /api/v1/log
- The latest signed tree head.
- GET /api/v1/log/entries?start=0&end=99
- Log entries. They hold hashes, server names, key fingerprints and timestamps, never account addresses.
- GET /api/v1/log/proof/inclusion?index=0
- Proof that an entry is in the tree.
- GET /api/v1/log/proof/consistency?first=1&second=2
- Proof that a newer tree only added entries to an older one.