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.

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(repo): fix some typos #15021

Merged
merged 1 commit into from
Oct 24, 2023
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
2 changes: 1 addition & 1 deletion packages/bridge-ui-v2/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ These are are the additional configuration files that have to be filled in:
| **/config/configuredBridges.json** | Defines the chains that are connected via taiko bridges and lists the contract addresses |
| **/config/configuredChains.json** | Defines some metadata for the chains, such as name, icons, explorer URL, etc. |
| **/config/configuredRelayer.json** | If chains have a relayer, the URL and the chain IDs it covers are entered here |
| **/config/configuredCustomTokens.json** | Defines a list of tokens that should be availabe in the token dropdowns |
| **/config/configuredCustomTokens.json** | Defines a list of tokens that should be available in the token dropdowns |

---

Expand Down
2 changes: 1 addition & 1 deletion packages/bridge-ui-v2/src/libs/proof/Prover.ts
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ export class Prover {
const key = await this._getKey(contractAddress, msgHash);

// Unfortunately, since this method is stagnant, it hasn't been included into Viem lib
// as supported methods. Still stupported by Alchmey, Infura and others.
// as supported methods. Still stupported by Alchemy, Infura and others.
// See https://eips.ethereum.org/EIPS/eip-1186
// Following is a workaround to support this method.
const clientWithEthProofRequest = client as ClientWithEthGetProofRequest;
Expand Down
4 changes: 2 additions & 2 deletions packages/protocol/test/L1/TaikoL1Oracle.t.sol
Original file line number Diff line number Diff line change
Expand Up @@ -166,7 +166,7 @@ contract TaikoL1OracleTest is TaikoL1TestBase {
/// @dev So in case we have regular proving mechanism we shall check if
/// still a cooldown happens
/// @dev when proving a block (in a normal way).
/// @notice In case oracle_prover is disbaled, there
/// @notice In case oracle_prover is disabled, there
/// is no reason why
/// @notice cooldowns be above 0 min tho (!).
function test_L1_if_oracle_is_disabled_cooldown_is_still_as_proofRegularCooldown(
Expand Down Expand Up @@ -391,7 +391,7 @@ contract TaikoL1OracleTest is TaikoL1TestBase {
proveBlock(Carol, Carol, meta, parentHash, blockHash, signalRoot);

/// @notice: Based on the current codebase we still need to wait
/// even if the system and oracle proofs are disbaled, which
/// even if the system and oracle proofs are disabled, which
/// @notice: in such case best to set 0 mins (cause noone could
/// overwrite a valid fk).
vm.warp(block.timestamp + conf.proofRegularCooldown);
Expand Down
Loading