Polkadot programming - development using node template

 Polkadot - Substrate development Step by Step


Following commands will work on macOS... Good luck


This steps are for starting single node at backend and starting front end to explore ( e.g. transfer fund from one account to another)


----start----


Install Homebrew

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"


Install opensssl

brew update && brew install openssl


Install Rust and RustToolchain


curl https://sh.rustup.rs -sSf | sh


source ~/.cargo/env

rustup default stable

rustup update

rustup update nightly

rustup target add wasm32-unknown-unknown --toolchain nightly


verify installation by 


rustc --version

rustup show


Prepare a Substrate node using the node template


Setup node template. Its a provides a working development environment so that you can start building on Substrate right away.



git clone https://github.com/substrate-developer-hub/substrate-node-template

cd substrate-node-template

# We want to use the `latest` tag throughout all of this tutorial

git checkout latest

cargo build --release



install the front-end template:


Install node.js

verify by

node --version


sudo npm install --location=global yarn


verify by

yarn --version


Install front end inside recently created node template directory


git clone https://github.com/substrate-developer-hub/substrate-front-end-template


cd substrate-front-end-template

# We want to use the `latest` tag throughout all of this tutorial

git checkout latest

yarn install


Start the local Substrate node



 ~ % cd substrate-node-template 

substrate-node-template % ./target/release/node-template --dev

   


Start the front-end template


To use the front-end template:

  1. Open a new terminal shell on your computer, change to the root directory where you installed the front-end template.
  2. Start the Front-end template by running the following command

    yarn start

Open http://localhost:8000 in a browser to view the front-end template.


Test


select the account for Dave and transfer minimum amount stated on UI


...success....


----end----

Comments

Post a Comment

Popular posts from this blog

Qlik Sense Important Links

Qlik Sense learning https://learning.qlik.com/ https://www.qlik.com/us/services/training/self-paced-learning Qlik sense pricing   https://www.capterra.com/p/145530/QlikSense/#pricing https://www.qlik.com/us/pricing/qlik-sense-client-managed Qlik Sense Server Installation Document preview of Qlik Sense Server Installation Step By Step Guide.pdf https://community.qlik.com/t5/Documents/Qlik-Sense-Server-Installation-Step-By-Step-Guide/ta-p/1480562 https://community.qlik.com/t5/New-to-Qlik-Sense/how-to-download-Qlik-Sense-server/td-p/869140 Support Portal https://support.qlik.com/QS_Home_Page Qlik FIPS Support FIPS mode is not supported out of the box for Qlik Sense, QlikView, and Qlik NPrinting. Workarounds exist for NPrinting and Sense.  For general information about FIPS and Microsoft's statement around it, see  Microsoft's Security Guidance blog. https://community.qlik.com/t5/Knowledge-Base/Qlik-Software-and-FIPS-mode/ta-p/1717239 https://docs.microsoft.com/en-US/windows/...
Read more

Cloud Architecture Notes

Image
The architectural priorities and needs of every app are different, but the four pillars of architecture are an excellent guidepost you can use to make sure that you have given enough attention to every aspect of your application: Security : Safeguarding access and data integrity and meeting regulatory requirements Performance and scalability : Efficiently meeting demand in every scenario Availability and recoverability : Minimizing downtime and avoiding permanent data loss Efficiency and operations : Maximizing maintainability and ensuring requirements are met with monitoring A layered approach to security Defense in depth is a strategy that employs a series of mechanisms to slow the advance of an attack aimed at acquiring unauthorized access to information The common principles used to define a security posture are confidentiality, integrity, and availability, known collectively as CIA. Confidentiality - Principle of least privilege. Restricts access to informa...
Read more

AWS Rout53 NS records do not match with whois dns records OR Your site NOT working with registered domain name? Check this...

  Log in to your AWS web console Select Route53 service Select Hosted Zones in the left pane Select domain name (but do not click on the domain name, just select the radio button) Notice the 4 name servers in the right pane. Next, go to domain registrar site (in your case stay in Route53), log in and configure name servers for your domain. In Route53: select 'Registered domains' in the left pane, click on your domain name, verify that in the upper right you have name servers from step 5, if they don't exactly match, click 'Add/Edit Name servers' and enter name servers from step 5) After this you will receive email on your registered email id with AWS. Once the sync os done you will get notified. After notification you can try your ULR <some-name>.com or www.<some-name>.com "A" records created during route 53
Read more