Skip to content

Error codes

Every custom error social_gate can return, 6000 to 6026, and what to do about it.

When social_gate rejects something, the transaction fails with a custom program error and a log line naming it. Numbers start at 6000 (0x1770). Traders only ever meet the first one; the rest concern launches and administration.

transaction logs
Program JCru37BxoujobuWBFR7kBCWXNCDUuoRuWRgKHAzpkduG invoke [4]
Program log: Error Code: BuyNotAllowed. Error Number: 6000. Error Message: Buying on the curve requires fomo's sponsor signature or a FOMOPRIME approve_buy for this destination and amount.
Program JCru37BxoujobuWBFR7kBCWXNCDUuoRuWRgKHAzpkduG failed: custom program error: 0x1770

The one traders see

6000 BuyNotAllowed means a buy from the curve arrived without fomo's signature or a FOMOPRIME approval: for example from a trading bot, an aggregator, or an exported fomo key in another app. Nothing was bought and only the network fee was spent. Buy from the fomo app or on FOMOPRIME instead. After graduation this error can no longer happen.

Tip

Wallets and explorers often show only the hex code, such as 0x1770 for 6000. The table below lists both forms.

All errors

CodeHexNameMeaning
60000x1770BuyNotAllowedBuying on the curve requires fomo's sponsor signature or a FOMOPRIME approve_buy for this destination and amount
60010x1771NotTransferringTransfer hook called outside of a Token-2022 transfer
60020x1772InvalidSourceAccountSource account is not a Token-2022 account
60030x1773MintMismatchSource token account mint does not match the mint
60040x1774InvalidInstructionsSysvarInvalid instructions sysvar account
60050x1775MalformedInstructionsSysvarMalformed instructions sysvar data
60060x1776MintNotHookedToThisProgramThe mint's transfer hook program is not this program
60070x1777MintNotFromDbcThe mint's transfer hook authority is not the DBC pool authority
60080x1778UnauthorizedUnauthorized
60090x1779NoBuyKeysSponsors and approvers must not both be empty
60100x177aTooManyKeysToo many keys in a list (max 8)
60110x177bInvalidKeyKey must not be the default pubkey
60120x177cDuplicateKeyDuplicate key in a list
60130x177dInvalidDbcProgramInvalid DBC program
60140x177eRoleConflictA key may hold only one role: admin/launcher, sponsor or approver
60150x177fInvalidApprovalapprove_buy needs a non-default destination and max_amount > 0
60160x1780InvalidDbcPoolPool is not this mint's DBC transfer-hook pool
60170x1781MintHasAuthorityThe mint must have no mint authority and no freeze authority
60180x1782InvalidDbcConfigConfig is not the pool's DBC transfer-hook config
60190x1783TokenAuthorityNotAllowedThe DBC config's token authority option must be 0, 1 or 2
60200x1784PartnerMismatchThe DBC config's fee claimer is not the FOMOPRIME partner
60210x1785SupplyMismatchMint supply and base vault balance must equal the pool's base reserve
60220x1786InvalidBaseVaultBase vault is not the pool's base vault
60230x1787ConfigNotHookedToThisProgramThe DBC config's transfer hook program is not this program
60240x1788DbcConfigNotRegisteredThe DBC config is not registered (register_dbc_config by the admin or the launcher)
60250x1789DbcConfigAlreadyRegisteredThe DBC config is already registered
60260x178aRegistrationStaleThe DBC config was registered by a key that is no longer the admin or the launcher

Account-level problems use Solana's built-in errors instead: NotEnoughAccountKeys, MissingRequiredSignature, InvalidAccountOwner, InvalidSeeds and InvalidInstructionData.