Back to Nodes

Brickken Sign

Last updated Nov 28, 2025

n8n community node for signing blockchain transactions locally

24 Weekly Downloads
598 Monthly Downloads

Included Nodes

Brickken Sign

Description

n8n-nodes-brickken-sign

npm version

n8n community node for signing blockchain transactions locally using a private key. This node allows you to sign transactions generated by the Brickken API (or any other source) without exposing your private key to external services.

Features

  • Local Signing: Signs transactions securely within your n8n instance using ethers.js.
  • Secure Credentials: Safely stores your Private Key in n8n credentials.
  • Flexible Input: Accepts transaction JSON objects from any source.

Installation

Community Nodes (Recommended)

  1. Go to Settings > Community Nodes
  2. Select Install
  3. Enter n8n-nodes-brickken-sign
  4. Click Install

Manual Installation

To install this node manually in your n8n instance:

npm install n8n-nodes-brickken-sign

Credentials

This node requires a Private Key to sign transactions.

  1. Private Key: Your wallet's private key (64 hex characters, with or without 0x prefix).
    • Security Note: The private key is stored encrypted within your n8n instance and is never sent to any external API.

Operations

Sign Transaction

Signs a transaction object using the provided private key.

Input:

  • Transaction JSON: A JSON object containing the transaction details.
    • Example:
      {
        "to": "0x...",
        "value": "0",
        "data": "0x...",
        "gasLimit": "21000",
        "chainId": 11155111
      }
      

Output:

  • signedTransaction: The raw signed transaction string (hex).
  • transactionHash: The hash of the signed transaction.
  • signerAddress: The address of the wallet that signed the transaction.

Usage Example

This node is typically used after an HTTP Request node that fetches transaction data from an API (like the Brickken API).

  1. HTTP Request: Create unsigned transaction (e.g., from POST /prepare-transaction).
  2. Brickken Sign: Connect the HTTP Request output to this node.
    • Map the Transaction JSON field to the output of the previous node (e.g., {{ $json }}).
  3. HTTP Request: Send the signed transaction to a blockchain provider or API (e.g., POST /send-transaction).

Example Workflow:

[Trigger] -> [HTTP Prepare Tx] -> [Brickken Sign] -> [HTTP Send Tx]

Documentation

License

MIT

Author

Brickken

Support

For issues, questions, or feature requests:

Keywords

n8n-community-node-package, brickken, tokenization, blockchain, real-world-assets, rwa