Routes

To secure transfers of funds, Xfer uses routes defined by each user.

Xfer routes are customizable pathways that include easily remembered names, target recipients, and optional memos, empowering users to manage their Hive asset transfers with precision.

These routes are established and maintained by initiating micro-transfers of either HIVE or HBD to the @xfer account with a structured memo containing commands and parameters. Users can seamlessly add, update, delete, and retrieve lists of routes, offering a high level of control and security in their blockchain transactions.

Managing routes with Xfer is the first crucial step to ensure your transfers go smoothly.

Remember, you choose the asset you want to create a route for. If you send a command using HIVE, you will manage an HIVE route. If you send HBD, you will manage an HBD route.

Each command sent to Xfer may require one or more of the following parameters:

{"cmd":"[command]", "route":"[name]","target":"[recipient]","memo":"[memo]"}

Parameter	Description
[command]	A route management command
[name]	An easy to remember route name.
[recipient]	The final recipient for your transfer (without the @)
[memo] (optional)	A memo you want to send to the recipient. If prefixed with #, the memo will be encrypted.

Additional considerations about route management

• With the exception of the [memo] parameter, all content is case insensitive. This means that a structured memo like: {"cmd":"ADD", "route":"demo","target":"username","memo":"A Memo"} will be treated in the same way as: {"CMD":"add", "Route":"DeMo","TargeT":"USERname","MEmo":"A Memo"}

• When sending commands to @xfer, you can choose to encrypt the structured memo separately from the memo sent to the final recipient. This added layer of security enhances the privacy of your interactions with Xfer. To do this, simply prefix your memo structure with a # Example: #{"cmd":"ADD","route":"binance","target":"deepcryto8","memo":"123456789"} In the above example, only the structured memo will be encrypted, not the one sent to the final recipient (@deepcrypto8)