Fees, authorities & verification.

Know what an action costs, who can change what, and what evidence backs the lock.

Technical reference

In this guide

Show every cost before signing

Cost categories
Cost	What must be disclosed
Network	Transaction base fee and any priority fee; failed execution can still incur fees.
Accounts	Rent-exempt funding for the accounts the transaction creates.
Media / metadata	Storage or service charges, if any.
Platform / engine	Creation and trading fees, recipients and calculation order.
Migration	Pool creation, migration costs and any capped keeper reimbursement; identify the funding source.
Optional creator purchase	The actual trade amount, slippage and fees, separate from creation costs.

Solana network fees are paid in SOL and include a base fee plus any priority fee. RalliPad has not selected a universal fee schedule. Estimate from the actual transaction and current accounts; do not advertise an example as a permanent all-in cost.

Primary referencesSolana · Transaction fees

Different authorities control different things

Authority map
Authority	Power / required policy
Mint authority	Can create more tokens. The fixed-supply baseline removes it after initial issuance.
Freeze authority	Can restrict transfers from token accounts. The baseline has none.
Metadata authority	Can change permitted metadata; disclose its policy independently.
Vault token authority	Can authorize token transfers under the controlling program’s rules.
Program upgrade authority	Can change program code while upgradeability exists; disclose governance and limits.
Eligibility / settlement publisher	Can affect datasets or results if the design delegates these tasks; publish evidence and review rights.

Revoking a mint authority does not revoke metadata control or a program’s upgrade authority. A statement about one permission is not a statement about all of them.

Primary referencesSolana · Setting and revoking authority

Evidence to verify for a real launch

Network, program identity and selected engine/configuration match the displayed launch.
Mint supply, decimals and authority state match the signed terms.
Reserve inventory or external beneficiary assignment matches the full advertised amount.
Winner entitlements and release policy match the immutable campaign terms.
Claims go to the validated beneficiary and cannot exceed the stored award.
Migration records and actual LP state support any liquidity-protection claim.
Published review/audit coverage names its program version and scope.

A live counter or a database row is not proof of custody. An internal code review is not an independent security audit. Addresses and evidence must come from the deployed system, never from illustrative documentation.

Failures must preserve obligations

Rejected signatures leave the action unsubmitted. An expired or ambiguous transaction requires status reconciliation before retrying. Failed migration must retain the protected assets and permit only the documented recovery path. Duplicate initialization, settlement or claim attempts must not duplicate obligations or payments.

No pause, account-close or emergency function may silently erase earned member claims. The release policy must define what happens when a campaign fails, a token never graduates or rewards remain unclaimed.