Skip to content

Conversation

@lmcmz
Copy link

@lmcmz lmcmz commented Jan 13, 2026

Closes: #163

Add flow blockchain with CAIP2

@lmcmz lmcmz mentioned this pull request Jan 13, 2026
Where `<network>` is one of the following reserved identifiers:

- `mainnet`
- `testnet`
Copy link
Collaborator

Choose a reason for hiding this comment

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

whether here or in an additional ### Governance section, it would be helpful to mention who decides when/whether to add a third reserved identifier, whether or not private networks are allowed by OS tooling, etc.


**Sample request (mainnet):**

`GET https://rest-mainnet.onflow.org/v1/network/parameters`
Copy link
Collaborator

Choose a reason for hiding this comment

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

where does a consumer find out or confirm the REST endpoints? are they fixed or do/can they change over time? worth mentioning here and/or in a ### Governance section.

Copy link
Collaborator

@bumblefudge bumblefudge left a comment

Choose a reason for hiding this comment

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

I think this could be merged as-is because it's a pretty straight-forward chainId system, but the clarifying questions I left would all be worth answering if they can be dispensed by adding a sentence and/or a link each! I recommend doing so because these profiles serve as a kind of onboarding resource for devs new the space, and avoid cross-chain footguns firing off because of faulty assumptions about the underlying semantics or mechanics of network identification/resolution systems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CAIP-2 for flow chain

3 participants