Charging for computationally expensive computations in RSpace, part I

Description

The work of this ticket was to investigate the issue and decide on next steps. Please see comments for outcomes.

Some complex functions such as sorting, ordering of terms occur in the tuplespace, and the tuplespace is not aware of the complexity of these operations. These operations are not accounted for as a result.

These operations are expensive, and in principle, should be charged for. Perhaps an option is to charge a flat rate to interact with the tuplespace. It also heavily depends on the RSpace implementation.

We need to sort out how much we will charge, will we charge for specific operations, if so, what those operations are, and if that is feasible. If not, what is the flat rate to call the tuplespace API, and what Rholang operations this applies to.

Status

Assignee

Kelly Foster

Reporter

Medha Parlikar

Components

Story Points

2

Epic Link

Labels

None

Sprint

None

Priority

Medium