PulseVMTokenized deposits on a network your institution owns.

Named accounts, maker-checker approval and settlement that is final in about a second are built into the ledger. On Ethereum and other EVM chains, your team would build them as contracts and audit them for as long as they run.

Talk to us about a pilot

For banks and credit unions

Start building

Give a key one job

Every account is a readable name with its own approval structure: 3 of 5 treasury officers, 2 of 3 for operations, and a service key that can perform exactly one action. It is configuration, and the ledger enforces it on every transaction. On EVM chains the same controls are a contract wallet and a key module your team deploys and audits.

Accounts and permissions See it in production

treasury.bank

ownerTreasury officers, 3 of 5
- activeOperations, 2 of 3 keys
  - paymentsLinked to token::transfer only. 1 key.
  - traderLinked to vault::trade only. Bot key.

31 of 31attempts to move funds or take over the account were refused by the ledger, using a live service's real key. That key was permitted exactly one action. The service runs in production on XPR Network; the attack exercise ran on its test network.Read the case study

Settlement you can put in an SLA

A payment is final in about a second, as soon as its block is accepted. There is no confirmation count to wait out and no reorganization afterwards.

Finality and settlement

PulseVM

BlockFinal. It cannot be reversed.

Chains that count confirmations

Probably final. Before this it could still be reorganized.

Your payment is sent at 0 s. Each square is a block.

No gas for your customers

The institution stakes compute and bandwidth once and provisions storage. Customers see your app, never a token purchase. Costs become capacity planning, not per-transaction tolls.

Resource model

Your customer sees

$50.00

Toalex.cu

Network feeNone

Sent and settled

Your institution manages

Stake CPU and bandwidth once
Provision storage for accounts
Plan capacity like any other system

Your network, your rules

PulseVM runs as a plugin for metalgo. An institution or a consortium deploys its own chain with its own validators, and the chain's rules are system contracts it owns and can change.

Launch your own network

Also built in

Keep deposits at home

Issue tokenized dollars your customers can move instantly, while the deposits stay on your balance sheet.

For banks and fintechs

Native, not bolted on

Account abstraction, batched payments, fee sponsorship, and passkey (WebAuthn) and secure-enclave (R1) keys are part of the account model.

What is built in

Build in Rust, C++ or TypeScript

Rust is the canonical contract kit. C++ carries the Antelope heritage. TypeScript suits teams who prefer it.

Start building

Compliance and identity

Allow-lists, freeze and clawback under legal order are controls you implement in contracts you own, operated under dual control. Pairs with Metal Identity.

Metal Identity

Everything a bank needs is built in. On Ethereum or any EVM chain, you would build it.

That holds for public Ethereum and for private EVM networks alike. Each row in the middle is code your team writes, audits and defends for as long as it runs. Each row on the right is how PulseVM accounts already work.

You need toOn Ethereum or an EVM chainOn PulseVM

Know who is on the other side of a paymentMap hex addresses to customers in your own systemsAccounts carry names: acme.treas, branch.14, payroll

Require two officers to approve large paymentsDeploy a multisig wallet contract, then audit and maintain itSet 2 of 3 on the account. The ledger enforces it

Let a processor or a bot do one thing onlyAdd a session-key module and a guard contract, and audit bothGrant one permitted action. The ledger refuses that key for anything else

Revoke a departed officer's authorityMove assets to a new wallet, or build a recovery moduleReplace the key in one approved change. Nothing moves

Spare customers any network feesRun a paymaster and relayer service, and keep it fundedThe institution provisions capacity. Customers hold nothing

Audit how authority worksEvery wallet, module and paymaster is a separate auditOne account model, the same for every application

Know when a payment is finalMainnet: about 13 minutes. Private EVM: depends on the consensus you chooseAbout a second, never reorganized, nothing to configure

Keep transactions out of public viewMainnet: public forever. Private EVM: yes, on your own networkYour network, your members, your boundary

Details: vs a permissioned EVM, vs Ethereum, and accounts vs smart-contract wallets.

Also used for insurance, trade finance, capital markets, title and escrow, healthcare and loyalty. All industries.

Built by a team already inside the US payment system

PulseVM comes from Metallicus, the team behind XPR Network and Metal Blockchain, founded in 2015.

FedNowMetallicus is live on the Federal Reserve’s instant payment service, certified to send, receive and request payments.
600+credit unions in the Cornerstone League can run the Metallicus stablecoin pilot as a member benefit.
SOC 2compliance audit completed with an independent third-party auditor.

Who is behind PulseVM, with sources

Start with a pilot, not a platform build

Run a 90-day pilotA small validator network, a tokenized test deposit and real intra-member settlement. Scoped, measured, with an exit.See the pilot plan Check it against your requirementsCustody, key ceremony, dual control, data residency, recovery, upgrades and audit access, answered plainly.Open the buyer's checklist Talk to MetallicusThe team behind PulseVM and XPR Network runs pilots with institutions and consortia.Start a conversation

Building it yourself? Deploy a contract and give a key one job in fifteen minutes.

The account model has run in production on XPR Network for years. PulseVM runs it on Metal Blockchain, from Metallicus.