subnet-evm VS gRPC

Since you can define your own VM, you can define whatever minting logic you want! You have complete control to create per block minting logic or otherwise to manipulate the EVM state however you see fit by creating a fork of Subnet-EVM. The simplest way to define some form of minting logic will be to set the Coinbase address that the Subnet-EVM will use such that all of the fees will be sent directly to that address allowing you to re-distribute these funds as you see fit.

Subnet-EVM APIs are identical to Coreth APIs, except Avalanche Specific APIs starting with avax. Subnet-EVM also supports standard Ethereum APIs as well. For more information about Coreth APIs see here.

Once you've developed a stable Subnet you like, see Create an EVM Subnet on Fuji Testnet to take your Subnet one step closer to production.

Familiarity with process of Deploying a Subnet on Testnet and Deploying a Permissioned Subnet on Mainnet

Avalanche is closing out the year strong with the final AvalancheGo release of 2022. Avalanche Warp Messaging (AWM) is rolling out in AvalancheGo Banff 5, bringing fast, reliable native communications to all Avalanche Subnets. AWM Is available today in both the Golang and Rust VM SDKs for use by any VM builder. Soon, this capability will be rolled out to the subnet-evm, giving Subnet creators native, cross-chain communication capabilities out-of-the-box.

To create an Ethereum Virtual Machine (EVM) compatible Subnet, Avalanche-CLI runs Subnet-EVM as its virtual machine.

After architecting your Subnet environment on the local machine, proving the design and testing it out on the testnet, eventually you will need to deploy your Subnet to production environment. Running a Subnet in production is much more involved than local and testnet deploys, as your Subnet will have to take care of real world usage, maintaining uptime, upgrades and all of that in a potentially adversarial environment. The purpose of this document is to point out a set of general considerations and propose potential solutions to them.

A Subnet and EVM blockchain has been created. Avalanche tools allow users to do this on Mainnet, Fuji or a Local network.

The Subnet-EVM is a simplified version of Coreth VM (C-Chain). This chain implements the Ethereum Virtual Machine and supports Solidity smart-contracts as well as most other Ethereum client functionality. It can be used to create your own fully Ethereum-compatible Subnet running on Avalanche. This means you can run your Ethereum-compatible dApps in custom Subnets, defining your own gas limits and fees, and deploying solidity smart-contracts while taking advantage of Avalanche's validator network, fast finality, consensus mechanism and other features. Essentially, think of it as your own Ethereum where you can concentrate on your business case rather than the infrastructure. See subnet-evm for further information.

official gRPC link

Choose a consistent communication protocol for inter-service communication. Common protocols include HTTP, gRPC, and message brokers like RabbitMQ or Kafka. NestJS supports various communication strategies, allowing you to choose the one that best fits your needs.

gRPC is an open-source high-performance RPC framework developed by Google. The design goal of gRPC is to run in any environment, supporting pluggable load balancing, tracing, health checking, and authentication. It not only supports service calls within and across data centers but is also suitable for the last mile of distributed computing, connecting devices, mobile applications, and browsers to backend services. For more on the motivation and principles behind gRPC's design, refer to this article: gRPC Motivation and Design Principles.

And, gRPC is a high-performance, open-source protocol used for creating APIs. It uses Google's Protocol Buffers as a data format and provides support for streaming and bi-directional communication.

gRPC, built on HTTP/2, inherently supports flow control. The server can push updates, but it must also respect flow control signals from the client, ensuring that it doesn't send data faster than what the client can handle.

Yes, grpc_cli tool uses essentially the same mechanism except implemented as a grpc service rather than as a stubby service. The basic principle of both is implementing the C++ proto library's DescriptorDatabase interface with cached recursive queries of (usually) the server's compiled in FileDescriptorProtos.

See also https://github.com/grpc/grpc/blob/master/doc/server-reflecti...

The primary difference between what grpc does and what stubby does is that grpc uses a stream to ensure that the reflection requests all go to the same server to avoid incompatible version skew and duplicate proto transmissions. With that said, in practice version skew is rarely a problem for grpc_cli style "issue a single RPC" usecases: even if requests do go to two or more different versions of a binary that might have incompatible proto graphs, it is very common for the request and response and RPC to all be in the same proto file so you only need to make one RPC in the first place unless you're using an extension mechanism like proto2 extensions or google.protobuf.Any.

While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future.

The loadBalancingConfig is what we use in order to decide which policy to go for (round_robin in this case). This JSON representation is based on a protobuf message, then why does the name resolver returns it in the JSON format? The main reason is that loadBalancingConfig is a oneof field inside the proto message and so it can not contain values unknown to the gRPC if used in the proto format. The JSON representation does not have this requirement so we can use a custom loadBalancingConfig .

The Dart implementation of gRPC which puts mobile and HTTP/2 first. It's built and maintained by the Dart team. gRPC is a high-performance RPC (remote procedure call) framework that is optimized for efficient data transfer.