A simple feature that could add a lot of benefits.

That is to allow datafields to be included in each SAFEcoin that is sent to another ID.

Many coins now allow additional data to be included in a transaction. E.G. bitcoin. This idea is to allow use of the remaining space in a safecoin’s MD to be able to send details of the payment to the receiver.

The idea came when answering a query about what exchanges might need to do to accept SAFEcoins and trade them.

One method is for the exchange to have one ID per user and monitor each ID for received coin. Using this idea then the exchange could have one ID for receiving coin and the user uses a APP that allows the insertion of data to the safecoins being sent. So then when a person sends their coin to the exchange the user’s username for the exchange could be added to each coin being sent. This way the exchange monitors only one ID and simply credits the user specified in the safecoin data field.

How to implement it?

The send safecoin API would allow a supplied data block to be written into the safecoin’s MD before actually sending the safecoin.

Will coins be filled up with data?

No the API would delete any fields in the safecoin always to ensure anonymity and privacy of previous senders. If a person wanted to include the previous data then they would need to first read the safecoin’s MD contents and include that in the data block included in the API call.

Will the data block be optional?

Yes, it needs to be (see below). The current field(s) in the safecoin will be deleted always so no need to supply a blank data block

Will there be a cost?

YES, it will cost a put charge to place data within the safecoin when sending. While a simple sending of safecoin will remain free the addition of the data block is preformed prior to sending but as a single API call. If the users writes to the safecoin’s MD prior to sending it then it would be wiped.