Astar Network is an interoperable blockchain based the Substrate framework and the hub for dApps within the Polkadot Ecosystem

This contains bugfix for fixing era length, related tests, and OnRuntimeUpgrade hooks. Documentation for configuring it for each network is included

Check list

• [x] modifies existing feature (bug fix or improvements)
• [x] tests

Pull Request Summary Dapps staking root-only contract registration.

Right now, when devs register a dapp for dapps-staking, they first need to be whitelisted. But only their account is whitelisted, we don’t know exactly which dapp they will deploy. If we make the entire process atomic without developer_pre_approval process, whoever wants to register can specify exactly what the dev account is and which contract will be used. Also, this is required for governance over dapps registration, because RootOrigin call will be scheduled to pallet-scheduler by pallet-democracy once referendums passed.

Check list

• [x] added unit tests
• [ ] updated documentation

Logs of try-runtime against Shibuya

Description

I'm trying to utilize the SR25519.sol interface to verify a sr25519 encrypted message

I have tried on Shiden at 0x0000000000000000000000000000000000005001 but it threw a VM exception: revert

Pull Request Summary

This PR isn't a kill switch :) The purpose is to provide call to disable pallet - this means that users won't be able to stake or claim rewards anymore. Therefore, it is important that all rewards have been claimed prior to putting the pallet into maintenance mode.

The flow for ending the staking festival is as follows:

• uprgrade Astar with new runtime (maintenance mode support)
• claim all pending rewards
• enable maintenance mode for the pallet
• unregister all dapps (this will unlock the entire TVL)
• purge all dapps-staking pallet related DB entries
• upgrade Astar with new runtime that contains individual claim

Check list

• [ ] contains breaking changes
• [ ] adds new feature
• [x] modifies existing feature (bug fix or improvements)
• [ ] relies on other tasks
• [ ] documentation changes
• [ ] tests and/or benchmarks are included
• [ ] changed API client type definition or chain metadata

Pull Request Summary

Adds automatic restaking of reward to claim_staker extrinsic by checking the ledger.reward_handling property and staking the claimed amount right after claim.

Check list

• [ ] contains breaking changes
• [X] adds new feature
• [X] modifies existing feature (bug fix or improvements)
• [ ] relies on other tasks
• [ ] documentation changes
• [X] tests and/or benchmarks are included
• [ ] changed API client type definition or chain metadata

This pull request makes the following changes:

Adds

• ledger.reward_handling check to claim_staker
• RewardAndRestake, RewardHandlingChange events
• enable_compound_staking extrinsic
• update_staking_values helper function
• tests to check claiming after unstake or manually switching reward_handling

Fixes

• fix assert_claim_staker test utility function to take into account reward_handling state

Changes

• claim_staker now checks for reward_handling state, and restakes the claimed value if needed
• bond_and_stake uses update_staking_values helper function

To-dos

• [ ] update docs

Currently we identify assets being transferred by specifying an H160 style address (XC20), so this prevents us from sending native token since there's no representation for it.

This PR adds a workaround to interpret address 0x0 as native token to be sent (parents: 0, interior: Here), it can be used to pay for transaction.

Pull Request Summary

Removed deprecated pre-approval items from dapps-staking pallet and removed storage cleanup code.

Once Astar has been upgraded, we should ensure we update to latest astar-frame dependencies.

Pull Request Summary

Removes unused storage items from pallet-dapps-staking. We don't need to bring these to Astar chain.

Migration code was kept for future reference. We can remove it later if needed.

Check list

• [ ] contains breaking changes
• [ ] adds new feature
• [x] modifies existing feature (bug fix or improvements)
• [ ] relies on other tasks
• [ ] documentation changes
• [ ] tests and/or benchmarks are included
• [ ] changed API client type definition or chain metadata

Pull Request Summary

Reproduced and fixed issue where incorrect contract era stake is overwritten.

Check list

• [ ] contains breaking changes
• [ ] adds new feature
• [ ] modifies existing feature (bug fix or improvements)
• [ ] relies on other tasks
• [ ] documentation changes
• [ ] tests and/or benchmarks are included
• [ ] changed API client type definition or chain metadata

This pull request makes the following changes:

Pull Request Summary

Rename plasm to Astar and fix links

Check list

• [ ] contains breaking changes
• [ ] adds new feature
• [ ] modifies existing feature (bug fix or improvements)
• [ ] relies on other tasks
• [x] documentation changes
• [ ] tests and/or benchmarks are included
• [ ] changed API client type definition or chain metadata

This pull request makes the following changes:

Adds

• (ex: Add feature A)

Fixes

• (ex: Fix validation function)

Changes

• (ex: Change document B)

To-dos

*Feel free to remove this section if it's not applicable

• [ ] (ex: add user list)

Pull Request Summary

This precompile helps to verify Sr25519 signatures in EVM smart contracts.

Proposed interface:

interface SR25519 {
    /**
     * @dev Verify signed message using SR25519 crypto.
     * @return A boolean confirming whether the public key is signer for the message. 
     */
    function verify(
        bytes32 public,
        bytes signature,
        bytes message
    ) external view returns (bool);
}

Check list

• [ ] contains breaking changes
• [x] adds new feature
• [ ] modifies existing feature (bug fix or improvements)
• [ ] relies on other tasks
• [ ] documentation changes
• [ ] tests and/or benchmarks are included
• [ ] changed API client type definition or chain metadata

This pull request makes the following changes:

Adds

• (ex: Add feature A)

Fixes

• (ex: Fix validation function)

Changes

• (ex: Change document B)

To-dos

*Feel free to remove this section if it's not applicable

• [ ] (ex: add user list)

Pull Request Summary Optimize custom pallets' weights by using benchmark machine as is already done for DappsStaking pallets https://github.com/AstarNetwork/astar-frame/pull/122

Target pallets

• block_rewards
• xc_asset_config
• collator_selection

Machine spec used

Hardware
CPU
Intel Xeon-E 2136 - 6c/12t - 3.3 GHz/4.5 GHz
RAM
32 GB ECC 2666 MHz

Data disks
2×500 GB SSD NVMe

Expansion cards
Soft RAID

machine bench result

2022-12-19 07:35:38 Running machine benchmarks...    
2022-12-19 07:36:04 
+----------+----------------+--------------+--------------+-------------------+
| Category | Function       | Score        | Minimum      | Result            |
+=============================================================================+
| CPU      | BLAKE2-256     | 1.01 GiB/s   | 1.00 GiB/s   | ✅ Pass (100.1 %) |
|----------+----------------+--------------+--------------+-------------------|
| CPU      | SR25519-Verify | 658.82 KiB/s | 666.00 KiB/s | ✅ Pass ( 98.9 %) |
|----------+----------------+--------------+--------------+-------------------|
| Memory   | Copy           | 14.51 GiB/s  | 14.32 GiB/s  | ✅ Pass (101.3 %) |
|----------+----------------+--------------+--------------+-------------------|
| Disk     | Seq Write      | 1.36 GiB/s   | 450.00 MiB/s | ✅ Pass (310.4 %) |
|----------+----------------+--------------+--------------+-------------------|
| Disk     | Rnd Write      | 497.77 MiB/s | 200.00 MiB/s | ✅ Pass (248.9 %) |
+----------+----------------+--------------+--------------+-------------------+
From 5 benchmarks in total, 5 passed and 0 failed (10% fault tolerance).    
2022-12-19 07:36:04 The hardware meets the requirements

Pull Request Summary

This PR implements following EVM tracing RPC methods:

• debug_traceTransaction
• debug_traceBlockByHash
• trace_filter

Check list

• [ ] added unit tests
• [ ] updated documentation

Pull Request Summary

Prevents a potential scenario where user would make reward claiming impossible without first having something staked.

Check list

• [x] added unit tests

Description

When I want to do an XVM call using XVM chain-extension in a wasm contract. the estimated gas is too high (and execute button is grayed - thus impossible to execute the tx). When I edit this estimated gas and reduce it from 500% to 50% the call works. so it is an estimated gas issue only.

By adding the extra metadata needed, we are:

• making it simpler to add assets to our XCM bridge UI dapp, by removing the extra step of also making a PR to add to a config
• providing all on-chain information needed for a 3rd party to facilitate the creation of their own UI

Currently exposed metadata:

Fields needed by the current dapp:

RmrkCore::change_collection_issuer requires permission in order to accept ownership - set_accept_ownership via the Uniques pallet.

A chain-extension exposing Uniques::set_accept_ownership is required in order for an ink! contract to be able to call this function.