Skip to content
Closed
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
4 changes: 2 additions & 2 deletions packages/webapp/src/lib/constants.ts
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
export const REGISTRY_URL =
'https://raw.githubusercontent.com/rainlanguage/rain.strategies/cf96aab81a59704ea8d9300130ac888eb86f5eff/registry';
'https://raw.githubusercontent.com/rainlanguage/rain.strategies/28eecb662bc19dd9d43ec74941cfaf32e54cebbc/registry';
export const REMOTE_SETTINGS_URL =
'https://raw.githubusercontent.com/rainlanguage/rain.strategies/cf96aab81a59704ea8d9300130ac888eb86f5eff/settings.yaml';
'https://raw.githubusercontent.com/rainlanguage/rain.strategies/28eecb662bc19dd9d43ec74941cfaf32e54cebbc/settings.yaml';
12 changes: 12 additions & 0 deletions subgraph/networks.json
Original file line number Diff line number Diff line change
Expand Up @@ -10,5 +10,17 @@
"address": "0x8a3C8E610d827093F7437E0C45EFa648563c0dDA",
"startBlock": 76772162
}
},
"base": {
"OrderBook": {
"address": "0x52CEB8eBEf648744fFDDE89F7Bc9C3aC35944775",
"startBlock": 36667253
}
},
"flare": {
"OrderBook": {
"address": "0x8Dbc50485e7C6994923B9A2c603a2B6b2d8Eef64",
"startBlock": 49782578
}
Comment on lines +14 to +24

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Verify OrderBook addresses and start blocks for new networks.

Please confirm:

  1. The OrderBook addresses are correct for each network:
    • Base: 0x52CEB8eBEf648744fFDDE89F7Bc9C3aC35944775
    • Flare: 0x8Dbc50485e7C6994923B9A2c603a2B6b2d8Eef64
  2. The start blocks accurately reflect the OrderBook deployment block:
    • Base: block 36667253
    • Flare: block 49782578
  3. The network names "base" and "flare" match The Graph's network identifiers

Starting from an incorrect block can cause the subgraph to miss events or take longer to sync.


🏁 Script executed:

#!/bin/bash
# Search for any existing references to these addresses or networks in the codebase

echo "=== Searching for Base OrderBook address ==="
rg -i "52CEB8eBEf648744fFDDE89F7Bc9C3aC35944775" -C 2

echo -e "\n=== Searching for Flare OrderBook address ==="
rg -i "8Dbc50485e7C6994923B9A2c603a2B6b2d8Eef64" -C 2

echo -e "\n=== Searching for existing base/flare network references ==="
rg -i "(\"base\"|\"flare\").*network" -C 2

Length of output: 686


🏁 Script executed:

#!/bin/bash
# Check if there's any documentation or comments about network deployment in the codebase

echo "=== Searching for deployment or network documentation ==="
rg -i "deployment|network.*identifier|graph.*network" -C 2 | head -50

echo -e "\n=== Checking for any README or docs mentioning networks ==="
fd -e md -e txt | xargs grep -l -i "base\|flare" 2>/dev/null | head -10

Length of output: 4780


🌐 Web query:

The Graph supported networks identifiers base flare

💡 Result:

Short answer:

  • Base — use network identifier "base" (testnets/examples also use "base-sepolia"). [1][2]
  • Flare — not currently a supported network on The Graph (community requests exist, but no official support listed). [3][4]

Sources:

  1. The Graph subgraph manifest / docs (network examples). [The Graph Docs]. (thegraph.com)
  2. Examples/tutorials showing network: base / base-sepolia in subgraph.yaml. (docs.chainstack.com)
  3. The Graph blog post announcing Base support. (thegraph.com)
  4. Community forum discussion asking for Flare support (no official support announced). (forum.thegraph.com)

If you want, I can look up the exact network identifier for a specific hosting (Hosted Service vs Graph Network) or check again for any recent Flare integration announcements.

Citations:


🏁 Script executed:

#!/bin/bash
# Check if this is a The Graph subgraph or uses different indexing infrastructure

echo "=== Looking for subgraph.yaml or subgraph configuration ==="
fd -name "subgraph.yaml" -o -name "subgraph.yml"

echo -e "\n=== Searching for The Graph indexing references ==="
rg -i "graph-node|the graph|hosted service" -C 2 | head -30

echo -e "\n=== Checking subgraph directory structure ==="
ls -la subgraph/ 2>/dev/null || echo "subgraph/ directory not found"

echo -e "\n=== Looking at networks.json to understand context ==="
head -30 subgraph/networks.json

Length of output: 2094


🌐 Web query:

Flare network The Graph 2025 support

💡 Result:

Short answer: No — as of Nov 1, 2025 The Graph does not list Flare Network as a supported chain and there is no public announcement of an official integration. The Graph maintains a public "Supported Networks" list (90+ chains) and Flare does not appear there. [1][2]

Sources

  • The Graph — Supported networks listing (network index page). [1]
  • The Graph community forum thread asking about Flare (no indication of an official integration). [2]

Remove or document "flare" network—it is not currently supported by The Graph.

The Graph does not list Flare Network as a supported chain, so the "flare" entry in networks.json will fail during subgraph deployment or indexing. Either remove this entry or move it to a separate configuration for custom indexing infrastructure. The "base" identifier is correct.

Additionally, verify the OrderBook addresses and start blocks externally (Etherscan, Block Explorer) before deploying, as incorrect start blocks cause the subgraph to miss events or sync inefficiently.

🤖 Prompt for AI Agents
In subgraph/networks.json around lines 14 to 24, the "flare" network entry is
not supported by The Graph and will break deployment; either delete the entire
"flare" object from this file or move it into a separate custom-config (e.g.,
networks.custom.json) used only by your internal indexing infra, and if you keep
it add a clear comment documenting that Flare is unsupported by The Graph and
should not be used for public deployments; finally, before committing verify the
OrderBook contract addresses and startBlock values against the appropriate block
explorer for each network and correct any mismatches.

}
}
4 changes: 2 additions & 2 deletions subgraph/src/float.ts
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,9 @@ export function getCalculator(): DecimalFloat {
export function getDecimalFloatAddress(): Address {
let network = dataSource.network();
if (network == "flare") {
return Address.fromString("0xDbcb964760d021e18A31C9A731d8589c361E0E20");
return Address.fromString("0x2F665EcE3345bF09197DAd22A50dFB623BD310A7");
} else if (network == "base") {
return Address.fromString("0x83e4c7732e715b5E7310796A4A2a21d89f3FB59A");
return Address.fromString("0x2F665EcE3345bF09197DAd22A50dFB623BD310A7");
} else if (network == "bsc") {
return Address.fromString("0xDbcb964760d021e18A31C9A731d8589c361E0E20");
} else if (network == "arbitrum-one") {
Expand Down
2 changes: 1 addition & 1 deletion tauri-app/src/lib/services/loadRemoteSettings.ts
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
const REMOTE_SETTINGS_URL =
'https://raw.githubusercontent.com/rainlanguage/rain.strategies/cf96aab81a59704ea8d9300130ac888eb86f5eff/settings.yaml';
'https://raw.githubusercontent.com/rainlanguage/rain.strategies/28eecb662bc19dd9d43ec74941cfaf32e54cebbc/settings.yaml';

export async function loadRemoteSettings() {
const response = await fetch(REMOTE_SETTINGS_URL);
Expand Down