Present: @frol, @uint, @agostbiro

@frol gives background on Near tooling development:

• Collections recap:
  • Rust STD lib collections: usable but high gas since entire collection must be loaded and serialized each time it’s used.
  • near-sdk-rs collections: solve gas problem, but not std compatible interface bc of ownership differences, no way to get mut reference.
  • near-sdk-rs store: works like rust collections, drop flushes, must do manual flush if checking storage size before drop.
• We should import near cli functionality to cargo near
• We should unify as much as possible between the tooling crates
  • Abi crates sit between the tooling crates
• Some open source smart contracts to contribute to:
  • https://github.com/near/core-contracts
  • https://github.com/NearSocial/social-db
• Github CI vs Buildkite in near-sdk-rs: Buildkite is running on beefy spot instances as the tests there are more comprehensive and sometimes need recompiling nearcore
• Alternate no_std near-sdk-rs implementation with optimized code size and operations: https://github.com/austinabell/nesdie
  • Motivated by rising NEAR prices
• BOS: blockchain operating system
  • JS runtime that fetches code from NEAR blockchain and execute in secure environment
  • BOS + smart contract = DevHub
  • BOS apps can be served on alternate domains: near.org, near.social, boss.gg