Sending messages using desktop wallet

Sending messages using desktop wallet

Sending public messages over the SCS blockchain is very simple with desktop wallets version 1.2.1 and newer.

Basically, you just have to fill required transaction parameters (Pay To address and Amount) and then click the Message button.

In the field that will appear, enter your message:

And then just press Send button. After successful sending, the wallet automatically switches page to the the Transactions view. Here you can double-click on the corresponding transaction entry (the latest one in our case; they are displayed in order new to old) with the small message icon:

And the message itself will be displayed:

It will also be published over the SCS blockchain automatically with the transaction details. This data can be viewed on the Block Explorer:

And also it will be available on the JDS server with the following request (only valid for this test case; please read about JDS API in case you need the one that fits for you):

http://jds.scash.ml:15081/messages?count=1&srcaddr=ShYVgSqNpYHeRccx19vTXKmoPTPZHDrEWd

The messages are public; however, the message receiver (the one you filled in destination address) will have an additional notification of the incoming message and can read it the same way as you (by double-clicking the transaction with message icon on the Transactions page).

Things are easy here, but let's describe some useful tricks now.

Sending messages to yourself

This is the simplest way to publish some information on the SCS blockchain. To do so, you just have to send a message to one of your addresses from the same wallet:

Press the "New Address" button, fill the Label for this address (for instance "test") and the newly generated address will appear on the list of your wallets addresses. You can have unlimited addresses count, and the creation of a new one is free.

Then you can copy the new address (right click on the required entry and use "Copy Address" item from the context menu). Then you can paste it on the Send coins page (as Pay To address) and enter any amount in Amount field. Only the basic transaction fee will be charged for sending message to yourself (around 0.001 SCS), and the amount you specified will be returned to your new address within transaction.

Sending message with preserving the sending address

Next trick is a more complex version of the previous one. In some cases, like that of Trusted Signatures manipulation, you need to preserve the exact address for the sending of coins, and here it will be explained how to do so.

If you don't have the complete understanding why you need it, then is best not spend time on reading the next part. After your own due diligence and experience with features like this, we kindly encourage you to return here for further reading if you are interested.

Firstly, you have to activate the Coin Control feature. This can be managed by running "Settings > Options..." in main application menu.

Check the "Display coin control settings" here and press OK.

Now you will have the "Coin control" button on the Send coins page:

Push the Coin Control button and then "Inputs..." button:

You will see the list of SCS addresses you have with the coin amount of each address. Select the one you would like to use next (with non-zero amount of coins and no sub items of change addresses):

Use the "Copy address" by the right click on this address in context menu and click OK. Paste this address to "custom change address" and Pay To address fields:

Once you have filled in these fields correctly, you can enter the message and simply click the "Send" button.

This will generate the transaction, where the Source, Destination and Change addresses are the same (and the only owner of this address is you). Only a transaction fee will be charged from this address by network (standard one). In explorer, the message will be displayed like this:

Note that this transaction is very easy to trace. Any transaction history leads to similar transactions being traceable. Messages with preserved addresses are currently required to register a new Trusted Signature.

Leave a Reply

Your email address will not be published. Required fields are marked *