What is REITs CHAIN?

REITs CHAIN global asset digitization ecological public chain, is decentralized and open source public chain with smart contracts. With a rich Web3+DeFi+NFTs+DAOs+Metaverse new ecology. With PoW+DPoS hybrid mechanism, two ledgers running simultaneously, decentralized, high throughput, security, encryption, privacy and other features, and more flexible mining method and more stable block output, it will provide unlimited new opportunities for various asset digitization services. It becomes a super underlying service public chain that supports a large number of commercial-grade applications.

The mechanism of PoW is prone to bifurcation due to different community consensus, thus generating different blockchains and communities, and the dominant force of bifurcation is mainly miners and developers, which will bring great uneasiness to investors. And the introduction of DPoS consensus mechanism will be good to avoid the community split generated by the fork.

The DPoS mechanism is efficient and responsible for selecting legitimate transactions from the transaction storage pool, packing them into blocks, and then broadcasting them to the network via the p2p protocol, while the implied PoW requires miners to complete a certain proof of workload to prevent the main chain from forking, and establishes an elimination mechanism, so that any node that makes a false entry or has a biased record within 14 seconds will be eliminated. Thus, speed, security and decentralized nature are taken into account. This will make the community and ecological development more stable, orderly and effective.

So to summarize, when you send RCH to someone, the transaction must be added to the block which will get mined. The updated state is then shared with the entire network.

What is REITs Chain's API?



REITs CHAIN is an Ethereum Virtual Machine (EVM) compatible, the "operating system" of the blockchain world. The REITs CHAIN public chain builds distributed data storage space, network transmission environment, transaction and computing channels for the blockchain, uses encryption algorithms to ensure network security, and realizes the normal operation of the node network through consensus mechanism and incentive mechanism. REITs Chain is REITs CHAIN's leading blockchain browser, search, API and analytics platform. As a way to provide fair access to blockchain data, the community developed REITs Chain's development API interface, enabling developers to directly access REITs Chain's block explorer data and services through GET/POST requests. The API interface of REITs Chain is open to the community and can be called by developers (including third-party) API endpoints, and then develop applications that meet their business needs.

API Endpoints Introduction

Your app may need to show a user's RCH balance , check the transaction history of an address  or get the latest information about a new token and its price .

For that you may find a suitable endpoint from our wide range of APIs that you can simply query to provide data while you remain fully focused on building your applications.

REITs Chain's API provides requests including the following:

ACCOUNTS:An REITs CHAIN account is an entity with an ether (RCH) balance that can send transactions on REITs CHAIN. Accounts can be user-controlled or deployed as smart contracts.

The Account-related HTTP requests link is as follows:
https://github.com/REITsCHAIN/rch_api_doc/blob/main/reference/api-reference/account.md

REITs CHAIN has two account types:

Externally-owned – controlled by anyone with the private keys
Contract – a smart contract deployed to the network, controlled by code. 

Both types of accounts are the same for EVM.

The difference and relationship between an external account and a contract account is this: an external account can send a message to another external account or contract account by creating and signing the transaction with its own private key.

Transferring a message between two external accounts is a process of value transfer. However, a message from an external account to a contract account activates the contract account's code, allowing it to perform various actions (such as transferring tokens, writing to internal storage, mining a new token, performing some operations, creating a new contract, etc.).

Only when an external account issues a command, the contract account performs the corresponding action.

Contract deployment is the deployment of the compiled contract bytecode to the REITs CHAIN blockchain by sending a transaction from an external account (the real deployment is successful after the block is released by the actual miner).

Contracts and tokens: Token contracts are a type of contract, so they will have data similar to a contract. But because they have value and can be traded, they also have other data points.

Type - They are RRC-20, RRC-721 or other token standards.
Price - If they are RRC-20, they will have a current market value.
Market Value - If they are RRC-20, they will have a market value (calculated from price \ * total supply).
Total Supply - The number of tokens in circulation.
Holders - The number of addresses holding the tokens.
Transfers - The number of times tokens have been transferred between accounts.
Transaction History - History of all transactions including tokens.
Contract Address - The address of the token deployed to the main network.
Fractional Digits - RRC-20 tokens are divisible and have fractional digits.

Links to requests related to contracts and tokens are as follows:
https://github.com/REITsCHAIN/rch_api_doc/blob/main/api-reference/contracts-and-tokens.md

Blocks:Blocks are batches of transactions with a hash of the previous block in the chain. This links blocks together (in a chain) because hashes are cryptographically derived from the block data. This prevents fraud, because one change in any block in history would invalidate all the following blocks as all subsequent hashes would change and everyone running the blockchain would notice.

How do blocks work?

To preserve the transaction history, blocks are strictly ordered (every new block created contains a reference to its parent block), and transactions within blocks are strictly ordered as well. Except in rare cases, at any given time, all participants on the network are in agreement on the exact number and history of blocks, and are working to batch the current live transaction requests into the next block.

Once a block is put together (mined) by some miner on the network, it is propagated to the rest of the network; all nodes add this block to the end of their blockchain, and mining continues. The exact block-assembly (mining) process and commitment/consensus process is currently specified by REITs CHAIN’s “PoW+DPoS” protocol.

Links to requests related to the blocks are as follows:
https://github.com/REITsCHAIN/rch_api_doc/blob/main/api-reference/blocks.md

TRANSACTIONS:Transactions are cryptographically signed instructions from accounts. An account will initiate a transaction to update the state of the REITs CHAIN network.The simplest transaction is transferring RCH from one account to another.

What's a transaction?

An RCH transaction refers to an action initiated by an externally-owned account, in other words an account managed by a human, not a contract. For example, if Bob sends Alice 1 RCH, Bob's account must be debited and Alice's must be credited. This state-changing action takes place within a transaction.

Links to requests related to the transactions are as follows:
https://github.com/REITsCHAIN/rch_api_doc/blob/main/api-reference/blocks.md

RPC PROXY:RPC (Remote Procedure Call), that is, remote procedure call, does not require users to understand the underlying network technology, and requests services from remote computer programs through the network. The RPC protocol assumes the existence of some transport protocol, such as TCP or UDP, to carry information data between communicating programs. The protocol used in REITs CHAIN is the HTTP protocol.

Links to requests related to the RPC proxy are as follows:
https://github.com/REITsCHAIN/rch_api_doc/blob/main/api-docments/rpc-proxy.md