ARC is a cutting-edge transaction processor that streamlines the submission of transactions to the Bitcoin network. By providing seamless connectivity and exceptional performance, ARC paves the way for unparalleled global scalability in the BSV ecosystem.

API Interaction

Interact with the REST API microservice to submit transactions, authenticate, and validate data.

Metamorph Processing

Transactions are sent to Metamorph, which processes and resends them if they are not acknowledged by the network within a certain time period.

BlockTx Handling

BlockTx processes blocks mined on the Bitcoin network and propagates transaction statuses to Metamorph instances that have subscribed to this service.

Callbacker Notifications

Callbacker sends callbacks to clients when a transaction has been accepted by the Bitcoin network.

Transaction Completion

Once the transaction is processed and validated, it is included in the next block, and the client receives a confirmation through the Callbacker microservice.

ARC Components

Learn more about each component of ARC and how they work together to create a seamless transaction processing experience.


API is the REST API microservice for interacting with ARC. It handles authentication, validation, and sending transactions to Metamorph. The API communicates with one or more Metamorph instances using client-based, round-robin load balancing.

Frequently asked questions

Have a question not covered in our FAQs? Our dedicated support team is here to help. Just send us an email and we’ll get back to you as soon as possible to provide the assistance you need.

What is the main advantage of using ARC over mAPI?
ARC provides a more efficient and scalable solution for transaction processing. Unlike mAPI, which relies on the rpc interface of a Bitcoin node, ARC broadcasts transactions on the p2p network, allowing for greater connectivity and reduced bandwidth costs.
How does ARC improve transaction lifecycle management?
ARC monitors the Bitcoin network for transaction and block messages, and keeps track of various transaction states. If a transaction isn't seen on the network within a set time period, ARC resends the transaction, ensuring a higher likelihood of successful processing.
What are the microservices in ARC, and how do they contribute to its functionality?
ARC consists of four microservices: API, Metamorph, BlockTx, and Callbacker. The API handles authentication, validation, and transaction submission; Metamorph processes transactions and resends them if needed; BlockTx processes blocks and propagates transaction status; Callbacker sends callbacks to clients when transactions are accepted.
How does ARC's extended format improve transaction validation?
The extended format includes satoshis and scriptPubKey for each input, which allows ARC to validate transactions without downloading parent transactions. This reduces processing time and network overhead, making the system more efficient.
What is the significance of BIP-239 in relation to ARC?
BIP-239 describes the extended format used by ARC for transactions. It serves as a comprehensive specification for this new format, which aims to become the standard for interchange between wallets and non-mining nodes on the Bitcoin network.
How does ARC ensure scalability and robustness?
ARC's microservices are designed to be horizontally scalable, allowing them to be deployed on single or multiple machines. The system's modular architecture ensures efficient resource utilization and enables ARC to handle increasing transaction volumes over time.
If you have any questions or need technical support,
please contact: