sphinx-ffi-0.6.10

• bump sphinx dep
• payment_hash_from_invoice util

sphinx-ffi-0.6.9

• make_invoice
• pay_invoice
• state_to_delete on RunReturn

sphinx-ffi-0.6.8

• tribe info on make_invite

sphinx-ffi-0.6.7

• inviter alias in invite QR

sphinx-ffi-0.6.6

• add "code" to RunReturn msg.sender json, so inviter can link invited user

sphinx-ffi-0.6.5

• better invite utils

sphinx-ffi-0.6.4

• async pay!

sphinx-ffi-0.6.3

• topics/payloads are arrays

sphinx-ffi-0.6.2

• make sure sender json appears on all message types (even key exchange)

sphinx-ffi-0.6.1

Instead of msg, msg_type, msg_index, msg_msat, msg_sender, msg_uuid, msg_timestamp, and sent_to being a part of the RunReturn object, there is an array of messages called msgs on RunReturn:

pub struct Msg {
    pub type: Option<u8>,
    pub message: Option<String>,
    pub sender: Option<String>,
    pub uuid: Option<String>,
    pub index: Option<String>,
    pub msat: Option<u64>,
    pub timestamp: Option<u64>,
    pub sent_to: Option<String>,
}

This is so that we can do batches messages later on, when restoring an account. When you receive a message from a contact or in a tribe, there is just one item in the array