Add Rust programs using pinocchio

[febo]

This PR adds Rust programs for Transfer-Lamports and CPI using pinocchio. It does not include a Helloworld since it would be the same as the current Rust version.

Results

• Transfer-Lamports: moves 5 lamports from a source account to a destination

Language	CU Usage
Rust	464
Zig	43
C	103
Assembly	22
Rust (pinocchio)	23

This one starts to get interesting since it requires parsing the instruction
input. Since the assembly version knows exactly where to find everything, it can
be hyper-optimized. The C version is also very performant.

Zig's version should perform the same as C, but there are some inefficiencies that
are currently being fixed.

• CPI: allocates a PDA given by the seed "You pass butter" and a bump seed in
  the instruction data. This requires a call to create_program_address to check
  the address and invoke_signed to CPI to the system program.

Language	CU Usage
Rust	3662
Zig	2825
C	3122
Rust (pinocchio)	2816

[joncinque]

Looks really good! Once we figure out how to run these, could you add a step in CI to run these? It would look just like rust-test at https://github.com/joncinque/solana-program-rosetta/blob/89efc3b4ebc11139a73a4d5c97f99ab710e29d3c/.github/workflows/main.yml#L46C3-L77C54

But instead of cargo test-sbf it would use test-pinocchio.sh

[joncinque]

Is there a way to avoid this copy and reuse the existing tests at cpi/tests? We might be able to get away with something similar to the C / Zig / Assembly test runner, where there's a test-pinocchio.sh script that builds the program and then specifies some environment variable for the program name, ie:

#!/usr/bin/env bash
PROGRAM_NAME="$1"
ROOT_DIR="$(cd "$(dirname "$0")"; pwd)"
set -e
PROGRAM_DIR=$ROOT_DIR/$PROGRAM_NAME
cd $PROGRAM_DIR/pinocchio
cargo build-sbf
ROSETTA_PROGRAM_NAME="pinocchio_rosetta_cpi" SBF_OUT_DIR="target/deploy" cargo test --manifest-path "$PROGRAM_DIR/Cargo.toml"

And then use std::env::var("ROSETTA_PROGRAM_NAME").unwrap_or("solana_program_rosetta_cpi") for the program name in the test.

What do you think?

[febo]

Good idea! I had to use a ROSETTA_LIBRARY variable to then choose the program name, since the name has to be a &'static str.

[joncinque]

Same here for the tests -- maybe we can ditch the copy and do something else

[leafaar]

awesome!

[joncinque]

Thanks for updating these! It's very close, just a few last bits to sort out. And if I'm being too annoying, just let me know and I'll take over 😅

[joncinque]

Needing to specify the ROSETTA_LIBRARY env variable and also hard-code it into the test seems a bit overkill -- how about having an environment variable like PROGRAM_NAME and just using that or the default?

Then test-pinocchio.sh just needs to combine pinocchio with the program name. What do you think?

[febo]

Hmmm, but we still have the issue that ProgramTest::new expects the program_name as a &'static str. That is the only reason for hard-coding the name on the test file.

[joncinque]

how about using env! in that case? https://doc.rust-lang.org/std/macro.env.html

[febo]

Great idea - ended up using option_env! so we can specify a default value if the variable is not set.

[joncinque]

Everything looks good, just need to figure out the environment variable for the test

[joncinque]

Beautiful, thanks for the contribution!