Skip to main content

Mar 18, 2022 updates

ยท 2 min read
Bohdan Khorolets
Olga Telezhnaya
Vlad Frolov

๐Ÿ‘‹ How's it going, everyone? Seems like we are renaming to Data Team ๐Ÿคท, so Data Team is here with fresh weekly updates. All the week we were working on NEAR Lake pushing it to MVP release as hard as we could.

Since the previous week:

  • We have finished the revision of the StreamerMessage structure and decided to leave it as-is for now. In the future, we plan to adjust the way the underlying structures are serialized to JSON, but this is going to be in the future.
  • NEAR Lake has been deployed to both testnet and mainnet networks in order to index the data from the genesis. (@khorolets) Unfortunately, or maybe, fortunately, yesterday we've noticed that the order of the data we get from S3 is somehow broken. It happens because the object keys on S3 are strings and we forgot about the way numbers represented in strings are being sorted ๐Ÿคฆ. But the fix is on the way and we will restart the indexing process one more time. (@khorolets)
  • Meanwhile, NEAR Lake has been empowered with the CI ๐Ÿ’ช. However, some differences between the environment we build the release in and the servers we run it on causes problems. You can follow the progress by subscribing to this issue. We'll figure it out. (@khorolets)
  • NEAR Lake Framework has been refactored. We are trying different API approaches but looks like we are done here. (@khorolets)
  • Check out the new fancy README for NEAR Lake Framework we wrote this week. (@khorolets)

That's all for this week, folks! Thanks for being with us all this week. Please, have a great and peaceful weekend! Looking forward to see you all next week! Let's keep rocking! ๐Ÿค˜