Skip to content

Latest commit

 

History

History
64 lines (51 loc) · 2.61 KB

fip-0034.md

File metadata and controls

64 lines (51 loc) · 2.61 KB
fip title status type author created updated
34
Allow unlimited size of content parameter in Record OBT Data
Final
Functionality
Pawel Mastalerz <[email protected]>
2021-11-24
2022-04-25

Abstract

After this FIP is adopted:

  • Unlimited size of content parameter in Record OBT Data is allowed. Transaction would still be subject to transaction limit.
  • record_obt_data fee is assessed based on size of request.
  • Bundled transactions charged by record_obt_data are assessed based on size of request.

Modified actions

Contract Action Endpoint Description
fio.reqobt recordobt /record_obt_data Modifies processing to allow unlimited size of content parameter and changes fee/bundles calculation to be based on request size.

Motivation

The size on content parameter in New Funds Request was changed to unlimited in FIP-32. It is therefore logical to allow unlimited size of content field in Record OBT Data.

Specification

Modified actions

Record OBT Data

Modifies processing to allow unlimited size of content parameter and changes fee/bundles calculation to be based on request size.

Contract: fio.reqobt

Action: recordobt

Request body

No change

Processing

  • content parameter max size validation is removed.
  • The fee is determined based on the following logic:
    • If paying with fee: record_obt_data fee is charged per each X bytes of request or content parameter size.
    • If paying with bundled transactions: Y bundled transactions are charged per each X bytes of request or content parameter size.
    • Account's RAM is bumped by Z per each X bytes of request or content parameter size.

X, Y, Z, and if sizing is based on request or content parameter will be determined during implementation and this FIP will be updated.

Response body

No change

Rationale

Same approach was implemented in FIP-32.

Implementation

Release information

Released in:

Backwards Compatibility

Since there is no change to the request or response parameters in recordobt action, there should be no impact on existing implementations.

However, if an integrator is currently expecting that the size of the content parameter will not exceed a certain size, their integration may have to be updated. An advisory to all existing integrators should be issued once this FIP is deployed.

Future considerations

None

Discussion link

https://fioprotocol.atlassian.net/browse/WP-163