The Nakji Network (‘Nakji’) team pushed out a 0.2.0 release on November 11th, 2022. Nakji is a real-time data infrastructure platform that indexes multi-chain data. Using Nakji’s data agnostic, modular, and composable solution, you can easily ingest and query real-time and historical data from multiple blockchains using familiar tools such as REST API and Websocket.
Listed below are areas of improvement and new features that are available as of November 11th, 2022.
- Built Golang SDK and Typescript SDK, which allows any third-party developer to develop a source connector using Golang or Typescript. The documentation on how to use the SDKs will be released in the near future.
- Implemented latency telemetry, which allows us to measure the timing and latency of each subsystem within all parts of our system.
This serves as additional metrics that measure and display the health of our system in the future.
- Created Nakji Connector Explorer, making it easier to explore different data streams that are available on Nakji. The Connector Explorer displays available data streams and examples of returned data.
System-related Bug Fixes
- Keys with zero-length strings were not properly handled and were stored in our database. 0.2.0 purged all records with zero-length keys and now prevents them from being written into the database.
- Certain database table names would impact the system’s ability to query the database. 0.2.0 updated all the names to conform to what the primary database requires, allowing the system to connect consistently and reliably.
- System would crash upon receiving a null timestamp record when sending data to a sink connector. 0.2.0 addressed this issue by not accepting a null record during data insertion.
Source Connector-related Bug Fixes
- The TraderJoe connector requested too many blocks in a single transaction from the RPC provider, resulting in an error when blocks were not acquired and stored. 0.2.0 updated the limits on requests and eliminated this error.
- A subset of EVM connectors were failing due to no response from RPC providers. 0.2.0 added RPC monitoring logic and increased configuration parameters, preventing these connectors from crashing.
- An inconsistency in our BTC full node made our connector unreliable. 0.2.0 refactored the BTC connector to use the new connector library logic, thus eliminating the inconsistency. The connector is now reliably running.
- A rate-limit issue with our connectors for smart contracts that are deployed on the BNB chain led them to crash. 0.2.0 addressed the issue by adjusting the rate limits. In addition, we added more descriptive error messages to identify the cause of the issue faster.
- The AAVE connector was not publishing data to WebSockets. 0.2.0 migrated the AAVE connector to a new connector repo and is now publishing data to WebSocket reliably.
- The Bybit connector had a fatal error during the data conversion process, crashing the connector. 0.2.0 addressed the issue and the connector no longer produces this fatal error.
- Increased request and memory limits in the internal core system due to growing usage. This aims to prevent overconsumption of our resources during public beta.
- Removed message-type field as part of data that is collected in the system and database. Implemented a double-checking logic for null, zero-length strings, or zero as timestamp in the database to verify and filter invalid records.
- Enhanced internal incident handling and management system, allowing the team to mitigate issues faster. Added the ability to create Kafka transactions within the Nakji connector library, eliminating the need for every connector to set up a Kafka connection manually.
- Disabled TTK and CHI connectors due to extremely low transaction volumes.
- Drastically improved the RPC connection stability through a new library that automatically reconnects the connectors to their respective RPCs. TraderJoe and Candymachine connectors are examples that benefited from this new library.
- Refactored all DEX connectors into a single reusable connector that handles multiple smart contracts from multiple chains.
- Improved the backfill system to increase the speed of backfilling and detect any missing blocks in case of a connector failure.
- Added a Protobuf registry system that all connectors can now use to synchronize data shapes, improving developer experience and increasing efficiency.
- Secured additional partnerships with blockchain RPC providers, improving RPC reliabilities for all connectors.
- Released source connectors for WooFi Network and WooSwap for both historical and real-time data streams.
- Released the source connector for Near protocol base chain for real-time data streams. Backfill of historical data is in progress.
- Released the source connector for Flow protocol base chain for real-time data streams. Backfill of historical data is in progress.
About Nakji Network
Nakji Network aids in the relay of information from traditional blockchains to any off-chain that can receive on-chain data points. It does this with industry-setting speed, outpacing competitors while providing an added layer of security to ensure the safety and accuracy of the data being transported.