Skip to main content

Create a TAP rule

  • Updated

Overview

With the TAP Editor, creating Transaction Authorization Policy (TAP) rules to suit your business's financial security needs is quick and easy.

Please note the following:

  • Only one Admin-level user can use the TAP Editor at a time.
  • You are automatically logged out of the TAP Editor after 30 minutes of inactivity.
  • If you plan to perform DeFi operations, we recommend creating a DeFi policy.

Create a TAP rule

  1. In the Fireblocks Console, go to Settings > Transaction Policy.
  2. Select Edit policy.
  3. On the TAP editor page, select + on the policy's header.
  4. On the Add a rule window, build the rule using the appropriate rule parameters.
  5. Select Add rule. The rule appears on the policy. If necessary, use the up and down arrows on the policy's left side to change the rules' order in accordance with the first-match principle.
  6. Select Publish, review your changes, and then select Publish policy to submit your changes for Admin Quorum and Owner approval.

Rule parameter fields

The table below provides a brief description of the fields on the Add a rule window. For more information about specific rule parameters, refer to the Rule parameters article.

Field name Description
Type The type of transaction to which the rule applies. Depending on the type you select, the available rule fields may change.
Source
  • Any: Allow a transaction to use all sources in or linked to your workspace.
  • Groups and accounts: Enter one or more specific source accounts.
Destination
  • Any: Allow a transaction to use all destinations in or linked to your workspace.
  • Groups and accounts: Enter one or more specific destinations.
  • Any: Allow transfers to both one-time addresses and whitelisted addresses.
  • One-time address only: Allow transfers to only one-time addresses.
  • Whitelisted only: Allow transfers to only whitelisted addresses.
Contract call methods

Applies only to contract calls.

  • Any: Allow a transaction to use any contract call method.
  • Specific method: Enter one or more specific contract call methods.
Initiated by
  • Any: Allow current and future users with the appropriate roles to create transactions.
  • Specific initiator or groups: Enter one or more specific users.
Designated signer Defaults to the transaction's initiator. Use the drop-down list to change it to a single signer or multiple signers, then enter the user (or users) that you want to act as signers for transactions that match the rule.
Asset
  • Asset: The rule applies to assets. Defaults to Any. Use the drop-down list to change it to a specific asset.
  • NFT: The rule applies to non-fungible tokens (NFTs).
Minimum amount The base amount a transaction must exceed to trigger the rule.
Currency Select USD or EUR. If you selected a specific asset above, you can also select that asset here.
Limit
  • Time Period: The rule applies to all matching transactions within a specific time period. Use the Hours field to specify the time period and the Initiator, Source, and Destination fields to configure whether you want to apply the limit to individual parameters or the aggregate total of each parameter.
  • Single transaction: The rule applies to every matching transaction, regardless of time period.
Action
  • Require approval: The transaction requires approval before it can be completed. Use the Number and Of fields to configure the approval threshold. If the transaction's initiator is listed as an approver, select Initiator counts as approver to allow them to approve their own transaction. If you want to add another approval layer, select Add group. Note that each approval layer's threshold must be met for the transaction to be approved.
  • Allow: The transaction is automatically approved and sent to be signed.
  • Block: The transaction is automatically rejected.
Applies to typed messages Applies only to contract calls. Turn on this setting if you want the rule to apply to typed messages.
Applies to approve Applies only to contract calls. Turn on this setting if you want the rule to apply to Approve transactions.
Applies to deployment Applies only to contract calls. Turn on this setting if you want the rule to apply to deploying smart contracts.
Was this article helpful?
2 out of 2 found this helpful

Related Articles