plamper.fun

Organizational wallet layer

Org-grade crypto wallet Non-custodial · Policy-driven · Auditable

A wallet layer built for organizations.

plamper.fun gives teams a clean, non-custodial interface to hold and move digital assets with policy controls, role-based access, and a full audit trail — without giving up control of keys or funds.

For DAOs, companies, treasuries, and foundations. Designed to feel like a modern consumer wallet, with the controls your security and finance teams expect in production.

Org workspace Core Treasury

main net · live

$4,210,384.19

Aggregated across wallets · mark-to-oracle

7fX3…PLMPR.ORG

SOL

Base collateral

9,024.15

Yield strategy: active

USDC

Ops runway

2,310,000.00

Daily cap: $500k

ORG

Governance

32,000,000

Quorum: 2/3 required

Policy: transactions > $50k require multi-team approval (3 of 5).

What plamper.fun does

Wallet coordination for real teams

A focused surface for organizations to keep, move, and account for on-chain value — without turning every signer into a full-time wallet operator.

Org-aware access & roles

Separate workspaces for entities, projects, and desks. Fine-grained roles determine who can view balances, draft payments, approve flows, or execute transactions.

Access control

Policy-driven transaction checks

Every outbound transaction is evaluated against your rules: value limits, allowlists/denylists, time windows, and quorum requirements for key wallets.

Policy engine

Full audit event stream

Drafts, approvals, rejections, and final signatures are all emitted as structured events so you can plug into SIEM, accounting, and reporting systems.

Observability

Non-custodial by design

Keys stay on devices and hardware you control. plamper.fun orchestrates how signers interact — it never takes custody of seed phrases or private keys.

Key model

Treasury-first UX

A minimal, calm interface tuned for recurring treasury workflows: vendor payouts, runway management, liquidity moves, and governance execution.

Interface

APIs for internal systems

Back-office tools can create payment intents, while plamper.fun enforces policies, collects approvals, and executes on-chain with the correct signers.

Integrations

Secure by default

Security posture that fits organizations

plamper.fun is built as coordination infrastructure around your existing custody choices — not a new place to trust with your keys.

Architecture

Device-bound keys: signing keys live in secure enclaves or hardware modules where available; only signatures cross the network.
MPC & multi-sig friendly: attach to existing multi-sig or MPC setups; the control plane coordinates human approvals, not secrets.
Immutable policy history: every policy change is versioned, signed, and can be anchored on-chain for tamper-evident records.
Least-privilege roles: scoped access for operators, reviewers, and approvers minimizes blast radius when credentials leak.

Org use cases

DAOs & foundations: execute grants, incentives, and buybacks with transparent approval chains verifiable by your community.
Crypto-native companies: run vendor payments, payroll streams, and on-chain expenses with policies aligned to your finance playbook.
Funds & trading desks: enforce per-strategy risk budgets, track who approved each move, and export events for compliance.
Nonprofits & ecosystems: custody donated assets and distribute them with auditable, accountable workflows.

Under the hood

Technical surface

Focused on predictable, inspectable flows: a thin wallet client, a policy control plane, and clean integration points to the rest of your stack.

Client

· Web + extension wallet client
· Typed RPC calls into supported chains (Solana + EVM)
· Local secure storage backed by device hardware where possible

Interface · Signing

Control plane

· Policy evaluation service for transaction intents
· Org directory, workspaces, and role management
· Event stream for audit, analytics, and alerts

Policy · Org model

Integrations

· REST + webhooks for back-office tools
· Connectors into SIEM / logging systems
· Price oracles and risk checks pre-sign

APIs · Observability

Questions

FAQ for organizations

A quick snapshot of how plamper.fun fits into an existing treasury and security model.

Is plamper.fun a custodian?

No. plamper.fun never takes custody of keys or funds. Keys stay with your devices and custody providers. We coordinate approvals and execute transactions according to your policies.

What chains do you support?

The initial focus is Solana with an EVM-compatible surface, designed so organizations can standardize process and policy across multiple chains as support expands.

Can we plug in our existing key setup?

Yes. plamper.fun is designed to sit alongside HSMs, MPC providers, and multi-sig contracts. The wallet client respects your custody model while giving operators a single surface to work from.

How do we start an evaluation?

Most teams start with a single workspace, map their policies into the control plane, and connect a small treasury or ops wallet. From there we expand to additional teams and entities once everyone is comfortable with the flows.

Get in touch

Bring plamper.fun into your org

Share a work email, organization name, and a short description of your treasury setup. We’ll follow up with technical docs and a safe evaluation path.