Conversation
| Where `<network>` is one of the following reserved identifiers: | ||
|
|
||
| - `mainnet` | ||
| - `testnet` |
There was a problem hiding this comment.
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` |
There was a problem hiding this comment.
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.
bumblefudge
left a comment
bumblefudge
left a comment
There was a problem hiding this comment.
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.
3 participants
Closes: #163
Add flow blockchain with CAIP2