...

FIP-46 complete detailed design (created)

FIP-46 complete development and dev testing. (created)

Design

Summary of changes to fio and fio.contracts

• Note files that will be updated

• Note any changes to global functionalitynone

Actions and Endpoints

• List new/updated actions and endpointsnone

Structs and ABIs

• Note changes to structs and ABIsnone

Tables

• Detail any table updates or migrations

Risks

• Summary of risks, impacts and logistics analysis

SDK Requirements

• Note functional updates needed for SDKsnone

Risks

• we propose setting the timeout for FIO secondary indices to become 10X the present setting. this may have un-expected impacts to node performance (NONE have been found yet)

SDK Requirements

• none

Functional Testing

Design

• Overview of test plan with high-level bulleted test cases

Results

• Link to JS tests and description of which test sections were updated/added

• Paste results of teststest domains access with get_fio_domains for an account with 25k domains.

• run regression tests on all feature/function of FIO. (dev testing will run the smoke tests).

Performance Testing

Design

• Overview of test plan with high-level bulleted test cases

Results

• Summary of performance tests that were run and resultsperf testing is same as functional testing for get_fio_domains with one account owning 25k domains.

Fork Testing plan

• List all of the pertinent tests, required setup, and expected results.List all pertinent tests pertaining to testing with different versions of the core code.

• List all pertinent tests pertaining to pre-contracts update and post contracts update

Rollout/Release plan

• Make a comprehensive list of all necessary changes

• Include (new actions, removed actions, MSIGs for all required operations, and step by step instructionsno fork testing is required.

• this is not a forking change to the FIO Core.

Rollout/Release plan

• documentation must be updated on dev hub for the new timeouts for primary and secondary indices.

• new FIO nodeos version needs to be supplied to the community.

Rollout/Release verification plan

• Include step by set instructions for how to verify that the changes are on chain after rollout.

• Bonus points if you make an automated script performing the verificationsverify domain access works as expected.

• verify test net smoke tests complete without errors on test net.