Near

Please consider this document as a draft. There will be other iterations, perhaps one written by you.

Near Protocol. In their website, Near is described as not just a blockchain protocol, but an operating system that offers a common layer for browsing and discovering open web experiences and is compatible with any blockchain. A few blockchains I know about are scalable by design, allowing a natural operability between actors involved in different node.

Blockchain Scaling Approaches

Interestingly Near is scalable by design. I suggest you to have a read at this document. The summary is that we could compare Near Shards to Ethereum with rollups, where each shard is similar to an optimistic rollup. While Ethereum is evolving in that direction, Near have been designed for scaling, and the smart contract infrastructure is conceived to allow transparently interoperability between shards. Actually taking a look at the concrete implementation it looks like it will not be 100% transparent, but perhaps in a new iteration of this document we'll be able to share some concrete experience. For now, lets analyze the lifecycle of a transaction in a shared context.

Transactions in a sharded context

The immediate outcome of the transaction execution is merely an acknowledgment indicating that the transaction will be executed on the blockchain. This internal execution request is known as a receipt. Conceptually, you can envision the receipt as an internal transaction that facilitates the transfer of information across different shards within the NEAR blockchain.

Tooling

Insturctions for installing the standard tolling for cli(near-cli) and development go to the smart contracts section

Test net transactions explorer: https://explorer.testnet.near.org/transactions/

Mainnet, testnet, and local

I'll add some information here. When you install near-cli you may have a local blockchain, just like, lets say Ganache. More information will be added, let me try it first :)