### BUILDER UPDATE: Feb 8 - Feb 14, 2024 (posted via [Build DAO Gateway](https://nearbuilders.org/feed?tab=update)) **✅ DONE** - I've rewritten the nearbader verifiers API to ES6, as initially I've written it using CommonJS to validate PoC: [NearBadger GitHub PR #2](https://github.com/NEARBuilders/nearbadger-verifiers-api/pull/2) - I've added support for Farcaster on nearbadger verifiers API: [NearBadger GitHub PR #3](https://github.com/NEARBuilders/nearbadger-verifiers-api/pull/3) - I've enhanced challenge security on nearbadger API: [NearBadger GitHub PR#4](https://github.com/NEARBuilders/nearbadger-verifiers-api/pull/4) - I've added support for X (Twitter) verifications on nearbadger verifiers API: [NearBadger GitHub PR #5](https://github.com/NEARBuilders/nearbadger-verifiers-api/pull/5) - I've replaced nonce by maxBlockHeight on nearbadger verifiers API, in order to limit the amount of time our issued proof is valid to claim in the smart contract: [NearBadger GitHub PR #6](https://github.com/NEARBuilders/nearbadger-verifiers-api/pull/6) - I've reviewed Prometheus' PR on nearbadger verifiers API, it adds endpoints to verify NEAR account's info such as account age and issue a signature:[NearBadger GitHub PR #7](https://github.com/NEARBuilders/nearbadger-verifiers-api/pull/7) - I've reviewed and merged Megha's PR improving the Sputnik DAO SDK: [sdks.near GitHub PR #12](https://github.com/NEARBuilders/sdks.near/pull/12) - I've been working on the nearbadger authentication page for nada.bot, which I expect to finish tomorrow: [NearBadger Authentication Component](https://near.org/near/widget/ComponentDetailsPage?src=mattb.near/widget/NearBadger.Pages.Authentication) - I've been setting up the VM project locally and created a new VM method (WIP). The new methods I'm working on are called `VM.prepare` and `VM.import`: - `VM.prepare([src])` is a method that loads the components into the cache and waits until they are actually cached. Returns a Promise that resolves to a Boolean indicating whether it has loaded successfully or not. It is useful before using `VM.require(src)`, as the components will be already cached and no error will be displayed. - `VM.import([src])` it loads a list of components. Returns a Promise that resolves to key/value object containing the required components, where key is the component name (i.e. `SDKs.Utils.CryptoJS` would be `CryptoJS`). Internally it leverages the new `VM.prepare` method to cache the components, and once cached, it uses `VM.require` to return them in an object: [Test Component using VM.import (formerly VM.asyncRequire)](https://near.org/mattb.near/widget/TestVmAsyncRequire) **⏩ NEXT** - Start working on the Lens SDK Beta version, lately been quite busy with nearbadger for nada.bot release - Finish nearbadger Authentication page and finish implementing X (Twitter) verification - Submit the `VM.prepare` and `VM.import` proposal & PR to the Social VM repo - Recover from my toothache 😭 **🛑 BLOCKERS** - None