YEARONE

Our @YearOneIO projects are about to get some assistance thanks to @NOWNodes 🙏

"Look, if you had one smart contract or one protocol To build everything you ever wanted in one moment Would you capture it, or just let it slip?" Let's talk about it.

Ever wonder why on most blockchain wallets you have to import an asset you hold into your wallet instead of the wallet already knowing what it holds?! It's annoying isn't it... That's because on Ethereum (and most EVMs) there's a quirky design choice where ONLY assets know which wallets hold them instead of wallets also knowing, so that's why you have to manually let them know. Thankfully @lukso_io Universal Profiles (@ERC725Account) have a standard built into them (LSP5 - Received Assets) that solves this problems. This standard enables accounts to keep an inventory of received assets in special storage slots on the blockchain which is not something EOAs can do. This both makes the User Experience a whole lot better AND opens up endless possibilities for additional applications that can be built for the user. Very clever! $LYX #pinkpilled

Finally onto the GRAVE UI integration with the Universal Assistants Protocol (UAP). Crazy that the idea for the UAP was born over a year ago. Soon after the @lukso_io Build UP #2 on @buidlbox we realized an UP!'s full potential could only be truly unlocked if multiple different automations could operate together on the same LUKSO transaction. It's true what they say about ideas though...

GRAVE: Over the last couple of days updated the new Screening Assistant contracts that will be specific to the GRAVE as well as devising a new "primitive" for the Universal Assistant Protocol, called a "list". This primitive is useful when a user relying on a Screener might at times want to override its result for a specific set of assets or addresses :). Example: User relying on a curated list to allow asset to bypass the GRAVE might want to also add exceptions for assets on the curated list. Wrote some unit tests for all this!

GRAVE: another day, and we keep digging. 1. migration to ethers6 complete as well as getting UI back to functional state after all the LUKSO package updates 2. created new mocks for new GRAVE UI that i’ll be implementing as part of its upgrade 3. Upgraded UAP so that executive can choose not to execute a tx and tell protocol about it with a NO_OP code 4. GRAVE might be getting its first Curated List courtesy of @JakGrills and @_CupCo! 5. Additionally, in a brainstorm, @JakGrills suggested another pretty cool Screener Assistant! One that checks how many followers the creator of an LSP7 or LSP8 asset has and trusts/distrusts a digital asset based on that. Could be very useful in the GRAVE and many other applications. attaching rough new GRAVE mocks for glimpse into how building happens for me

Today continuing on the GRAVE frontend upgrade. Going from Ethers 4 to 6 is no fun. Then also refactoring the wallet connection to be simpler and solely built using ethers. This is all taking much longer than expected. A lot of refactoring of existing GRAVE set up functionality so that it’s based on the Universal Assistants Protocol (UAP). As a side quest, upgraded the UAP smart contracts today to handle chaining Screening Assistants with AND or OR chains. That means that an Executive Assistant can be configured to execute only if all Screener conditions are met in the case of an AND chain, or if at least one Screener condition is met in the case of an OR chain. This might sounds abstract now but the possibilities this architecture open up for Universal Receiver Delegates will be evident very soon. This also completes elements the core protocol we hoped to build. Now that the foundation is built the possibilities are quite literally endless. #LUKSO $LYX