📣 Masa Protocol release v0.9

[Luka-Loncar]

🌍 Protocol/P2P

• Have a brainstorming session about malicious workers masa-oracle#568
• https://github.com/masa-finance/product-issues/issues/83
• Spike: run signed oracle binary masa-oracle#563
• Spike: investigate Cosmos SDK masa-oracle#595
• Spike: AI classificator for rating miner responses masa-oracle#562
• https://github.com/masa-finance/product-issues/issues/87
• feat(tee): gate nodes with remote attestation masa-oracle#588
• spike: interoperability between Cosmos SDK and libp2p masa-oracle#619
• fix(blockchain): be more strict on blockchain data masa-oracle#577

💅 Scraper

• refactor(twitter): set User-Agent globally from config file masa-oracle#545

Product:

• https://github.com/masa-finance/product-issues/issues/74

🚑 Code health

• feat: embed contracts into the binary masa-oracle#523
• chore(refactor): move node logic to the node package masa-oracle#533

🧪 Code testing

• ci: Smoke test suite masa-oracle#367
• ci: Run unit tests in github actions runners masa-oracle#369
• tests: Twitter package: auth, save cookies, scrape masa-oracle#571
• tests: web scraper integration test masa-oracle#572

⚒ QA

💻 Infra

• https://github.com/masa-finance/issues/issues/198
• https://github.com/masa-finance/issues/issues/193

📶 CI

• ci: Container images release masa-oracle#396
• Automate release note creation masa-oracle#515
• ci: goreleaser fails #80
• test: worker selection integration test masa-oracle#532

📖 Documentation

• Use container images in documentation #73
• Standardize Node Naming Conventions Across All Documentation masa-oracle#425

🔦 Highlights

this release will be focused on get rid of technical debt and consolidating on the new features

✅ Release Checklist

• Stage 0 - Finishing Touches
  • Make sure CI tests are passing.
  • Ensure SDK is aligned to have the neded Oracle features exposed for the release
  • Ensure the CLI is aligned to consume the latest SDK correctly
  • There is a Masa-Oracle release
  • Update release files to bump the version in the Oracle
• Stage 1 - Manual testing
  • How: Using the assets from master, make sure that test scenarios not covered by automatic tests are passing, and that docs are still aligned
    • ...
• Stage 3 - Release
  • Tag Oracle
  • Tag SDK
  • CLI and App needs to point to SDK version and have its own tag
• Stage 4 - After release
  • Release notes needs to be updated in the documentation here: https://developers.masa.ai/docs/masa-oracle/RELEASE_NOTES
  • Update notion documentation about release