WIRE on BLOCKCLAIMED

Guides / Hands-on

Request a contract policy for gasless resources

How Wire covers user resources through Node Owner policies instead of gas.

Wire's promise of no user gas has to be paid for somewhere. The answer is the resource-owner model: node owners hold the chain's resource capacity and allocate it to applications through contract policies managed by the sysio.roa system contract. Users transact free because the application's policy covers them.

The model in one diagram's worth of words

  • Node owners hold resource capacity (CPU time, network bandwidth, RAM) in proportion to their stake in the network's infrastructure.
  • Contract policies are allocations of that capacity to a specific contract account. A policy says: transactions hitting this contract draw from this budget.
  • Users sign transactions that execute under those budgets. No fee market, no gas estimation, no failed-for-out-of-gas surprises.

Why not just make everything free?

Unmetered compute on a public chain is a denial-of-service invitation. Policies keep the metering while moving it from the user to the application, which is where capacity planning belongs. An application knows its own load profile; a user should not have to.

Requesting a policy on the testnet

  1. Deploy the contract that needs coverage (previous guide).
  2. From the pre.wire.network suite, find the resource or policy section and request an allocation for your contract account, sized for your expected transaction volume.
  3. On the testnet, allocations are granted from testnet capacity for learning purposes. On any future network the same request is a business conversation with node owners; the mechanism is the contract policy either way.

Check your resource state

curl -X POST https://testnet-api-use1.dev.wire-dev.com/v1/chain/get_account \
  -d '{"account_name":"yourcontract"}'

The account response includes CPU, NET and RAM figures: what is allocated, what is used. If an action starts failing with a resource error, this is the first place to look.

Resource numbers you see on the V2 testnet are testnet parameters. They demonstrate the mechanism; they do not represent the capacity or the economics of any future network.

That closes the hands-on loop: account, funds, swap, contract, policy. If you walked all five guides you have touched every core mechanism the architecture explainers describe.