Q2 2024 Goals

[lastmjs]

Working on Now

Backlog

• NestJS: NestJs #1754
  • Should we make an easy way for the dev, through dfx.json or package.json, to hook up their own polyfills? That might make it really easy to debug in real life...then we could exclude things during the initial compilation process
• dfx extensions: dfx extensions #1124
• introduce the custom field to the dfx.json, breaking change
• we should ensure underscores on all Rust public methods in Azle, and we should simplify the large file uploading hashing to use ic.chunk
• large file uploads from clients over HTTP
• Databases and ORMs: Databases and ORMs #1765
• Kysely
• Drizzle
• TypeORM
• Prisma
• Sequelize
• NextJS
• NuxtJS
• Azle 0.22.0: Azle 0.22.0 #1762
• Kybra 0.7.0: Kybra 0.7.0 kybra#488 (wait until dfx 0.21.0, or whichever has dfx extensions officially)
• Write security page? Show each component of Azle and it's maturity? What do we do about the title of Azle? Do we keep it Beta? Release candidate? Maybe we just move to Azle and keep the disclaimer with a link to the security page?
• npx azle clean seems to not remove images or everything sometimes
• Should we build an EVM example?? Show how to build Ethereum L2s with Azle?
• Can we get some kind of zkVM to run? What about the zkWasm VM?
• finish the work on backend fetch, determine how to communicate with HTTP canisters...we can do cross-canister calls to candid canisters with icp://, we can do HTTPS Outcalls with https://, but what about cross-canister calls to HTTP canisters?
• Cross-canister HTTP requests: if you put in a public canister URL, Azle's fetch should intercept that and do a cross-canister call. They can opt out and do a regular HTTP call with an option in ic.setOutgoingHttpOptions. For custom domains HTTP will be used by default, but they can set a mapping of domain name to canister id with setOutgoingHttpOptions, or maybe we resolve the name in some other way
• Full fetch-based backend canister communication
• Improving HTTP outcalls with automatic consensus?
• Get rid of Candid files if possible, put them in the .azle directory along with the other generated files #1753
• WebSockets?
• Simple stack
  • SQLite heap tests and documentation
  • NestJS
  • TypeORM with SQLite heap
• Databases
  • SQLite examples and tests
  • PGLite (wasm bindgen?)
  • Full Wasm support (wasm bindgen?)
  • ORMs
    • TypeORM
    • Prisma?
• Large HTTP downloads #1742
• Pullable Azle canisters by default (automatically upload Wasm binary to file system at a location like /.config/azle/canister.wasm
• Finish Learnings from ETH Denver: Learnings from ETH Denver #1687
• stable memory filesystem
• Management canister candid updates
• Do we have any tests for environment variables?
• Documentation revamp: Azle 0.21.0 Documentation #1698
• TensorFlow/AI documentation/examples excellent
• Ethereum documentation/examples excellent
  • Make sure to show actually calling into smart contracts...perhaps usdc is one of the best ways of showing this
  • Make all variables in the documentation either automatic or easy to update
  • create a beautiful base l2 example, purchasing things, show people how to use L2 USDC
• Bitcoin documentation/examples excellent
• Before we go to JS conferences we want a complete development stack
  • DB
    • Postgres
      • heap
      • stable memory
    • SQLite
      • heap
      • stable memory
  • ORM
    • TypeORM
    • Prisma
    • Sequelize
  • Server
    • Node
    • Express
    • Nest
    • Next
  • Server-side rendering
    • React
    • Vue
• kybra up-to-date
  • Large Wasm binaries
  • Podman
  • Large uploads
  • assets
  • large assets
• JsonWebToken (waiting on wasi-crypto)
• Create implementations of ICRC tokens
• tECDSA SaaS API?
  • USDC payments
• Automated semantic versioning releases with dependency updates in Rust and npm
• Push http implementation as far down in the stack as possible
• Protocol-level arbitrary message chunking
• Large HTTP uploads
• Everything socket-based at the ICP layer
• Boundary node JWT authentication
• Wasm binary developer environment
• worker threads

Waiting for review and merge

• Get rid of horrible azle error output with stdout/stderr arrays and everything #1752
• get reloadjs to be authenticated now...maybe it should work in production? #1749

Done

• Finish ETH LatAm: ETH LatAm #1691