Pact REST API
For full documentation of Pact endpoints for Chainweb nodes, including sample requests and responses, see the Pact OpenAPI.
local
Use the /local endpoint to submit a synchronous command for non-transactional execution.
In a blockchain environment, this call would be a node-local “dirty read” that can act as a read-evaluate-print-loop for testing or a fully gassed transaction simulation and transaction validation.
Any database writes or changes to the environment are rolled back.
POST /local
Query parameters
Content type: application/json
| Parameter | Type | Description |
|---|---|---|
preflight | boolean | Trigger fully-gassed mainnet transaction execution simulation and transaction metadata validations. |
rewindDepth | integer >= 0 | Rewind transaction execution environment by a number of block heights. |
signatureVerification | boolean | Require user signature verification when validating transaction metadata. |
Request body schema
Content type: application/json
| Parameter | Type | Description |
|---|---|---|
cmd (required) | string | Stringified JSON payload object. Canonic non-malleable signed transaction data. |
hash (required) | string | Unpadded Base64URL of Blake2s-256 hash of the cmd field value. Serves as a command requestKey since each transaction must be unique. |
sigs (required) | Array of objects >= 0 items | List of signatures corresponding one-to-one with signers array in the payload. |
Successful response (200)
Content type: application/json
Executing the command returns either the command results or preflight results.
Command results
| Parameter | Type | Description |
|---|---|---|
reqKey (required) | string | Unique ID of a Pact transaction consisting of its hash. (Request Key) = 43 characters ^[a-zA-Z0-9_-]{43}$ |
result (required) | object | Success (object) or Failure (object). |
txId | number | Database-internal transaction tracking ID. |
logs (required) | string | Backend-specific value providing image of database logs. |
metaData (required) | object | Metadata included with the transaction. |
events | Array of object | Array of event objects. |
continuation | object | Describes result of a defpact execution. |
gas (required) | number | Gas required to execute the transaction. |
Preflight /local results
| Parameter | Type | Description |
|---|---|---|
preflightResult (required) | object (Command Result) | The result of attempting to execute a single well-formed Pact command. |
preflightWarnings (required) | Array of strings | A list of warnings associated with deprecated features in upcoming Pact releases. |
Invalid command response (400)
Content type: text/plain
The command was invalid.
| Parameter | Type | Description |
|---|---|---|
| string (Validation Failure) | Failure message of unexecuted command due to an invalid gas payer, metadata, or other environments issues. |
send
Use the /send endpoint for asynchronous submission of one or more public (unencrypted) commands to the blockchain for execution.
POST /send
Request body schema
Content type: application/json
| Parameter | Type | Description |
|---|---|---|
cmds (required) | Array of objects | Pact commands (non-empty). |
Successful response (200)
Content type: application/json
The commands were successfully submitted. The response contains their request keys.
| Parameter | Type | Description |
|---|---|---|
requestKeys (required) | Array of strings | Request keys you can use with poll or listen to retrieve results. Request key = 43 characters ^[a-zA-Z0-9_-]{43}$. |
Invalid command response (400)
Content type: text/plain
The command was invalid.
| Parameter | Type | Description |
|---|---|---|
| string (Validation Failure) | Failure message of unexecuted command due to an invalid gas payer, metadata, or other environments issues. |
poll
Use the /poll endpoint to check for one or more command results by request key.
POST /poll
Query parameters
Content type: application/json
| Parameter | Type | Description |
|---|---|---|
confirmationDepth | integer >= 0 | Configures how many blocks should be mined until the requested transaction is ready. |
Request body schema
Content type: application/json
| Parameter | Type | Description |
|---|---|---|
requestKeys (required) | Array of strings | Request keys (non-empty). [ items = 43 characters ^[a-zA-Z0-9_-]{43}$ ] |
Request example
{ "requestKeys": [ "y3aWL72-3wAy7vL9wcegGXnstH0lHi-q-cfxkhD5JCw" ]}{ "requestKeys": [ "y3aWL72-3wAy7vL9wcegGXnstH0lHi-q-cfxkhD5JCw" ]}Successful response (200)
Content type: application/json
The command results for some of the request keys included in the /poll request.
| Parameter | Type | Description |
|---|---|---|
property-name* | object (Command Result) | The result of attempting to execute a single well-formed Pact command. |
reqKey (required) | string | Unique ID of a pact transaction consisting of its hash. Request key = 43 characters ^[a-zA-Z0-9_-]{43}$. |
result (required) | object | Success (object) or Failure (object). |
txId | number | Database-internal transaction tracking ID. |
logs (required) | string | Backend-specific value providing image of database logs. |
metaData (required) | object | Metadata included with the transaction. |
events | Array of object | Array of event objects. |
continuation | object | Describes result of a defpact execution. |
gas (required) | number | Gas consumed by the transaction. |
events |
Response example
{ "property1": { "gas": 123, "result": {}, "reqKey": "cQ-guhschk0wTvMBtrqc92M7iYm4S2MYhipQ2vNKxoI", "logs": "wsATyGqckuIvlm89hhd2j4t6RMkCrcwJe_oeCYr7Th8", "metaData": null, "continuation": null, "txId": "456", "events": [] }, "property2": { "gas": 123, "result": {}, "reqKey": "cQ-guhschk0wTvMBtrqc92M7iYm4S2MYhipQ2vNKxoI", "logs": "wsATyGqckuIvlm89hhd2j4t6RMkCrcwJe_oeCYr7Th8", "metaData": null, "continuation": null, "txId": "456", "events": [] }}{ "property1": { "gas": 123, "result": {}, "reqKey": "cQ-guhschk0wTvMBtrqc92M7iYm4S2MYhipQ2vNKxoI", "logs": "wsATyGqckuIvlm89hhd2j4t6RMkCrcwJe_oeCYr7Th8", "metaData": null, "continuation": null, "txId": "456", "events": [] }, "property2": { "gas": 123, "result": {}, "reqKey": "cQ-guhschk0wTvMBtrqc92M7iYm4S2MYhipQ2vNKxoI", "logs": "wsATyGqckuIvlm89hhd2j4t6RMkCrcwJe_oeCYr7Th8", "metaData": null, "continuation": null, "txId": "456", "events": [] }}listen
Use the /listen endpoint to submit a blocking request for single transaction result.
POST /listen
Request body schema
Content type: application/json
| Parameter | Type | Description |
|---|---|---|
listen (required) | string | Unique ID of a Pact transaction consisting of its hash. Request key = 43 characters ^[a-zA-Z0-9_-]{43}$. |
Successful response (200)
Content type: application/json
The transaction result for the request key was found.
| Parameter | Type | Description |
|---|---|---|
reqKey (required) | string | Unique ID of a pact transaction consisting of its hash. Request key = 43 characters ^[a-zA-Z0-9_-]{43}$. |
result (required) | object | Success (object) or Failure (object). |
txId | number | Database-internal transaction tracking ID. |
logs (required) | string | Backend-specific value providing image of database logs. |
metaData (required) | object | Metadata included with the transaction. |
events | Array of objects | Array of event objects. |
continuation | object | Describes result of a defpact execution. |
gas (required) | number | Gas consumed by the transaction. |
private
Use the /private endpoint for asynchronous submission of a single command transmitted with end-to-end encryption between addressed entity nodes. Private payload metadata is required.
POST /private
Request body schema
Content type: application/json
| Parameter | Type | Description |
|---|---|---|
cmd (required) | string | Stringified JSON payload object. Canonic non-malleable signed transaction data. |
hash (required) | string | Unpadded Base64URL of Blake2s-256 hash of the cmd field value. Serves as a command requestKey since each transaction must be unique. |
sigs (required) | Array of objects >= 0 | List of signatures corresponding one-to-one with the signers array in the payload. |
Successful response (200)
Content type: application/json
The command was accepted.
| Parameter | Type | Description |
|---|---|---|
requestKeys (required) | Array of strings | Request keys you can use with poll or listen to retrieve results. Request key = 43 characters ^[a-zA-Z0-9_-]{43}$. |
spv
Use the /spv endpoint to issue a blocking request to fetch a simple payment verificiation (spv) proof of a cross-chain transaction.
The request must be sent to the chain where the transaction initiated.
POST /spv
Request body schema
Content type: application/json
| Parameter | Type | Description |
|---|---|---|
requestKey (required) | string | Request Key of an initiated cross-chain transaction at the source chain. |
targetChainId (required) | string | Target chain ID of the cross-chain transaction. |
Successful response (200)
Content type: application/json
The requested spv proof.
| Parameter | Type | Description |
|---|---|---|
| string | Backend-specific data for continuing a cross-chain proof. |
Invalid command response (400)
Content type: text/plain
The requested spv proof could not be found.
| Parameter | Type | Description |
|---|---|---|
| string (Validation Failure) | Error message with the description of failed proof requests. |
Pact commands, results, and payloads
Pact commands consist of the following parameters:
| Parameter | Type | Description |
|---|---|---|
cmd (required) | string | Stringified JSON payload object. Canonic non-malleable signed transaction data. |
hash (required) | string | Unpadded Base64URL of Blake2s-256 hash of the cmd field value. Serves as a command requestKey since each transaction must be unique. |
sigs (required) | Array of objects >= 0 | List of signatures corresponding one-to-one with the signers array in the payload. |
Pact results consist of the following parameters:
| Parameter | Type | Description |
|---|---|---|
reqKey (required) | string | Unique ID of a Pact transaction consisting of its hash. Request key = 43 characters ^[a-zA-Z0-9_-]{43}$. |
result (required) | object | Success (object) or Failure (object). |
txId | number | Database-internal transaction tracking ID. |
logs (required) | string | Backend-specific value providing image of database logs. |
metaData (required) | object | Metadata included with the transaction. |
events | Array of object | Array of event objects. |
continuation | object | Describes result of a defpact execution. |
gas (required) | number | Gas consumed by the transaction. |
Pact command payloads consist of the following parameters:
| Parameter | Type | Description |
|---|---|---|
payload (required) | object | The exec message object or continuation message object. |
meta (required) | object | Public Chainweb metadata object or private metadata object. |
signers (required) | Array of objects | List of signers, corresponding with list of signatures in outer command. |
networkId (required) | string | Backend-specific identifier of the target network such as "mainnet01" or "testnet04". |
nonce (required) | string | Arbitrary user-supplied value. |
Pact built-in server
Pact ships with a built-in HTTP server and SQLite backend.
To start up the server issue pact -s config.yaml, with a suitable config.
pact-lang-api JS Library
The pact-lang-api JS library is available as an npm package for web
development.
API request formatter
The pact tool accepts the --apireq option to format an API request JSON using a YAML file as input to describe the request.
The output can then be used with a POST tool like Postman or even piping into curl.
For example, you can create a my-api-request.yaml file with the following content:
code: '(+ 1 2)'data: name: Stuart language: PactkeyPairs: - public: ba54b224d1924dd98403f5c751abdd10de6cd81b0121800bf7bdbdcfaec7388d secret: 8693e641ae2bbe9ea802c736f42027b03f86afe63cae315e7169c9c496c17332code: '(+ 1 2)'data: name: Stuart language: PactkeyPairs: - public: ba54b224d1924dd98403f5c751abdd10de6cd81b0121800bf7bdbdcfaec7388d secret: 8693e641ae2bbe9ea802c736f42027b03f86afe63cae315e7169c9c496c17332You can then pass this file to pact to create a valid API request like this:
$ pact -a tests/apireq.yaml -l{"hash":"444669038ea7811b90934f3d65574ef35c82d5c79cedd26d0931fddf837cccd2c9cf19392bf62c485f33535983f5e04c3e1a06b6b49e045c5160a637db8d7331","sigs":[{"sig":"9097304baed4c419002c6b9690972e1303ac86d14dc59919bf36c785d008f4ad7efa3352ac2b8a47d0b688fe2909dbf392dd162457c4837bc4dc92f2f61fd20d","scheme":"ED25519","pubKey":"ba54b224d1924dd98403f5c751abdd10de6cd81b0121800bf7bdbdcfaec7388d","addr":"ba54b224d1924dd98403f5c751abdd10de6cd81b0121800bf7bdbdcfaec7388d"}],"cmd":"{\"address\":null,\"payload\":{\"exec\":{\"data\":{\"name\":\"Stuart\",\"language\":\"Pact\"},\"code\":\"(+ 1 2)\"}},\"nonce\":\"\\\"2017-09-27 19:42:06.696533 UTC\\\"\"}"} $ pact -a tests/apireq.yaml -l{"hash":"444669038ea7811b90934f3d65574ef35c82d5c79cedd26d0931fddf837cccd2c9cf19392bf62c485f33535983f5e04c3e1a06b6b49e045c5160a637db8d7331","sigs":[{"sig":"9097304baed4c419002c6b9690972e1303ac86d14dc59919bf36c785d008f4ad7efa3352ac2b8a47d0b688fe2909dbf392dd162457c4837bc4dc92f2f61fd20d","scheme":"ED25519","pubKey":"ba54b224d1924dd98403f5c751abdd10de6cd81b0121800bf7bdbdcfaec7388d","addr":"ba54b224d1924dd98403f5c751abdd10de6cd81b0121800bf7bdbdcfaec7388d"}],"cmd":"{\"address\":null,\"payload\":{\"exec\":{\"data\":{\"name\":\"Stuart\",\"language\":\"Pact\"},\"code\":\"(+ 1 2)\"}},\"nonce\":\"\\\"2017-09-27 19:42:06.696533 UTC\\\"\"}"} Here's an example of piping the output to curl and hitting a pact server running on port
8080:
$ pact -a tests/apireq.yaml -l | curl -d @- http://localhost:8080/api/v1/local{"status":"success","response":{"status":"success","data":3}}$ pact -a tests/apireq.yaml -l | curl -d @- http://localhost:8080/api/v1/local{"status":"success","response":{"status":"success","data":3}}Request YAML file format
You can create two types of request yaml files:
- An execution request yaml file describes the
execpayload. - A continuation request yaml file describes the
contpayload.
YAML exec command request
The execution request yaml for a public blockchain takes the following keys:
code: Transaction code codeFile: Transaction code file data: JSON transaction data dataFile: JSON transaction data file keyPairs: list of key pairs for signing (use pact -g to generate): [ public: base 16 public key secret: base 16 secret key caps: [ optional managed capabilities ] ] nonce: optional request nonce, will use current time if not provided networkId: string identifier for a blockchain network publicMeta: chainId: string chain id of the chain of execution sender: string denoting the sender of the transaction gasLimit: integer gas limit gasPrice: decimal gas price ttl: integer time-to-live value creationTime: optional integer tx execution time after offset type: exec code: Transaction code codeFile: Transaction code file data: JSON transaction data dataFile: JSON transaction data file keyPairs: list of key pairs for signing (use pact -g to generate): [ public: base 16 public key secret: base 16 secret key caps: [ optional managed capabilities ] ] nonce: optional request nonce, will use current time if not provided networkId: string identifier for a blockchain network publicMeta: chainId: string chain id of the chain of execution sender: string denoting the sender of the transaction gasLimit: integer gas limit gasPrice: decimal gas price ttl: integer time-to-live value creationTime: optional integer tx execution time after offset type: execYAML continuation command request
The continuation request yaml for a public blockchain takes the following keys:
pactTxHash: integer transaction id of pact step: integer next step of a pact rollback: boolean for rollingback a pact proof: string spv proof of continuation (optional, cross-chain only) data: JSON transaction data dataFile: JSON transaction data file keyPairs: list of key pairs for signing (use pact -g to generate): [ public: string base 16 public key secret: string base 16 secret key caps: [ optional managed capabilities ] ] networkId: string identifier for a blockchain network publicMeta: chainId: string chain id of the chain of execution sender: string denoting the sender of the transaction gasLimit: integer gas limit gasPrice: decimal gas price ttl: integer time-to-live value creationTime: optional integer tx execution time after offset nonce: optional request nonce, will use current time if not provided type: cont pactTxHash: integer transaction id of pact step: integer next step of a pact rollback: boolean for rollingback a pact proof: string spv proof of continuation (optional, cross-chain only) data: JSON transaction data dataFile: JSON transaction data file keyPairs: list of key pairs for signing (use pact -g to generate): [ public: string base 16 public key secret: string base 16 secret key caps: [ optional managed capabilities ] ] networkId: string identifier for a blockchain network publicMeta: chainId: string chain id of the chain of execution sender: string denoting the sender of the transaction gasLimit: integer gas limit gasPrice: decimal gas price ttl: integer time-to-live value creationTime: optional integer tx execution time after offset nonce: optional request nonce, will use current time if not provided type: contNote that the optional "proof" field only makes sense when using cross-chain continuations.
Signing transactions
As of Pact 3.5.0, the pact command line tool now has several commands to
facilitate signing transactions. Here's a full script showing how these commands
can be used to prepare an unsigned version of the transaction and add signatures
to it. This transcript assumes that the details of the transaction has been
specified in a file called tx.yaml.
# At some earlier time generate and save some public/private key pairs.pact -g > alice-key.yamlpact -g > bob-key.yaml # Convert a transaction into an unsigned prepared form that is signatures can be added topact -u tx.yaml > tx-unsigned.yaml # Sign the prepared transaction with one or more keyscat tx-unsigned.yaml | pact add-sig alice-key.yaml > tx-signed-alice.yamlcat tx-unsigned.yaml | pact add-sig bob-key.yaml > tx-signed-bob.yaml # Combine the signatures into a fully signed transaction ready to send to the blockchainpact combine-sigs tx-signed-alice.yaml tx-signed-bob.yaml > tx-final.json # At some earlier time generate and save some public/private key pairs.pact -g > alice-key.yamlpact -g > bob-key.yaml # Convert a transaction into an unsigned prepared form that is signatures can be added topact -u tx.yaml > tx-unsigned.yaml # Sign the prepared transaction with one or more keyscat tx-unsigned.yaml | pact add-sig alice-key.yaml > tx-signed-alice.yamlcat tx-unsigned.yaml | pact add-sig bob-key.yaml > tx-signed-bob.yaml # Combine the signatures into a fully signed transaction ready to send to the blockchainpact combine-sigs tx-signed-alice.yaml tx-signed-bob.yaml > tx-final.json The add-sig command takes the output of pact -u on standard input and one or
more key files as command line arguments. It adds the appropriate signatures to
to the transaction and prints the result to stdout.
The combine-sigs command takes multiple unsigned (from pact -u) and signed
(from pact add-sig) transaction files as command line arguments and outputs
the command and all the signatures on stdout.
Both add-sig and combine-sigs will output YAML if the output transaction
hasn't accumulated enough signatures to be valid. If all the necessary
signatures are present, then they will output JSON in final form that is ready
to be sent to the blockchain on the /send endpoint.
If you would like to do a test run of the transaction, you can use the -l flag to generate
output suitable for use with the /local endpoint.
The above example adds signatures in parallel, but the add-sig command can
also be used to add signatures sequentially in separate steps or all at once in
a single step as shown in the following two examples:
cat tx-unsigned.yaml | pact add-sig alice-key.yaml | pact add-sig bob-key.yamlcat tx-unsigned.yaml | pact add-sig alice-key.yaml add-sig bob-key.yamlcat tx-unsigned.yaml | pact add-sig alice-key.yaml | pact add-sig bob-key.yamlcat tx-unsigned.yaml | pact add-sig alice-key.yaml add-sig bob-key.yamlOffline signing with a cold wallet
Some cold wallet signing procedures use QR codes to get transaction data on and
off the cold wallet machine. Since QR codes can transmit a fairly limited amount
of information these signing commands are also designed to work with a more
compact data format that doesn't require the full command to generate
signatures. Here's an example of what tx-unsigned.yaml might look like in the
above example:
hash: KY6RFunty4WazQiCsKsYD-ovu-_XQByfY6scTxi9gQQsigs: 368820f80c324bbc7c2b0610688a7da43e39f91d118732671cd9c7500ff43cca: null 6be2f485a7af75fedb4b7f153a903f7e6000ca4aa501179c91a2450b777bd2a7: nullcmd: '{"networkId":"mainnet01","payload":{"exec":{"data":{"ks":{"pred":"keys-all","keys":["368820f80c324bbc7c2b0610688a7da43e39f91d118732671cd9c7500ff43cca"]}},"code":"(coin.transfer-create \"alice\" \"bob\" (read-keyset \"ks\") 100.1)\n(coin.transfer \"bob\" \"alice\" 0.1)"}},"signers":[{"pubKey":"6be2f485a7af75fedb4b7f153a903f7e6000ca4aa501179c91a2450b777bd2a7","clist":[{"args":["alice","bob",100.1],"name":"coin.TRANSFER"},{"args":[],"name":"coin.GAS"}]},{"pubKey":"368820f80c324bbc7c2b0610688a7da43e39f91d118732671cd9c7500ff43cca","clist":[{"args":["bob","alice",0.1],"name":"coin.TRANSFER"}]}],"meta":{"creationTime":1580316382,"ttl":7200,"gasLimit":1200,"chainId":"0","gasPrice":1.0e-5,"sender":"alice"},"nonce":"2020-01-29 16:46:22.916695 UTC"}'hash: KY6RFunty4WazQiCsKsYD-ovu-_XQByfY6scTxi9gQQsigs: 368820f80c324bbc7c2b0610688a7da43e39f91d118732671cd9c7500ff43cca: null 6be2f485a7af75fedb4b7f153a903f7e6000ca4aa501179c91a2450b777bd2a7: nullcmd: '{"networkId":"mainnet01","payload":{"exec":{"data":{"ks":{"pred":"keys-all","keys":["368820f80c324bbc7c2b0610688a7da43e39f91d118732671cd9c7500ff43cca"]}},"code":"(coin.transfer-create \"alice\" \"bob\" (read-keyset \"ks\") 100.1)\n(coin.transfer \"bob\" \"alice\" 0.1)"}},"signers":[{"pubKey":"6be2f485a7af75fedb4b7f153a903f7e6000ca4aa501179c91a2450b777bd2a7","clist":[{"args":["alice","bob",100.1],"name":"coin.TRANSFER"},{"args":[],"name":"coin.GAS"}]},{"pubKey":"368820f80c324bbc7c2b0610688a7da43e39f91d118732671cd9c7500ff43cca","clist":[{"args":["bob","alice",0.1],"name":"coin.TRANSFER"}]}],"meta":{"creationTime":1580316382,"ttl":7200,"gasLimit":1200,"chainId":"0","gasPrice":1.0e-5,"sender":"alice"},"nonce":"2020-01-29 16:46:22.916695 UTC"}'To get a condensed version for signing on a cold wallet all you have to do is
drop the cmd field. This can be done manually or scripted with
cat tx-unsigned.yaml | grep -v "^cmd:". The result would look like this:
hash: KY6RFunty4WazQiCsKsYD-ovu-_XQByfY6scTxi9gQQsigs: 368820f80c324bbc7c2b0610688a7da43e39f91d118732671cd9c7500ff43cca: null 6be2f485a7af75fedb4b7f153a903f7e6000ca4aa501179c91a2450b777bd2a7: nullhash: KY6RFunty4WazQiCsKsYD-ovu-_XQByfY6scTxi9gQQsigs: 368820f80c324bbc7c2b0610688a7da43e39f91d118732671cd9c7500ff43cca: null 6be2f485a7af75fedb4b7f153a903f7e6000ca4aa501179c91a2450b777bd2a7: nullKeep in mind that when you sign these condensed versions, you won't be able to
submit the output directly to the blockchain. You'll have to use combine-sigs
to combine those signatures with the original tx-unsigned.yaml file which has
the full command.
Detached signature transaction format
The YAML input expected by pact -u is similar to the
Public Blockchain YAML format
described above with one major difference. Instead of the keyPairs field which
requires both the public and secret keys, pact -u expects a signers field
that only needs a public key. This allows signatures to be added on
incrementally as described above without needing private keys to all be present
when the transaction is constructed.
Here is an example of how the above tx.yaml file might look:
code: |- (coin.transfer-create "alice" "bob" (read-keyset "ks") 100.1) (coin.transfer "bob" "alice" 0.1)data: ks: keys: [368820f80c324bbc7c2b0610688a7da43e39f91d118732671cd9c7500ff43cca] pred: 'keys-all'publicMeta: chainId: '0' sender: alice gasLimit: 1200 gasPrice: 0.0000000001 ttl: 7200networkId: 'mainnet01'signers: - public: 6be2f485a7af75fedb4b7f153a903f7e6000ca4aa501179c91a2450b777bd2a7 caps: - name: 'coin.TRANSFER' args: ['alice', 'bob', 100.1] - name: 'coin.GAS' args: [] - public: 368820f80c324bbc7c2b0610688a7da43e39f91d118732671cd9c7500ff43cca caps: - name: 'coin.TRANSFER' args: ['bob', 'alice', 0.1]type: execcode: |- (coin.transfer-create "alice" "bob" (read-keyset "ks") 100.1) (coin.transfer "bob" "alice" 0.1)data: ks: keys: [368820f80c324bbc7c2b0610688a7da43e39f91d118732671cd9c7500ff43cca] pred: 'keys-all'publicMeta: chainId: '0' sender: alice gasLimit: 1200 gasPrice: 0.0000000001 ttl: 7200networkId: 'mainnet01'signers: - public: 6be2f485a7af75fedb4b7f153a903f7e6000ca4aa501179c91a2450b777bd2a7 caps: - name: 'coin.TRANSFER' args: ['alice', 'bob', 100.1] - name: 'coin.GAS' args: [] - public: 368820f80c324bbc7c2b0610688a7da43e39f91d118732671cd9c7500ff43cca caps: - name: 'coin.TRANSFER' args: ['bob', 'alice', 0.1]type: exec