dappster.
Dashboard
Back to Dappster
// Trust and security

Verify Dappster before you sign.

This is Dappster's canonical trust center for users, wallet providers, security vendors, and integration partners. Verify the official domain, public addresses, and transaction behavior below.

dev@dappster.funRead the technical overview
Canonical domain: dappster.funLast reviewed August 1, 2026English reports preferred
01 / Official identity

Canonical public endpoints

Production application
https://dappster.fun
Security contact
dev@dappster.fun
Technical document
Download the public PDF
02 / Official onchain addresses

Public contracts and operational wallets

RoleNetworkAddress
Membership and creditsBase0xea7e37d45b6f75ae6826c1925d7b0ac314c7ecae
Owner and deployment fee recipientEVM0x5D69C42A3a481d0CCFd88CFA8a2a08e2BF456134
OwnerSolanaGxPoKNX26GCisuH8Sdr8rtfZY98L5t5eegKtDzSA9P6W
Technical deployerSolana MainnetDDrEPN9RtKiLN39VT7wkeu4ZG6Ycgh8mrxhsYDyEPLFo
Technical deployerSolana DevnetDDrEPN9RtKiLN39VT7wkeu4ZG6Ycgh8mrxhsYDyEPLFo

The same disclosed technical-deployer address is used on both Solana clusters. Mainnet and Devnet balances, transactions, and program accounts remain separate.

Never trust an address shown only in a social post or direct message. Compare it with this page and inspect the complete transaction in your wallet before signing.

03 / Transaction guarantees

What a legitimate Dappster prompt can do

  • Connecting a wallet or signing in does not transfer assets. Dappster never asks for a seed phrase or private key.
  • Credit purchases and memberships settle in native Circle USDC on Base and require an explicit transaction approval in the user's wallet.
  • EVM deployments are contract-creation transactions signed by the user's wallet. The generated constructor atomically forwards the disclosed 0.001 native-token deployment fee.
  • Credit consumption is authorized by the linked user wallet and protected by unique usage identifiers against replay.
  • Solana deployment funding is tied to one job by cluster, sender, recipient, amount, signature, and unique memo before the technical wallet can act.
EVM deployment fee0.001 native tokenCredit settlementUSDC on Base
04 / Security controls

Defense in depth

Non-custodial EVM flow

The connected wallet signs and broadcasts EVM transactions. Dappster does not receive wallet secrets.

Onchain verification

Backend checks validate chain, receipt status, destination, amount, emitted events, and deployed address before synchronizing state.

Account isolation

Supabase Row Level Security and linked-wallet ownership checks protect private projects, audits, payments, and deployment jobs.

Replay protection

Unique usage IDs, payment references, deployment job IDs, and Solana funding memos prevent reuse across actions.

Restricted compilation

Solidity imports are limited to bundled OpenZeppelin sources, while Solana builds run in an isolated environment.

Browser protections

Production responses use HTTPS, HSTS, Content Security Policy, anti-framing controls, and same-origin restrictions.

Independent review still mattersAI generation, compilation, simulation, and automated audits reduce risk but do not replace a professional audit for high-value applications.
05 / Vulnerability disclosure

Report a security issue

Email dev@dappster.fun with the affected URL or component, reproduction steps, observed impact, wallet and transaction identifiers when relevant, and a safe proof of concept. Do not include seed phrases, private keys, passwords, or other secrets.

Please avoid privacy violations, service disruption, social engineering, and accessing data that does not belong to you. We will use the same email thread to acknowledge, investigate, and coordinate remediation.