Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ class PredictionMarket(gl.Contract):
return result_json
```

You can check out this code on our [GitHub](https://github.com/genlayerlabs/genlayer-simulator/blob/main/examples/contracts/football_prediction_market.py)
You can check out this code on our [GitHub](https://github.com/genlayerlabs/genlayer-studio/blob/main/examples/contracts/football_prediction_market.py)

## Deploying the Contract

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ This result should be perfectly parseable by a JSON parser without errors.
return self.have_coin
```

You can check out this code on our [GitHub](https://github.com/genlayerlabs/genlayer-simulator/blob/main/examples/contracts/wizard_of_coin.py)
You can check out this code on our [GitHub](https://github.com/genlayerlabs/genlayer-studio/blob/main/examples/contracts/wizard_of_coin.py)

## Deploying the Contract

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ In addition to these built-in providers, you have the flexibility to integrate y

### Creating the Plugin

To integrate a new LLM provider plugin, you need to implement the `Plugin` protocol defined in the [llms.py](https://github.com/genlayerlabs/genlayer-simulator/blob/main/backend/node/genvm/llms.py) file. The protocol is structured as follows:
To integrate a new LLM provider plugin, you need to implement the `Plugin` protocol defined in the [llms.py](https://github.com/genlayerlabs/genlayer-studio/blob/main/backend/node/genvm/llms.py) file. The protocol is structured as follows:

```python
class Plugin(Protocol):
Expand Down Expand Up @@ -107,7 +107,7 @@ plugin_map = {

## Updating the JSON Schema

To maintain consistency and enable proper configuration validation, you must update the [JSON schema](https://json-schema.org/) in the [`providers_schema.json`](https://github.com/genlayerlabs/genlayer-simulator/blob/main/backend/node/create_nodes/providers_schema.json) file. This update should include your new provider and its specific configuration options.
To maintain consistency and enable proper configuration validation, you must update the [JSON schema](https://json-schema.org/) in the [`providers_schema.json`](https://github.com/genlayerlabs/genlayer-studio/blob/main/backend/node/create_nodes/providers_schema.json) file. This update should include your new provider and its specific configuration options.

The JSON schema plays a crucial role in validating the configuration options for each provider, ensuring that users input correct and compatible settings.

Expand Down
2 changes: 1 addition & 1 deletion theme.config.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ import DiscordIcon from "./components/discord";
const config: DocsThemeConfig = {
logo: <Logo />,
project: {
link: "https://github.com/genlayerlabs/genlayer-simulator",
link: "https://github.com/genlayerlabs",
},
docsRepositoryBase: "https://github.com/genlayerlabs/genlayer-docs/tree/main",
footer: {
Expand Down