This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Minimal collation work-flow and necessary traits (#25)
* collator crate skeleton and description * parachain primitives: proof -> witness and egress format * collation of ingress queues through trait * add ingress collation test * structure for collated ingress * add collated ingress to proposal * witness -> proof * ingress collation and candidate creation + code cleanup * update collator lib to new definitions * address formatting grumble
- Loading branch information
Showing
6 changed files
with
268 additions
and
1 deletion.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
[package] | ||
name = "polkadot-collator" | ||
version = "0.1.0" | ||
authors = ["Parity Technologies <rphmeier@gmail.com>"] | ||
description = "Abstract collation logic" | ||
|
||
[dependencies] | ||
polkadot-primitives = { path = "../primitives", version = "0.1" } | ||
futures = "0.1.17" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,218 @@ | ||
// Copyright 2017 Parity Technologies (UK) Ltd. | ||
// This file is part of Polkadot. | ||
|
||
// Polkadot is free software: you can redistribute it and/or modify | ||
// it under the terms of the GNU General Public License as published by | ||
// the Free Software Foundation, either version 3 of the License, or | ||
// (at your option) any later version. | ||
|
||
// Polkadot is distributed in the hope that it will be useful, | ||
// but WITHOUT ANY WARRANTY; without even the implied warranty of | ||
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the | ||
// GNU General Public License for more details. | ||
|
||
// You should have received a copy of the GNU General Public License | ||
// along with Polkadot. If not, see <http://www.gnu.org/licenses/>. | ||
|
||
//! Collation Logic. | ||
//! | ||
//! A collator node lives on a distinct parachain and submits a proposal for | ||
//! a state transition, along with a proof for its validity | ||
//! (what we might call a witness or block data). | ||
//! | ||
//! One of collators' other roles is to route messages between chains. | ||
//! Each parachain produces a list of "egress" posts of messages for each other | ||
//! parachain on each block, for a total of N^2 lists all together. | ||
//! | ||
//! We will refer to the egress list at relay chain block X of parachain A with | ||
//! destination B as egress(X)[A -> B] | ||
//! | ||
//! On every block, each parachain will be intended to route messages from some | ||
//! subset of all the other parachains. | ||
//! | ||
//! Since the egress information is unique to every block, when routing from a | ||
//! parachain a collator must gather all egress posts from that parachain | ||
//! up to the last point in history that messages were successfully routed | ||
//! from that parachain, accounting for relay chain blocks where no candidate | ||
//! from the collator's parachain was produced. | ||
//! | ||
//! In the case that all parachains route to each other and a candidate for the | ||
//! collator's parachain was included in the last relay chain block, the collator | ||
//! only has to gather egress posts from other parachains one block back in relay | ||
//! chain history. | ||
//! | ||
//! This crate defines traits which provide context necessary for collation logic | ||
//! to be performed, as the collation logic itself. | ||
extern crate futures; | ||
extern crate polkadot_primitives as primitives; | ||
|
||
use std::collections::{BTreeSet, BTreeMap}; | ||
|
||
use futures::{stream, Stream, Future, IntoFuture}; | ||
use primitives::parachain::{self, ConsolidatedIngress, Message, Id as ParaId}; | ||
|
||
/// Parachain context needed for collation. | ||
/// | ||
/// This can be implemented through an externally attached service or a stub. | ||
pub trait ParachainContext { | ||
/// Produce a candidate, given the latest ingress queue information. | ||
fn produce_candidate<I: IntoIterator<Item=(ParaId, Message)>>( | ||
&self, | ||
ingress: I, | ||
) -> (parachain::BlockData, primitives::Signature); | ||
} | ||
|
||
/// Relay chain context needed to collate. | ||
/// This encapsulates a network and local database which may store | ||
/// some of the input. | ||
pub trait RelayChainContext { | ||
type Error; | ||
|
||
/// Future that resolves to the un-routed egress queues of a parachain. | ||
/// The first item is the oldest. | ||
type FutureEgress: IntoFuture<Item=Vec<Vec<Message>>, Error=Self::Error>; | ||
|
||
/// Provide a set of all parachains meant to be routed to at a block. | ||
fn routing_parachains(&self) -> BTreeSet<ParaId>; | ||
|
||
/// Get un-routed egress queues from a parachain to the local parachain. | ||
fn unrouted_egress(&self, id: ParaId) -> Self::FutureEgress; | ||
} | ||
|
||
/// Collate the necessary ingress queue using the given context. | ||
// TODO: impl trait | ||
pub fn collate_ingress<'a, R>(relay_context: R) | ||
-> Box<Future<Item=ConsolidatedIngress, Error=R::Error> + 'a> | ||
where | ||
R: RelayChainContext, | ||
R::Error: 'a, | ||
R::FutureEgress: 'a, | ||
{ | ||
let mut egress_fetch = Vec::new(); | ||
|
||
for routing_parachain in relay_context.routing_parachains() { | ||
let fetch = relay_context | ||
.unrouted_egress(routing_parachain) | ||
.into_future() | ||
.map(move |egresses| (routing_parachain, egresses)); | ||
|
||
egress_fetch.push(fetch); | ||
} | ||
|
||
// create a map ordered first by the depth of the egress queue | ||
// and then by the parachain ID. | ||
// | ||
// then transform that into the consolidated egress queue. | ||
let future = stream::futures_unordered(egress_fetch) | ||
.fold(BTreeMap::new(), |mut map, (routing_id, egresses)| { | ||
for (depth, egress) in egresses.into_iter().rev().enumerate() { | ||
let depth = -(depth as i64); | ||
map.insert((depth, routing_id), egress); | ||
} | ||
|
||
Ok(map) | ||
}) | ||
.map(|ordered| ordered.into_iter().map(|((_, id), egress)| (id, egress))) | ||
.map(|i| i.collect::<Vec<_>>()) | ||
.map(ConsolidatedIngress); | ||
|
||
Box::new(future) | ||
} | ||
|
||
/// Produce a candidate for the parachain. | ||
pub fn collate<'a, R, P>(local_id: ParaId, relay_context: R, para_context: P) | ||
-> Box<Future<Item=parachain::Candidate, Error=R::Error> + 'a> | ||
where | ||
R: RelayChainContext, | ||
R::Error: 'a, | ||
R::FutureEgress: 'a, | ||
P: ParachainContext + 'a, | ||
{ | ||
Box::new(collate_ingress(relay_context).map(move |ingress| { | ||
let (block_data, signature) = para_context.produce_candidate( | ||
ingress.0.iter().flat_map(|&(id, ref msgs)| msgs.iter().cloned().map(move |msg| (id, msg))) | ||
); | ||
|
||
parachain::Candidate { | ||
parachain_index: local_id, | ||
collator_signature: signature, | ||
block: block_data, | ||
unprocessed_ingress: ingress, | ||
} | ||
})) | ||
} | ||
|
||
#[cfg(test)] | ||
mod tests { | ||
use super::*; | ||
|
||
use std::collections::{HashMap, BTreeSet}; | ||
|
||
use futures::Future; | ||
use primitives::parachain::{Message, Id as ParaId}; | ||
|
||
pub struct DummyRelayChainCtx { | ||
egresses: HashMap<ParaId, Vec<Vec<Message>>>, | ||
currently_routing: BTreeSet<ParaId>, | ||
} | ||
|
||
impl RelayChainContext for DummyRelayChainCtx { | ||
type Error = (); | ||
type FutureEgress = Result<Vec<Vec<Message>>, ()>; | ||
|
||
fn routing_parachains(&self) -> BTreeSet<ParaId> { | ||
self.currently_routing.clone() | ||
} | ||
|
||
fn unrouted_egress(&self, id: ParaId) -> Result<Vec<Vec<Message>>, ()> { | ||
Ok(self.egresses.get(&id).cloned().unwrap_or_default()) | ||
} | ||
} | ||
|
||
#[test] | ||
fn collates_ingress() { | ||
let route_from = |x: &[ParaId]| { | ||
let mut set = BTreeSet::new(); | ||
set.extend(x.iter().cloned()); | ||
set | ||
}; | ||
|
||
let message = |x: Vec<u8>| vec![Message(x)]; | ||
|
||
let dummy_ctx = DummyRelayChainCtx { | ||
currently_routing: route_from(&[2.into(), 3.into()]), | ||
egresses: vec![ | ||
// egresses for `2`: last routed successfully 5 blocks ago. | ||
(2.into(), vec![ | ||
message(vec![1, 2, 3]), | ||
message(vec![4, 5, 6]), | ||
message(vec![7, 8]), | ||
message(vec![10]), | ||
message(vec![12]), | ||
]), | ||
|
||
// egresses for `3`: last routed successfully 3 blocks ago. | ||
(3.into(), vec![ | ||
message(vec![9]), | ||
message(vec![11]), | ||
message(vec![13]), | ||
]), | ||
].into_iter().collect(), | ||
}; | ||
|
||
assert_eq!( | ||
collate_ingress(dummy_ctx).wait().unwrap(), | ||
ConsolidatedIngress(vec![ | ||
(2.into(), message(vec![1, 2, 3])), | ||
(2.into(), message(vec![4, 5, 6])), | ||
(2.into(), message(vec![7, 8])), | ||
(3.into(), message(vec![9])), | ||
(2.into(), message(vec![10])), | ||
(3.into(), message(vec![11])), | ||
(2.into(), message(vec![12])), | ||
(3.into(), message(vec![13])), | ||
] | ||
)) | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters