Skip to main content

planed_feature

#Decard planed for coming future

##Core

  1. The development of the current shell will be stopped to enable more resources for the core development.

    a. REST connection from the user end point will not be supported anymore.

Nginx should be used to interface to the core directly (Ex. Websocket)

(To enable web application with direct access to the core)

##Mode2 (To enable more stable network)

a. DART Sync

b. The lates hashgraph consensus voting stored in the DART.

c. Hashgraph synchronization (Enable active voting).

##Blake3 (Faster hash for data dart-indexing and merkle root)

a. The hash function for the DART should be independent of the Signing hash.

b. New hash function for the DART should be enabled

##DART conversion tool (Update the old data-base to blake3)

Tool to convert a DART from sha256 to blake3

The DART should have a hash function type and should be opened with the correct type.

The tool should make a conversion table for all the bills in the network from sha256 to blake3.

##Mirror Node (This should enable community members to run a node)

A mirror node is a full node that makes consensus and DART update without active hashgraph voting.

##TVM (VM for contracts)

Tvmutil should be implemented

TVM should be integrated into the core.

Tauon application library (Contract library).

##Mode3. (Enable a pool of nodes to swap into the network)

Selected the nodes to be swapped from active to mirror.

Swaps the node into the hashgraph as an active node.

##Multiple mode signature (To change the signature schema)

a. The signing method should be changeable in the HiPRC

##Contract identifier

Contract ID should be added to enable multiple types of contract functions groups.

(To prevent a contract from modifying data which is not generated by the contract)

##Wasm-API. (To generate HiBON/HiRPC/signatures in a web browser)

The wallet-api like the (flotter-dart) should be updated for wasm to enable prototyping.

As a test version. The current test CPR-F explore should be converted to use the wasm-api.

##Web/mobile app. (To develop test applications)

  1. Test of the Wasm-API can be used as a PWA.

    • The app should be able to open the camera for QR scanning.

  2. Signing app for QR.

    • Should be able to be use as an ID login. This could just be an HiRPC as stated below.

  3. HiRPC signing.

    • Should be able to sign the HiRPC in the QR and send it to the address in the QR.

##Test system

Set up a system test

It should be possible to start different test networks on different servers/machines.

Community nodes

Test node for community members which can be controlled as a part of the test platform.