# Assembler

More likely you'll want to use dApp-dev

The transaction assembler service allows you to bypass the node requirements for dApps.

### The Problem

Currently, with libraries like ergo-appkit, ergo-lib (aka sigma-rust), and ergo-ts, development on Ergo has become a lot more convenient and is becoming easier with further developments of ergo-lib. However, there are some big barriers for dApps to be extensively used by ordinary users. One of the main ones is that users can't use their assets to participate in dApps because current wallets don't support some key features needed by dApps like: - specifying input boxes - p2s protected boxes in inputs - specifying output registers - and simply not supporting dApp requests

These issues will be resolved in the future for sure with wallets like Yoroi, but not so soon, maybe! In this situation, dApps have no workarounds other than requiring users to have their node running or implement a kind of a wallet themselves and ask users to trust and deposit there! The former is the case with Ergo Auction House which prevents it from being extensively used by everyone!

Specifically, the problem that this topic is going to address is to bypass the node requirements by having an off-chain service to assemble arbitrary transactions for dApps.

### A Solution

The off-chain service will allow dApps to register some requests by providing an address (which the user will deposit her assets) and some other specifications. This topic is just for getting feedback, and I still haven't designed the APIs to provide concrete examples, however:

{
"returnTo":"address to return assets to in case of failure",
"startWhen":{ // start assembling when all needed assets are deposited maybe with multiple transactions
"erg":1002000000,
"d01bdce3959ff6b675f7ab40ec2479ca5ce1edf3ae6314631f09c0f9807752aa":71
},
"txSpec":{
"requests":[
{
"value":1000000000,
"assets":[
{
"tokenId":"d01bdce3959ff6b675f7ab40ec2479ca5ce1edf3ae6314631f09c0f9807752aa",
"amount":71
}
],
"registers":{
"R4":"0e240008cd02d84d2e1ca735ce23f224bd43cd43ed67053356713a8a6920965b3bde933648dc",
"R5":"04bacf2a",
"R6":"0580a8d6b907",
"R7":"0e0131",
"R8":"0e240008cd02d84d2e1ca735ce23f224bd43cd43ed67053356713a8a6920965b3bde933648dc",
"R9":"0e1c313030303030303030302c313030303030303030302c333439313433"
}
}
],
"inputs":[
"\$userIns",
"boxId1",
"boxId2",
"..."
],
"dataInputs":[
"boxId1",
"..."
],
"fee":2000000
}
}

The above is a potential request that Ergo Auction House can register to the service, which will start a new auction! So the Ergo Auction House app will ask the user to deposit the required assets to the address (will discuss what this address is in the next sections) using their favourite wallet and registers the request to the service.

After such a request, the service will follow the address and, when the conditions are met, assembles the transaction and makes sure it will be mined. In case of failures, assets will be returned to the user; for example, if the transaction is for placing a bid and someone else places a bid before us!

Note that all input and data input boxes are in ids, and no input raw will be required, which makes it safe for dApps to avoid running nodes for themselves or using random nodes in the network to get raw inputs.

Also, note that the above approach doesn't solve the problem of finding necessary boxes (e.g. in case of placing a bid, the auction box) for dApps, and it isn't the aim of this topic as well!

Furthermore, the txSpec is pretty raw, can be improved so that the service encodes the register to make it easier for dApps, but with the mentioned libraries around, I don't see it as a problem for dApps to encode registers themselves.

With some improvements on the node's side, the service can be very fast and effective by using chained transactions to avoid wasting time for the deposits to be mined! So basically, it will be like the user is running a node and is generating the transaction directly without intermediate operations.

Last but not least, the service will, of course, provide some other APIs for dApps to see the result of their registered requests.

### Trusting Issues

How dApps and users should trust such a service is still a big problem. Several solutions: - With the service being open-sourced and maybe being provided by a trusted party - dApps can run the service for themselves, resolving the trust issue for at least themselves - Using well-designed p2s addresses to prevent the service from stealing

Although one can argue that the first two options can work under some circumstances, the last option is the one which I think is applicable for most use-cases and doesn't require trust! For example, the Ergo Auction House can use p2s addresses, which will allow the assets to be spent only for placing a specific bid, and the user's address is specified as auction's bidder in the auction box and register; it to the service!

### Service Provider Incentives

Although there are no plans to make profits out of the service, one can have multiple options and plans to make some profits with the service. For example, the service can follow the registered request for some minutes for free, and after that remove the request if the conditions are not met to assemble the transaction, then dApps can pay the service to follow the request longer!

Until the dApp bridge in wallets is built, I think such a service will help a lot for the growth of dApps. Even after some wallets provide APIs for dApps, users still can benefit from such a service by using any wallet they wish! Please let me know if something is overlooked.

### Motivation

Currently, to craft a transaction, we need to use Kiosk, sigma-rust, Appkit or some other tool, which makes the entry barrier quite high. Motivated from @anon_real's Tx Assembler and other proposals, I had been working on a tool to automate tx building for the off-chain components of an Ergo dApp.

The tool called simply "Tx Builder" can be used to create transactions for participating in several Ergo application protocols. The goal of Tx Builder is to allow people with just knowledge of Json to craft a transaction following certain rules.

### Documentation

There is a very short introduction here. For further details, please refer to the source code here and the examples here.

### Example Script

As an example, the following Json can be used for creating a timestamp using the service described here

{
"constants": [
{
"name": "myBoxId",
"type": "CollByte",
},
{
"value": "2z93aPPTpVrZJHkQN54V7PatEfg3Ac1zKesFxUz8TGGZwPT4Rr5q6tBwsjEjounQU4KNZVqbFAUsCNipEKZmMdx2WTqFEyUURcZCW2CrSqKJ8YNtSVDGm7eHcrbPki9VRsyGpnpEQvirpz6GKZgghcTRDwyp1XtuXoG7XWPC4bT1U53LhiM3exE2iUDgDkme2e5hx9dMyBUi9TSNLNY1oPy2MjJ5seYmGuXCTRPLqrsi"
},
{
"value": "4MQyMKvMbnCJG3aJ"
},
{
"name": "myTokenId",
"type": "CollByte",
"value": "dbea46d988e86b1e60181b69936a3b927c3a4871aa6ed5258d3e4df155750bea"
},
{
"name": "minTokenAmount",
"type": "Long",
"value": "2"
},
{
"name": "one",
"type": "Long",
"value": "1"
},
{
"name": "minStorageRent",
"type": "Long",
"value": "2000000"
}
],
"dataInputs": [
{
"id": {
"value": "myBoxId"
}
}
],
"inputs": [
{
},
"tokens": [
{
"index": 0,
"id": {
"value": "myTokenId"
},
"amount": {
"name": "inputTokenAmount",
"value": "minTokenAmount",
"filter": "Ge"
}
}
],
"nanoErgs": {
"name": "inputNanoErgs"
}
}
],
"outputs": [
{
},
"tokens": [
{
"index": 0,
"id": {
"value": "myTokenId"
},
"amount": {
"value": "balanceTokenAmount"
}
}
],
"nanoErgs": {
"value": "inputNanoErgs"
}
},
{
},
"registers": [
{
"value": "myBoxId",
"num": "R4",
"type": "CollByte"
},
{
"value": "HEIGHT",
"num": "R5",
"type": "Int"
}
],
"tokens": [
{
"index": 0,
"id": {
"value": "myTokenId"
},
"amount": {
"value": "one"
}
}
],
"nanoErgs": {
"value": "minStorageRent"
}
}
],
"binaryOps": [
{
"name": "balanceTokenAmount",
"first": "inputTokenAmount",
"op": "Sub",
"second": "one"
}
]
}


### Using with KioskWallet

The above script was used to automatically generate this transaction using KioskWallet.