Particle CS Launch app (opens in a new tab)

No one should clear a payment alone.

Decide who can request a payment, who must approve it and where money may go. The treasury account enforces it — whichever app sends the request.

Map your treasury workflowSee it in practice
Where control breaks today

Keys are protected. Payments aren’t.

Most treasury setups secure signing well. What they don’t express is who may do what, where money may go, or how long there is to stop a mistake.

Multisigs count signatures, not roles

Three-of-five can’t say “the person who proposes isn’t the one who approves” or “finance may pay, engineering may not.”

Funds can go to any address

A valid signature can send funds anywhere. One pasted or swapped address and the money is gone.

No time to catch a mistake

Once enough people sign, the payment settles. A wrong amount or destination is noticed afterwards.

Audit trails rebuilt by hand

Finance reconstructs who approved which payment from explorers, spreadsheets and chat.

In practice

Separate who requests a payout from who approves it.

A finance operator requests, a treasury lead approves after the wait, and only listed addresses can be paid.

What you set up

  • Requester and approver roles
  • A waiting period — one day, say
  • Vendor addresses on the recipient list
  • Token contracts on the allowed list
Set up a team treasury, step by step (opens in a new tab)

Finance operator
requests

Treasury lead
approves

Vendor
paid

Unlisted
address

Refused

Illustrative

The approach

Rules that match how your team pays.

Set once on the treasury account and applied to every request — from the Platform, your own tools or a script.

Requesters and approvers

Give each person a role. Starting a payment and approving it are separate permissions.

Payments only to listed addresses

ETH and other native-coin payments go only to recipients on the account’s list. Tokens move only through the token contracts you list.

Time to catch a mistake

Requests wait out the account’s waiting period, so a wrong amount or address can be cancelled before it settles.

A record finance can use

Each payment keeps who requested it, who approved or cancelled it, and what ran.

Before you move funds

What the account enforces — and what your team owns.

Treasury controls are only as good as their setup. Here’s the split.

Enforced by the account

  • Who may request, approve and cancel each kind of payment
  • The waiting period on payments approved on-chain
  • The recipient and token-contract lists
  • An on-chain record of every step

Your responsibility

  • Choosing roles, the waiting period and the address lists
  • Watching the queue and cancelling in time
  • Key management for every participant
  • Accounting, reporting and incident response

Start with one treasury workflow.

We’ll map its roles, rules and test cases with you. Or start in the Platform yourself.

Talk to usBloxchain Platform