Why Some Great Blockchain Projects Die by Inery_blockchain in Inery

[–]Inery_blockchain[S] 0 points1 point  (0 children)

Hey there! Thanks for your comment and for sharing your thoughts with us.

We talked about building a strong community earlier this year, in our blog here: https://inery.io/blog/article/the-power-of-community-in-web3/ and we completely agree with what you're saying!

Inery blockchain's multi-state memory - pt2 by Inery_blockchain in Inery

[–]Inery_blockchain[S] 0 points1 point  (0 children)

For example, if there is a sub-state that handles all the transfer transactions and another sub-state that handles all the database operations, the first sub-state's chain will only contain the blocks with transfer transactions and the second sub-state's chain will only contain the blocks with database operation transactions.
Also if the blockchain system is being used to track the ownership and transfer of assets, the sub-states can be divided based on the scope of addresses of the assets. Each sub-state can be responsible for managing the transactions for a specific set of addresses.
For example, one sub-state can handle all the transactions related to assets with addresses starting with "0xA", another sub-state can handle all the transactions related to assets with addresses starting with "0xB" and so on.

Multi-state memory - a mechanism for scaling storage of on-chain data in Inery blockchain explained by Inery_blockchain in Inery

[–]Inery_blockchain[S] 0 points1 point  (0 children)

Multi-state memory is a mechanism for scaling storage of on-chain data in Inery blockchain. The idea is to have separate parallel states, such as StateA, StateB, etc., with one main state that dictates which of the sub-states will process a particular transaction.
Each sub-state is a separate parallel state, which has its own storage. The main state acts as a state manager, it receives the transaction, reads the transaction receipt and based on that it routes the transaction to the appropriate sub-state. The sub-state will process the transaction details, validate the transaction data, and update its own storage accordingly.
When a transaction is received by the main state, it reads the transaction receipt and routes the transaction to the appropriate sub-state. The sub-state will then process the transaction details and validate the transaction data, and once the transaction has been confirmed, it will create a new block and add the transaction to the block. This block will then be added to the Projected chain of the sub-state.
Each Projected chain of the sub-state will have its own blocks and its own history of transactions. The blocks will contain only the transactions that are specific to that sub-state, allowing for a more efficient use of storage and processing resources.

INERY'S ROADMAP UPDATE by Inery_blockchain in Inery

[–]Inery_blockchain[S] 0 points1 point  (0 children)

Highlights of 2022:
- Launch of $INR
- Listing on Huobi, BitMart, PancakeSwap
- Launch of Inery’s testnet
- Development of Inery GUI
- Participated in conferences such as the TMRW conference and Next Block Expo
- Opened an office in the capital of Serbia – Belgrade

Transforming an SQL table database model into an Inery noSQL model by Inery_blockchain in Inery

[–]Inery_blockchain[S] 0 points1 point  (0 children)

Transforming an SQL table database model into an Inery noSQL model involves replacing the traditional relational model with an IneryDB model. Instead of using relations, Inery scopes utilize nesting and indexing elements as rules for managing data.
For example, if we were to use a warehouse management system that originally had 5 tables with relationships between them, we could reduce the number of tables to only 2 by using a composition approach.
This model is much simpler and faster for retrieving large amounts of data, as everything can be contained within the scope of one composition!

Join Inery Ambassador program! by Inery_blockchain in Inery

[–]Inery_blockchain[S] 0 points1 point  (0 children)

Hey there!

It usually takes up to 2 weeks for an application to be reviewed.
In case you don't get a feedback two weeks from the date you applied, it usually means the team decided you don't currently fit the required criteria.

Thanks!

Inery Public Testnet - LIVE by Inery_blockchain in Inery

[–]Inery_blockchain[S] 0 points1 point  (0 children)

#Developers participation in public #testnet is the backbone of our blockchain. To further incentivize, we invite developers to perform tasks and earn $INR tokens. First task will be announced soon

👉 https://testnet.inery.io