solana-program-library/themis/program_ristretto/src/entrypoint.rs

//! Program entrypoint

use solana_program::{
    account_info::AccountInfo, entrypoint, entrypoint::ProgramResult, pubkey::Pubkey,
};

entrypoint!(process_instruction);
fn process_instruction(
    program_id: &Pubkey,
    accounts: &[AccountInfo],
    instruction_data: &[u8],
) -> ProgramResult {
    crate::processor::process_instruction(program_id, accounts, instruction_data)?;
    Ok(())
}
Add Themis using the BN curve (#549) * Add THEMIS Policy Contract * Add test with 128 ads * Add instructions * Allow clients to work concurrently * pub(crate) utils to find unused code * Remove serde_json dep * Drop dependency on primitive_types * Add a simpler inner_product * Use elgamal for proof verification * Migrate to Ristretto Also, use Serde for instruction serialization * Add remaining instructions to processor * Remove rand 0.6 dependency * Add instruction constructors * Add e2e test * Move client test out of BPF build * Add BPF instruction count test Shows us that serde makes too many recursive calls and causes a very high instruction count (Vec<U256> becomes impractical). * Use Borsh serialization and test calculate_aggregate() Bump BPF instruction count limits after upgrading compiler * Test SubmitProofDecryption BPF instruction count * Remove CompressedRistretto This drops SubmitProofDecryption instructions by ~2.5M. Also, box up more RistrettoPoints, because they're huge (120 bytes) and blow up the BPF stack. * Add transaction size metrics and update BPF counts * Switch back to BN * Add benchmarking * Use configured keypair path * Make num_users configurable * Make testnet benchmark an example, not a test * Exclude themis client from CI build Because of Travis failure on itertools dependency 2020-09-30 20:33:29 -07:00			`//! Program entrypoint`

Port SPL to solana-program and `cargo build-bpf` 2020-10-22 21:44:27 -07:00			`use solana_program::{`
Add Themis using the BN curve (#549) * Add THEMIS Policy Contract * Add test with 128 ads * Add instructions * Allow clients to work concurrently * pub(crate) utils to find unused code * Remove serde_json dep * Drop dependency on primitive_types * Add a simpler inner_product * Use elgamal for proof verification * Migrate to Ristretto Also, use Serde for instruction serialization * Add remaining instructions to processor * Remove rand 0.6 dependency * Add instruction constructors * Add e2e test * Move client test out of BPF build * Add BPF instruction count test Shows us that serde makes too many recursive calls and causes a very high instruction count (Vec<U256> becomes impractical). * Use Borsh serialization and test calculate_aggregate() Bump BPF instruction count limits after upgrading compiler * Test SubmitProofDecryption BPF instruction count * Remove CompressedRistretto This drops SubmitProofDecryption instructions by ~2.5M. Also, box up more RistrettoPoints, because they're huge (120 bytes) and blow up the BPF stack. * Add transaction size metrics and update BPF counts * Switch back to BN * Add benchmarking * Use configured keypair path * Make num_users configurable * Make testnet benchmark an example, not a test * Exclude themis client from CI build Because of Travis failure on itertools dependency 2020-09-30 20:33:29 -07:00			`account_info::AccountInfo, entrypoint, entrypoint::ProgramResult, pubkey::Pubkey,`
			`};`

			`entrypoint!(process_instruction);`
Drop lifetimes 2020-11-01 00:22:04 -07:00			`fn process_instruction(`
Add Themis using the BN curve (#549) * Add THEMIS Policy Contract * Add test with 128 ads * Add instructions * Allow clients to work concurrently * pub(crate) utils to find unused code * Remove serde_json dep * Drop dependency on primitive_types * Add a simpler inner_product * Use elgamal for proof verification * Migrate to Ristretto Also, use Serde for instruction serialization * Add remaining instructions to processor * Remove rand 0.6 dependency * Add instruction constructors * Add e2e test * Move client test out of BPF build * Add BPF instruction count test Shows us that serde makes too many recursive calls and causes a very high instruction count (Vec<U256> becomes impractical). * Use Borsh serialization and test calculate_aggregate() Bump BPF instruction count limits after upgrading compiler * Test SubmitProofDecryption BPF instruction count * Remove CompressedRistretto This drops SubmitProofDecryption instructions by ~2.5M. Also, box up more RistrettoPoints, because they're huge (120 bytes) and blow up the BPF stack. * Add transaction size metrics and update BPF counts * Switch back to BN * Add benchmarking * Use configured keypair path * Make num_users configurable * Make testnet benchmark an example, not a test * Exclude themis client from CI build Because of Travis failure on itertools dependency 2020-09-30 20:33:29 -07:00			`program_id: &Pubkey,`
Drop lifetimes 2020-11-01 00:22:04 -07:00			`accounts: &[AccountInfo],`
Add Themis using the BN curve (#549) * Add THEMIS Policy Contract * Add test with 128 ads * Add instructions * Allow clients to work concurrently * pub(crate) utils to find unused code * Remove serde_json dep * Drop dependency on primitive_types * Add a simpler inner_product * Use elgamal for proof verification * Migrate to Ristretto Also, use Serde for instruction serialization * Add remaining instructions to processor * Remove rand 0.6 dependency * Add instruction constructors * Add e2e test * Move client test out of BPF build * Add BPF instruction count test Shows us that serde makes too many recursive calls and causes a very high instruction count (Vec<U256> becomes impractical). * Use Borsh serialization and test calculate_aggregate() Bump BPF instruction count limits after upgrading compiler * Test SubmitProofDecryption BPF instruction count * Remove CompressedRistretto This drops SubmitProofDecryption instructions by ~2.5M. Also, box up more RistrettoPoints, because they're huge (120 bytes) and blow up the BPF stack. * Add transaction size metrics and update BPF counts * Switch back to BN * Add benchmarking * Use configured keypair path * Make num_users configurable * Make testnet benchmark an example, not a test * Exclude themis client from CI build Because of Travis failure on itertools dependency 2020-09-30 20:33:29 -07:00			`instruction_data: &[u8],`
			`) -> ProgramResult {`
			`crate::processor::process_instruction(program_id, accounts, instruction_data)?;`
			`Ok(())`
			`}`