Refresh repositories
Reload your GitHub repository list. This does not start a backup.
Practical guides for backing up your code, connecting your identity, and recovering your Git history.
Sign in with GitHub and save a public repository.
Read guide →Link JoyID, activate your identity, and sync backup proofs.
Read guide →Mint an optional developer collectible to your wallet.
Read guide →Restore saved Git history and prepare a recovery file.
Read guide →No wallet is needed. Rivet sponsors the CKB testnet backup anchor fee. Private repository backups are not available in this release.
Reload your GitHub repository list. This does not start a backup.
Save the latest history of a repository you have already backed up.
Enable GitHub push notifications for your already backed-up public repositories. Rivet starts a new backup when a notification arrives.
Check the progress percentage on your repository card. It estimates completed stages; confirmation can take longer than earlier steps. A slow or interrupted status request does not necessarily mean the backup stopped. Check the existing run before starting another backup.
If automatic backup setup fails, check your GitHub repository admin permissions and sign in again to refresh webhook access. A newly backed-up repository may need Auto-backup turned off and on to install its hook.
The optional Developer identity section connects your GitHub account and public backup proofs to your JoyID wallet.
It is a record of your developer identity and public backup commitments in your wallet-owned CoTA tree. View proof lets you inspect the transaction or download the verification package.
Syncing reuses existing backups. Reconnecting the same wallet or checking an unchanged state does not require a new publication transaction.
After your identity and manifest are verified, choose Create passport. Prepare the mint, review the locked capacity and network fee, then approve in JoyID.
Your wallet provides the passport’s locked test CKB and pays its network fee. This is separate from Rivet-sponsored identity activation.
The Sovereign Passport is a Spore digital object containing your identity snapshot at mint time. The app displays its visual card. Later backup updates appear in your current identity record without changing the original passport snapshot.
Reopening a saved mint or checking its status resumes the same operation. If an approval was interrupted, use the existing mint controls.
Open one of your backed-up repositories and use its restore controls. Browser restore requires a signed-in account authorized to access that backup. The Rivet CLI can also restore a new bare Git mirror on your computer.
Use Node.js 24+ and Git, then install a supplied Rivet CLI archive as described in the CLI guide. Sign in once using a GitHub personal token for your registered Rivet account.
rivet login
rivet restore owner/repository --target ./recovered.git
git clone ./recovered.git ./working-copyFor independent recovery, export a private recovery file with rivet status owner/repository --proof-out /private/location/recovery.secret.json. Keep it outside version control. With --proof, verification and restore use that file, CKB RPC, and the backup bundle without requiring Rivet sign-in or the original GitHub repository.
Attribution restore uses --mode attribution with an email map and your signing key. It keeps an exact original copy and signs a complete commit mapping. The CLI guide explains independent mapping verification and its separate testnet anchor. Hosted rollout and live acceptance remain pending. Backups cover public history pushed to GitHub; local-only commits and working files are excluded.
Look up a backup using its transaction hash, IPFS CID, or owner/repository. The lookup finds a public backup record and checks its referenced CKB anchor.
A backup anchor commits to a set of Git commits at a blockchain checkpoint. It does not certify the dates entered into those commits or guarantee that an IPFS gateway can currently serve the file.
A developer’s public profile separately checks a confirmed CoTA identity snapshot and current passport ownership. Use the exported manifest verifier for independent identity-proof checks.
V2 backup anchors also bind branch and tag refs, bundle file bytes, the IPFS CID, and commit count. Legacy anchors cover the commit set only; the CLI reports their remaining verification limits.
The CLI supports saved sign-in, project detection, backup, status, pushed-history monitoring, verification, and exact or attribution restore. Install it once and run it from your own project directories.
Read the CLI reference ↗Configure GitHub authentication, PostgreSQL, storage, workers, and CKB testnet services. Apply the documented release setup before enabling identity features.
Open the deployment guide ↗Inspect the manifest format, issuer setup, and standalone proof-verification procedure.
Open the identity runbook ↗