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 |
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.
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. |
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.
Modifies processing to allow unlimited size of content parameter and changes fee/bundles calculation to be based on request size.
No change
- 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.
No change
Same approach was implemented in FIP-32.
Released in:
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.
None