Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: typo and incorrect network. #55

Merged
merged 1 commit into from
Jul 8, 2024
Merged

fix: typo and incorrect network. #55

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 5 additions & 5 deletions code/API_definitions/blockchain_public_address.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -222,7 +222,7 @@ components:
schemas:
BindBlockchainPublicAddressRequest:
type: object
description: Payload to request the Bind of the Blockchain Public Adddress
description: Payload to request the Bind of the Blockchain Public Address
required:
- phoneNumber
- blockchainPublicAddress
Expand All @@ -247,7 +247,7 @@ components:
So far, in the scope of v0.2 of this specification, the following `<L1_Ecosystem>` values are covered:
- `evm`: Representing a common L1 Layer concept for EVM-based networks. Within this Ecosystem, `<sub_id>` concept is required and matches the value of chainId as per [EVM ChainId](https://chainid.network/). For instance:
- `ethereum` blockchain would be identified by `evm:1` value (i.e. ethereum mainnet).
- `polygon` blockhain would be identified by `evm:137` value (i.e. polygon mainnet).
- `polygon` blockchain would be identified by `evm:137` value (i.e. polygon mainnet).
- `celo` blockchain would be identified by `evm:42220` value (i.e. celo mainnet).
- `bitcoin`: Representing Bitcoin L1 blockchain. No `<sub_id>` concept applies for this L1 Ecosystem
- `solana`: Representing Solana L1 blockchain. No `<sub_id>` concept applies for this L1 Ecosystem
Expand Down Expand Up @@ -298,8 +298,8 @@ components:
So far, in the scope of v0.2 of this specification, the following `<L1_Ecosystem>` values are covered:
- `evm`: Representing a common L1 Layer concept for EVM-based networks. Within this Ecosystem, `<sub_id>` concept is required and matches the value of chainId as per [EVM ChainId](https://chainid.network/). For instance:
- `ethereum` blockchain would be identified by `evm:1` value (i.e. ethereum mainnet).
- `polygon` blockhain would be identified by `evm:137` value (i.e. polygon mainnet).
- `celo` blockchain would be identified by `evm:42220` value (i.e. polygon mainnet).
- `polygon` blockchain would be identified by `evm:137` value (i.e. polygon mainnet).
- `celo` blockchain would be identified by `evm:42220` value (i.e. celo mainnet).
- `bitcoin`: Representing Bitcoin L1 blockchain. No `<sub_id>` concept applies for this L1 Ecosystem
- `solana`: Representing Solana L1 blockchain. No `<sub_id>` concept applies for this L1 Ecosystem
- `cardano`: Representing Cardano L1 blockchain. No `<sub_id>` concept applies for this L1 Ecosystem
Expand Down Expand Up @@ -356,7 +356,7 @@ components:
status: 400
code: BLOCKCHAIN_PUBLIC_ADDRESS.INVALID_CURRENCY
message: Indicated currency is not found
RequiredCurrencyforBlockchain:
RequiredCurrencyForBlockchain:
value:
status: 400
code: BLOCKCHAIN_PUBLIC_ADDRESS.CURRENCY_REQUIRED
Expand Down