Derive Creator Pubkey

[leowvazd]

Hey guys,

At the level of curiosity and to share knowledge, with the new versions of the code, I understood that to derive creator vault we need the creator. This creator is retrieved from a data_log of an already confirmed creation that we got on chain.

But is there a way to derive this creator in the same way we derive creator vault in the code? Is this creator derived, for example, from user?

(I think there is some relationship, because in the user wallet below there are several attempts that generate the same creator from the same user)

Here's an example of mine:

I know that from SolScan:

user = "28RyKqczfJPkHDtb33ScWE3SPedcJAYmoJFfFKqvdGV6"

we got:

creator = 3xkwSoSfvBt6hqcW6eyEpxe3PaJw2bMxYFEugQp4LJQ2

and its expected (and correct!) derivation:

creator_vault = 2t7V4u1ik4C4xmUMqasNca8U2kBkGwAHUe4WGddAJWXD

I tried somethings like:

from solders.pubkey import Pubkey
user = Pubkey.from_string("28RyKqczfJPkHDtb33ScWE3SPedcJAYmoJFfFKqvdGV6")
PUMP_PROGRAM = Pubkey.from_string("6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P")
expected_creator = "3xkwSoSfvBt6hqcW6eyEpxe3PaJw2bMxYFEugQp4LJQ2"
test_seeds = [
    [b"creator", bytes(user)],
    [b"user-creator", bytes(user)], 
    [b"token-creator", bytes(user)],
    [b"pump-creator", bytes(user)],
    [b"creator-account", bytes(user)],
    [b"user", bytes(user)],
    [b"authority", bytes(user)],
    [b"signer", bytes(user)],
    [bytes(user), b"creator"],
    [bytes(user), b"user"],
    [b"creator_account", bytes(user)],
    [b"user_creator", bytes(user)],
    [b"pump_creator", bytes(user)],
]

for i, seeds in enumerate(test_seeds):
    try:
        creator, bump = Pubkey.find_program_address(seeds, PUMP_PROGRAM)
        print(f"Padrão {i+1}: {creator}")
        if str(creator) == expected_creator:
            print(f"FOUND! Seeds: {seeds}")
            break
    except Exception as e:
        print(f"Padrão {i+1}: Error - {e}")

But I still can't how we get the creator derivation right.

Thanks!

[smypmsa]

Hi! I believe you can't do that. Here is why (creator is a pubkey you pass while creating a token):
https://github.com/pump-fun/pump-public-docs/blob/77b08ed53b0b67632e0455025444cff7e731a030/docs/PUMP_CREATOR_FEE_README.md?plain=1#L79

[leowvazd]

I got your point. But at the same docs says:

"create(user, name, symbol, uri, creator) allows a user to create a new coin with the given name, symbol and uri. The creator pubkey is the creator which will be added to the mint Metaplex metadata creators array, together with the provided name, symbol and uri.

In general, user and creator are the same pubkey, but they can be different, for example, on the free coin creation flow, when the first coin buyer also creates the coin on-chain. In this case, creator pubkey is the original coin creator, while user pubkey is the first buyer. This is also the reason why creator pubkey is not required to be a signer for this instruction, as the original creator cannot sign the tx of the first coin buyer."

And I have an example in the chain, where the creator makes the first purchase with the creator and user generated from the log: 3.15 - Pump.fun: anchor Self CPI Log equal and, an example where creator and user are not generated equal and later the purchase with the creator goes successfully in the past. But now because of the creator vault derivation check for the purchase transaction, this goes wrong

So what would be the "trigger" for Anchor to understand when to generate a user other than creator?