Plasma is not directly a client feature. It's an architecture to facilitate certain scenarios.
How a Plasma implementation is actually done is a separate issue and I don't think any Ethereum client has built-in Plasma support. It's just something that is built around the Ethereum infrastructure and therefore any client can be used.
Actually most of the ...
That is called a Deflationary Token.
You can override the transfer function of an ERC-20 token and add a burn function that will burn a percentage of tokens that are being transferred.
Keep in mind that you should check both from and to addresses are non-zero, otherwise it would burn the mint and burn transfers.
Pantheon (0.8.1) has no account management. It will only create a server private key, which is stored unencrypted in datadir/key. This key will also be used as the sealer account in Clique-PoA. Hence the public address stored in extraData in genesis.json has to correspond to this private key.
Until client teams answer for themselves, here is information on non-GPL clients.
From What exactly is an Ethereum client and what clients are there? there's two of them:
Besu (Java) is Apache 2.
Trinity (Python) is MIT.
There are two types of scaling solutions for Ethereum: layer 1 and layer 2.
Layer 1 refers to the basic Ethereum instrastructure. Changes/improvements to layer 1 mean typically a hard fork. Eth2.0 is a good example of a layer 1 solutions and it's the most prominent one. Various other smaller improvements have been performed also earlier (check the ...
Besu supports Ethereum Mainnet and Ethereum Classic, each with over 11 million blocks, on Proof of Work consensus. There is also a consortium chain I am aware of that currently has well over 18 million blocks on IBFT2 consensus. These are all production networks.
You can specify solidity version for the web3j-maven-plugin via setting the following property: solidity.version.
In your case, it is already specified as your pom file contains:
So, the plugin will automatically install the right solc ...
Most likely you are using v1 secret engine. dev mode by default uses v2 secret engine and EthSigner also expects v2 secret engine. In production mode, you have to explicitly set v2 when creating it. See https://www.vaultproject.io/docs/secrets/kv/kv-v2 for more details. It also points to this tutorial which provides exact steps to enable it. https://learn....
What consensus type do you want to use ?
You can find a tutorial to create a private network depending on the consensus:
The Besu client supports
The Besu client supports common smart contract and Dapp development, deployment, and operational use cases, using tools such as Truffle, Remix, and web3j. The client supports common JSON-RPC API methods such as eth, net, web3, debug, and miner.
Besu doesn’t support key management inside the client. You can use EthSigner with Besu ...