feat: exex connection, read() macro

[rkdud007]

this PR target for exex connection initalization & minimal compliance example ( not full sophisticate logic ) - and tried to evaluate what UX is required for hdp-sp1, what additional macros are required.

read() macro

now we have client.write(v) method on DataProcessorClient and the value passed as v will be captured in program with hdp::read() macro. Reasoning behind is again, we need to abstract behavior of online mode and zkvm mode. v will be just assigned as value during online mode through stdio pipeline. during zkvm mode, v will be deliver to zkvm program via SP1Stdin. and this macro is abstracting this two behaviors in conditional compilation.

hdp-sp1/hdp-macro/src/lib.rs

Lines 25 to 45 in f688939

	let hdp_read_fn = quote! {
	mod hdp {
	use serde::{Serialize, de::DeserializeOwned};
	cfg_if::cfg_if! {
	if #[cfg(target_os = "zkvm")] {
	pub fn read<T: DeserializeOwned>() -> T {
	sp1_zkvm::io::read::<T>()
	}
	} else {
	use std::io::{self, Read};
	use std::fmt::Debug;
	pub fn read<T: DeserializeOwned + Debug>() -> T {
	let stdin = io::stdin();
	let mut reader = stdin.lock();
	let deserialized_value: T = bincode::deserialize_from(&mut reader).expect("Failed to deserialize input");
	deserialized_value
	}
	}
	}
	}
	};

exex connection with hdp-sp1

For compilance example, exex need to pass block_number and potentially some context related transaction ( for now simplicity i just passed tx length) to the hdp program. So base on the ability given by read() macro above, exex will keep stream dynamic values into hdp program that DataProcessorClient abstracted running online -> zkvm mode.

hdp-sp1/examples/compliance/compliance/src/main.rs

Lines 25 to 34 in f688939

	ExExNotification::ChainCommitted { new } => {
	info!(committed_chain = ?new.range(), "Received commit");
	let block = new.block(new.tip().block.hash()).unwrap();
	let block_number = block.number;
	let transaction_length = block.body.transactions.len() as u64;
	let mut client = DataProcessorClient::new();
	client.write(block_number);
	client.write(transaction_length);
	let (proof, vk) = client.prove("../program".into()).unwrap();
	client.verify(&proof, &vk).expect("failed to verify proof");

[Okm165]

LGTM