Auth ix to allow mine cpis

[HardhatChad]

• Creates a new auth instruction that is used to declare the proof that will be used in mine.
• Every mine introspects the transaction to find the authenticated proof, thus ensuring that only one proof can be used per transaction.
• Given the spam penalty, this means only one hash can be submitted per transaction while still allowing mine to be called via a CPI.

[cavemanloverboy]

Auth = 0,

rip my sdk and all active devnet miners lol. not super important.

[cavemanloverboy]

This is needlessly complex imo. You don't actually need the first ix to have a discriminator, or to invoke the ore program.

Just look for a noop program invocation (2 cus) that has zero accounts and instruction data with len=32. In fact, you don't even need to check for noop program. Just look at the instruction data. If the user calls some other program with this pubkey data, so be it. still unique for the transaction which is all you need; all we want here is 32 bytes that are static throughout the entire transaction.

please use my noop program bc spl noop is bloated and not actually noop. validators will load less program data and execute less bpf instructions.

[zakajd]

Why are you fighting sybil so hard with the new design? Given the adaptive difficulty mechanics and "choose your difficulty" mining it only makes sense to use all resources for a single wallet instead of spamming as in ORE v1

[HardhatChad]

If we allow multiple hashes per transaction, there's a financial incentive to fit as many hashes as possible in each transaction to minimize your overall fees/hash.