Fractal Bitcoin
  • Welcome to the Fractal Documentation
  • Everything you want to know about Fractal
  • Fractal Tokenomics
  • dev
    • Developer Home
    • brc-20 on Fractal
    • Runes on Fractal
    • Wallet Integration with Fractal
    • Full Node Configuration
  • MINING
    • How to Mine
    • Fractal Bitcoin (FB) Mining Q&A
  • User Guides
    • How to send / receive FB with self-custody wallets?
    • Fractal Vote Explained
      • How to Participate in the Fractal Vote?
      • Fractal Vote - FAQ
    • How to inscribe Ordinals?
    • How to trade Ordinals?
    • How to interact with PizzaSwap?
    • How to use the Simple Bridge?
    • How to use the Bool Bridge?
    • How to Interact with Runes?
      • How to Etch Runes?
      • How to Mint Runes?
      • How to Trade Runes?
    • Understanding CAT Protocol
      • How to send / receive CAT20?
      • How to Buy and Sell CAT on UniSat CAT Market?
  • FAQ
    • Fractal Telegram AMA Review - Mar. 15
    • Fractal Community Q&A Summary - Sept. 22
  • TESTNET
    • Participate in Public Testing
Powered by GitBook
On this page
  • Node
  • Protocol
  • RPC & API
  1. dev

Wallet Integration with Fractal

PreviousRunes on FractalNextFull Node Configuration

Last updated 8 months ago

This document is intended for wallet application providers that have already integrated the BTC mainnet, to facilitate the integration of the Fractal testnet into their applications.

Node

Fractal Bitcoin and Bitcoin have the following differences and notes on nodes:

  • Solo mining uses the same mechanism as Bitcoin.

  • Merged mining operates similarly to Namecoin.

  • Blocks from merged mining contain the BTC block header data. The data structure has changed.

  • However, to maintain compatibility with existing applications, the block data will be removed in the getblock and getblockheader methods of the RPC interface. Nevertheless, analyzing local block files will reveal this data.

Protocol

We remain neutral regarding the competition of different protocols.

Ordinals

  • The activation height of the ordinals index is 21000.

BRC20

  • Ticker names on this public testnet will be limited to 6 - 12 bytes. Tickers with 4 or 5 characters will not be permitted, as they are already in use on the Bitcoin mainnet.

  • For brc-20 on Fractal, ticker names can include letters (both uppercase and lowercase: a-z/A-Z), numbers (0-9), and underscores (_). In total, you have 63 different characters to work with.

  • All byte lengths of BRC-20s on Fractal can enable the self_mint field.

Runes Protocol

  • The activation height for runes is 84000.

  • More rules will be announced later.

RPC & API

Mempool API

  • The latest official version of Mempool can be used for deployment and operation.

Ord

  • Use the latest official version of Ord, configure ordinals to the activation height of 21000.

UniSat Open API

API Swagger:

How to get API-KEY:

Endpoint:

https://en.bitcoin.it/wiki/Merged_mining_specification
https://mempool-testnet.fractalbitcoin.io/v1/fees/recommended
https://ordinals-testnet.fractalbitcoin.io
https://open-api-fractal.unisat.io/swagger.html
https://developer.unisat.io/dashboard/fractal/testnet
https://open-api-fractal-testnet.unisat.io