Execute Rune Etch Order

Use this endpoint to execute a Rune Etch order.

Quick Start

post

Execute an etching order once funded.

Authorizations
x-api-keystringRequired
Path parameters
orderIdstring · uuidRequired
Body
fundTransactionIdstring · min: 64 · max: 64Required
Responses
200

Default Response

No content

post
/v1/runes-managed/etch/orders/{orderId}/execute
POST /v1/runes-managed/etch/orders/{orderId}/execute HTTP/1.1
Host: api.secretkeylabs.io
x-api-key: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 28

{
  "fundTransactionId": "text"
}
200

Default Response

No content

Execute Rune Etch Order - Request

Once you have

-> you can call the Execute Etch Order endpoint, using the orderID as path parameter

Execute Rune Etch Order - Response

A successful create Execute Etch request will:

  1. Return the fundTransactionId to your app, confirming that the funding transaction required to execute your order was detected.

  2. Prompt the Xverse API to process the Etch Order. Its Rune Etch service uses a two-phase commit/reveal procedure to process your order and etch the rune:

    • The funding transaction for the order also acts as a commit transaction: it contains a taproot output committing to a script containing the Rune to etch (and optionally the inscription content, if you chose to link an inscription with either inscriptionDetails or delegateInscriptionId)

    • Once the commit transaction has reached 6 block confirmations, the Rune Etch service will craft & broadcast a reveal transaction, which etches the rune (and optionally reveals your linked inscription). The reveal transaction is broadcast at the desired feeRate specified in the request, and signed with the funding address for the order. This mechanism protects your rune etching from mempool detection and front-running.

Next Step -> Monitor Rune Etch Order

Once you've sent the required amount to execute your order, you can call the Monitor Mint Order endpoint to track the status.

Last updated