# Engineering Weekly Update -- 2021-06-21

**URL:** <https://gov.near.org/t/engineering-weekly-update-2021-06-21/3053>\
**Category:** Engineering Updates\
**Tags:** weekly-updates\
**Created:** [June 21, 2021, 8:40pm UTC](https://gov.near.org/t/engineering-weekly-update-2021-06-21/3053 "2021-06-21T20:40:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nearmax](https://dub1.discourse-cdn.com/flex005/user_avatar/gov.near.org/nearmax/32/13344_2.png) [@nearmax](https://gov.near.org/u/nearmax)\
**Post date:** [June 21, 2021, 8:40pm UTC](https://gov.near.org/t/engineering-weekly-update-2021-06-21/3053/1 "2021-06-21T20:40:31Z")

</div>

# Brief Summary

- [Michal Nazarewicz](https://github.com/mina86) joined the Node Experience team!
- Rethinking and improving our communication channels with validators;
- Improving documentation for integration with exchanges;
- Join discussions:
  - [Contract testing framework](http://gov.near.org/t/revisiting-contract-testing-framework/2920);
  - [Protocol development roadmap](http://gov.near.org/t/protocol-development-roadmap/2903/7);

# Results

- Node Experience is almost done with [the new testing framework for the runtime](https://github.com/near/nearcore/issues/4335);
- Node Interfaces published [useful docs](https://docs.near.org/docs/roles/integrator/exchange-integration#fungible-tokens) on different balances with fungible tokens;
- Developer Platform team is working through near-sdk-rs improvements at a fast pace now that @austinabell and @tachyon joined us;
- Node Interfaces team released [Indexer v0.9.2](https://github.com/near/nearcore/discussions/4385);
- Contract Runtime team implemented ability to patch a state on a local node, useful for testing;
- We now also have [a tool](https://github.com/near/calibrator) to check whether your hardware is good enough for NEAR node. Kudos to the Contract Runtime team;

# Challenges and Blockers

- Contract Runtime teams needs more people to work on performance and safety of Wasm execution. We are actively hiring, see [EM](https://boards.greenhouse.io/near/jobs/5219666002) and [IC](https://boards.greenhouse.io/near/jobs/5297483002) positions;
- Chain+Transaction Runtime+Network teams also need more people. We are also actively hiring for see [IC](https://boards.greenhouse.io/near/jobs/4844629002) position;
- Adding host functions is difficult, because we need to be 100% sure of the correct fees estimation, which consumes a lot of time and blocks Aurora team;

# Action Items

- Everyone needs to prepare for nearcore 1.20.0 release on Testnet on Jun 21, 2021;
- Node Experience continues improving on our communication channels: sync with validators, setup mailchimp, create weekly meetings;
- Developer Platform will rethink versioning of `near-sdk-rs` and `near-api-js`;
- Contract Runtime are actively investigating performance benchmark from Aurora team, we are narrowing down;

# Full reports

- [Node Experience](https://github.com/near/community/discussions/64)
- [Developer Platform](https://github.com/near/community/discussions/65)
- [Contract Runtime](https://github.com/near/community/blob/master/meetings/contract-runtime-wg.md#17062021)
- We are working on Q3 OKRs so no update from Chain, Transaction Runtime, Network this time 🙂

---

<div class="post-metadata">

**Author:** ![khorolets](https://dub1.discourse-cdn.com/flex005/user_avatar/gov.near.org/khorolets/32/70_2.png) [@khorolets](https://gov.near.org/u/khorolets)\
**Post date:** [June 21, 2021, 9:06pm UTC](https://gov.near.org/t/engineering-weekly-update-2021-06-21/3053/2 "2021-06-21T21:06:27Z")

</div>

Upd: I was the source of this misleading. Mainnet is going to be updated to 1.20.0 on Jun 28, 2021

> [@nearmax](#):
>
> Everyone needs to prepare for nearcore 1.20.0 release on Mainnet on Jun 22, 2021;

Is this a mistake? Did you mean testnet? Partners who run indexers are preparing for 1.20.0 next week.

P.S. Thanks for doing this! I really appreciate these reports!