Add close instruction to claimable tokens #12771
Conversation
|
|
awesome. probably worth sorting those tests out for the sake of audit. one additional case id want to test is making sure we can upgrade a version of the previous program that's deployed and then close to the default addy |
| // then we must add instruction to create it | ||
| let derived_token_acc_data = config.rpc_client.get_account_data(&pair.derive.address); | ||
|
|
||
| println!("claimable_tokens program id: {}", claimable_tokens::id()); |
There was a problem hiding this comment.
Just curious: Are the println()s for debugging or do we want them permanently? Just wondering if it affects the number of compute units used.
There was a problem hiding this comment.
Debugging, will remove!
Tested this by virtue of it not working on the initial deploy and iterating on the deployment - worked great |
Adds the close instruction to claimable tokens program. Hardcodes the rent recipient to our relayer funder.
Tested locally using
solana-test-validator(tried writing a test but couldn't get the test file to compile)