Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the possibility to get the inputs in the smart contract #512

Closed
Neylix opened this issue Aug 12, 2022 · 1 comment · Fixed by #822
Closed

Add the possibility to get the inputs in the smart contract #512

Neylix opened this issue Aug 12, 2022 · 1 comment · Fixed by #822
Assignees
Labels
core team Assigned to the core team feature New feature request smart contracts Involve smart contracts

Comments

@Neylix
Copy link
Member

Neylix commented Aug 12, 2022

Is your feature request related to a problem?

In order to enhance the scalability of the smart contract, we can use some batching process.
This can work like this: create a smart contract triggered by interval, at the trigger time the smart contract will take all the inputs it got since the last trigger time and doing some actions.

Describe the solution you'd like

So to do this batching process we have to provide the way to get the inputs and all data associated (content, uco transfer ...) in the smart contract.

We can imagine a function like get_inputs that return a list with all the inputs of the smart contract. These inputs would have the same attribute as a transaction.

Additional context

Epic: #608

@Neylix Neylix added feature New feature request smart contracts Involve smart contracts core team Assigned to the core team labels Aug 12, 2022
@ghost
Copy link

ghost commented Aug 12, 2022

Hey team! Please add your planning poker estimate with ZenHub @apoorv-2204 @imnik11 @Neylix @prix-uniris

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core team Assigned to the core team feature New feature request smart contracts Involve smart contracts
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants