Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Availability of parachain data #371

Closed
rphmeier opened this issue Jul 18, 2018 · 0 comments · Fixed by #465
Closed

Availability of parachain data #371

rphmeier opened this issue Jul 18, 2018 · 0 comments · Fixed by #465
Assignees

Comments

@rphmeier
Copy link
Contributor

rphmeier commented Jul 18, 2018

(without economic games)

Part 1: Data store

We would want to plug this into the client's RocksDB instance somehow, and answer BlockData requests out of it.

In the consensus worker, we shouldn't cast an Available vote until we've actually ensured availability of the data.

https://github.com/paritytech/polkadot/blob/ddc8d705570fda5f492895373b69b9b84cae1d69/polkadot/consensus/src/shared_table/mod.rs#L256-L257

should be preceded by a call to store.make_available(block_data, extrinsic) or something similar.

For now, just storing block data, indexed by (Hash, ParaId), the relay chain block hash and parachain ID.

Part 2: Network protocol for fetching data

This would be used as a last resort in case the data doesn't appear to be easily available.
Finding validator who is bonded to have the data and requesting from them. The validator answers out of the data store

We would add this in the PolkadotProtocol, probably with a trait object DataStore

@rphmeier rphmeier self-assigned this Jul 25, 2018
lamafab pushed a commit to lamafab/substrate that referenced this issue Jun 16, 2020
…ytech#371)

* Claims module uses a hex representation of the address not raw

* Fix test
JoshOrndorff pushed a commit to moonbeam-foundation/substrate that referenced this issue Apr 21, 2021
Fix the link to the crate-level docs (rustdocs)
liuchengxu added a commit to chainx-org/substrate that referenced this issue Aug 23, 2021
* Ensure minimal validator count

Fixes paritytech#362

* Remove needless retain

* Slash validators on new session insteead of every block

Closes paritytech#369

* Trigger OnAssetChanged

Fixes paritytech#363

* Update acceleration of setup_trustee to 1000

- Closes paritytech#371

* Slash maximum between 1% of jackpot and minimum penalty

Closes paritytech#374

* Update wasm

* 1% instead of 1/10!!!
liuchengxu pushed a commit to chainx-org/substrate that referenced this issue Aug 23, 2021
Signed-off-by: koushiro <koushiro.cqx@gmail.com>
liuchengxu pushed a commit to autonomys/substrate that referenced this issue Jun 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant