Skip to content
Open
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
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,11 +13,11 @@ The repository has the following packages (sub projects):
- [Near](mapclients/near) - MAP Relay Chain light client on Near Protocol
- [light clients on MAPO](lightclients) - All light client deployed on MAP Relay Chain
- [BNB Smart Chain light client](lightclients/bsc) - BNB smart chain light client on MAP Relay Chain
- [Ploygon light client](lightclients/matic) - Playton light client on MAP Relay Chain
- [Polygon light client](lightclients/matic) - Playton light client on MAP Relay Chain
- [Ethereum light client](lightclients/eth2) - Ethereum light client on MAP Relay Chain
- [Near light client](lightclients/near) - Near Protocl light client on MAP Relay Chain
- [Near light client](lightclients/near) - Near Protocol light client on MAP Relay Chain
- [Klaytn light client](lightclients/klaytn) - Klaytn light client on MAP Relay Chain
- [Platon light client](lightclients/platon) - Platon light client on MAP Relay Chain
- [MAP Omnichain Service](mos) - MAP omnichain Service reference implementation, mos contracts will be deplyed on every chain to achieve cross-chain interoperablity
- [MAP Omnichain Service](mos) - MAP omnichain Service reference implementation, mos contracts will be deployed on every chain to achieve cross-chain interoperablity
- [MOS on evm chains](mos/evm) - mos on evm chains
- [MOS on near](mos/near)
4 changes: 2 additions & 2 deletions lightclients/README.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Light Client contracts
All light clients depolyed on MAP Relay Chain:
All light clients deployed on MAP Relay Chain:
- [BNB Smart Chain light client](bsc)
- [Ploygon light client](matic)
- [Polygon light client](matic)
- [Ethereum light client](eth2)
- [Near light client](near)
- [Klaytn light client](klaytn)
Expand Down
2 changes: 1 addition & 1 deletion lightclients/bsc/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ the light node implementation principle is to verify the legitimacy of the block

If we want to validate a transaction, we need to validate the block header that the transaction is in,to validate a block header and we need to validate the signature of the block header.

by tracking validatorSet changes light node can verify all bsc transations.
by tracking validatorSet changes light node can verify all bsc transactions, translations, transitions.

Here are some important public interfaces.

Expand Down
2 changes: 1 addition & 1 deletion lightclients/eth2/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -147,7 +147,7 @@ The file LightNode.sol implements the main logic of eth2.0 PoS light client. Her

```

* Everytime the maintainer calls the above interface to update the light client successfully, the finalized beacon
* Every time the maintainer calls the above interface to update the light client successfully, the finalized beacon
header number and finalized execution layer header number are updated. There is a gap between the latest finalized
execution layer header and the previous finalized header. The maintainer should call below method to update the block
headers one or more times, and the light client will verify the validity of the block headers and store the hashes
Expand Down
4 changes: 2 additions & 2 deletions mos/evm/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ npx hardhat relayDeploy --wrapped <wrapped token> --lightnode <lightNodeManager
````

* `wrapped token` is wrapped MAP token address on MAP mainnet or MAP Makalu.
* `lightNodeManager address` is the light client mananger address deployed on MAP mainnet or MAP Makalu. See [here](../protocol/README.md) for more information.
* `lightNodeManager address` is the light client manager address deployed on MAP mainnet or MAP Makalu. See [here](../protocol/README.md) for more information.

3. Init MOS Relay
```
Expand Down Expand Up @@ -118,7 +118,7 @@ npx hardhat tokenDeploy --name <token name > --symbol <token symbol> --balance <

2. Grant Mint Role to relay or mos contract
````
npx hardhat tokenGrant --token <token address > --minter <adress/mos/relay> --network <network>
npx hardhat tokenGrant --token <token address > --minter <address/mos/relay> --network <network>
````

### Register Token
Expand Down
2 changes: 1 addition & 1 deletion mos/evmv2/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ npx hardhat relayDeploy --wrapped <wrapped token> --lightnode <lightNodeManager
````

* `wrapped token` is wrapped MAP token address on MAP mainnet or MAP Makalu.
* `lightNodeManager address` is the light client mananger address deployed on MAP mainnet or MAP Makalu. See [here](../protocol/README.md) for more information.
* `lightNodeManager address` is the light client manager address deployed on MAP mainnet or MAP Makalu. See [here](../protocol/README.md) for more information.

3. Init MOS Relay
```
Expand Down