Skip to content
Prev Previous commit
Next Next commit
fix
  • Loading branch information
alindima committed Nov 13, 2023
commit a3ccf05553317c6107edbb9ae6d6116ae5172e9c
4 changes: 2 additions & 2 deletions text/0047-random-assignment-of-availability-chunks.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ via governance, only after all validators have upgraded the node to a version th
It needs to be explicitly stated that after the runtime upgrade and governance enactment, validators that run older
client versions that don't support this mapping will not be able to participate in parachain consensus.

### Getting access to core_index in different subsystems
### Getting access to core_index

Availability-recovery can currently be triggered by the following steps in the polkadot protocol:
1. During the approval voting process.
Expand Down Expand Up @@ -164,7 +164,7 @@ Using the candidate hash as a random seed for a shuffle is another option.

Has a fair amount of technical complexity involved:

- Introduces another runtime API that is going to be issued by multiple subsystems. With adequate client-side caching,
- Introduces another runtime API that is going to be queried by multiple subsystems. With adequate client-side caching,
this should be acceptable.

- Requires a networking protocol upgrade on the disputes request-response protocol
Expand Down