FYI: This is copy from: https://polkadot.polkassembly.io/post/103, and Elara is the fourth project that we planned in our roadmap https://polkadot.polkassembly.io/post/100.
Github: https://github.com/patractlabs/elara and Homepage will be: https://elara.patract.io
In Polkadot, Kusama and other parachains, RPC is the interface between DApp and the network. As the Polkadot network continues to expand, more and more parachains will be online, and more and more parachains will support smart contract functions. Faced with more and more parallel chains, developers need to build and maintain multiple blockchain nodes in order to interact with them, which will be a huge development cost for them. Whether it is facing the development and testing needs of developers or users' online DApp usage requirements, a convenient, fast and stable network access is one of the necessary conditions, and it is also the infrastructure of the Polkadot ecosystem.
Elara is inspired by Infura from the Ethereum ecosystem, named after Jupiter’s seventh moon. Elara's goal is to build a similar infrastructure and network public access services to provide developers with a unified access layer based on Substrate multi-chain. In addition, Elara will be used as part of the smart contract development service, and will be integrated with other components of the Patract toolchain in the future, in terms of contract development environment support, development tools component, contract deployment and DApp release. Elara will be Polkadot’s infrastructure, allowing developers to focus on building upper-level applications.
Summary of Elara's future plan:
** v0.1: Implement Substrate node access**
- Create a server-side framework to develop proxy access, automatic monitoring and data statistics to the RPC service of the Substrate node
- Support developers to use http and websocket protocols to uniformly access the network through the server framework
- Develop a front-end dashboard to display relevant monitoring statistics of the RPC service of the Substrate node
v0.2: Implement function expansion and performance optimisation
- Create account space for developers, support developers to use Github as a third-party login method
- Support multiple projects under the account space
- Provide developers with detailed access information of the DApp project by multiple dimensions, including statistical indicators such as daily and weekly requests, calling methods, and source of user group requests
- Optimise program performance
v0.3: Implement multi-link entry
- Extended program structure, support multi-chain architecture
- Access to Polkadot, Kusama, and other blockchains, such as Jupiter
- Provide developers with public access services of Polkadot, Kusama, and other parachains, such as Jupiter
- Provide multi-chain interface documentation
v0.4: Implement Polkadot ecological access & service operation and maintenance
- Establish a parallel link in Github to enter the process automation specification
- Access to more parallel chains in the Polkadot ecosystem
- Deploy and maintain hundreds of nodes globally
- Support 10,000 developers, each developer account can establish 20 DApp projects, and each DApp project can use 1M daily access service
Detailed design of v0.1 (5 weeks, 21 Sept ~ 26 Oct)
Milestone 1: Design ( (1 designer + 4 developers) * 1 week)
- Design Dashboard UX, displaying relevant monitoring statistics
- Design the data structure to store information such as the number of requests, calling methods, response bandwidth, response codes, etc.
- Design the program framework and complete the technical selection
Milestone 2: Development (4 developers * 2 weeks)
- Deploy a local Substrate node
- Develop a server-side program framework to implement basic functions such as request monitoring, distribution and logging
- Develop proxy access module to implement proxy access for http and websocket requests
- Develop monitoring statistics module to implement the statistics and analysis of requested data
- Develop a front-end dashboard page to display relevant monitoring statistics of the RPC service of the Substrate node
Milestone 3: Integration (4 developers * 1 weeks)
- Integrate agent access module, monitoring statistics module to service program framework
- Integrate front-end dashboard and back-end statistical data services
- Develop a client request program to simulate access requests
Milestone 4: Testing (4 developers * 1 weeks)
- Deploy and test the back-end service program
- Test client request access functions
- Test server monitoring statistics functions
- Test dashboard page functions
Cost of v0.1 (1 designer * week + 20 developers * weeks)
- Operating activities: $3400 ( Rent and Devices: $200 per employee * week )
- Designer payments: $1000 ($1000 per designer * week)
- Developer payments: $30000 ($1500 per developer * week)
- —————————— +
- Total Cost: $34400
- Exchange Rate: $4 / New DOT
- Treasury Proposal: 8600 New DOT
How to verify v0.1: Youtube demo video & Github source
- The Substreate node of the service can be accessed through http and websocket protocols
- Can monitor RPC requests of Substrate nodes
- Can view the relevant monitoring statistics from the dashboard