substrate-developer-hub / frontier-node-template

Standalone template based on upstream: https://github.com/paritytech/frontier/tree/master/template

(Old) Substrate Developer Hub (ARCHIVED)

THIS SITE IS ARCHIVED.

• New site: https://docs.substrate.io/
• Source available: https://github.com/substrate-developer-hub/substrate-docs/

This repository houses documentation for the Substrate blockchain framework.

The docs are written in markdown, processed by Docusaurus, and hosted at the Substrate Developer Hub.

Contributing

Thank you for your interest in contributing to the Developer Hub and to the larger Substrate community! Please review our contributor guidelines prior to any contribution. If you have any further questions, don't hesitate to reach out on our substrate technical community channel.

Directory Structure

This repository is structured as a Docusaurus project with the markdown files organized in the /docs directory. Images and other assets are in the /docs/assets/ directory. The /website directory is a Yarn Docusaurus project with many helpful scripts (e.g. yarn build, yarn start) for working with this codebase.  In the /website directory you will find sidebars.json and siteConfig.js, which are important Docusaurus files. You will find the source code for some top-level pages in /website/pages/en. Follow our contribution guidelines.

Adding a new document

To add a new markdown document:

• Create your markdown document in a suitable directory inside /docs.
• If you have images in your document, put them in the /docs/assets/ directory.
• Documentation should follow our contribution guidelines.
• If you want your document to appear in the sidebar, add its reference in the /website/sidebar.json file under the   corresponding section.

Rename an existing document

To rename an existing document:

• Change the name or path of the document.
• After the change has been merged, go to the Crowdin project,   make sure the translation is already migrated to the new file automatically for all the target languages.
• Then go to Crowdin project settings, remove the   old source file in Files tab.
• If you don't have access to the Crowdin project, please send email to [email protected] with the   file information you want to remove.

Local Testing

• cd into the /website directory.
• Execute yarn install and then yarn start.

The Substrate Developer Hub website should open in a browser window.

Link Checker

Once the website is running, you should use the included Yarn script (yarn check-links) to ensure that your changes do not introduce any broken links and to check for any links that have broken since the last time the check was executed. Please ensure all links are fixed before submitting any changes; if you have questions about broken links that you did not introduce, please create an Issue.

Once you are done with your changes, feel free to submit a PR.

Updates

There is a helper script that can be used to update substrate.dev/rustdocs links in the docs/knowledgebase directory.

# This examples demonstrates updating links from v2.0.0-rc3 to v2.0.0-rc4
OLD_VERSION=v2.0.0-rc3 NEW_VERSION=v2.0.0-rc4 ./scripts/update-kb-rustdocs

Production Deployment

Our production site is at substrate.dev. To deploy to production, merge your update into the source branch. This triggers the CI to build the website AND also pull in multilingual translation from our Crowdin project. The final built static site is then pushed to the master branch and hosted on GitHub Pages.

Staging Deployment

We have a staging deployment at devhub-maindocs.herokuapp.com, which is hosted on Heroku. Please check with the devhub team for the username and password to access the staging site.

To deploy to staging, you could push to the staging-source branch in the repository. This will trigger the CI to build the website, pull in multilingual translations from crowdin, and have the final built static site being pushed to staging branch. This in turn triggers Heroku to pick up the latest commit from staging branch and deploy to the staging site.

License

Substrate documentation is licenced under the Apache 2 license.

frontier-node-template's Issues

Gas Fee Calculation

I want to increase min gas price from 1_000_000_000 to 1_000_000_000_000_000_000 for pallet_evm. but when i try to deploy the contract it says evm.CreatedFailed. I am using polkadot ui explorer for deployment. Please see the below image for input data.

Run private network with alice and bob as Validators and got error!

2021-08-21 11:16:46 Substrate Node    
2021-08-21 11:16:46 ✌️  version 0.0.0-0001ce5-x86_64-macos    
2021-08-21 11:16:46 ❤️  by Parity Technologies <[email protected]>, 2017-2021    
2021-08-21 11:16:46 📋 Chain specification: SingNetwork Testnet    
2021-08-21 11:16:46 🏷 Node name: MyNode02    
2021-08-21 11:16:46 👤 Role: AUTHORITY    
2021-08-21 11:16:46 💾 Database: RocksDb at /tmp/frontier-node02/chains/local_testnet/db    
2021-08-21 11:16:46 ⛓  Native runtime: node-frontier-template-1 (node-frontier-template-1.tx1.au1)    
2021-08-21 11:16:46 Using default protocol ID "sup" because none is configured in the chain specs    
2021-08-21 11:16:46 🏷 Local node identity is: 12D3KooWAKEcB91iAaaRACCzA4uMp6EPvcLyD2BznJN1cyzEwssP    

2021-08-21 11:16:47 📦 Highest known block at #139    
2021-08-21 11:16:47 Listening for new connections on 127.0.0.1:9946.    
**2021-08-21 11:16:47 add_set_reserved_peer with unknown protocol: /paritytech/grandpa/1**    
2021-08-21 11:16:48 🔍 Discovered new external address for our node: /ip4/127.0.0.1/tcp/40334/p2p/12D3KooWAKEcB91iAaaRACCzA4uMp6EPvcLyD2BznJN1cyzEwssP    
2021-08-21 11:16:52 💤 Idle (1 peers), best: #139 (0xb761…229d), finalized #0 (0x4d1c…94a2), ⬇ 0.5kiB/s ⬆ 0.5kiB/s    
2021-08-21 11:16:54 🙌 Starting consensus session on top of parent 0xb761d0d46061a979f412ceb6d0f258a5ed6897e1a787ce40c477667689cd229d    
2021-08-21 11:16:57 💤 Idle (1 peers), best: #139 (0xb761…229d), finalized #0 (0x4d1c…94a2), ⬇ 62 B/s ⬆ 57 B/s  

and then no finalized blocks anymore
Everything is working fine with dev mode

What changes we need to do for connect it to Metamask?

if we need to deploy the smart contract from the Remix for which we need to connect it to the Metamask.
Can you help me what changes we need to do in this code to connect it to the Metamask?

system:ExtrinsicFailed

i try to Transfer with frontier.
but it tell me

system:ExtrinsicSuccess
[{"weight":"100,000,000","class":"Mandatory","paysFee":"Yes"}]
system:ExtrinsicFailed
[{"Module":{"index":"5","error":"0x03000000"}},{"weight":"159,200,000","class":"Normal","paysFee":"Yes"}]
balances:Withdraw
["5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY","125,000,141"]
system:ExtrinsicSuccess
[{"weight":"100,000,000","class":"Mandatory","paysFee":"Yes"}]
system:ExtrinsicSuccess
[{"weight":"100,000,000","class":"Mandatory","paysFee":"Yes"}]

what's wrong with this transaction?

Adding offchain worker throws tokio context error

When trying to add a offchian worker ( from ocw-example pallet ), the node throws Thread 'tokio-runtime-worker' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime'.

As much I can figure out, sc-cli from this template use tokio 0.x version and everything else use 1.x. Any method to resolve this?

MappingSyncWorker function takes 6 arguments but 5 arguments were supplied

frontier-node-template/node/src/service.rs

Line 318 in bc8c82e

MappingSyncWorker::new(

318 |         MappingSyncWorker::new(
    |         ^^^^^^^^^^^^^^^^^^^^^^ expected 6 arguments
319 |             client.import_notification_stream(),
    |             -----------------------------------
320 |             Duration::new(6, 0),
    |             -------------------
321 |             client.clone(),
    |             --------------
322 |             backend.clone(),
    |             ---------------
323 |             frontier_backend.clone(),
    |             ------------------------ supplied 5 arguments

How can I transfer token to the address that created by metamask

Hi @nukemandan
I tried to send some tokens to the address that I created by metamask
I used this code below to generate an ss58 format account then I transferred some values from ALICE account to it
But the balance on my metamask did not change

const { u8aToHex } = require('@polkadot/util');
const { evmToAddress, cryptoWaitReady } = require('@polkadot/util-crypto');

const init = async () => {
    await cryptoWaitReady();
    const args = process.argv.slice(2);

    console.log('evm', evmToAddress(args[0], 42, 'blake2'));
}

init()

How can I interact with the account created by Metamask?

Update for changes in testing for the README

Some breaking changes have been introduced upstream that need to be pulled in here
Waiting on: polkadot-evm/frontier#437

Update to latest master upstream template

Failed to get `fc-consensus` as a dependency of package `frontier-template-node v0.0.0

I've just forked the repo and run cargo build --release for the first time and got Failed to get fc-consensusas a dependency of packagefrontier-template-node v0.0.0`

I've run substrate-node-template previously without problem, so I assumed the frontier-node-template would be work in a similar way.

What might I miss?

getting substrate-prometheus-endpoint error

Getting no matching package found searched package name: substrate-prometheus-endpoint error when I tried to run cargo build --release after deleting cargo.lock file and also getting this error when try to add a new dependency in cargo.toml file.
@nukemandan , kindly check this out.