dapp | Decentralized database of genomic and clinical data | Blockchain library

obviously I would have to have some extrinsic functions that are exposed through my dapp so that when they click and pay for membership, in the runtime, the membership pallet will add that user as a member. Can anyone confirm my thoughts on this?

You can easily do this. pallet_membership is just a container for members. As you will find in the pallet_membership::Config, there are special origins that can be defined as those who have the authority to add or remove a member.

You need a new pallet that will handle the payment to join new members. Let's call this pallet_membership_payment. Once pallet_membership_payment has received the correct payment, it can call into pallet_membership::add_member with whatever origin is required to satisfy it. Not that even if the origin requirement of add_member is EnsureRoot, pallet_membership_payment can still practically get over it, if it is coded as such.

Should I just create a smart contract to handle membership logic and deploy it on edgeware or some other parachain that already exists.

The answer to this really depends on how much further logic does your application have next to handling this membership via fees. Also, it depends on the smart contract payment model (end user pays the fees) works for you If this is it, then it is pretty simple. You might have an easier time in a smart contract model. But, if you need certain optimisations, less fees, more performance etc. you will probably have to consider being your own (para)chain.

You cannot use MetaMask in Electron apps.

But you can use WalletConnect that already may have some desktop clients available.

The first account from the list is referred as a “cow” seed in this file in RSKj. You can take the corresponding private key from there.

Do the following:

1. copy the private key c85ef7d79691fe79573b1a7064c19c1a9819ebdbd1faaab1a8ec92344438aaf4,
2. open your Metamask browser plugin
3. select regtest network
4. import the account
   1. Account icon in the upper right corner
   2. Import account
   3. ‘Paste your private key string here:’
5. Set the just imported account as an active one
6. Enjoy sending your transactions

You can do a CROSS join of the 2 queries:

I assume you have already found Metamask docs on Ethereum Provider API. This section specifies three steps you need to do to make your app work:

• Detect the Ethereum provider (window.ethereum)
• Detect which Ethereum network the user is connected to
• Get the user's Ethereum account(s)

Your snippet does the first part - it detects the provider. As per this section, to detect network you can use the following code

It appears 1.10.9-stable version has a problem and is returning a -rpc error. GETH 1.10.8-stable version works fine when running the geth command with --rpc

web3 is an older implementation which still some clients might use,

window.ethereum is the new api. since some clients still use web3 we should still check for it.

Metamask connects you to the blockchain. Blockchain consists of blocks of data and these blocks of data are stored on nodes. Without nodes, you cannot access blockchain data.

MetaMask allows connectivity to the Ethereum blockchain through the infrastructure available at Infura ( https://infura.io ). This allows users to interact with the blockchain without having to install any node locally. infura connects to to different nodes in a different environment, such as mainnet, rinkeby, ropsten, etc.

web3js or web3py libraries are not related to metamask web3. Metamask provides a provider to web3.js library. This provider tells web3.js library which network we are going to communicate with and then connects to a node in that network.

Once you get the provider, you instantiate a web3 instance:

Issue being that you have more than one provider installed, if you want to only target MetaMask you need to pick that provider alone.