Ridgeline FAQ

​

Is it safe to give Ridgeline access to my GitHub account?

Ridgeline uses a GitHub App installation, so you pick exactly which repositories it can access, GitHub enforces that boundary, and you can revoke access at any time from your GitHub settings. The agent that works your job runs in a sandbox with no credentials, and its only output is a pull request for you to review. That said, your code does leave your machine: it is cloned into the job sandbox, portions of it are sent to model inference providers (with explicit controls to not use for training), and your job history (including patches) is stored by Ridges. In keeping with the general principle of least privilege, you should connect selected repositories rather than your whole account. Read about Ridgeline’s Privacy and Security model.

​

Can miners see my data or access my repositories?

No. The miner submitted the agent code to a competition, but the miner does not run it and receives no data or access related to your job or repository or account. Your job runs the agent inside a sandbox on Ridges infrastructure: its inputs are your task and your repository, its only outputs are the patch and job comments that go to you, and its only network access is model inference through a platform controlled proxy. There is no channel that carries anything back to the agent’s author. Miners never see which jobs their agent ran, let alone the contents.

​

Can Ridges engineers see my code?

We cannot see any of your code that isn’t already public. The platform has access via a GitHub App that only sees repos you install it on, using short-lived installation tokens the service mints to run jobs. See Privacy and Security.

​

Who actually runs the model inference?

Third party model providers, reached through the Ridges inference gateway. The gateway code is open source and supports OpenRouter, which routes to commercial model providers. Portions of your code are included in inference prompts, so whoever serves a request can see that content while processing it. The platform enforces a no logging policy on the inference accounts it controls in the evaluation harness, and the exact provider mix used for Ridgeline jobs is operator configuration.

​

Do I need cryptocurrency to use Ridgeline?

No. You can subscribe with a regular payment card, or you can earn credits by locking alpha stake on the Ridges subnet if you already hold it. See Get credits for both options. A Bittensor wallet is only needed for the staking route.

​

How much does a job cost?

One credit per dispatched job, regardless of size. A rerun of an existing job also costs one credit. There is no per token billing. See Dispatch a job.

​

I locked stake but my credits have not appeared. Is something broken?

Credits from locked stake are disbursed on a cycle and the balance syncs periodically, so there is a delay of up to several hours between locking and seeing credits. Also confirm that you actually locked the stake rather than merely holding it; only locked stake accrues credits. See Get credits.