[Proposal] Plugins about warp HOT 4 CLOSED

Hey @andreespirela .

Can you please explain what is the potential use case?
I'm afraid that using non-standard (maybe even non-public?) plug-ins (that somehow extend the base protocol) could potentially break the contract state evaluation on endpoints, that are un-aware of such add-ons.

from warp.

Hey.

Can you please explain what is the potential use case? I'm afraid that using non-standard (maybe even non-public?) plug-ins (that somehow extend the base protocol) could potentially break the contract state evaluation on endpoints, that are un-aware of such add-ons.

We have a cache API and the idea is to be able to pass some of these functions to do some verifications to the contract. In the future, it might also be useful to create our own execution functions or utilities that users can use inside Verto.

from warp.

Hey.
Can you please explain what is the potential use case? I'm afraid that using non-standard (maybe even non-public?) plug-ins (that somehow extend the base protocol) could potentially break the contract state evaluation on endpoints, that are un-aware of such add-ons.

We have a cache API and the idea is to be able to pass some of these functions to do some verifications to the contract. In the future, it might also be useful to create our own execution functions or utilities that users can use inside Verto.

I see, we will discuss this internally and will let you know soon.

from warp.

@andreespirela , as we're really having some doubts re. this feature (as mentioned previously - using some custom plugins will basically ruin the option to properly evaluate the state by any of the network participants) - one last proposal - have you considered extracting your caching API to a separate class and (with the help of a proper build process) - merge it with the contract's code?

An example of such feature is available here:
https://github.com/redstone-finance/redstone-smartweave-contracts/blob/main/src/common/ContractAdmin.ts
or here
https://github.com/redstone-finance/redstone-smartweave-contracts/blob/main/src/common/ContractInteractions.ts

These classes are then bundled into the resulting contract's source code (using esbuild's iife bundle format - https://github.com/redstone-finance/redstone-smartweave-contracts/blob/main/build.js#L11) and used within contracts like this:
https://github.com/redstone-finance/redstone-smartweave-contracts/blob/main/src/token/token.contract.ts#L139

or:
https://github.com/redstone-finance/redstone-smartweave-contracts/blob/main/src/providers-registry/providers-registry.contract.ts#L45

from warp.