What this PR does / why we need it:

Develop and test on a simple smart contract functionality on substrate-based blockchain.

Which issue(s) does this PR fixes?:

Fixes #

Additional comments?:

What would you like to be added:

Add mainnet and testnet address prefixes

Where to add -> https://github.com/paritytech/ss58-registry

Why is this needed:

The address prefix that identifies an address as belonging to a specific network.

What would you like to be added:

Builds should use docker qemu + buildx. Building on docker engine will allow us to utilize qemu.

Why is this needed:

To make the builds as OS agnostic as possible.

Reference Conversation

What this PR does / why we need it:

Add ability to pass in a configModifier so the consumer will be able to override the default config used to start the container.

Which issue(s) does this PR fixes?:

Fixes #107

Additional comments?:

What this PR does / why we need it:

Adds initial code required for meta node with manual seal.

Which issue(s) does this PR fixes?:

Fixes #

Additional comments?:

What would you like to be added:

As per title

Why is this needed:

In order to make sure our binaries are able to run on all the environments that we expect. Our builds should target all those environments.

Reference Conversation

What this PR does / why we need it:

/kind chore

Which issue(s) does this PR fixes?:

Fixes #

Additional comments?:

What this PR does / why we need it:

Refactor and move ts-tests into mono-repo style packages to allow separation of context and downstream usability. This is the continuation of #42

@defimetachain/testcontainers

Provides easy to use and test lightweight, throwaway instances of MetaChain provisioned automatically in a Docker container.

MetaChainContainer and StartedMetaChainContainer follows the convention defined in testcontainers/testcontainers-node

let container: StartedMetaChainContainer;
let rpc: ethers.providers.JsonRpcProvider;

beforeEach(async () => {
  container = await new MetaChainContainer().start();
});

afterEach(async () => {
  await container.stop();
});

it('should createBlock', async function () {
  await container.createBlock();
  expect(await rpc.getBlockNumber()).toStrictEqual(1);
});

Which issue(s) does this PR fixes?:

Fixes #78

Additional comments?:

The current implementation in ts-tests isn't yet migrated to use the new standard and convention defined here. That should be done as part of https://github.com/DeFiCh/metachain/issues/79.

What would you like to be added:

At JellyfishSDK/jellyfish, there was a strong use of Containers + Javascript-based API for end-to-end (e2e) testing of services. Similarly, we need something like that here. Not to confuse integration or unit with e2e, e2e tests the resulting artifacts, and the entire artifact/binary lifecycle from start to finish. Hence it might not make sense to do it in Rust?

Unit Tests

The purpose of unit tests is to test each unit of code in isolation from the rest of the code to quickly pinpoint where code is and isn’t working as expected. You’ll put unit tests in the src directory in each file with the code that they’re testing. The convention is to create a module named tests in each file to contain the test functions and to annotate the module with cfg(test).

Integration Tests

In Rust, integration tests are entirely external to your library. They use your library in the same way any other code would, which means they can only call functions that are part of your library’s public API. Their purpose is to test whether many parts of your library work together correctly. Units of code that work correctly on their own could have problems when integrated, so test coverage of the integrated code is important as well. To create integration tests, you first need a tests directory.

https://doc.rust-lang.org/book/ch11-03-test-organization.html

Why is this needed:

Quality.

/triage accepted /area workflow

What would you like to be added:

• Publish Docker Image (PR/Main/Release)
  • matrix: (linux,windows,mac)
• Publish Binary (PR/Main/Release)

/area workflow /triage accepted

What this PR does / why we need it:

Details in the issue https://github.com/DeFiCh/metachain/issues/79

Which issue(s) does this PR fixes?:

Fixes #79

Additional comments?:

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | @​birthdayresearch/eslint-config | 0.3.1 -> 0.3.2 | | | | | | @​birthdayresearch/sticky-prettier | 0.3.1 -> 0.3.2 | | | | | | @​birthdayresearch/sticky-turbo-jest | 0.3.1 -> 0.3.2 | | | | |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Bumps secp256k1 from 0.24.1 to 0.24.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | hardhat (source) | ^2.12.2 -> ^2.12.5 | | | | |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

What would you like to be added:

To disable p2p block sync. Note: do not sync whatever announced block

Why is this needed:

By design, safety wise, we don't allow p2p call in between substrate node. The block generation will be all controlled by DNC. For more details ---> https://metachain.netlify.app/meta-chain-protocol/consensus#block-connecting

What happened:

During testing of the metachain build targeting multiple oses [ubuntu, mac, windows] the windows build failed. The windows build failed with the following error message.

failed to run custom build command for `tikv-jemalloc-sys v0.4.3+5.2.1-patched.2`

This is because the library tikv-jemalloc-sys v0.4.3+5.2.1-patched.2 does not support windows at the time.